What are BVLOS Operations?
BVLOS (Beyond Visual Line of Sight) operations allow drones to fly outside the pilot's direct visual range using onboard sensors, GPS, and detect-and-avoid systems. These operations require regulatory approval through waivers or specific authorizations and enable long-range missions for inspection, delivery, surveying, and emergency response applications.
Table of contents
- Understanding BVLOS regulatory requirements
- FAA BVLOS waivers and Part 108
- EASA specific category and SORA
- Technical requirements for BVLOS
- Documentation and risk assessment
- Operational procedures
- Frequently asked questions
- Implementation considerations
- Ready to manage BVLOS compliance?
Understanding BVLOS regulatory requirements
BVLOS compliance starts with understanding which regulatory framework applies to your operation and what level of approval you need. The requirements differ significantly from standard visual line of sight operations.
While VLOS flights are permitted under basic commercial licenses like Part 107, BVLOS requires explicit approval from aviation authorities. The core concern is maintaining separation from manned aircraft and obstacles without direct visual observation. That concern drives documentation requirements far beyond what standard operations demand.
In the United States, the FAA handles BVLOS through two paths: Part 107 waivers (the current system) and the upcoming Part 108 framework. European operators follow EASA regulations using the Specific category and SORA methodology. Canadian operators work with Transport Canada's standardized BVLOS pathways.
Every regulatory system shares common safety requirements regardless of jurisdiction. Operators must demonstrate detect-and-avoid capability, reliable command and control links, comprehensive risk mitigation strategies, and documented operational procedures. The approval process validates these elements through detailed review of your safety case.
FAA BVLOS waivers and Part 108
Current waiver process
The FAA issues BVLOS waivers under 14 CFR Part 107.31, which normally requires operations within visual line of sight. Waiver applications go through FAADroneZone using Form 7711-2.
Three primary waiver approaches exist. Shielded operations use physical barriers to prevent the drone from leaving a controlled area. Visual observer networks position trained observers to maintain visual contact throughout the mission. Certified detect-and-avoid systems provide technical means to identify and avoid other aircraft without observers.
The waiver application centers on the Concept of Operations (CONOPS). This document describes your operation in detail: mission profile, geographic boundaries, altitudes, aircraft specifications, crew qualifications, and safety procedures. The CONOPS must address how the operation achieves equivalent safety to standard Part 107 requirements.
Risk analysis forms the second critical component. Operators identify hazards, assess their likelihood and severity, and detail mitigation measures. The FAA evaluates whether proposed mitigations adequately address identified risks. Operational risk assessment methodologies help structure this analysis, and a formal risk register keeps findings organized for audit.
Processing times vary from 90 to 120 days for complete applications. Incomplete submissions receive a notification of deficiencies and require resubmission. Approved waivers include specific limitations on operations, aircraft, locations, and conditions. Read the full FAA drone waiver guide for a step-by-step walkthrough.
Public safety organizations access streamlined Part 91 waivers for drone-as-first-responder programs. These waivers support emergency response applications where BVLOS capability provides critical operational advantage.
Recent approvals demonstrate that the waiver process works for operators who submit thorough safety cases. DroneDeploy received a nationwide BVLOS waiver for construction monitoring in February 2025. DEXA secured a national BVLOS delivery waiver in July 2025. ResilienX obtained approval for remote BVLOS operations without visual observers in March 2026.
Part 108: the new standardized framework
The FAA published the Part 108 Notice of Proposed Rulemaking (NPRM) in August 2025, with the comment period closing in October 2025. The final rule is expected in spring 2026, with implementation 6 to 12 months after publication.
Part 108 replaces the slow, case-by-case waiver system with a predictable framework for routine BVLOS operations. Key elements include:
- Two approval levels. Permitted Operations (self-certified for lower-risk missions) and Certificated Operations (FAA-reviewed for higher-risk scenarios). The permitted vs certificated distinction determines how much oversight applies.
- Five risk categories based on population density and operational complexity, from rural unpopulated areas to dense urban environments.
- New crew roles. Operations Supervisor (overall responsibility) and Flight Coordinator (managing individual flights), replacing the single Remote Pilot in Command structure. See the Part 108 requirements checklist for the full breakdown.
- Airworthiness acceptance rather than full aircraft certification, lowering the barrier for commercial platforms.
- Operations up to 1,320 pounds, covering everything from small inspection drones to large cargo delivery platforms, well beyond Part 107's 55-pound limit.
Part 146, published alongside Part 108, creates a certification framework for UTM service providers that support BVLOS operations with traffic management and deconfliction services.
EASA specific category and SORA
European operators conduct BVLOS operations under the specific category framework. This risk-based system requires operational authorization from national aviation authorities.
The Specific Operations Risk Assessment (SORA) provides the methodology for risk classification. EASA updated SORA to version 2.5, refining the methodology for complex BVLOS missions while streamlining procedures for lower-risk operations. The process evaluates ground risk, air risk, and required mitigation measures.
Ground risk assessment considers the operational area's population density and characteristics. Operations over urban areas receive higher risk scores than remote locations. The assessment determines the required Ground Risk Class and corresponding mitigation measures.
Air risk evaluation focuses on collision risk with manned aviation. Factors include airspace class, altitude, proximity to airports, and local traffic patterns. The resulting Air Risk Class drives requirements for detect-and-avoid capability and tactical mitigation procedures.
Operators combine ground and air risk assessments to determine the overall Specific Assurance and Integrity Level (SAIL). Higher SAIL ratings require more robust safety measures, operational procedures, and potentially third-party validation of the safety case. The SORA methodology guide covers this process in detail.
Three authorization paths are available:
- Standard Scenarios (STS-01, STS-02). Pre-defined operational envelopes where operators submit a declaration rather than applying for individual authorization.
- Pre-Defined Risk Assessments (PDRAs). PDRA-01 covers BVLOS over sparsely populated areas. Using a PDRA reduces documentation requirements compared to full SORA analysis.
- Full SORA. Required for operations that do not fit standard scenarios, such as corridor inspections or large-area surveys.
U-space, Europe's UTM framework, is becoming essential for scalable BVLOS. U-space airspace requires network Remote ID and continuous connectivity to U-space service providers. Operators planning BVLOS in urban or controlled airspace need to factor U-space compliance into their planning from the start.
Member state aviation authorities review applications and issue operational authorizations specifying permitted operations, geographic boundaries, required procedures, and crew qualifications. Some nations maintain additional requirements beyond the EU baseline.
Technical requirements for BVLOS
Command and control link reliability forms the foundation of BVLOS operations. Systems must maintain connectivity throughout the operational area with sufficient bandwidth for telemetry, video, and control commands. Backup communication systems provide redundancy if the primary link fails. Options include cellular (4G/5G), satellite, mesh radio, and dedicated RF links.
Detect-and-avoid systems prevent mid-air collisions. Electronic conspicuity solutions broadcast the drone's position to nearby aircraft. Cooperative DAA uses ADS-B receivers to detect transponder-equipped aircraft. Non-cooperative systems employ radar, optical sensors, or acoustic detection to identify non-transponder targets. Companies like Iris Automation and Skydio have developed certified DAA systems that satisfy FAA requirements for operations without visual observers.
Navigation accuracy requirements exceed standard GPS performance. Real-Time Kinematic (RTK) positioning ensures centimeter-level accuracy for obstacle avoidance and mission execution. Operators must account for GPS degradation or loss scenarios in their contingency procedures.
Automated flight termination provides a safety backstop. If the aircraft exits defined geographic boundaries, loses communication, or encounters critical system failures, the termination system executes a safe landing or controlled descent within approved areas.
Weather monitoring integrates real-time conditions into operational decisions. Wind speed, visibility, precipitation, and temperature all affect BVLOS flight safety. Platforms with integrated weather data can automatically pause or abort missions when conditions exceed operational parameters.
System health monitoring provides continuous assessment of critical components. Battery status, motor temperatures, link quality, and navigation accuracy receive active monitoring. Degraded performance triggers warnings or automated safety responses.
Geofencing prevents inadvertent entry into restricted areas. Multi-layer boundaries create warning zones before hard limits. The system automatically prevents flight into prohibited airspace or maintains required separation distances.
Documentation and risk assessment
The operational manual defines procedures for all phases of BVLOS operations. It covers pre-flight planning, crew responsibilities, normal procedures, emergency procedures, and post-flight reporting. This document serves as the foundation for crew training and operational consistency.
Pre-flight planning for BVLOS requires more detailed preparation than standard flights. Mission planning includes route analysis, airspace coordination, weather assessment, NOTAM review, and system verification. Documentation captures planning decisions and authorization confirmations. A thorough pre-flight checklist adapted for BVLOS covers communication link verification, DAA system checks, and geofence configuration on top of standard items.
Crew qualifications extend beyond basic pilot licensing. BVLOS operations require specific training on system operation, emergency procedures, crew resource management, and regulatory requirements. Tracking pilot certifications and training records documents competency verification and recurrent training completion.
Maintenance procedures ensure aircraft reliability. Scheduled inspections, component replacements, and system tests follow manufacturer recommendations and operational experience. Maintenance tracking documents all service actions and component history. For BVLOS, maintenance records carry extra weight because aircraft reliability directly affects the safety case in your waiver or authorization.
Incident reporting procedures align with regulatory requirements. Operators must identify reportable events, notification timelines, and investigation procedures. Documentation of incidents provides safety data and identifies improvement opportunities.
The safety management system integrates these elements into a coherent framework. It includes safety policy, risk management processes, safety assurance activities, and safety promotion efforts. Regular reviews identify trends and drive continuous improvement.
Insurance requirements for BVLOS operations typically exceed standard commercial policies. Specialized coverage addresses higher risk exposure and regulatory requirements. Insurance costs vary by jurisdiction, operation type, and coverage limits. Securing adequate coverage before applying for BVLOS authorization is essential, as most authorities require proof of insurance.
Operational procedures
Mission execution begins with comprehensive preflight procedures. Beyond standard preflight checklists, BVLOS operations verify communication links, detect-and-avoid systems, geofencing configuration, and emergency systems. Each system receives functional verification before flight approval.
Airspace coordination requirements vary by jurisdiction and operation type. Operations in controlled airspace require prior authorization through LAANC or manual coordination. Some regulatory frameworks support digital coordination through UTM systems, while others rely on traditional procedures.
Crew coordination protocols define roles and responsibilities. Under Part 107 waivers, the remote pilot in command maintains overall authority. Under Part 108, the Operations Supervisor and Flight Coordinator roles replace this structure. Visual observers, if used, follow specified scanning patterns and communication procedures. Technical operators monitor system health and performance parameters.
Takeoff and landing procedures require particular attention in BVLOS operations. These phases typically occur within visual range before transitioning to BVLOS segments. Launch and recovery sites must provide safe operations and meet regulatory requirements for separation from people and property.
En route operations follow approved routes and altitude profiles. Pilots monitor aircraft performance, navigation accuracy, and system health through live tracking systems. Deviations from planned routes require approval or trigger predefined contingency procedures. Continuous risk assessment during flight identifies changing conditions that may require mission modification.
Lost link procedures execute if the command and control connection fails. Aircraft typically enter a holding pattern while attempting to reestablish the link. If communication cannot be restored within specified timeframes, automated procedures execute a safe landing or controlled flight termination.
Emergency procedures address various contingency scenarios. System failures, weather deterioration, airspace incursions, and equipment malfunctions each have defined responses. Crew training emphasizes decision-making under time pressure and coordination during emergencies.
Post-flight procedures include mission debriefing, flight log documentation, data download, and equipment inspection. Anomalies or deviations from standard operations receive investigation and documentation. This information feeds into safety management and continuous improvement processes.
Frequently asked questions
How long does it take to get BVLOS approval?
FAA waiver applications typically take 90 to 120 days for complete submissions. EASA specific category authorizations vary by member state but generally require 30 to 90 days. Once Part 108 is finalized, Permitted Operations (the lower-risk tier) should offer faster approval through self-certification. The timeline depends on application completeness, operation complexity, and authority workload. Starting the process early and ensuring thorough documentation reduces delays.
Can I use my existing Part 107 license for BVLOS operations?
Your Part 107 certification is a prerequisite, but it is not sufficient alone. You need a specific BVLOS waiver through FAADroneZone, or (once available) a Part 108 authorization. The application demonstrates how you will achieve equivalent safety to standard Part 107 requirements. Additional training on BVLOS-specific procedures and systems is typically required.
What does detect-and-avoid equipment cost?
DAA system costs range from $5,000 to $50,000 depending on capability and integration requirements. Basic ADS-B receivers start around $5,000. Integrated radar and optical systems from providers like Iris Automation cost $20,000 to $50,000. Operating costs include maintenance, calibration, and software updates. Consider total system cost including integration with your aircraft platform and ground control systems.
Should I wait for Part 108 or apply for a waiver now?
It depends on your timeline. The Part 108 final rule is expected spring 2026, with implementation 6 to 12 months after that. If you need BVLOS capability before late 2026 or early 2027, apply for a Part 107 waiver now. If your timeline is longer, you may benefit from building your safety case and documentation to Part 108 standards from the start, since much of the groundwork (CONOPS, risk assessment, crew training) transfers directly.
Implementation considerations
Building a BVLOS capability requires significant investment in equipment, training, and documentation. Start by identifying specific operational requirements and use cases. Understanding mission profiles helps determine appropriate technology solutions and regulatory pathways.
Technology selection should align with operational needs and regulatory requirements. Evaluate aircraft endurance, payload capacity, communication range, and sensor capabilities. Consider system integration complexity and vendor support availability. Choose platforms with proven track records in BVLOS applications.
Regulatory pathway selection depends on your jurisdiction, operation type, and timeline. In the US, determine whether Part 107 waivers or the upcoming Part 108 framework best fits your needs. In Europe, assess whether PDRAs apply or full SORA analysis is required. The compliance management burden is substantial either way.
Training program development encompasses technical skills, regulatory knowledge, and operational procedures. Create structured training for remote pilots, visual observers, and support personnel. Include scenario-based training for emergency procedures and decision-making under pressure. Track pilot flight hours and training completion centrally.
Consider partnering with organizations experienced in BVLOS operations. Drone service providers with existing approvals can provide valuable guidance. Some operators offer consulting services to support waiver applications and program development.
Budget both initial and ongoing costs. Initial expenses include equipment, documentation development, training, and application fees. Ongoing costs cover maintenance, insurance, recurrent training, and regulatory compliance activities. Fleet management systems help track costs and optimize operations across your entire program. Running the numbers through an ROI analysis before committing helps set realistic expectations.
Ready to manage BVLOS compliance?
BVLOS operations generate more compliance documentation than any other category of drone work. Risk assessments, CONOPS documents, flight logs, crew certifications, maintenance records, and audit reports all need to stay current and accessible at all times.
DroneBundle centralizes the entire compliance workflow. Plan missions with integrated weather data, track flights with live monitoring, manage crew certifications, maintain equipment records, and generate audit-ready reports from a single platform.
Start your free trial today, no credit card required.
Or try the live demo to see how BVLOS compliance tracking works in practice.




