In 2019, drones flew over the streets of downtown Reno, Nevada, buzzing above a riverside plaza between office blocks. They were not dodging each other by luck or by radio calls to a controller. They were testing a system in which drone traffic is coordinated by computers talking to computers.
That was the final phase of NASA’s research into UAS Traffic Management, or UTM: the idea that low-level drone traffic can be organised without air traffic controllers at all. Six years later it is the foundation of the FAA’s proposed rules for routine beyond-visual-line-of-sight (BVLOS) drone flight, and of Europe’s U-space.
Datos rápidos
- Qué es: UAS Traffic Management: automated, low-altitude traffic management for drones, separate from air traffic control
- How it talks: Machine to machine via APIs, not voice
- Who provides it: Private UAS Service Suppliers (USSs) and Supplemental Data Service Providers
- Core service: Strategic deconfliction of overlapping operational intents before flight
- También: Conformance monitoring, airspace constraints, identification, weather
- US status: Operational Evaluation since 2023; Part 146 certification proposed in August 2025, no final rule yet
- Europe: U-space regulations (EU) 2021/664-666, in force since January 2021
- Research: NASA UTM project, four test levels 2015-2019, ended May 2021
Why not just use air traffic control?
Conventional air traffic control is built on people. A controller watches a radar picture, talks to each pilot by voice and issues instructions to keep aircraft apart. That works for airliners. It would not scale to dozens or hundreds of small drones working the same neighbourhood at low level, each flying short, frequent sorties.
The FAA describes UTM as “separate from but complementary to” air traffic services. Its own page is blunt about the mechanics: the primary means of coordination is “a distributed network of highly automated systems via application programming interfaces (API), not voice communications between pilots and air traffic controllers.” Drone operators stay responsible for flying safely within the constraints the system shares, without receiving what the FAA calls positive air traffic control services.
The FAA also explains why the old tools fail. Legacy methods such as filing and reading Notices to Airmen, it says, are not well suited to automated operations flying close together at a high tempo. UTM replaces the paperwork with machine-readable data shared in real time.

Who runs it: a federated network
If there are no controllers, who is in charge? In the American model, the answer is a network of private companies called UAS Service Suppliers, or USSs. A drone operator connects to one USS, which shares data with all the others. Supplemental Data Service Providers add things like weather or terrain information. As the system matures, the FAA says it will provide real-time airspace constraints into the network.
The FAA calls this a federated network, and it took care to spell out what that means.
According to the FAA, connectivity and data sharing between the suppliers rely on network components such as a Discovery and Synchronization Service and an automated digital test harness, built on industry consensus standards. The first UTM-style service many pilots met was LAANC, the system that gives Part 107 pilots near-instant authorisation near airports; its suppliers are still managed by the FAA’s Air Traffic Organization.
Strategic deconfliction: solving conflicts before take-off
The heart of UTM drone traffic management is a concept called strategic deconfliction. Before a drone launches, its operator shares an “operational intent”. The FAA proposal defines it as a volume-based representation of the intended flight path: one or more 3-dimensional volumes of airspace, each with a beginning and ending time. The network compares it with everyone else’s, and under the proposal certain operators would need a deconflicted intent accepted before take-off.
The FAA’s 2025 BVLOS proposal defines the pieces precisely. Strategic conflict detection is “the process of identifying overlapping operational intents among unmanned aircraft,” and strategic conflict resolution is the process of resolving them. Two delivery drones planning to cross the same street at the same minute are separated on the ground, before either has spun up a propeller.
Zipline’s short explainer on Unmanned Aircraft System Traffic Management and why delivery drones need it.
That differs from tactical separation, the split-second avoidance that happens in the air. Here the proposal is candid: there is not yet a demonstrated, operationally validated solution for tactical collision avoidance between drones. An airborne standard for small drones, ACAS sXu, exists, but it needs a way to detect other drones first. That is why UTM puts so much weight on planning.
Crewed aircraft are a separate problem. The FAA states that all drone operators need a way to avoid them, whether or not they use a USS, through visual observers or an approved detect-and-avoid system. UTM does not make a drone invisible to a crop duster; it keeps drones out of each other’s way.
Conformance monitoring: are you where you said?
A plan is only useful if the drone sticks to it. Conformance monitoring, in the FAA proposal’s words, is “the real-time ability to determine whether an unmanned aircraft is flying in accordance with its operational intent,” and to share situational awareness with other airspace users when something goes wrong.
If a drone drifts out of its reserved volume because of wind, a lost link or a fault, the network flags it and neighbouring operators learn about it. Identification is part of the same picture: Remote ID already requires most drones in the US to broadcast their identity and position, and Europe’s U-space makes network identification one of its mandatory services.

From NASA test fields to the FAA
NASA’s Ames Research Center led the UTM research with more than 100 partners in four stages, called Technical Capability Levels. TCL1, completed in August 2015, tested basics such as scheduling and geofencing. TCL2 in October 2016 moved to BVLOS flights over sparsely populated areas. TCL3 in spring 2018 focused on keeping drones spaced out over moderately populated areas, and TCL4, from May to August 2019, took the system into cities such as Reno.
The project officially ended in May 2021, and its results were handed to the FAA. In 2023 the FAA and NASA began working with an industry consortium on a UTM Operational Evaluation, in which operators and service providers manage overlapping BVLOS flights using shared standards. The FAA has started issuing Letters of Acceptance to service providers in that consortium for strategic deconfliction services.
NASA’s video on its UTM research project and the field tests that shaped drone traffic management.
Part 146: certifying the private layer
The bigger change is on paper. The FAA’s notice of proposed rulemaking of 7 August 2025, which also proposed Part 108 for BVLOS operations, includes a new Part 146 for Automated Data Service Providers. In a footnote, it defines UTM as “a set of automated data services provided by a federated, distributed network of providers.”
Instead of building a government drone control system, the FAA would certificate the companies that provide safety-critical services. The proposal draws the line clearly: a provider of strategic deconfliction for BVLOS flights in controlled airspace under Part 108 would need a Part 146 certificate, because that service is a requirement. A provider monitoring the temperature of blood samples in the cargo hold would not, because that is not an aviation safety concern.
This remains a proposal. The comment periods closed in October 2025 and February 2026, and as of mid-November 2026 no final rule has been published in the Federal Register.
Europe’s version: U-space
Europe has written its version into law already. The U-space regulations, Commission Implementing Regulations (EU) 2021/664, 2021/665 and 2021/666, entered into force in January 2021. A U-space airspace is a zone designated by an EU member state after an airspace risk assessment, and drone operators flying in it must subscribe to services from certified U-space Service Providers.
EASA lists four mandatory services: UAS flight authorisation, geo-awareness, network identification and traffic information on crewed aircraft. Weather information and conformance monitoring are optional, though national authorities can make them mandatory. A certified provider can then offer its services in any U-space airspace in the EU.
The FAA’s “Unmanned Update” on the agency’s journey toward integrating drones into the National Airspace System.
The two systems use different words for the same idea. Air traffic control keeps aircraft apart by telling pilots what to do. UTM keeps drones apart by making sure their plans never collide, and by letting every participant see the same picture. The controllers have not been replaced by a robot in a tower. They have been replaced by an agreement between machines.
Sources: Federal Aviation Administration (UTM page), Federal Register 90 FR 38212 (Part 108/146 NPRM), NASA Ames Research Center, EASA (U-space FAQ and regulatory overview)
Header photo: NASA / Dominic Hart




0 Comments