Putting the Needs of Public Safety First
How Avision UTM supports public safety prioritization, BVLOS coordination, and shared airspace operations
Source context: This article references NASA Ames coverage of North Texas public safety drone prioritization testing and the Autonomy Global op-ed on safe public safety operations with drone deliveries and air taxis. NASA article | Autonomy Global op-ed
The airspace problem is no longer theoretical
It’s 2026, and low-altitude airspace is getting busy. Commercial drone delivery, BVLOS inspection, public safety UAS, and future Advanced Air Mobility operations are all moving toward the same operating environment. When that environment gets crowded, public safety cannot be treated like just another burrito delivery.
NASA put it in a very simple way: on the road, drivers understand that a police car, fire engine, or ambulance with lights and sirens needs room to move. In the sky, similar rules apply. First response drones need a similar kind of priority handling — but implemented through data, rules, coordination, and airspace management tools, like Avision UTM.
Avision is helping build the coordination layer that allows multiple drone operations to share low-altitude airspace while still giving public safety missions the operational priority they may need during emergencies.
What NASA tested in North Texas
NASA Ames, the FAA, Texas public safety agencies, and industry partners recently worked in North Texas to explore exactly how first response drones can operate safely alongside commercial drones. North Texas is especially relevant because commercial drone delivery is already part of daily operations in the region, making it a realistic environment for testing shared airspace procedures.
The exercise focused on a question that sounds simple but gets complicated fast: when emergency drones launch, how should nearby drone operations respond?
- Public safety drones may not follow predictable routes during a search, chase, rescue, or hazardous area scan.
- Commercial drone operations may already be planned, accepted, or active in the same general airspace.
- Multiple public safety agencies may respond to the same incident at once, creating high-priority vs. high-priority conflicts.
- Operators need timely, useful notifications — not just a generic “conflict detected” message.
NASA also highlighted that public safety operations can be dynamic. A tested scenario involved a drone following an officer during a simulated pursuit, scanning an unsafe area, or shifting directions as new information comes in from central command. That kind of movement is very different from a predictable commercial delivery route.
Avision’s role: turning priority handling into airspace coordination
Avision participated in the North Texas work alongside NASA, the FAA, Texas DPS, and police departments from Fort Worth, Arlington, and Irving, Texas. Avision’s role centered on UTM coordination, public safety prioritization, and focusing on the user experience around how operations are submitted, accepted, rejected, or adjusted when conflicts appear.
In practical terms, the work was about answering the questions public safety operators actually care about in the field:
- Can a high-priority public safety operation be accepted when it overlaps a lower-priority BVLOS operation?
- What should happen if a low-priority operation is already accepted or active?
- How should two high-priority public safety missions be deconflicted if they need the same area?
- What information should the operator see when they need to replan?
- Can the system support dynamic operational volumes as an incident evolves?
Shortened scenario summary
During the project, Avision tested several public safety scenarios designed to stress the UTM system in realistic ways. Instead of treating these as abstract demonstrations, the team looked at how priority, timing, activation status, and operator notification affect real users submitting operations.
1. High-priority public safety operation overlapping a low-priority BVLOS operation
In one scenario, a low-priority BVLOS operation was already planned and accepted across multiple quadrants. A public safety agency then submitted a higher-priority operation that overlapped the same airspace.
- The UTM system accepted the higher-priority public safety operation.
- The lower-priority operator received a conflict notification.
- The higher-priority operator was also notified that its operation intersects one or more lower-priority operations, so the public safety team had a complete picture of who else was in the airspace.
- The lower-priority operation was not simply erased; it remained valid until activation state rules applied.
This matters because public safety prioritization should be transparent and rule-based. The goal is not chaos or arbitrary cancellation. The goal is coordinated access to shared airspace when a higher-priority mission needs room to operate.
What the standard actually says about conflict detection
This behavior is not an Avision design preference — it follows the model defined in ASTM F3548-21, the industry standard for UTM services.
The key distinction in the standard is that strategic conflict detection detects conflicts; it does not resolve them. When operations of different priorities overlap, the responsibility to resolve the conflict falls to the lower-priority side: the USS, the UAS personnel, and/or the operator’s automation system are notified, and they must act.
What “act” means depends on the activation state of the lower-priority operation:
- Not yet activated — the conflict must be resolved before the operational intent can be activated at all.
- Already activated, with sufficient time remaining — the lower-priority operator (or their automation) resolves the conflict by adjusting the operational intent.
- Already activated, with insufficient time — the operator must take other steps. Tactical conflict resolution falls outside the scope of the standard entirely.
That last line is worth sitting with. The standard deliberately stops at the strategic layer, which means the industry still has to answer the tactical question separately — and public safety missions are precisely where that gap gets tested.
This is also why activation state matters so much in the scenarios above. “Accepted” and “active” are not the same thing, and the rules that apply to each are different.
2. High-priority vs. high-priority public safety missions
The more difficult scenarios involved two high-priority public safety operations during a simulated flood response. In the example scenario, one agency was actively searching an area where a victim had been located, while another agency attempted to send a drone into that same area with critical supplies such as medical aid, food, or water.
- The existing activated high-priority operation kept priority under first-come, first-served rules.
- The later high-priority delivery operation was rejected because of the conflict.
- The second agency needed to replan based on the conflict information.
This is where the testing became especially valuable. A simple low-versus-high priority model may work for some cases, but high-versus-high public safety conflicts raise harder operational questions. A search mission, a rescue delivery, a tactical law enforcement operation, and a fire response mission may all be high priority — but they may still require different coordination rules.
3. Dynamic operational intent for public safety
Avision also tested public safety UI and USS integration around dynamic operational intent volumes. In plain English, the system needs to support operations that change as the incident changes. Public safety work rarely stays inside a perfectly predictable box.
- A search area may expand.
- A rescue operation may shift toward a newly located victim.
- A response drone may need to move with a vehicle, officer, or changing hazard.
- The UTM system needs to keep the operational picture understandable for everyone sharing the airspace.
The bigger lesson: “priority” is not just a label
It is tempting to think of priority as a simple setting: low or high. But the North Texas work shows that priority is really an operational workflow. It affects whether an operation is accepted, whether another operator gets notified, whether replanning is required, and how much context users receive when the airspace situation changes.
A strong public safety UTM workflow needs to answer several things at once:
- Who has priority right now?
- Is the conflicting operation planned, accepted, or already active?
- Is the conflict based on geography, altitude, time, or operational status?
- Can one operator replan without disrupting the emergency response?
- What exact information does the user need to take the next safe action?
That last point is often overlooked. Operator notifications are not just a design detail. In emergency response, the quality of the notification can shape the next operational decision.
Why this matters for BVLOS, Drone as First Responder, and AAM
BVLOS operations will not scale safely if every conflict has to be resolved manually. Drone as First Responder programs will not scale if agencies lack a shared operating picture. Advanced Air Mobility will not scale if priority rules are unclear when emergency aircraft, public safety drones, and commercial aircraft all need low-altitude access.
The future will be overlapping operations, not isolated flights. That means the industry needs UTM systems that can support coordination before takeoff, during activation, and while missions are changing in real time.
Avision UTM is built for that reality: helping operators submit operational intent, coordinate with other airspace users, detect conflicts, understand priority outcomes, and maintain transparency across shared airspace.
A safer shared sky starts before the emergency
The most important time to define public safety priority workflows is before the flood, before the fire, before the missing-person search, and before the airspace is already crowded.
That is why exercises like the North Texas demonstration matter. They give agencies, regulators, and technology providers a way to test the rules before they are needed in the field. And they help answer the real questions that public safety operators will face as drone delivery, BVLOS, and advanced air mobility continue to expand.
For public safety agencies, drone operators, and organizations preparing for BVLOS, now is the time to test how priority, deconfliction, and coordination will work in your own operating environment.
Explore Avision UTM: https://avision.io/avision-utm/
Register or request access: https://app.avision.io/
Contact: https://avision.io/contacts/
