The FAA's Twelve Million Dollar BVLOS Bet, the Detect-and-Avoid Gap That Keeps Drones Out of Your Airspace, and the Traffic Management Architecture That Has to Work Before Any of This Scales

The FAA has distributed $12 million in research funding aimed at solving the technical gaps that currently prevent routine beyond visual line of sight (BVLOS) drone operations in the national airspace system. The money targets three specific problems: detect-and-avoid systems, satellite communications for command and control, and unmanned traffic management interoperability. None of these problems has a solution ready to regulate yet - which is exactly why the agency is funding the research.

What BVLOS Means and Why It Isn’t Legal Yet

Under Part 107, finalized by the FAA in 2016, commercial drone operators must maintain visual contact with their aircraft at all times. That single requirement caps practical operating range at roughly half a mile under good conditions. It is the reason large-scale drone delivery, extended pipeline inspection, and precision agriculture across thousands of acres remain either future projections or narrow regulatory exceptions rather than standard commercial operations.

BVLOS waivers do exist. The FAA has granted them to Wing Aviation, Amazon Prime Air, UPS Flight Forward, and a small number of other operators. Each waiver is tailored to a specific operator, a specific geography, and specific documented mitigations. Each expires. Building a national logistics network on a patchwork of individual exemptions is not viable at scale, and the industry has been pressing the FAA toward a general BVLOS rule accordingly. The agency has been working toward that rule since at least 2019.

The Detect-and-Avoid Problem

Detect-and-avoid is the hardest of the three challenges the funding addresses. A small commercial drone has a radar cross-section close to nothing. A delivery drone operating at 1,500 feet will not register on most traffic collision avoidance systems and may not appear on ADS-B at all. The FAA requires ADS-B Out equipment on drones in certain airspace categories, but that requirement does not apply universally to smaller systems operating outside controlled airspace. The gap is real.

The approaches being researched include onboard cameras running computer vision algorithms, small solid-state radar units, and acoustic sensors that detect propeller and engine signatures from other aircraft. Each involves tradeoffs in size, weight, power draw, and detection range. The latency constraint is severe: at a combined closure rate of 250 to 300 knots between a drone and a light aircraft, the detection, threat classification, and avoidance maneuver have to execute in seconds.

A parallel approach moves the processing off the vehicle entirely. In ground-based detect-and-avoid models, radar, ADS-B receivers, and other ground sensors assemble a common operating picture that gets pushed to the drone through the command link. That model reduces onboard hardware requirements but is entirely dependent on the reliability of that communications link.

Satellite Communications for Command and Control

For BVLOS operations beyond radio range, the drone needs a reliable, low-latency data link to the ground. FAA standards require that the remote pilot retain the ability to intervene at any time. When the link fails, the drone executes a contingency - return to home, hold, or controlled landing. In normal operations, the command and control channel has to function reliably at ranges of 40 to 50 miles with terrain in between.

Low-Earth orbit satellite constellations have drawn significant attention from the drone industry as a solution. These networks offer global coverage with latency in the range of 20 to 40 milliseconds, which is usable for command and control. Integrating that hardware into a vehicle weighing a few pounds and operating on battery or small fuel load is an engineering challenge, but a tractable one. The FAA-funded research will characterize what satellite links actually do under real operational conditions - reliability distributions, latency under load, handoff behavior between satellite footprints, and interference scenarios. A regulation that simply requires satellite-based command and control is not technically enforceable without data defining what acceptable performance looks like in practice.

The Traffic Management Architecture

The FAA has been developing the Unmanned Aircraft System Traffic Management (UTM) architecture for several years. In the UTM model, operators planning a BVLOS flight file their intended corridor, the system checks for conflicts with other drone traffic and with manned aviation operations, and the operator receives a clearance or rerouting suggestion before launch. The Low Altitude Authorization and Notification Capability (LAANC), operational since 2018, already handles real-time authorizations for drone flights in controlled airspace and is a functional early component of this ecosystem.

The integration gap the current funding addresses is the interface between UTM and existing ATC infrastructure. A controller in a TRACON has limited situational awareness of drone operations in their sector, and a drone operator has limited visibility into the manned traffic picture in their corridor. The research is focused on making that exchange functional at scale: what format a drone’s flight path needs to take to be useful to a controller, how ATC pushes relevant traffic information to a drone operator in a form they can act on, and how that two-way exchange scales to thousands of simultaneous operations without generating data loads that overwhelm the system.

Altitude is also in scope. The current airspace construct puts unmanned traffic primarily below 400 feet AGL, theoretically below most manned operations. BVLOS missions push higher - pipeline inspection over mountainous terrain, corridor deliveries crossing highway overpasses and tree lines, infrastructure surveys in complex topography. These operations will share altitude bands with helicopter operators, aerial applicators, banner towers, survey aircraft, and low-altitude VFR traffic. The safety case for BVLOS has to address those users specifically.

How This Compares to the European Approach

The European Union has been developing a parallel framework called U-space, which defines service requirements for UAS traffic management, network identification, geofencing, and weather information. Several European countries have active U-space implementations at varying maturity levels. The FAA has been monitoring that work closely. The technical problems are identical across jurisdictions; the regulatory culture and airspace structures differ. Engineering solutions developed in both systems have informed each other.

What the $12 Million Actually Buys

The funding is distributed across research organizations, universities, and industry partners. The deliverables are technical reports and proposed performance standards - not finished products. This is the foundational data work the FAA needs before it can write a rule that holds up to legal and technical scrutiny. The agency cannot publish a standard for detect-and-avoid performance without first knowing what performance is achievable and measurable. The same applies to satellite link reliability and UTM interoperability.

The rulemaking process is where this investment either pays off or stalls. Progress on BVLOS regulation has been methodical, at times slow from the industry’s perspective, partly because the technology was not mature enough to write standards against and partly because the stakeholder landscape is genuinely complex - drone manufacturers, commercial operators, general aviation pilots, airlines, airport operators, the military, and emergency services all have legitimate interests in how the rule gets written.

Why This Matters for Pilots Flying Today

The near-term practical effect on your flying is limited. BVLOS waivers currently cover a small footprint of US airspace and are held by operators carrying significant compliance burdens. The probability of an unannounced BVLOS drone encounter on a typical cross-country is low.

The picture five to ten years out is different. If the detect-and-avoid research produces performance standards the industry can meet, if the satellite communications work leads to a certifiable link reliability requirement, and if the UTM interoperability effort meaningfully integrates the drone ecosystem with ATC, routine BVLOS operations in the national airspace system become real. At that point, every preflight involves considering how your altimeter, your eyes, and your traffic display interact with autonomous aircraft sharing your altitude band.

There is also a direct benefit worth noting for the GA community. The sensor fusion and threat-geometry work being developed for autonomous drone detect-and-avoid has direct application to general aviation collision avoidance. TCAS functions well at transport category speeds and sizes. Below that threshold, the collision avoidance problem in uncontrolled airspace remains largely biological - your eyes and the other pilot’s. If BVLOS research produces reliable, low-cost, solid-state detect-and-avoid hardware small enough for a delivery drone, some of that technology will eventually reach light aircraft. That would be a meaningful safety gain for the GA community from a program most GA pilots are not currently tracking.

Key Takeaways

• The FAA awarded $12 million to research the three unsolved problems blocking a general BVLOS rule: detect-and-avoid, satellite command and control, and UTM-to-ATC integration.
• Current Part 107 visual line of sight requirements cap commercial drone range at roughly half a mile; BVLOS waivers exist but are not scalable infrastructure.
• A combined closure rate of 250–300 knots between a drone and a light aircraft means detect-and-avoid systems must operate in seconds with minimal latency.
• LAANC has been handling real-time drone authorizations in controlled airspace since 2018, but the connection between UTM and ATC is still incomplete.
• The practical impact on most pilots is low in the near term; the five-to-ten year horizon is where the airspace picture changes materially.