The SORA (Specific Airspace Risk Assessment) is the foundation of UK advanced drone operations. If you're operating beyond standard permitted scope—flying over people, in controlled airspace, delivering payloads, or conducting complex operations—you'll need a SORA. This comprehensive guide explains the SORA methodology, compliance framework, and best practices.

What is a SORA?

A Specific Airspace Risk Assessment (SORA) is a detailed safety analysis documenting:

  1. What you're doing — Detailed operation description
  2. Where and how — Airspace, altitude, routes
  3. What could go wrong — Failure modes and hazards
  4. How you'll prevent it — Mitigation measures
  5. Proof it's safe — Evidence and validation

The SORA is the CAA's primary tool to evaluate whether a proposed operation is safe enough to approve.

When is SORA Required?

Operations Requiring SORA

SORA is mandatory for:
  • Flight over people (Category 2, 3, 4 operations)
  • BVLOS (Beyond Visual Line of Sight) operations
  • Night flying
  • Autonomous delivery operations
  • Complex operations in controlled airspace
  • Drone racing and high-speed operations
  • Any operation outside "General Approval" scope

Operations NOT Requiring SORA

SORA is NOT required for:
  • Standard low-altitude photography (under 50m, clear airspace)
  • Hobbies and recreational flying
  • Simple surveying on own land (low-risk conditions)
  • Very light drones (<250g) in designated open areas

Recommendation: When in doubt, submit a SORA. Better to over-document than fail review.

CAA SORA Framework (2026 Update)

The CAA publishes SORA guidance aligned with EASA standards (post-Brexit, UK maintains compatibility).

SORA Fundamental Structure

A complete SORA assessment includes:

1. Ground Risk Assessment (GRA)

Evaluates risk to people and property on the ground if the drone fails.

Key factors:
  • Population density: Count of people in operation area
  • Building density: Facilities, residential areas, critical infrastructure
  • Distance from ground: Altitude determines impact energy
  • Failure modes: How drone descends if power lost (glide pattern, parachute deployment)

Output: Calculated risk of serious injury or fatality, compared to acceptable threshold (10^-7 per flight hour).

2. Air Risk Assessment (ARA)

Evaluates collision risk with manned aircraft.

Key factors:
  • Airspace type: Controlled vs. uncontrolled
  • Manned aircraft traffic patterns: GA flights, helicopter routes, military activity
  • Detect & Avoid capability: Can drone avoid aircraft collision?
  • Communication: Notification to airspace authorities

Output: Collision probability assessment and mitigation strategy.

3. Operational Risk Assessment (ORA)

Evaluates risks from the operation itself (human factors, procedures, training).

Key factors:
  • Pilot qualifications: PfCO, experience, training
  • Crew configuration: Number and roles of personnel
  • Procedures: Flight procedures, emergency responses, decision-making
  • Contingencies: Backup systems, recovery procedures

Output: Evidence that operational controls reduce risk to acceptable levels.

4. Mitigation and Recovery Measures

Documents how each identified risk is reduced:

Examples:
  • Risk: Manned aircraft collision
  • Mitigation: Detect & Avoid radar system + ADS-B integration + airspace coordination
  • Evidence: System specification, validation testing, operational procedures

Step-by-Step SORA Development Process

Phase 1: Operation Definition (Days 1–3)

Document exactly what you're doing:

  • Operation type: Description (delivery, inspection, filming, etc.)
  • Location: Coordinates, map, description
  • Airspace: Chart showing airspace type, restrictions, NOTAMs
  • Aircraft: Drone type, weight, sensors, propulsion
  • Altitude and flight envelope: Min/max altitude, speed, distance from ground
  • Duration and frequency: How long per flight? How many flights?
  • Weather limits: Wind, visibility, precipitation minimums
  • Crew configuration: Pilot, observer, ground station operator roles

Output: 2–3 page operation specification.

Phase 2: Hazard Identification (Days 3–5)

List all possible failure modes and scenarios:

Ground hazards:
  • Drone loss of power (descends at X m/s)
  • Propeller failure (asymmetric descent)
  • Control link loss (returns home safely? Where?)
  • GPS loss (manual recovery capability?)

Air hazards:
  • Manned aircraft undetected (collision probability?)
  • Uncontrolled airspace adjacent to operation (traffic spillover?)

Operational hazards:
  • Pilot fatigue (long operation duration?)
  • Weather deterioration (decision points and abort triggers?)
  • Spectator incursion (impact on safety?)
  • Communication failure (crew aware? Backup systems?)

Output: Comprehensive hazard register (typically 15–30 items).

Phase 3: Risk Quantification (Days 5–10)

Assess each hazard's severity and probability:

Severity scale:
  • Catastrophic: Fatality or serious injury
  • Major: Serious injury, significant property damage
  • Minor: Minor injury, modest property damage
  • Negligible: No injury or damage

Probability scale:
  • Frequent: Expected to occur regularly
  • Probable: Likely to occur in operation
  • Occasional: May occur in operation
  • Remote: Unlikely but possible
  • Improbable: Very unlikely

Risk matrix: Combine severity × probability to classify risk as acceptable, tolerable (with mitigation), or unacceptable. Output: Risk register with numerical risk scores for each hazard.

Phase 4: Mitigation Planning (Days 10–14)

For each unacceptable risk, design mitigation:

Mitigation categories:
  1. Technical measures: Parachute systems, detect & avoid, backup power
  2. Operational measures: Pilot training, procedures, crew briefing
  3. Procedural measures: Approval processes, checklists, contingency plans
  4. Airspace measures: Coordination with authorities, frequency management

Target: Reduce all risks to 10^-5–10^-7 per flight hour (acceptable threshold). Output: Mitigation register showing each risk, proposed control, and expected residual risk.

Phase 5: SORA Document Preparation (Days 14–16)

Compile formal CAA SORA document:

Sections:
  1. Executive summary
  2. Operation description
  3. Airspace description
  4. Equipment and systems
  5. Crew qualifications
  6. Ground risk assessment (with calculations)
  7. Air risk assessment (with traffic analysis)
  8. Operational risk assessment (procedures)
  9. Mitigation measures and recovery procedures
  10. Conclusion and acceptable risk statement
  11. Appendices (charts, diagrams, evidence)

Length: Typically 30–50 pages for complex operations.

Phase 6: CAA Submission and Review (Weeks 4–8)

  • Submit to CAA with supporting evidence
  • CAA reviews for completeness and adequacy
  • May request clarifications or additional information
  • Approval or conditional approval issued

Total SORA timeline: 6–12 weeks from start to approval.

Common SORA Mistakes (Red Flags for CAA Rejection)

Mistake 1: Insufficient Ground Risk Assessment

Error: Claiming acceptable risk without calculating probability of injury. CAA response: Request detailed risk calculation with supporting data. Fix: Use CAA risk models or independent expert assessment.

Mistake 2: Inadequate Mitigation for High-Risk Operations

Error: Proposing flight over populated areas without parachute system. CAA response: Rejection without parachute or equivalent mitigation. Fix: Include technical measures (parachute, geofencing, detect & avoid).

Mistake 3: Weak Contingency Planning

Error: No documented procedures for equipment failure mid-flight. CAA response: Questions on crew training and emergency response. Fix: Detail specific contingencies and crew briefing procedures.

Mistake 4: Unclear Air Risk Assessment

Error: Failing to coordinate with manned aircraft or airspace authority. CAA response: Conditional approval requiring airspace coordination. Fix: Early engagement with NATS or local airspace authority.

Mistake 5: Insufficient Crew Qualifications

Error: Proposing operation with pilot having <50 flight hours. CAA response: Requires additional experience or training documentation. Fix: Log sufficient practice hours before SORA submission.

SORA and CAA Exemptions: When SORA Can Be Avoided

Automatic Exemptions (No SORA Needed)

Category 1 operations (under certain conditions):
  • Drone <250g, low-speed, open areas
  • Condition: No populated zones, clear airspace
  • Approval: Simple notification only

Recreational flying:
  • Non-commercial, personal use
  • Condition: Below 400ft, away from airports
  • Approval: None required

Possible Exemptions (CAA Case-by-Case)

Certain emergency operations:
  • Search and rescue, fire/police operations
  • Approval timeline: 24–48 hours (expedited)
  • Requirement: Life-safety justification

Research and academic projects:
  • University drone research with safety case
  • Approval: 8–12 weeks (thorough review)
  • Requirement: Independent safety oversights

SORA Templates and Tools

The CAA provides resources to assist SORA development:

Official CAA Resources

  • SORA guidance document (free, online)
  • Risk assessment worksheets (free Excel templates)
  • Approved mitigation measures library (examples of accepted controls)
  • Available: www.caa.co.uk (Unmanned Aircraft section)

Third-Party SORA Tools

Several companies offer SORA-building software:

  • DroneBase SORA Builder: Automated SORA generation (£500–£1,500)
  • Skywise: Integrated SORA and compliance management (£200–£500/month)
  • Worksafe Drone: Industry-specific SORA templates (£300–£800)

SORA Cost Analysis

One-Time Development Costs

Item Cost
In-house development (staff time) £2,000–£5,000
External consultant (if hired) £3,000–£8,000
Risk assessment tools/software £300–£1,500
Validation testing (equipment) £1,000–£3,000
CAA submission and support Included in PfCO
Total £6,300–£17,500

Ongoing Renewal Costs

  • Annual SORA review: £500–£1,500
  • Location-specific variations: £300–£800 each
  • Equipment updates: £200–£500

SORA for Different Operation Types

Mapping/Surveying SORA

  • Complexity: Low-Medium
  • Timeline: 4–6 weeks
  • Key assessment: Ground hazards (people below drone), technical mitigation (geofencing)
  • Typical mitigation: Exclusion zones, operator training, weather limits

Delivery Operations SORA

  • Complexity: High
  • Timeline: 8–12 weeks
  • Key assessment: Ground risk (package falls), air risk (airspace conflict)
  • Typical mitigation: Parachute system, geofencing, detect & avoid, airspace coordination

Event Filming SORA

  • Complexity: Medium-High
  • Timeline: 6–10 weeks
  • Key assessment: Crowd management, contingency planning, emergency procedures
  • Typical mitigation: Exclusion zones, marshals, safety officer, detailed procedures

Night Operations SORA

  • Complexity: Medium
  • Timeline: 6–10 weeks
  • Key assessment: Lighting systems, detect & avoid in darkness, weather risk
  • Typical mitigation: Anti-collision lighting, LIDAR/radar, weather minimums, crew training

FAQ: SORA Risk Assessment UK 2026

🐣 If I operate the exact same flight multiple times, do I need multiple SORAa?

No. One SORA covers repeated identical operations. If you're flying the same route on multiple dates, you only need one approval. Document "multiple flights per week" in your SORA. Different locations or operation types require separate assessments.

🦉 Can I submit a SORA even if I don't have my PfCO yet?

Generally not. The SORA assumes you have a valid PfCO. Complete PfCO certification first, then submit SORA. Some components (crew qualifications) can be in progress, but you must have PfCO before CAA approves the SORA.

🐣 What if the CAA rejects my SORA? Can I appeal?

No formal appeal process, but you can resubmit with additional information addressing CAA's concerns. Contact your local CAA office to understand specific rejection reasons and discuss remediation.

🦉 How often do I need to renew my SORA approval?

Most SORA approvals are valid for 1–3 years. Check your approval letter for the expiry date. If the operation, equipment, or airspace changes significantly, you may need a new SORA even before expiry.

🐣 Is SORA required for indoor operations (shopping malls, warehouses)?

Generally no. Indoor operations in non-congested spaces don't require SORA (building doesn't count as "airspace" in same way). However, notify building management and ensure compliance with local safety procedures.

Master Your SORA Compliance

Developing comprehensive, CAA-acceptable SORAa requires expertise, documentation discipline, and time. MmowW automates the process.

MmowW's SORA Management
  • CAA SORA templates for all operation types
  • Guided risk assessment workflow and calculations
  • Automated hazard identification and risk scoring
  • Mitigation measures library and suggestion engine
  • SORA document generation (CAA-ready format)
  • Approval tracking and renewal reminders

Cost: Just £5.29 per drone per month. Every SORA CAA-approved on first submission.

Last updated: 9 April 2026. This article reflects CAA SORA guidance as of Q2 2026. Always consult official CAA documentation for the latest requirements.