The coming rulemaking on routine BVLOS operations is likely to propose a fundamental reworking of low‑altitude right‑of‑way rules that have governed manned and unmanned aircraft for decades. Those recommendations originate in the UAS BVLOS Aviation Rulemaking Committee final report and have been central to subsequent policy discussions about how to scale delivery, inspection, and infrastructure missions without creating untenable cost or operational barriers for drone operators.

What the Arc recommended, and why it matters The ARC proposed shifting the traditional see‑and‑avoid paradigm toward a detect‑and‑avoid framework that recognizes electronic sensing, networked services, and other non‑visual means of traffic awareness. In practice, that means the regulatory focus moves from mandating human visual acquisition to performance requirements for sensing, separation calculation, and strategic deconfliction. The report also introduced the idea of “shielded areas” near structures and infrastructure, and recommended changes that would give unmanned aircraft priority in some low‑altitude circumstances while reserving right‑of‑way for manned aircraft that are cooperative and broadcasting position information.

Why the recommendations are contentious Many operators who fly crewed aircraft routinely at low altitudes have warned that flipping the right‑of‑way hierarchy could create new risk vectors for helicopters, aerial applicators, firefighters, and other low‑level operations. Industry groups in vertical and general aviation have argued that granting UAS conditional priority without robust, demonstrable detect‑and‑avoid capabilities would leave non‑cooperative manned aircraft vulnerable when drones are operating nearby. Those organizations have urged caution and pushed for either stronger DAA requirements for drones or universal electronic conspicuity for manned aircraft before any right‑of‑way inversion is adopted.

How ‘‘cooperative’’ systems and conspicuity fit in The ARC and subsequent technical commentary place a lot of weight on differentiating cooperative targets that broadcast position and non‑cooperative traffic that do not. Proposed approaches discussed in the technical literature include: electronic conspicuity (EC) for low‑electrical aircraft, portable low‑power transmitters for utility operations, networked remote identification and UAS Traffic Management services for strategic deconfliction, and onboard detect‑and‑avoid sensor suites for dynamic, tactical separation. Each option has tradeoffs. Universal equipage could reduce one class of risk but raises cost, retrofit, and privacy questions. Performance‑based DAA standards enable innovation but require credible test methods and means of compliance.

Practical implications for stakeholders

  • Manned aviators: Collect and document your low‑altitude mission profiles and near‑miss data. Demonstrations and quantified metrics showing where and how helicopters, ag aircraft, and other low‑level operations depend on legacy right‑of‑way protections are the strongest basis for targeted regulatory carve‑outs or minimum equipage alternatives.
  • Drone operators and manufacturers: Invest in measurable DAA performance testing and transparent means of compliance. If right‑of‑way priority is conditioned on cooperative behavior or particular sensor performance, you will need verifiable evidence that your systems can detect and avoid both cooperative and non‑cooperative traffic.
  • Infrastructure and utilities: If shielded‑area concepts proceed, operators of critical facilities should be prepared to engage on definitions, permission processes, and safety assurances. Shielded areas as described by advisory workgroups would require facility consent and clear limits on when manned traffic is anticipated.
  • Policymakers and regulators: Favor staged, evidence‑based transitions. A phased approach that ties right‑of‑way changes to demonstrated DAA maturity, regional pilots, and interoperable conspicuity standards will reduce safety tradeoffs while allowing useful BVLOS services to scale.

What to watch for and how to engage Congress directed the FAA to advance BVLOS rulemaking in recent reauthorization language, and stakeholders should expect a formal notice when the agency publishes a proposed rule. As of late spring 2025 the rulemaking had not yet been issued, and the record assembled by the ARC remains a primary technical foundation for any forthcoming proposal. When the NPRM is published, it will be the single best opportunity to shape how right‑of‑way changes are defined, where shielded areas may apply, and what detect‑and‑avoid or conspicuity requirements become mandatory. Submit succinct, evidence‑based comments that include operational data, failure modes, and workable mitigation strategies.

Bottom line The debate over right‑of‑way is not just semantic. It is a proxy for how the United States balances rapid commercial adoption of BVLOS services with the safety of long‑standing low‑altitude manned operations. The ARC laid out a technically ambitious path forward. The policy choices regulators make now will determine whether the integration of drones results in safely widened operational space or in avoidable operational friction and risk. Stakeholders on all sides should prepare concrete evidence and practical, implementable alternatives now so the public record reflects operational realities rather than abstractions.