The United States has had the technical building blocks for routine beyond visual line of sight operations for years, but regulatory timetables and interagency review processes have repeatedly slowed the transition from experimental waivers to a predictable, nationwide regime. The 2024 FAA Reauthorization Act codified that frustration by directing the FAA to publish a performance‑based BVLOS notice of proposed rulemaking within four months of enactment and a final rule shortly thereafter, creating a statutory yardstick that the agency has struggled to meet.
What an executive order could actually change, and what it cannot, is important to separate. An executive order can reprioritize agency resources, require interagency coordination, and set compressed timelines for rule publication or other administrative actions. It cannot, however, rewrite the technical work that underpins a safe rule. The FAA must still define acceptable levels of risk, set pilot and system standards, and provide clear pathways for design and operational approvals. Those technical elements are precisely what the BVLOS Aviation Rulemaking Committee laid out in its March 2022 final report, which remains the most complete public roadmap for performance‑based BVLOS requirements and risk‑based operational categories.
Where executive direction is most effective is in clearing procedural roadblocks. Over the last 18 months the BVLOS NPRM drafting and review path hit conventional choke points: internal DOT review, interagency (OIRA) review, and the need to resolve national security and privacy questions with partner agencies. Reginfo and congressional materials show that the BVLOS rule was expected on the regulatory agenda, but the statutory deadline tied to the 2024 reauthorization was missed as the draft proceeded through those review stages. That is a procedural delay, not a technical one, and it is precisely the kind of problem an executive order can accelerate by mandating timelines and elevating interagency dispute resolution.
Even with procedural acceleration, stakeholders must focus on three technical pillars before routine BVLOS scales safely: detect‑and‑avoid (DAA) and well‑defined performance requirements, resilient command and control and communications, and traffic management integration at low altitude. The ARC recommended a performance‑based Part 108 that ties operational approvals to risk outcomes rather than prescriptive boxes. That gives the FAA flexibility, but it also means operators, manufacturers, and third‑party service providers must demonstrate that their systems meet measurable safety metrics in real operations or test ranges. Executive orders can task agencies to speed testing at federal UAS test ranges and to prioritize consensus standards, but they cannot substitute for the empirical safety data those tests produce.
A practical timeline if an administration chooses to push: require the DOT and FAA to publish the NPRM within a short, fixed window; limit but not eliminate interagency review time by setting firm OIRA coordination deadlines; and direct FAA to publish a streamlined comment period and use modern tooling to triage comments. Those levers compress calendar time but shift the work into implementation and adjudication phases where the FAA and industry will still need months of testing and iterative updates. The law already contemplates a reasonable period between NPRM and final rulemaking to allow for comment adjudication; an executive order can compress that period but cannot eliminate the need for reasoned responses.
Security and provenance concerns complicate the political appetite for fast action. Remote identification and the Ops‑Over‑People/Night rules that the FAA finalized earlier are foundational pieces for scaled BVLOS. Remote ID in particular provides authorities with the basics of attribution and tracking that make expanded operations politically and operationally palatable. Those foundations exist today, but privacy, counter‑UAS authorities, and supply‑chain risk assessments are still active policy debates that an executive order would need to acknowledge and provide a mechanism to resolve across agencies.
Industry expectations have understandably been high: associations and operators see routine BVLOS as the unlock for large‑scale delivery, infrastructure inspection, and public safety use cases. Their requests to Congress and DOT have focused on predictability, use of consensus standards, and preservation of a risk‑based approach rather than one‑size‑fits‑all prescriptive requirements. Executive direction that reinforces the performance‑based posture recommended by the ARC and required by statute would be welcomed by those stakeholders, provided it preserves robust safety and security review.
Bottom line: an executive order can shorten the procedural latency that has delayed publication of the BVLOS NPRM and can require agencies to prioritize the rule and related testing. It cannot, and should not, short‑circuit the operational testing, consensus standardization, and interagency risk mitigation that make routine BVLOS safe and sustainable. Anyone planning business or public safety programs around BVLOS should watch for two things from the administration: concrete, dated milestones for NPRM publication and a paired implementation plan that funds and schedules test range activities and standards adoption. Those two signals would be the clearest evidence that procedural acceleration is being married to the technical work that actually makes BVLOS safe at scale.