Beyond Visual Line of Sight (BVLOS) flying is the future of commercial drone operations—but it's tightly regulated. Want to fly an autonomous survey drone over a 500-hectare farm without a spotter? That requires CAA approval via SORA (Specific Operations Risk Assessment) and proof of mitigation at the appropriate SAIL (Specific Assurance and Integrity Level). This guide explains the pathway, the costs, and what the CAA actually expects.

What Is BVLOS?

BVLOS means operating a drone beyond the range where you can see it with the unaided eye. Typically:

  • VLOS (Visual Line of Sight): Operator sees drone continuously; range < 500m, altitude < 120m
  • BVLOS (Beyond VLOS): Drone operates beyond operator's sight; range up to several kilometres; requires approved flight plan and monitoring systems

Examples:
  • VLOS: Aerial photography of a building, farmer walking fields with a mapping drone
  • BVLOS: Autonomous pipeline inspection over 10km, precision agriculture over entire field complex, long-range delivery trial

Challenge: Flying BVLOS eliminates the human safety net of direct observation. You can't dodge a manned aircraft you can't see. So CAA requires proof of:
  1. Hazard identification (what could go wrong?)
  2. Risk mitigation (how will you prevent it?)
  3. Residual risk acceptance (is it safe enough?)
That's where SORA comes in.

SORA: Specific Operations Risk Assessment

SORA is a document you submit to CAA requesting approval for BVLOS operations. It's a risk assessment framework adapted from manned aviation.

SORA Structure (CAA Version)

Section 1: Operation Description
  • Type of operation (surveying, inspection, delivery, research)
  • Airspace class (controlled, uncontrolled, restricted)
  • Altitude and range
  • Duration and frequency
  • Aircraft characteristics (weight, speed, endurance, systems)
  • Environmental conditions (weather limits, day/night, terrain)

Section 2: Airspace Analysis
  • Manned aircraft activity (commercial routes, private airstrips, military ranges)
  • Obstacles (buildings, power lines, terrain elevation)
  • Population density (urban, rural, remote)
  • Sensitive areas (hospitals, schools, prisons)

Section 3: Hazard Identification

List potential failures and their consequences:

  • Loss of control (engine failure, propeller loss, software crash)
  • Loss of communication (signal jamming, interference)
  • Loss of navigation (GPS spoofing, magnetic anomalies)
  • Collision (with manned aircraft, with terrain, with obstacles)
  • System failure (battery critical, sensor malfunction, parachute failure)

Section 4: Risk Assessment

For each hazard, estimate:

  • Probability: 1–5 (1 = remote, 5 = frequent)
  • Severity: 1–5 (1 = minor injury, 5 = multiple deaths)
  • Risk: Probability × Severity
  • Mitigation: How you'll prevent or reduce the risk

Section 5: Mitigation Measures

Specific controls:

  • Airspace coordination (NOTAMs, ATC notification)
  • Detect-and-Avoid (DAA) systems
  • Communication redundancy
  • Contingency procedures (emergency landing zones, recovery protocols)
  • Operator qualifications and training
  • Maintenance and pre-flight checks

Section 6: Residual Risk Assessment

After applying all mitigations, is the remaining risk acceptable?

  • If yes: State acceptable risk threshold
  • If no: Add more mitigations or reject the operation as unfeasible

Section 7: Safety Case

Executive summary of how you've proven the operation is safe.

Example SORA Hazard Analysis

Operation: Autonomous tree inspection (LiDAR mapping) over a 50-hectare farm

Hazard Probability Severity Risk Mitigation Residual Risk
Loss of GPS signal 3 (occasional) 4 (crash) 12 Inertial Navigation System (INS) backup; flight corridor pre-planned with visual references 2 (reduced to remote event)
Collision with power line 2 (unlikely) 3 (major damage, fire) 6 Digital terrain model includes utilities; 50m safety buffer; visual spotter; low-altitude flight (50m max) 1 (very remote)
Loss of radio link 2 (unlikely) 3 (uncontrolled descent) 6 Dual communication channels (900MHz + LTE); return-to-home on signal loss; 2-minute hover buffer 1 (very remote)
Mid-air collision with manned aircraft 1 (remote) 5 (catastrophic) 5 Airspace coordination via NOTAM; ATC notification; Remote ID broadcast; flight corridor below common flight paths 1 (acceptable)
---

SAIL Levels: What CAA Requires

After you submit SORA, CAA evaluates it and assigns a SAIL (Specific Assurance and Integrity Level). This determines what additional approvals or evidence you must provide.

SAIL Risk Profile Description Typical Operations CAA Decision
SAIL I Low risk BVLOS over sparsely populated area, established procedures, mature technology Precision agriculture over farm, pipeline inspection over open land, forest surveying Approval: Likely (£2,185 application fee)
SAIL II Moderate risk Higher population density, complex airspace, newer technology, more complex mitigation Delivery trials over suburban areas, infrastructure inspection near roads, research in controlled zones Approval: Conditional (£3,994+ fee + re-assessment required)
SAIL III High risk Urban operations, high-consequence failures, novel procedures Delivery over city centre, autonomous swarm operations, medical supply drops over hospitals Approval: Rare (Custom pricing, typically £10,000+; may require independent review)

SAIL I: Low-Risk Pathway (Most Common)

Criteria met if:
  • BVLOS over rural/sparsely populated land
  • Below 120m altitude
  • No residential areas within 1km
  • Established aircraft type (DJI, PrecisionHawk, etc., proven track record)
  • Standard mitigation (Return-to-Home, geo-fencing, RemoteID)
  • Operator has GVC or equivalent qualification
  • 50+ hours BVLOS experience

CAA Fee: £2,185 (fixed) Timeline: 8–12 weeks for review and decision Approval duration: 1 year (renewable) Example SAIL I operation:

Agricultural surveying company has 100 hectares of client farms in rural Yorkshire. No houses within 2km. Flight corridor 500m above terrain, autonomous return-to-home at 80% battery. Remote ID active. Operator holds GVC with 200+ flying hours. SORA submitted; CAA approves SAIL I after 10 weeks. Cost: £2,185.

SAIL II: Moderate-Risk Pathway

Criteria met if:
  • BVLOS with some urban/populated areas nearby
  • 120–500m altitude
  • Residential areas 500m–2km away
  • Emerging technology (e.g., novel DAA system)
  • Complex mitigation (redundant systems, real-time monitoring)
  • Operator GVC + specialist training in new procedures
  • 100+ hours experience with the specific aircraft/system

CAA Fee: £3,994 (base) + potential re-assessment fees (£500–£2,000 per reassessment) Timeline: 12–20 weeks Approval duration: 1 year (renewable, often with additional conditions) Conditions often applied:
  • Mandatory independent safety audit
  • Quarterly operational reports to CAA
  • Incident notification within 24 hours
  • Retesting of new systems before expanding operation

Example SAIL II operation:

Urban delivery startup wants to trial package delivery in Edinburgh suburbs. Residential areas < 1km away. Uses novel detect-and-avoid system (not yet certified for SAIL I). Pilot holds GVC + training on DAA. SORA submitted with independent safety audit (£2,000 cost). CAA approves SAIL II after 16 weeks, with condition: "Monthly incident reports + altitude restriction to 100m". Cost: £3,994 + £2,000 audit = £5,994.

🦉
Poppo 🦉 (Compliance Expert)

Poppo: "SAIL I is achievable for most agricultural operators. Rural operations, proven aircraft, standard procedures. £2,185 and you're approved."

Piyo: "What if I want to do something more complex?" Poppo: "SAIL II costs more and takes longer. You'll need independent technical review—maybe £2,000–£5,000 extra. The CAA will likely add operational conditions: monthly reporting, restricted airspace, limits on expansion." Moo: "Has anyone done SAIL III?" Poppo: "Rarely. UK Government trials (autonomous delivery, police search & rescue) sometimes get SAIL III approval. Cost: £10,000–£50,000+. They're custom reviews with national security implications."

:::

SORA Preparation Checklist

Pre-Submission (4–8 Weeks Before)

  • [ ] Define your operation precisely (area, altitude, frequency, aircraft, personnel)
  • [ ] Conduct airspace analysis (manned traffic, obstacles, sensitive areas)
  • [ ] Identify 10–15 major hazards relevant to your operation
  • [ ] Design mitigation for each (technical systems, procedures, training)
  • [ ] Document your equipment specifications and certification status
  • [ ] Gather evidence of pilot qualifications (GVC, experience logs)
  • [ ] Develop emergency procedures and contingency plans
  • [ ] Commission pre-flight safety audit (optional but recommended for SAIL II+)

Submission

  • [ ] Complete CAA SORA template (available at caa.co.uk)
  • [ ] Include all supporting documents (equipment specs, procedure manuals, audit reports)
  • [ ] Submit via CAA online portal + pay application fee (£2,185 minimum)
  • [ ] Designate point of contact (usually operations manager)
  • [ ] Await CAA's Acknowledgement of Receipt (typically within 5 days)

Post-Submission (8–20 Weeks)

  • [ ] CAA may request clarifications (respond within 10 days)
  • [ ] Participate in CAA technical review meetings (virtual or in-person)
  • [ ] Modify SORA based on CAA feedback
  • [ ] Prepare for potential re-assessment
  • [ ] Receive Final Approval or Conditional Approval with requirements

Real SAIL I Example: Precision Agriculture

Operation: Farmer wants autonomous NDVi (vegetation) mapping over 300 hectares of wheat fields in Lincolnshire. No houses nearby. 10 flights per season, each lasting 45 minutes. SORA Submission (simplified):
  • Aircraft: Fixed-wing autonomous platform, 2kg, endurance 60 minutes, cruise altitude 80m
  • Airspace: Class G uncontrolled, below 120m, no known commercial traffic
  • Hazard & Mitigation:
  • GPS loss → INS + visual landmarks pre-mapped
  • Propeller failure → parachute system on board
  • Loss of signal → return-to-home after 30 seconds
  • Collision with birds → low speed (12 m/s), early morning operations
  • Operator: Farmer holds GVC, 150+ hours flying experience, 50+ hours autonomous flying
  • Mitigation: RemoteID active, NOTAM issued 24 hours pre-flight, local airstrip notified, weather minimums (wind <10 m/s, visibility >5km)

CAA Assessment: Low risk, sparsely populated, mature technology, proven procedures. SAIL I approved. Cost: £2,185. Valid for 1 year. Farmer can now conduct 10 flights/season legally.

🐮
Moo 🐮 (MmowW Founder)

Moo: "So if I'm already GVC and experienced, SAIL I approval is mostly paperwork?"

Poppo: "Mostly yes. The CAA doesn't invent barriers for established, safe operations. But you have to document it properly. Sloppy SORA gets rejected." Piyo: "Can I do BVLOS without CAA approval?" Poppo: "Legally? No. It's a violation. You'll get fined £20,000–£50,000+ if caught. CAA actively monitors BVLOS via Remote ID and airspace reports." Moo: "What if my SORA gets rejected?" Poppo: "You can re-submit with modifications. First rejection usually gives you feedback. Address it and reapply. But plan for 4–5 months total from initial submission to final approval."

:::

Future Outlook: BVLOS Beyond 2026

The CAA is simplifying BVLOS approvals. By 2027–2028, they expect:

  • Standardised SAIL I procedures (minimal paperwork for rural operations)
  • Pre-approved aircraft types (DJI, Freefly, PrecisionHawk platforms automatically accepted)
  • Expedited approvals (4 weeks instead of 12 weeks)
  • Self-certification option (operators certify compliance; CAA spot-checks)
This is good news for the agriculture and surveying sectors. BVLOS will transition from "special permission" to "standard business practice."

FAQ: BVLOS Operations UK

Q: Do I need GVC to do BVLOS?

A: Yes. Minimum requirement is GVC holder. Some SAIL II operations may allow A2-equivalent experience + specialist training, but CAA prefers GVC.

Q: How long does SORA approval take?

A: SAIL I: 8–12 weeks. SAIL II: 12–20 weeks. SAIL III: 6–12 months+. Plan accordingly.

Q: Can I do BVLOS over a city?

A: Only with SAIL III approval, which is rare. Stick to rural or low-density areas (SAIL I).

Q: If I operate in multiple regions (England, Scotland, Wales), do I need separate SORAa?

A: One SORA can cover multiple regions if the operation is identical. But airspace differences may require region-specific addenda.

Q: How often do I renew SAIL I approval?

A: Annually. Submit renewal documentation 2 months before expiry. If no incidents occurred, renewal is typically automatic.

Q: What counts as a reportable incident?

Compliance with MmowW

At MmowW (£5.29/drone/month), we provide:

  • SORA template generator (pre-populated with your operation data)
  • Hazard matrix builder with CAA-aligned scoring
  • Mitigation library (500+ proven mitigations by operation type)
  • Airspace analysis integration (manned traffic alerts)
  • Incident tracking & CAA notification support
  • Renewal reminders (1, 3, 6 months before expiry)
This cuts SORA preparation from 8 weeks to 2–3 weeks, and ensures CAA-compliant documentation.

Last updated: 8 April 2026. Information reflects CAA SORA guidance and SAIL definitions. Confirm current fees at caa.co.uk.