The Risk We Don’t Talk About: Public Safety Drones, Commercial UAS, and the Future of Shared Airspace Deconfliction

In aviation, one of the hardest risks to manage is the one everyone assumes someone else is handling.

As drone programs expand across public safety, infrastructure, emergency response, research, utilities, construction, and critical infrastructure protection, organizations are being forced to confront a difficult question: are their policies, procedures, and assumptions keeping pace with the airspace they now operate in?

There is often an unspoken belief in operational organizations that once a problem is formally identified, someone inherits responsibility for solving it. That belief is not entirely wrong. Once a risk is acknowledged, the natural follow-up questions begin: What is the mitigation? Who owns the issue? What policy applies? What training is required? What funding is needed? Who is accountable if something goes wrong?

Because of that, the easier path can be silence. The problem with that mindset is that in aviation, unspoken risk does not disappear. It matures.

For the drone industry, that risk is becoming increasingly clear. Multiple lawful operators may soon be using the same low-altitude airspace at the same time without a reliable way to coordinate. And drones are not alone in that environment. Helicopters, emerging air mobility aircraft, airport traffic, and other low-altitude aviation activity will continue to share the same operating environment. This is not a public safety drone versus commercial drone issue, even if some view it that way. It is an aviation industry airspace integration issue because the sky is shared, and it needs to be managed that way.

The Airspace Is No Longer Empty

For years, many UAS operations were conducted under a practical assumption that low-altitude airspace was mostly empty. That assumption is becoming less reliable.

A public safety agency may be responding to an emergency. A utility company may be inspecting a transmission line. A construction firm may be documenting a project site. A research team may be collecting environmental data. A commercial operator may be mapping infrastructure. A drone-in-a-box system may be launching for an automated mission. A helicopter may enter the area. An airport may be operating nearby.

• Each mission may be lawful.
• Each operator may be trained.
• Each aircraft may be operating for a valid reason.

The problem is not that a particular operator is doing something wrong. The problem really is that multiple operators may be doing the right thing in the same airspace without a reliable mechanism for knowing, coordinating, or adapting to one another in real time.

That is the shared airspace challenge and it is no longer a theoretical problem.

Public Safety Mindset and Mission Urgency

Public safety deserves specific attention because public safety UAS operations often occur under time pressure. Police, fire, EMS, emergency management, and other response agencies are trained to act under uncertainty, make decisions quickly, and accept a level of operational risk in service of a greater public need. 

That culture has value. It saves lives.

A missing child, active fire, mass casualty incident, tactical emergency, disaster response, or urgent search mission may justify immediate action and rapid deployment of a drone. In many cases, public safety may also have a strong operational claim to priority. But priority is not the same thing as uncontrolled freedom.

Mission urgency may explain why an aircraft was launched. It does not, by itself, explain how the aircraft was safely integrated into shared airspace. That distinction matters.

A drone used by public safety is not just a camera. It is not just a piece of field equipment. Once it is airborne, it is participating in an aviation environment that may include other drones, crewed aircraft, airports, infrastructure, terrain, obstacles, and other lawful operators.

The sky is not empty simply because the mission is important.

Public safety UAS programs provide tremendous value by helping locate missing people, improving firefighter safety, documenting crash scenes, supporting disaster response, enhancing situational awareness, and reducing unnecessary risk to personnel.

That value should be protected by strong aviation discipline, clear procedures, and a shared understanding of the airspace around the operation.

Priority Must Be Supported by Procedure

There will be times when one mission should take priority over another.

A public safety response may need immediate operational consideration. A medical aircraft may need clear access. A utility inspection after a storm may be time-sensitive. A critical infrastructure operation may have security implications. A commercial operator may have an approved route and a lawful authorization.

The issue is not whether priority should exist. The issue is how priority is communicated, coordinated, and exercised. No UAS program should rely on the assumption that mission urgency, by itself, resolves the need for coordination.

The harder question the industry must take the time to answer is:
How do multiple lawful operators share low-altitude airspace when missions are dynamic, time-sensitive, and sometimes competing?

Altitude De-Confliction Is Helpful, but It Is Not Enough

One of the most common answers to this problem is altitude separation.

One operator flies at one altitude. Another operator flies at another altitude. Everyone stays in their lane. That sounds simple, and in some cases it may help. But altitude alone is not a complete de-confliction strategy.

Altitude-based separation assumes several things are true:

• The operators know about each other.
• The aircraft remain within assigned altitude blocks.
• Altitude readings are accurate and consistent.
• Terrain, buildings, trees, antennas, and other vertical obstructions are accounted for.
• The operation does not require climbing, descending, orbiting, or emergency repositioning.
• The aircraft can detect and avoid each other if the plan breaks down.

In the real world, those assumptions do not always hold.

A public safety drone may climb to gain a better view. A commercial drone may descend for a closer inspection. A fire department drone may reposition around smoke or heat. A utility drone may follow a linear asset through the same area. A construction drone may fly a repeatable mapping pattern. A research drone may need a specific altitude for data collection. A helicopter may enter the broader airspace.

Altitude helps. But altitude is a control, not a strategy. De-confliction must include and require layers.

The Layers We Should Be Talking About

A mature airspace de-confliction model should include more than “stay low” or “use visual observers.”

It should include strategic planning, tactical awareness, and detect-and-avoid capability.

• Strategic de-confliction happens before the conflict. This includes known routes, planned operating areas, common altitude procedures, agency notification practices, standing agreements, response zones, and pre-incident coordination.
• Tactical de-confliction happens during the operation. This includes real-time airspace awareness, communication between operators, Remote ID monitoring, dispatch support, contact procedures, crew coordination, and the ability to alter or terminate a flight when needed.
• Detect-and-avoid is the safety layer that helps when planning and communication are not enough. This may include onboard sensors, ground-based systems, radar, optical systems, acoustic sensors, cooperative tracking, networked surveillance, or other technologies that help identify aircraft and prevent conflicts.

The future will likely require a combination of all three.

No single method solves the problem. Not altitude. Not visual observers. Not Remote ID alone. Not mission priority. Not operator judgment.

The real solution is layered airspace awareness.

Calculated Risk Requires Calculation

Organizations often talk about calculated risk. That phrase matters, but it is sometimes used too loosely.

Operating below 200 feet may be a control, but it is not a complete risk calculation. Visual observers may strengthen awareness, but they do not solve every coordination problem. An urgent mission may explain why an aircraft was launched, but it does not fully explain how shared airspace risk was managed. And a plan to land if another aircraft is seen assumes the aircraft will be detected with enough time and distance for that decision to matter.

The preparedness questions are straightforward, but they require honest answers:

• What other lawful airspace users may be present?
• How would we know?
• Who is monitoring the airspace?
• Who is communicating with other operators?
• What system supports that awareness?
• What is our lost-link or conflict procedure?
• How do we notify other operators?
• How do other operators notify us?
• When does priority apply?
• Who has authority to stop, modify, or continue the operation?
• How is this trained?
• How is this audited?
• How is it reviewed after the mission?

That is what calculated risk looks like.

Why These Conversations Are Avoided

These conversations are often avoided because they bring unresolved gaps into focus. They may reveal that an organization has aircraft but not a fully developed airspace management policy, that pilots are trained to operate the aircraft but not to coordinate in a multi-user airspace environment, or that dispatch, command staff, and operations teams lack a clear process for maintaining UAS airspace awareness. They may also raise difficult questions about neighboring operators, Remote ID monitoring, data sharing, detect-and-avoid capability, funding, and governance. In some cases, they show that current procedures depend more on trust and experience than on documented controls.

That can be uncomfortable to acknowledge. But when a risk is foreseeable, avoiding the conversation does not make the organization safer. It only makes the response less prepared.

UAS Programs Need a Stronger Airspace Governance Model

Strong drone programs should be supported and expanded because they are delivering real value across public safety, infrastructure inspection, environmental research, emergency response, construction documentation, utility management, and many other mission areas. But as adoption grows, governance has to grow with it.

A strong UAS program should include:

• Clear launch authority.
• Defined mission priority criteria.
• Airspace monitoring procedures.
• Remote ID awareness where practical.
• Coordination with airports and ATC when applicable.
• Procedures for operating near other UAS activity.
• Common altitude guidance that is helpful but not treated as the only mitigation.
• Documented de-confliction procedures.
• Training for dynamic airspace conflicts.
• After-action review of airspace issues.
• A pathway for integrating detect-and-avoid or networked awareness tools as they become available.

This is not about slowing operations down. It is about making them safer, more repeatable, and more defensible as the airspace becomes more crowded. For many organizations, the next step is not another aircraft. It is an honest look at the policies, procedures, training, airspace awareness, and assumptions that currently support their drone operations.

The Industry Needs to Stop Treating This as Someone Else’s Problem

• Commercial operators need to understand that public safety missions may create urgent airspace needs.
• Public safety agencies need to understand that commercial operators may also be operating lawfully and professionally.
• Infrastructure owners need to understand that their airspace activity may affect neighboring operators.
• Technology companies need to build systems that allow aircraft, operators, command centers, and networks to communicate.
• Regulators need to continue enabling safe integration without pretending one rule or one technology will solve the entire issue.
• Emergency managers, commercial operators, airports, and UAS program leaders need to bring the topic into planning before an incident forces it into litigation, media scrutiny, or after-action review.

This is not about assigning blame. It is about recognizing that shared airspace creates shared responsibility.

The Better Conversation

The better conversation is not whether public safety drones should be allowed to fly during emergencies. Of course they should. It is also not whether commercial operators should sometimes yield to urgent public safety missions. In some cases, they may need to.

The better conversation is:
How do we build a shared low-altitude airspace system where urgent response, commercial operations, infrastructure work, research missions, and other lawful UAS activity can coexist safely?

That is the conversation the drone industry needs to have now. Not after a near miss. Not after an incident. Not after public confidence is damaged. Not after someone asks why the risk was foreseeable but undocumented.

The future of drone operations will require more than aircraft, pilots, and authorizations. It will require communication, governance, technology, and a willingness to address risks before they become incidents.

For organizations building or expanding UAS programs, the next step is often not another aircraft. It is a clearer understanding of the assumptions, procedures, and coordination gaps that already exist.

Program maturity is not measured by how many drones you own, but by how well you understand and manage the airspace risk around them.