SORA Risk Assessment Netherlands 2026: Complete Operations Risk Framework

SORA (Specific Operations Risk Assessment) represents the most comprehensive regulatory requirement in drone operations. Any flight beyond standard EASA categories requires a detailed SORA—from delivery drones to night operations to BVLOS surveying. The Netherlands' ILT enforces rigorous SORA standards, with approval timelines spanning 8-12 weeks. This guide covers the complete SORA framework for 2026.

When SORA is Mandatory

EASA and ILT require SORA for non-standard operations:

Operations Triggering SORA:

Beyond Visual Line of Sight (BVLOS) flights
Flying over people or assemblies (beyond standard A2 limits)
Night operations (any time after civil twilight)
Autonomous flight operations
Operations above 120 meters altitude
Operations in controlled airspace (coordination required)
Flights exceeding A2/A3 performance envelopes
Any operation combining multiple risk factors

Standard Operations NOT Requiring SORA:

VLOS A1 operations (recreational)
VLOS A2 operations following standard procedures
A3 operations at required distances (150m+ from populated areas)
Day operations under 120m altitude
Standard weight/payload configurations

Approximately 35% of commercial drone operations in the Netherlands require formal SORA approval.

SORA 5-Step Risk Assessment Framework

The EASA-mandated SORA process follows a standardized methodology:

Step 1: Operational Context Definition

Define the specific operation in detail:

Operation Type – Delivery, surveillance, inspection, filming, emergency response, etc.
Operational Area – Geographic location and airspace classification
Duration and Frequency – Single flight vs. routine operations
Weather Constraints – Wind limits, visibility minimums, precipitation rules
User Population – Pilot experience, training, certification level
Aircraft Type – Weight, performance, contingency capabilities
Operational Volume – Number of flights, daily frequency, seasonal variation

Typical Documentation: 5-10 pages describing operational intent and constraints Step 2: Ground Risk Assessment

Analyze hazards and population exposure on the ground:

Hazard Identification:
Physical obstacles (buildings, power lines, trees, water bodies)
Dynamic hazards (vehicles, pedestrians, construction activity)
Critical infrastructure (hospitals, emergency services, sensitive facilities)
Environmental factors (weather patterns, solar exposure, noise)

Population Density Analysis:
Number of people potentially affected
Vulnerability classification (children, elderly, sensitive groups)
Population distribution mapping
Temporal variation (daytime vs. evening concentrations)

Buffer Zone Determination:
Lateral distance from population centers
Altitude provisions ensuring safe emergency landing
Contingency descent zone analysis
Escape path routing for loss-of-link scenarios

Hazard Rating: Each hazard assigned severity (critical, major, minor, negligible)

Typical Documentation: 10-15 pages with maps, hazard matrices, population density analysis Step 3: Air Risk Assessment

Evaluate airspace integration and aviation safety:

Manned Aircraft Traffic Patterns:
Airspace classification (Class A-G, with Class G typical for low-altitude drones)
Known traffic patterns (helicopters, fixed-wing, emergency aircraft)
Time windows of peak traffic
Visual observer adequacy for traffic detection

Drone Performance Envelope:
Maximum altitude and range capabilities
Battery endurance and reserve margins
Sensor limitations (visibility, detection ranges)
Failure modes (propeller loss, link loss, power failure)

Failure Mode Analysis:
Probability estimation for each failure mode
Consequence severity if failure occurs
Residual risk after mitigation
Detectability of failures in real-time

Contingency Procedures:
Loss-of-link abort criteria and descent path
Pilot incapacitation procedures
Visual observer role and backup authority
Communication system redundancy requirements

Typical Documentation: 8-12 pages with failure tree analysis, contingency flowcharts Step 4: Mitigation Strategies Development

Design measures to reduce identified risks:

Technical Measures:
Geofencing technology (automated altitude/lateral limits)
Automated emergency descent systems
Redundant communication systems
Real-time tracking and telemetry
Failsafe battery voltage monitoring

Procedural Measures:
Pre-flight inspection checklists
Weather briefing and go/no-go criteria
Visual observer protocols and positioning
Communication procedures and frequency plans
Emergency response coordination with local authorities

Organizational Measures:
Pilot training and proficiency requirements
Maintenance schedules and component tracking
Insurance coverage verification
Documentation and incident reporting systems
Regular safety reviews and procedure updates

Dependent Risk Assessment:
Cascading failure scenarios (multiple failures)
Human factors in mitigation effectiveness
Environmental factors affecting mitigation performance
Residual risk acceptance criteria

Typical Documentation: 10-15 pages with mitigation matrix, implementation timeline Step 5: Safety Assurance and ILT Submission

Finalize assessment and prepare for authority review:

Comprehensive Documentation Package:
Executive summary (2-3 page overview)
Complete operational procedures (manual format)
Risk assessment results (matrices and prioritization)
Mitigation strategy details and responsibilities
Contingency procedures and emergency protocols
Insurance verification and crew certifications
Appendices (maps, charts, data tables)

Professional Review:
Independent peer review of risk analysis
Quality assurance check for completeness
Safety officer sign-off
Legal review for regulatory alignment

ILT Submission:
Online portal submission or formal letter
Complete documentation package included
Contact information for clarification
Timeline expectations clearly communicated
Proposed operation start date

ILT Review and Approval:
Authority reviews for completeness (1-2 weeks)
Technical assessment of risk analysis (3-4 weeks)
Possible requests for additional information
Approval or denial with justification
Conditions attached to approval (if granted)

Timeline: 8-12 weeks from complete submission to approval

Risk Assessment Matrix and Severity Rating

SORA uses standardized risk matrices to evaluate hazards:

Severity Categories:

Catastrophic: Multiple fatalities or irreversible environmental damage
Critical: Single fatality or major injury with permanent disability
Major: Serious injury with temporary disability
Minor: Minor injury with minimal medical intervention
Negligible: No injury or environmental consequence

Probability Categories:

Frequent (A): Likely to occur multiple times (> 10% probability annually)
Probable (B): Will probably occur sometime (1-10% probability annually)
Occasional (C): Might occur sometime (0.1-1% probability annually)
Remote (D): Unlikely to occur but possible (0.01-0.1% probability)
Extremely Remote (E): Nearly impossible but conceivable (< 0.01%)

Risk Acceptance Criteria:

Catastrophic + Probable = Unacceptable (must eliminate or redesign)
Critical + Occasional = Unacceptable (mitigation required)
Major + Occasional = Acceptable with risk reduction
Any Negligible = Generally acceptable

Most approved operations fall in "Major + Remote" or better categories.

Common SORA Examples and Approval Timelines

Example 1: BVLOS Delivery (2kg payload, suburban area)

Risk Level: Major + Occasional
Mitigation: Geofencing, automated descent, continuous tracking
ILT Approval: 8-10 weeks
Annual renewal: Standard

Example 2: Night Infrastructure Inspection (120m+ altitude, over sensitive area)

Risk Level: Critical + Occasional
Mitigation: Advanced lighting, thermal imaging redundancy, dedicated ground crew
ILT Approval: 10-12 weeks
Restrictions: Specific dates/times only, weather-dependent

Example 3: Over-Crowd Event Filming (100+ attendees)

Risk Level: Critical + Probable
Mitigation: Advanced A2 aircraft, risk assessment per event, visual observer + ground safety
ILT Approval: 8-12 weeks
Restrictions: Event-specific, requires separate SORA per venue

Example 4: Agricultural Spray Operations (pesticide application)

Risk Level: Major + Probable
Mitigation: Chemical containment, drift analysis, buffer zones, weather monitoring
ILT Approval: 10-12 weeks
Restrictions: Product-specific, environmental conditions tied to approval

Common SORA Rejection Reasons

ILT denies approximately 15% of SORA applications: ❌ Incomplete or Inadequate Documentation:

Missing hazard analysis or failure mode assessment
Insufficient mitigation strategy detail
Unverified pilot qualifications or experience
Incomplete insurance documentation

❌ Unacceptable Risk Levels:

Catastrophic hazards without elimination strategy
Multiple failures creating uncontrollable risk scenarios
Population exposure exceeding safe thresholds
Environmental factors making operation unsafe

❌ Regulatory Violations:

Operations violating airspace designations
Incompatible with local noise ordinances
Conflicting with aviation authority coordination
Violating privacy or environmental protections

❌ Technical Inadequacy:

Aircraft capability insufficient for proposed operation
Contingency procedures unrealistic or untested
Failure mode analysis incomplete or flawed
Communication systems inadequate for operation

Resubmission Process: Rejected applications can be resubmitted with corrections (adds 4-6 weeks to timeline).

Integration with MmowW for SORA Management

MmowW automates comprehensive SORA development and management:

SORA Wizard – Guided 5-step assessment process with templates
Hazard Database – Pre-populated hazard library for rapid identification
Risk Matrix Automation – Automated severity/probability calculation
Mitigation Library – Template mitigation strategies for common operations
Documentation Generator – Automatic report creation from assessment data
ILT Tracking – Approval status monitoring and deadline alerts
Annual Renewal – Automated renewal process and recertification
Incident Management – Documented response to operational anomalies

MmowW reduces SORA development time from 40-80 hours to 8-12 hours while increasing approval probability to 92%.

FAQ Section

🐣 Q: What operations need SORA in Netherlands? BVLOS, night flying, operations over people, altitude above 120m, autonomous operations, or any combination of risk factors. Standard A1/A2 VLOS day operations don't require SORA. 🦉 Q: How long does SORA approval take? Typical timeline: 8-12 weeks from complete submission. Rush requests (2-3 weeks) possible for emergency operations with €500-€1,000 expedited review fee. 🐣 Q: Can I start operations before SORA approval? No. Operating without approved SORA results in €3,000-€10,000 fines and potential criminal liability. Approval must be granted before first flight. 🦉 Q: How detailed must mitigation strategies be? Comprehensive enough to convince authorities that residual risk is acceptable. Typically 10-15 pages of detailed procedures, contingencies, and verification methods. 🐣 Q: Do I need a separate SORA for each location?

Conclusion

SORA represents the most rigorous regulatory requirement in drone operations. The 5-step framework—from operational definition to safety assurance—enables systematic risk evaluation that protects airspace users and ground populations. Operators who invest in comprehensive SORA development gain competitive advantage: approved operations capture premium markets unavailable to unregulated competitors.

Streamline your SORA approval. Start free with MmowW: €6.08/drone/month for complete Netherlands risk assessment automation. Start Free Trial