Congress set a clear clock for routine beyond visual line of sight operations when it enacted the FAA Reauthorization Act of 2024. The statute requires the FAA to publish a notice of proposed rulemaking for BVLOS within four months of the Act’s enactment and to issue a final rule within 16 months after the NPRM is published. These are statutory deadlines operators and policymakers should plan around when assessing readiness and risk.

Where things stood as of June 24, 2025 is important to underline. The NPRM deadline imposed by Congress would have been in the fall of 2024, but the FAA had not produced a publicly posted proposed rule by mid 2025. Industry reporting at the time described the agency as preparing a proposal and continuing work toward publication. That means most operators still relied on existing waiver and exemptions pathways and program pilots to conduct BVLOS at scale.

What that regulatory posture means in practice is twofold. First, there is legal and commercial uncertainty around how a final BVLOS regime will allocate responsibilities between manufacturers, operators, and airspace managers. Second, the technical requirements that a final rule will impose are likely to focus on several well established risk controls: robust identification and tracking, detect and avoid capability, secure command and control links, integrated traffic-management interoperability, and operator safety management systems. These elements already appear across FAA programs and industry guidance, and they are the levers regulators use to translate safety goals into operational permissions.

Preparedness checklist for operators and programs

1) Policy and regulatory monitoring

  • Track the Federal Register and Regulations.gov for the BVLOS NPRM. When the NPRM publishes, comment timelines are limited. Prepare to submit operational, technical, and economic comments during the public comment window.

2) Maintain and expand waiver-friendly operations

  • Continue to use Part 107 waivers and public aircraft authorizations where appropriate while moving toward compliance with the anticipated performance-based regime. Keep meticulous records of waivers, safety cases, and mitigations; those artifacts will shorten the path to permit or certificate later.

3) Technical building blocks

  • Remote ID and tracking. Ensure aircraft broadcast and record Remote ID where available and plan for higher-fidelity networked identification. Operators should inventory their fleet for Remote ID capability and telemetry logging.
  • Detect and avoid. Develop, test, and document detect-and-avoid (DAA) systems appropriate to your risk profile. Regulators will look for objective evidence that DAA reduces collision risk in the intended operational environment.
  • Communications resilience. Implement redundant command and control links and hardened telemetry channels. Demonstrate how handoffs, signal loss, and contingency returns-to-home are managed.
  • Airworthiness evidence. Begin compiling manufacturer test data, consensus standard conformance, and Declaration of Compliance materials. A performance-based framework may rely on FAA-accepted consensus standards rather than type certification, so preparing cohesive technical dossiers now buys time later.

4) Organizational controls

  • Safety management systems. Build or expand an SMS commensurate with the size and complexity of operations. Include hazard logs, risk assessments, and continuous improvement processes. Regulators expect organizational allocation of safety responsibility.
  • Training and roles. Define clear roles such as operations supervisors and flight coordinators. Document training curricula, recurrent checks, and personnel vetting. Expect the final rule to reference operator competency standards.
  • Cyber and data governance. Draft cybersecurity policies for command and control, supply chain, and data retention. Maintain incident reporting procedures that map to potential regulatory reporting requirements.

5) Technology and partner alignment

  • UAS Traffic Management. If you plan operations in managed airspace or expect multiple operators in the same area, build interfaces to commercial UTM services and participate in local testbeds. The FAA’s BEYOND tests and similar partnerships provide data and operational lessons that will influence the final rule.
  • Vendor and supply chain. Work with manufacturers and service providers today to ensure their roadmaps include the kinds of testing artifacts and documentation that a performance-based approval process will require. Request audit-ready records for software builds, hardware tests, and safety cases.

6) Community and airspace coordination

  • Public outreach. BVLOS operations change how communities experience low-altitude aviation. Proactively engage local stakeholders, first responders, and conventional aviation users with transparent safety briefs and response plans. Documentation of community engagement will strengthen permit applications later.
  • General aviation interfaces. Establish operational procedures to reduce conflict risk with manned aircraft, especially for operations near small-airport traffic patterns and agricultural flight corridors. Regulators will treat demonstrated mitigations to protect manned aircraft as high priority.

Recommended timeline and sequencing (practical view)

  • Months 0 to 3: Establish a cross-functional BVLOS readiness team, complete a gap analysis against the checklist above, and begin compiling technical artifacts and waiver histories. Submit early questions to regional FAA UAS offices and join ongoing BEYOND or state pilot programs where feasible.
  • Months 3 to 9: Harden DAA testing, communications redundancy, and Remote ID/data architectures. Formalize SMS and training programs. If an NPRM appears in that window, mobilize to prepare targeted comments that reflect operational realities and data from your test flights.
  • Months 9 to 18: Be ready to convert paper evidence and test reports into a permit or certificate application once the final rule takes shape. Expect regulators to require documented operational history and objective test results for acceptance.

Final thoughts The statutory mandate for BVLOS rulemaking creates an opportunity and a risk. Operators who treat the next 12 to 18 months as a period for disciplined technical work, robust record keeping, and stakeholder engagement will be best positioned when the FAA publishes its proposal and later issues a final rule. The path to routine BVLOS is likely to be performance based. That means real world data, repeatable safety processes, and clear organizational responsibility will matter more than rhetoric. For policymakers and operators alike, the principle is simple: prepare now, measure rigorously, and engage constructively when the NPRM opens the public record.