BVLOS waivers: how operators get approval to fly beyond line of sight

A BVLOS waiver is how an operator gets FAA approval to fly a drone beyond visual line of sight under the current small-drone rules. Because the standard rules require a remote pilot to keep the aircraft in sight, flying past that point means asking the FAA to waive the visual-line-of-sight requirement, and the agency grants that only when the operator can show it will still detect and avoid other aircraft safely. The waiver is a safety argument rather than a formality or a paperwork exercise, and the quality of that argument decides whether an operation gets to fly the advanced missions that beyond-line-of-sight work makes possible.

This article covers what a beyond-line-of-sight waiver approves, how to build the safety case that earns one, the proposed Part 108 rule that would change this path, and how a program manages beyond-line-of-sight approvals so the operations flown under a waiver stay inside its terms. The regulatory ground is shifting here, so it is worth being clear about what the path is today and what may be coming.

What a BVLOS waiver approves

A beyond-line-of-sight waiver is a waiver of the visual-line-of-sight rule, one of the specific rules the FAA allows to be waived. Granting it lets the operator fly past the point where unaided vision can meet the see-and-avoid duty, under the terms the certificate spells out. Those terms are specific: particular operations, particular conditions, and particular limitations, and flying outside them is the same violation as flying with no waiver at all. The waiver does not hand an operator a general license to fly out of sight; it authorizes a defined operation the FAA has agreed can be conducted safely.

It is worth keeping the waiver separate from an airspace authorization. A beyond-line-of-sight operation in controlled airspace still needs the usual airspace authorization, and the waiver of the visual-line-of-sight rule is a distinct approval addressing a distinct problem. An operation can need both, and each is evaluated on its own terms. The waiver answers the question of how the operator will stay clear of traffic without watching the aircraft; the authorization answers the question of whether the aircraft may be in that airspace at all.

Building the safety case

The safety case is the whole game. An application has to identify the hazards of flying an out-of-sight aircraft and explain how each will be mitigated, and the central hazard is the loss of the pilot's ability to see and avoid other traffic. Operators address that with some combination of detect-and-avoid measures: ground-based radar, onboard sensors, receiving other aircraft's position broadcasts, visual observers stationed along the route, or shielded operations that keep the aircraft close to structures where crewed aircraft are unlikely to be. Alongside detection, a strong case addresses command-and-control reliability and lost-link procedures, so the operation stays safe if the link drops. The FAA's guidance on the Part 107 waiver process lays out the operational detail a reviewer expects.

The application mechanics reward precision. If the hazard identification and mitigation strategies are missing, the FAA cannot complete a safety analysis and will disapprove the request for insufficient information, so a vague application is the most common way a beyond-line-of-sight request dies. The FAA aims to decide within about 90 days, though complex requests take longer, and an application cannot be amended once submitted. That combination puts a premium on getting the safety case right the first time: a complete, specific demonstration of how the operation detects and avoids traffic and manages its other hazards is what moves the request forward, and anything less invites questions and delay.

The Part 108 transition

The path described here is the current one, and it is the one the FAA has proposed to change. The proposed Part 108 framework would move routine beyond-line-of-sight flight from case-by-case waivers to a standardized, performance-based system, and as part of that shift the proposal would eliminate the ability to obtain new beyond-line-of-sight waivers under the current rules. Industry commenters have pressed the FAA on how operators already flying under waivers would transition to the new framework, and how proven safety records would be recognized, which are among the open questions in the rulemaking.

The important caveat is that Part 108 is a proposed rule, not law. The FAA published the proposal in August 2025, took comment through October 2025, and reopened the record briefly in early 2026 on limited technical questions, but a final rule had not been issued at the time of writing, and the timing remains uncertain. For now, the beyond-line-of-sight waiver remains the path to advanced operations, and an operator that needs one should pursue it while watching the rulemaking, since the mechanism it relies on is exactly what the proposal would replace. Confirming the current status with the FAA before planning is the sensible step, because this is an area that is actively changing.

Managing BVLOS approvals across a program

A beyond-line-of-sight waiver carries heavier terms than most, and living within them is its own task. The conditions attached to the approval, the operations it covers, the mitigations it depends on, define exactly what may be flown, and a program has to keep the operation inside those lines. When the safety case and the approved terms live in scattered files, it is easy for a job to drift outside what the waiver authorized, which puts the whole approval at risk. Keeping the safety case and the certificate's terms together, where the people running the operation can see them, is what keeps the flying aligned with the approval.

Access is part of that discipline. When a program's platform is set up to restrict each pilot to the jobs assigned to them, a beyond-line-of-sight job can be scoped to the pilots trained and authorized for it, so a mission that depends on specific mitigations is flown only by the crew qualified to run them. An approval this demanding is worth protecting, and tying the waiver's terms, its safety case, and the qualified crew together in one record is what keeps an operation defensible when the FAA, an insurer, or a client asks how a given flight stayed inside its authorization.

Common mistakes in BVLOS waivers

Submitting a request without a real safety case. The FAA disapproves beyond-line-of-sight requests that do not identify hazards and mitigations, because it cannot complete a safety analysis without them. An application that leans on ambition rather than a detect-and-avoid plan is the most common way to earn a denial.

Treating the waiver as broader than its terms. A beyond-line-of-sight waiver authorizes specific operations under specific conditions. Flying outside those terms is the same violation as flying with no waiver, so the conditions and mitigations have to be tracked as carefully as the approval itself.

Confusing the waiver with an airspace authorization. A waiver of the visual-line-of-sight rule and an airspace authorization are separate approvals. A beyond-line-of-sight operation in controlled airspace needs both, and filing only one leaves a requirement unaddressed.

Assuming Part 108 has already replaced the waiver path. Part 108 is a proposed rule that had not been finalized at the time of writing. The beyond-line-of-sight waiver remains the current path, and planning as though the new framework is in effect is premature.

Relying on hardware to make the case. Detect-and-avoid equipment supports a beyond-line-of-sight operation, but the waiver rests on demonstrating that the whole operation manages risk. Listing sensors without explaining how they mitigate the specific hazards does not satisfy the reviewer.

FAQ

What is a BVLOS waiver?

A beyond-line-of-sight waiver is FAA approval to fly a drone past the point of unaided sight by waiving the visual-line-of-sight rule. The FAA grants it when the operator demonstrates it can still detect and avoid other aircraft safely, under specific terms and conditions.

How do I get approved to fly beyond visual line of sight?

Apply for a waiver of the visual-line-of-sight rule and build a safety case that identifies the hazards of an out-of-sight flight and how you will mitigate them, primarily through detect-and-avoid measures. The application must include hazard identification and mitigations, or the FAA will disapprove it.

Will Part 108 replace the BVLOS waiver?

The proposed Part 108 framework would move routine beyond-line-of-sight flight to a standardized system and would eliminate new waivers under the current rules. As of this writing it is a proposed rule that had not been finalized, so the waiver remains the current path.

How long does a BVLOS waiver take?

The FAA aims to decide within about 90 days of submission, but complex requests take longer, and beyond-line-of-sight requests are among the more complex. A complete, specific safety case moves faster; an incomplete one invites requests for more information and delay.

Closing thought

A BVLOS waiver is a safety argument in the form of an application, and it is the current path to the advanced missions that beyond-line-of-sight flight enables. Earning one means demonstrating how the operation will detect and avoid traffic without the pilot's eyes on the aircraft, and living within the specific terms the FAA grants. The proposed Part 108 framework would change that path, but until it is final the waiver is what operators rely on, and a program that keeps its safety case and approved terms together is the one that stays defensible under either regime.

If you are pursuing approval to fly beyond visual line of sight, FlybyOps was built for the operational record problem at the center of regulated drone work. A document vault that tracks waivers and their expirations, a risk register for identified hazards and their mitigations, role-based access control, and an append-only audit log are all part of how the platform keeps a waiver's safety case and its approved terms in one place.