Beyond visual line of sight (BVLOS) operations — flying a drone beyond the distance at which the remote pilot can see it with unaided eyes — represent the commercial frontier for unmanned aerial systems (UAS). Package delivery at scale, infrastructure inspection across long linear assets, precision agriculture over large fields, emergency response and search-and-rescue, and autonomous aerial logistics all require BVLOS capability. Under the current 14 C.F.R. Part 107 (14 C.F.R. § 107) framework, BVLOS operations require an FAA waiver. The waiver process is demanding, the approval rate is selective, and the operational conditions attached to approvals are extensive.
This post addresses the current BVLOS regulatory framework, what the United States Federal Aviation Administration (FAA) requires for waiver approval, how the embedded systems and sense-and-avoid (SAA) technology technology landscape intersects with regulatory requirements, and where the regulatory pathway is heading.
The Current Legal Framework: Part 107 Waivers
Part 107 of the FAA's regulations governs small UAS operations for commercial purposes. The default rule under Part 107 requires that the remote pilot in command (RPIC) maintain visual line of sight with the drone throughout the operation. Section 107.200 authorizes the FAA to issue waivers of this and other Part 107 requirements where the applicant demonstrates that the proposed operation can safely be conducted under the terms of the waiver.
BVLOS waiver applications must demonstrate that the operator has identified and mitigated the safety risks that visual line of sight normally addresses — primarily the risk of collision with other aircraft (manned and unmanned) and with people and property on the ground. The FAA evaluates waiver applications using a performance-based safety case framework: the applicant must show that its proposed operation achieves an equivalent or better level of safety compared to the visual line of sight standard, using whatever combination of technology, procedures, and operational constraints are appropriate for the specific operation.
This performance-based approach is fundamentally different from a prescriptive regulatory standard. It does not specify what technology you must use. It requires you to demonstrate that your technology, operating procedures, and risk mitigations together achieve an acceptable safety outcome. This is a familiar framework for embedded systems engineers who work in functional safety — it maps closely to the hazard analysis and risk assessment approach of ISO 26262, where the goal is achieving an acceptable residual risk rather than compliance with a prescribed design standard.
What the FAA Evaluates in a BVLOS Waiver Application
The FAA's BVLOS waiver evaluation focuses on four primary risk areas: collision with other aircraft in controlled and uncontrolled airspace; collision with people and structures on the ground; loss of command and control link between the ground control station and the drone; and loss of Global Positioning System (GPS) or navigation capability.
For each risk area, the applicant must identify the specific hazards, characterize the probability and severity of adverse outcomes, describe the mitigations in place, and demonstrate that the residual risk is acceptable. The FAA has published a BVLOS Aviation Rulemaking Committee (ARC) report that provides detailed guidance on the safety case elements it expects to see.
For collision avoidance, the critical technology is detect-and-avoid (DAA) — the embedded systems capability that allows the drone to detect conflicting traffic and maneuver to avoid it without pilot input. DAA systems for BVLOS operations must meet demanding performance requirements: detection range sufficient to allow avoidance maneuvers given the closing speeds involved, low false positive rates that would cause unnecessary avoidance maneuvers, and high probability of detection for the traffic types present in the operating environment. The FAA has endorsed ASTM International F3442 as the standard for DAA performance in some BVLOS contexts.
Embedded Systems Requirements for BVLOS
BVLOS operations place demanding requirements on the embedded systems that enable them. The command and control (C2) link — the radio communication system between the ground control station and the drone — must be highly reliable, with defined link loss procedures that ensure safe behavior when the link degrades or fails. The FAA requires that BVLOS applicants specify the C2 link performance parameters and demonstrate that link loss procedures prevent unsafe outcomes.
The flight control system must be capable of autonomous flight — maintaining stable flight, following a mission plan, executing avoidance maneuvers — without continuous pilot input. This requires a flight control architecture that meets the reliability requirements appropriate for the operational risk. For operations over people or in congested airspace, these reliability requirements approach the levels associated with functional safety standards in other domains.
The positioning and navigation system must provide accurate, reliable position information throughout the operational volume. GPS-only navigation is generally insufficient for demanding BVLOS operations — GPS can be jammed, spoofed, or unavailable in certain environments. BVLOS systems increasingly incorporate inertial navigation, barometric altitude, terrain-following radar, or vision-based navigation as supplements or backups to GPS.
The Path Toward a BVLOS Regulatory Rule
The FAA has committed to developing a specific regulatory rule for routine BVLOS operations, moving beyond the case-by-case waiver approach. The BVLOS ARC report, published in 2022, provided a detailed framework for how such a rule might be structured. The FAA's reauthorization legislation has included direction to accelerate BVLOS rulemaking.
A specific BVLOS rule, when finalized, is expected to create defined operational categories — similar to the Category 1 through Category 4 framework for operations over people — where operators meeting specified equipment and procedural requirements can conduct BVLOS operations without individual waivers. This would dramatically expand the commercial BVLOS market by reducing the per-operation regulatory overhead.
guibert.law Insight
Companies developing embedded systems for BVLOS-capable drones — DAA processors, C2 radio systems, flight control computers, navigation systems — should be engaging with the FAA's BVLOS rulemaking process now. The performance standards and safety case frameworks being developed in the rulemaking will define the product requirements for the BVLOS market. Early engagement means your technical approach can inform the standards rather than being constrained by them.
Attorney advertising. The information in this post is provided for general informational purposes and does not constitute legal advice. Prior results do not guarantee a similar outcome. © 2026 guibert.law