What is a BVLOS waiver? A BVLOS waiver is an FAA authorization that allows drone operators to fly beyond visual line of sight under Part 107 (commercial) or Part 91 (public safety). The application requires a detailed Concept of Operations, risk analysis, and proof that your operation achieves equivalent safety to standard visual line of sight flight.
Table of contents
- BVLOS waiver basics
- Three BVLOS approval approaches
- Part 107 vs Part 91 BVLOS waivers
- Writing a BVLOS CONOPS that gets approved
- Risk analysis for BVLOS operations
- Common BVLOS waiver denial reasons
- Companies with approved BVLOS waivers
- BVLOS waivers vs Part 108
- Frequently asked questions
- Ready to prepare your BVLOS waiver application?
BVLOS waiver basics
A BVLOS waiver grants permission to fly a drone outside the pilot's direct visual range. Under standard Part 107 rules, section §107.31 requires the remote pilot in command to maintain visual line of sight with the aircraft at all times. A waiver to this section removes that requirement for a specific operation.
The waiver application is free. You submit it through the FAA's Aviation Safety Hub portal using Form 7711-2. The FAA evaluates your application based on one question: does your proposed operation achieve an equivalent level of safety to standard VLOS flight?
That question drives everything in the application. Every section of your CONOPS, every line of your risk analysis, every equipment specification must answer it. The FAA is not looking for promises that you will "be careful." They want documented evidence of how your specific equipment, procedures, and mitigations replace the safety function that visual contact normally provides.
Processing time runs 90 to 120 days for complete applications. Incomplete submissions get bounced with a deficiency notice, which resets the clock. Approved waivers specify the operation type, geographic area, altitude limits, aircraft, and conditions. They typically last two to four years.
Before starting a BVLOS waiver application, you need a valid Part 107 certificate. If your operation also requires flying over people, at night with modified lighting, or above 400 feet, you will need to request waivers to those sections simultaneously. Read the complete FAA drone waiver guide for the full list of waivable regulations.
Three BVLOS approval approaches
The FAA recognizes three primary methods for maintaining safety during BVLOS flight. Your application must use one of these approaches, or a combination.
Shielded operations
Shielded operations use physical terrain or structures to contain the drone within a defined area. Buildings, terrain features, or other obstacles prevent the aircraft from entering airspace where it could encounter manned aircraft. This approach works for operations in canyons, between buildings, or within fenced industrial sites.
The shielding must physically prevent the drone from climbing above the obstacle boundary. The FAA evaluates whether the shielding is continuous (no gaps), whether the drone's performance envelope keeps it within the shielded area, and what happens if the drone attempts to fly above the shielding height.
Public safety agencies use shielded operations extensively for drone-as-first-responder programs. The FAA's standardized 200-foot shielded operations checklist provides a streamlined pathway for these operations, keeping the drone below building and tree height.
Shielded operations have the simplest documentation requirements because the physical environment provides the primary safety mitigation. If your operation fits within terrain or structural constraints, this is the fastest path to approval.
Visual observer networks
Visual observer (VO) networks extend coverage beyond the pilot's direct line of sight. Trained observers positioned along the flight route maintain visual contact with the drone and communicate with the pilot. Each observer covers a segment of the route, and handoffs occur as the drone moves between segments.
Your application must detail observer placement, maximum distances, communication protocols, and handoff procedures. The FAA wants to know the exact positions, what each observer can see, how they communicate with the pilot and each other, and what happens if an observer loses visual contact.
This approach works well for linear infrastructure like power line inspections or pipeline surveys where the route is predictable. The downside is crew size. A 10-kilometer route might need 6 to 8 observers, making it expensive and logistically complex.
VO networks are sometimes used as an interim step while operators build the case for DAA-based operations. The operational data and safety record from VO operations strengthens future applications for observer-free BVLOS.
Detect-and-avoid (DAA) systems
DAA-based waivers are the highest bar but also the most operationally valuable. Approved DAA systems replace the pilot's eyes entirely, using sensors to detect other aircraft and obstacles, then maneuvering the drone to maintain safe separation.
Two categories exist:
- Cooperative DAA uses ADS-B receivers to detect transponder-equipped aircraft. This works for manned aircraft that carry transponders but does not detect non-equipped traffic (ultralights, gliders, some helicopters).
- Non-cooperative DAA uses radar, optical cameras, LiDAR, or acoustic sensors to detect any aircraft regardless of transponder status. This is what the FAA typically requires for operations in shared airspace.
Companies like Iris Automation (Casia system) and Skydio have developed DAA solutions that satisfy FAA requirements. Your application must include the system's detection range, classification accuracy, response time, and false-alarm rate, along with data from flight testing that demonstrates real-world performance.
DAA-based waivers take longer to process because the FAA evaluates the technology itself alongside the operational procedures. But once approved, these waivers often cover broader geographic areas and do not require visual observers, significantly reducing per-mission costs.
Part 107 vs Part 91 BVLOS waivers
Two regulatory pathways exist for BVLOS waivers. The right one depends on who you are and what type of operation you are conducting.
| Part 107 (Commercial) | Part 91 (Public Safety) | |
|---|---|---|
| Who qualifies | Any Part 107 certificate holder | Public Aircraft Operators that are also Public Safety Organizations |
| Typical operations | Infrastructure inspection, delivery, surveying, agriculture | Emergency response, law enforcement, fire, search and rescue |
| Processing time | 90 to 120 days | As fast as 1 week for shielded DFR operations |
| Documentation | Full CONOPS + risk analysis | Streamlined for qualifying PSOs using FAA checklist |
| Geographic scope | Operation-specific area | Can be jurisdiction-wide for public safety |
| Weight limit | 55 lbs (Part 107 limit) | No weight limit under Part 91 |
Public safety agencies have a significantly faster path. The FAA streamlined Part 91 BVLOS waivers for qualified Public Aircraft Operators (PAOs) that also meet the definition of Public Safety Organization (PSO). These organizations submit a certification letter confirming their status along with Form 7711-2. For shielded operations under 200 feet, the FAA provides a standardized checklist that replaces much of the custom documentation.
Skydio received FAA approval in March 2026 for one pilot to fly four drones simultaneously under BVLOS conditions, specifically targeting law enforcement applications. Twelve police departments were already participating at launch.
Commercial operators use the Part 107 pathway, which requires the full documentation package. There are no shortcuts here, but the process is well-documented and the FAA publishes section-specific evaluation guidance that tells you exactly what reviewers look for.
Writing a BVLOS CONOPS that gets approved
The Concept of Operations is the centerpiece of your BVLOS waiver application. A weak CONOPS is the single most common reason applications get denied. The FAA has stated publicly that many submissions are "two sentences or less," which obviously fail.
A BVLOS CONOPS must cover these elements:
Mission description. What are you doing, where, when, and why? Specify the operation type (inspection, delivery, mapping, monitoring), the geographic area with coordinates, altitude range, time of day, and expected frequency.
Aircraft specifications. Make, model, weight, maximum speed, maximum altitude, endurance, communication systems, navigation systems, and DAA equipment. Include performance data: climb rate, descent rate, maximum wind tolerance, and minimum operating temperature.
Airspace analysis. Identify the airspace class, proximity to airports, traffic density, and any temporary flight restrictions that may apply. Show that you understand the airspace environment and have coordinated with relevant authorities. If the operation is in controlled airspace, describe your LAANC or manual coordination procedures.
Crew roles and qualifications. Define each crew position, their responsibilities, required certifications, and training requirements. For VO-based operations, specify observer positions and communication procedures. Document minimum flight hour requirements for each role.
Safety mitigation. This is the core of the CONOPS. For every hazard that visual line of sight normally mitigates (collision avoidance, obstacle clearance, aircraft state awareness), explain specifically how your operation achieves equivalent safety. Generic statements fail. "We will use DAA" fails. "The Casia G system provides 120-degree field of view with 750-meter detection range for cooperative and non-cooperative traffic, triggering automated avoidance maneuvers when traffic enters a 500-meter safety buffer" passes.
Contingency procedures. Lost communication link, GPS failure, DAA system failure, weather deterioration, airspace incursion, flyaway. Each scenario needs a defined response that the FAA can evaluate. Pre-flight checklists should include verification of all contingency systems before launch.
Geographic boundaries and geofencing. Define the operational area, buffer zones, and hard geofence limits. Show how the system prevents the drone from exiting the approved area. Include flight planning procedures that verify geofence configuration before each mission.
The FAA evaluates your CONOPS against their section-specific evaluation criteria. Read that document before writing a single word of your CONOPS. It tells you exactly what the reviewer will look for in a §107.31 application.
Risk analysis for BVLOS operations
The risk analysis complements your CONOPS by systematically identifying hazards, assessing their likelihood and severity, and documenting mitigations. The FAA wants to see structured analysis, not narrative reassurance.
Start by identifying every hazard specific to BVLOS operations:
- Mid-air collision with manned aircraft
- Mid-air collision with other drones
- Ground collision with people or property
- Lost command and control link
- Navigation or GPS failure
- DAA system failure or degraded performance
- Weather changes (visibility, wind, precipitation)
- Geofence breach
- Battery or propulsion failure during extended flight
- Communication failure between crew members
For each hazard, assess likelihood (rare, unlikely, possible, likely, frequent) and severity (negligible, minor, major, hazardous, catastrophic). Then document the specific mitigation that reduces either likelihood or severity to an acceptable level.
A formal risk register keeps this analysis organized. The FAA expects to see how each mitigation maps to specific equipment, procedures, or training. An operational risk assessment framework such as SORA (even for US operations) provides a recognized methodology that FAA reviewers understand.
The strongest applications include testing data. If your DAA system detected 47 out of 48 aircraft during 200 hours of field testing, include that data. If your lost-link procedure successfully returned the aircraft in 15 out of 15 simulated scenarios, document it. The FAA weighs demonstrated performance far more heavily than theoretical capabilities.
Common BVLOS waiver denial reasons
Understanding why applications fail helps you avoid the same mistakes.
Vague or missing CONOPS. The number one reason. "We will fly BVLOS for inspections" tells the FAA nothing. They need the level of detail described in the section above. If your CONOPS does not answer every question a reviewer might ask, it is not complete.
No detect-and-avoid solution (or an inadequate one). For operations in shared airspace without visual observers or shielding, you must demonstrate how the drone detects and avoids other aircraft. Saying "we will monitor ADS-B" is insufficient because ADS-B only works for transponder-equipped traffic. Non-cooperative detection is required unless your operation guarantees no non-equipped traffic will be present.
Cookie-cutter applications. The FAA sees the same template submissions repeatedly. Your application must be tailored to your specific aircraft, equipment, location, and operation type. A BVLOS waiver for power line inspection in rural Kansas has different risk factors than one for construction monitoring in suburban Denver.
Incomplete lost-link procedures. The FAA needs to know exactly what happens at every stage of a communication failure: immediate response, hold pattern, reacquisition attempts, automated landing, and flight termination. Vague statements like "the drone will return home" are not sufficient. Specify altitudes, timing, and decision criteria.
Failure to respond to deficiency notices. If the FAA sends a deficiency notice, respond promptly and thoroughly. Slow or partial responses signal that you are not a serious operator. Each deficiency notice resets the review clock, so a single incomplete response can add months to your timeline.
Insufficient crew training documentation. The FAA wants evidence that your crew is trained specifically on BVLOS procedures, not just standard Part 107 operations. Provide training syllabi, evaluation criteria, and records showing each crew member has completed the required training.
Companies with approved BVLOS waivers
These approvals show what successful applications look like and the scale of operations the FAA has authorized.
| Company | Type | Year | Scope |
|---|---|---|---|
| DroneDeploy | Part 107 | 2025 | Nationwide BVLOS for construction site monitoring |
| DEXA | Part 107 | 2025 | National BVLOS delivery waiver |
| ResilienX | Part 107 | 2026 | Remote BVLOS without visual observers, valid through 2029 |
| Skydio | Part 91 | 2026 | Multi-drone BVLOS for law enforcement (1 pilot, 4 drones) |
| Cyberhawk | Part 107 | 2024 | Nationwide BVLOS for industrial asset inspection |
The FAA maintains a public database of all issued Part 107 waivers. Reviewing approved BVLOS waivers in your industry gives you direct insight into what the FAA accepts. Pay attention to the conditions and limitations attached to each waiver, as they reveal the FAA's expectations.
BVLOS waivers vs Part 108
The FAA published the Part 108 NPRM in August 2025. The final rule is expected in spring 2026, with implementation 6 to 12 months after that. Part 108 creates a standardized framework that will eventually replace much of the waiver process for routine BVLOS operations.
Key differences between the current waiver system and Part 108:
| Part 107 Waiver | Part 108 | |
|---|---|---|
| Process | Case-by-case review | Standardized categories |
| Timeline | 90 to 120 days | Expected to be faster for Permitted Operations |
| Weight limit | 55 lbs | Up to 1,320 lbs |
| Scope | Operation-specific | Broader operational authorizations |
| Crew structure | Remote PIC | Operations Supervisor + Flight Coordinator |
| Duration | 2 to 4 years | TBD (expected ongoing under operating permits) |
Read the full Part 108 overview and Part 108 vs Part 107 comparison for detailed analysis.
Should you wait for Part 108? If you need BVLOS capability before late 2026 or early 2027, apply for a waiver now. The documentation work transfers: your CONOPS, risk analysis, crew training, and equipment validation all carry over to Part 108. Building that foundation now puts you ahead when the new framework takes effect. If your timeline is longer, consider building your safety case to Part 108 requirements from the start.
Frequently asked questions
How much does a BVLOS waiver cost?
The FAA waiver application itself is free. The real costs are in preparation: DAA equipment ($5,000 to $50,000+), documentation development (typically 100 to 200 hours of work), crew training, and flight testing to generate safety data. Many operators also hire consultants with BVLOS waiver experience, which adds $10,000 to $30,000 depending on the operation's complexity. Insurance costs for BVLOS operations also run higher than standard VLOS policies.
Can I get a BVLOS waiver for any location?
BVLOS waivers are location-specific. Your application defines the geographic area where the operation will take place. Some operators receive jurisdiction-wide waivers (especially public safety), while commercial operators typically get approval for defined operational areas. Nationwide waivers exist but are rare, granted only to operators with extensive safety records and proven systems (DroneDeploy and DEXA are examples).
What drone do I need for BVLOS?
No specific aircraft is required, but your drone must support the technical requirements: reliable command and control links, GPS/RTK navigation, geofencing, automated lost-link procedures, and integration with your chosen DAA system. Flight endurance matters more for BVLOS than VLOS since missions cover greater distances. Most approved BVLOS operations use enterprise-grade platforms from DJI, Skydio, or specialized manufacturers, not consumer drones.
How long does a BVLOS waiver last?
Approved Part 107 BVLOS waivers typically remain valid for two to four years. ResilienX's 2026 waiver is valid through September 2029. Waivers include specific conditions that must be followed on every flight. Violating conditions can result in waiver revocation. Plan for renewal 6 months before expiration, as the renewal process requires updated documentation showing continued compliance.
Ready to prepare your BVLOS waiver application?
A successful BVLOS waiver requires months of documentation: CONOPS, risk analysis, crew training records, equipment specifications, flight logs, and maintenance records. Keeping all of that organized and audit-ready is the difference between a smooth review and a deficiency notice.
DroneBundle centralizes your compliance documentation in one platform. Track pilot certifications, manage fleet maintenance, log flights automatically, and generate the reports your BVLOS application demands.
Start your free trial today, no credit card required.
Or try the live demo to see how compliance tracking supports BVLOS waiver preparation.
