The FAA’s move to normalize routine beyond visual line of sight operations is no longer hypothetical. Congress wrote a statutory timeline into the FAA Reauthorization Act of 2024 directing the agency to publish a notice of proposed rulemaking to establish a performance based BVLOS pathway, and the industry has been operating in a mix of limited approvals, exemptions, and programmatic pilots while the rulemaking works its way through the process.

That regulatory background matters because the path to routine BVLOS will be performance based rather than prescriptive. The Aviation Rulemaking Committee that advised the FAA recommended performance based standards, layered mitigations, and clear means of compliance so that different technologies and operations can scale safely. If you run or manage drone operations, treat this as a transition window: the rules will change the baseline, and the operators who already have data, mitigations, and community engagement in place will be able to move faster.

Practical priorities for operators

  • Lock down Remote ID and basic compliance. Remote identification and the operations over people/night changes are the regulatory foundation that enables more advanced operations. Make sure every aircraft and flight-control point in your inventory has an accepted Remote ID compliance path and that your operational manuals reflect the relevant means of compliance. The Remote ID rule is already the baseline for enforcement and airspace awareness, so this is not optional.

  • Treat detect and avoid as core equipment, not experimental. Performance based BVLOS will hinge on predictable, testable mitigations for traffic avoidance and loss of command and control. Start with documented engineering and operational tests of your detect and avoid, sensor fusion, or ground-based radar layers. Collect telemetry and encounter logs in formats that let you show detection ranges, time-to-avoid, false positive and false negative rates, and any human-in-the-loop interventions. The ARC and FAA reviewers look for that evidence.

  • Build an evidence package modeled on existing approvals. The FAA has already authorized scaled operations in tightly controlled programs and through Part 135 and waiver pathways. These approvals are concrete examples of the safety cases regulators accept. If your goal is routine BVLOS, map your ConOps to the elements regulators accepted for past approvals: airworthiness, crew/ground procedures, communications redundancy, detect-and-avoid performance, and community/airspace integration. Use industry precedents to reduce surprises.

  • Collect and present community and environmental data early. Expect NEPA or similar environmental inputs for delivery hubs, corridors, or programmatic approvals. Operators that proactively complete noise, safety, and community outreach plans will be easier to permit and authorize. Where available, reference programmatic NEPA documents and build your local mitigation plan to match them. This will shorten review on subsequent applications.

  • Harden C2, cybersecurity and supply-chain declarations. The future rulemaking is likely to require documented security practices and responsibility assignments for third-party services. Start formalizing supplier security questionnaires, encryption and C2 redundancy, software update procedures, and logging that ties a flight back to authenticated personnel and hardware. These measures protect both safety and your ability to get approvals quickly.

Operational checklist you can use now

  1. Inventory and Categorize
    • Aircraft by type, weight, and Remote ID compliance method. Confirm registration and label numbers.
    • Ground and mobile control stations with software versions and vendor MOCs.
  2. Data and Test Packages
    • DAA/obstacle avoidance test vault: annotated logs of sensor detections, trajectories, decision latencies, and repeatability tests. Provide post-flight analyses that show margin to failure modes.
    • Communications and C2 loss scenarios: command failover timelines and recovery success rates.
  3. Formalized ConOps and Safety Case
    • Written ConOps that ties altitudes, corridors, population density thresholds, and contingency actions to specific mitigations.
    • Risk assessment linked to mitigations and measurable acceptance criteria.
  4. Regulatory Pathway Selection
    • Short term: continue to use waivers or §44807 exemptions and Part 135 where applicable while you build your performance portfolio. Learn from existing case studies and align your packages to precedent approvals.
    • Medium term: design your documentation for rapid translation into the performance metrics the final BVLOS pathway will require.
  5. Community Engagement and NEPA Inputs
    • Early notice to local stakeholders, simple noise and overflight maps, and a documented complaint response process. Where a programmatic NEPA exists for your operating model, map your operation to that PEA to accelerate review.

Business and policy considerations

  • Insurance and contracting. Talk with insurers now about changing exposure as BVLOS scales. Policies that incorporate your DAA performance and operational controls will be easier to underwrite.

  • Partnerships for traffic awareness. Consider relationships with traffic surveillance providers, remote ID UAS Service Suppliers, and UTM-like providers. Regulators will expect networked information-sharing and clearly assigned responsibilities in contested airspace. Start pilots with these partners so you can demonstrate reliability and clarify service-level expectations.

  • Be ready for an iterative rule. The FAA and stakeholder bodies have favored performance based standards. That means compliance will be judged against objective metrics not a single mandated sensor or vendor. Expect the rule to evolve as more operational data arrives. Plan for continuous improvement rather than a single compliance sprint.

Conclusion

You do not need to wait for a final rule to prepare. The specific building blocks that a performance based BVLOS pathway will require are visible today. They include Remote ID compliance, demonstrable detect-and-avoid performance, documented ConOps backed by repeated tests, NEPA-aligned environmental work, and robust security for C2 and supply chains. Operators who assemble those pieces now will face shorter approval cycles and less business risk when the FAA sets the new baseline. In practical terms, start with a prioritized gap analysis, a test program that produces reproducible metrics, and community outreach that reduces friction during authorization. The rule will rest on evidence. The operators who bring the best evidence will move first.