The Federal Aviation Administration has spent years assembling the pieces of a digital airspace management system for drones — DroneZone for registration, LAANC for airspace authorization, Remote ID for identification, ADS-B for surveillance. On August 17, 2026, the agency published an updated NextGen fact sheet holding those pieces up as evidence of progress toward integrating drones into the National Airspace System. But a Government Accountability Office report released earlier this year says the FAA is still missing the one thing that would actually let a drone and a manned aircraft avoid each other in real time: a technical plan for how the two will talk.

The report, GAO-26-107648, concludes that while the FAA has produced high-level vision documents describing where it wants airspace integration to go, it has not defined "specific actions such as clear roles or technical milestones" for enabling two-way communication between drones and other aircraft. That is a gap regulators, operators and Congress have been pointing to with increasing urgency as commercial drone operations — particularly beyond-visual-line-of-sight (BVLOS) delivery flights — scale up far faster than the airspace architecture meant to contain them safely.

What GAO Actually Found

GAO's review lands at a moment when the numbers describing the U.S. drone fleet have become difficult to ignore. According to the report, the commercial drone fleet was projected to exceed 1 million aircraft by the end of 2025 and grow to 1.18 million by 2029. As of December 2025, the FAA had approved more than 1,000 BVLOS waivers — the authorizations that let drone operators fly package-delivery and other long-range missions without a human spotter keeping the aircraft in sight.

That expansion has a safety record attached to it. GAO's report notes 37 domestic drone incident investigations since 2006, five of which involved mid-air collisions. Against that backdrop, the report's core finding is a planning gap: the FAA has vision documents, but not the roles, responsibilities or technical milestones needed to turn that vision into a working system for drones and manned aircraft to communicate with each other in the air. GAO recommended the FAA establish those roles and milestones, and the Department of Transportation concurred with the recommendation, according to the report.

The stakes are not abstract. Congress has directed the FAA to deliver an integrated National Airspace System plan by May 2027. Separately, a June 2025 executive order required the agency to publish an integration roadmap by February 2026 — a deadline GAO found the FAA's response fell short of in substance: the resulting roadmap sketched milestones only through 2026 and, per the report, did not include additional information on how detect-and-avoid would be achieved for the full drone fleet, according to the GAO report and coverage of its findings by Unmanned Airspace. A GAO statement dated February 4, 2026 put the underlying problem bluntly: "Commercial drones are flying further distances, including for package delivery and public safety operations. But existing technologies don't allow for two-way communication between drones and other aircraft."

The FAA's NextGen Pitch — and Where It Falls Short

The FAA's own messaging tells a different story, at least at first glance. The agency's updated NextGen fact sheet, covered by DroneLife on August 17, 2026, cites $10.9 billion in NextGen benefits delivered between 2010 and 2023 and names four technologies — DroneZone, LAANC, the Airborne Collision Avoidance System, and Remote ID — as the supporting infrastructure for what the agency calls UAS Traffic Management, or UTM. The fact sheet points to published concepts of operation for both UTM and Urban Air Mobility, and frames the effort in characteristically incremental terms: "Part of NextGen is accommodating the growth of non-traditional forms of aviation operating at different altitudes."

Read next to the GAO report, the mismatch is notable. DroneZone, LAANC and Remote ID are largely one-way or ground-based systems: they register aircraft, authorize airspace access, and — in Remote ID's case — broadcast a drone's identity and position by radio signal to nearby receivers, not necessarily communicate operational intent bidirectionally between a drone in flight and a manned aircraft sharing its airspace. GAO's report describes Remote ID in exactly those terms, noting that broadcast-only signaling "is not sufficient for providing real-time, networked data about a drone's location and status" for advanced operations. ADS-B, which the fact sheet also references as a building block, has real limits of its own here: FAA rules generally bar drones flying under Part 107 from operating ADS-B Out in transmit mode, and while ADS-B In — receiving traffic data from other aircraft — is the detect-and-avoid method most BVLOS waivers rely on, it still is not the two-way channel GAO says is missing, since it lets a drone see manned traffic without giving a pilot any equivalent way to see or coordinate with the drone. None of the four technologies the FAA cites as supporting UTM directly solves the specific problem GAO flagged — a live, two-way channel for a drone and a piloted aircraft to exchange information and deconflict a shared flight path. The fact sheet points to published concepts of operation, not the technical milestones or defined federal and nonfederal roles GAO says are absent.

Why the Gap Matters More as BVLOS Scales

The urgency in GAO's findings tracks directly with the trajectory of BVLOS operations. A drone operator flying within visual line of sight relies on human eyes to avoid other traffic — an imperfect but understood mitigation. BVLOS flights, the kind that make package delivery and long-range public safety missions viable, remove that safeguard and lean instead on technology to detect and avoid other aircraft, or on some form of communication that lets pilots and remote drone operators coordinate directly. With more than 1,000 BVLOS waivers already issued and the fleet approaching 1.2 million aircraft within three years, GAO's report argues that the FAA's current mix of high-level vision and fragmented technical building blocks is not enough to keep pace with how quickly the operational environment is changing.

Why It Matters

The gap GAO identified is not cosmetic. Two-way communication between drones and manned aircraft is the technical foundation on which any credible BVLOS scaling plan has to rest — without it, deconfliction depends on visual separation, geographic restrictions, or waiver-by-waiver risk mitigations that do not scale to a million-plus-aircraft fleet. The FAA's NextGen fact sheet demonstrates that the agency has invested in adjacent infrastructure — registration, authorization, identification — but GAO's finding is that none of it adds up to the specific roles and technical milestones needed to solve the harder problem. With Congress requiring an integrated NAS plan by May 2027 and the FAA's response to a February 2026 executive-order deadline already found lacking in substance by GAO, the timeline for closing this gap is compressing even as the fleet it needs to cover keeps growing. DOT's concurrence with GAO's recommendation suggests the agency does not dispute the finding — the open question is how fast it can turn concurrence into an actual technical roadmap.

Sources