SORA 2.5 Risk Assessment Netherlands 2026: ILT Application Guide

SORA 2.5 (Specific Operations Risk Assessment) is the ILT's structured process for approving drone operations beyond standard rules. If your operation is too complex for simple VLOS flying, SORA 2.5 is your path to ILT approval. This guide explains the entire framework.

What is SORA 2.5?

SORA = Specific Operations Risk Assessment Scope: Applies to BVLOS operations and/or operations exceeding normal category rules Key principle: Risk-based approach (not one-size-fits-all)

SORA 2.5 vs. Other Approval Paths

Path	Use Case	Timeline	Complexity
Open Category (no approval needed)	VLOS only, simple operations	0 weeks	Minimal
Operator Approval (OA)	Commercial operator, multiple aircraft	8-16 weeks	High (standardized procedures for all operations)
SORA 2.5 (per-project)	One-time complex operation	4-8 weeks	Medium (customized risk assessment per operation)
SORA 3 (populated areas)	Flying over people/crowds	12-16 weeks	Very high (extremely restrictive mitigations)

Typical path for Dutch operators:

Starting: SORA 2.5 per-project (low cost, faster approval)
Scaling: Transition to Operator Approval (OA) when 5+ projects/year planned

SORA 2.5 Framework (Simplified)

Step 1: Define the Operation

Answer these questions clearly:

What aircraft? (specific model, weight, capabilities)
What location? (GPS coordinates, map)
What activity? (inspection, delivery, surveying, etc.)
How many flights? (one-time or repeated)
Who's involved? (pilot, observers, ground crew)
When? (specific dates, times, duration)

Step 2: Identify Hazards

Hazard = potential threat to safety

Examples:

People on ground (residential area, park, farm)
Obstacles (power lines, buildings, trees)
Weather (wind, precipitation, visibility)
Airspace (helicopter routes, airport proximity)
Equipment failure (motor loss, battery failure)
Cyber security (hacking, signal interference)

Step 3: Assess Risk

For each hazard, evaluate:

Severity: How bad if it happens? (Minor injury vs. fatality)
Likelihood: How probable is it? (Rare vs. very likely)
Combined risk: (Severity × Likelihood = Risk Level)

Risk matrix:

Severity / Likelihood	Rare	Unlikely	Possible	Likely	Very Likely
Minor	Low	Low	Low	Medium	Medium
Moderate	Low	Low	Medium	Medium	High
Serious	Low	Medium	Medium	High	High
Severe	Medium	Medium	High	High	Unacceptable
Catastrophic	Medium	High	High	Unacceptable	Unacceptable

ILT approval rule:

Step 4: Propose Mitigations

Mitigation = control to reduce risk

Types of mitigations:

Type	Example	Effectiveness
Design control	Aircraft with parachute system	Very high
Procedural control	Visual observer maintains watch	High
Equipment	Real-time tracking, geofencing	Medium-High
Operational	Flight only during daylight	Medium

Step 5: Re-evaluate Risk After Mitigations

Does proposed mitigation reduce risk to acceptable level?

If yes → Proceed to ILT submission
If no → Add more mitigations or reject operation

Real-World SORA 2.5 Example: Wind Turbine Inspection

Scenario:

Step 1: Define Operation

Parameter	Value
Aircraft	DJI M300 RTK (2.7kg)
Location	Friesland, Netherlands (GPS: 53.15N, 6.25E)
Activity	Blade inspection via close-proximity flight
Flights	4 flights per turbine (8 turbines = 32 flights total)
Crew	1 pilot + 1 visual observer
Schedule	2-day operation, 6am-4pm

Step 2: Identify Hazards

People on ground – 3 farmhouses within 500m
Blade collision – Moving turbine blades (risk if hovering)
Weather – Wind gusts (turbines = wind amplification)
Power lines – 3 power lines crossing site
GPS denial – Magnetic interference from turbine structure
Equipment failure – Battery loss, motor failure mid-flight

Step 3: Assess Risk (Before Mitigations)

Hazard	Severity	Likelihood	Risk
People hit by drone	Serious	Unlikely (buffer zone)	Medium
Blade collision	Catastrophic	Rare (daylight-only)	Medium
Wind gust takedown	Severe	Possible (wind site)	High ⚠️
Power line strike	Severe	Possible (proximity)	High ⚠️
GPS loss (crashes)	Severe	Possible (turbine field)	High ⚠️
Battery failure (drops)	Serious	Unlikely	Medium

Status:

Step 4: Propose Mitigations

Hazard	Mitigation	Effectiveness
People	100m buffer zone + local notification	Reduces to: Low
Blade collision	Daylight only, turbine off inspection (pre-scheduled shutdown)	Reduces to: Low
Wind gusts	Wind speed limit: <8 m/s (automatic cancel if exceeded)	Reduces to: Low
Power lines	Flight altitude limit: <80m (below power line height at site)	Reduces to: Low
GPS loss	Use compass navigation + LOS backup (if GPS fails, VO takes direct control)	Reduces to: Medium
Battery loss	Dual battery system, plus parachute deployment if both fail	Reduces to: Low

Step 5: Re-evaluate Risk (After Mitigations)

Hazard	Risk After Mitigation
People hit	Low ✓
Blade collision	Low ✓
Wind gust	Low ✓
Power line strike	Low ✓
GPS loss	Medium (acceptable with procedures) ✓
Battery failure	Low ✓

Conclusion:

Step 6: Document in SORA 2.5 Application

Operational Manual sections required:

Wind turbine inspection procedures

Pre-flight shutdown coordination (schedule turbine off-time with operator)
Flight path (specific altitude, distance from blades)
Emergency procedures (lost signal recovery, blade restart)
Weather limits (wind <8 m/s, visibility >2 km)

Crew qualifications

Pilot: EASA Part-FCL A + wind energy training (20+ hours wind turbine inspections)
Observer: Wind turbine safety certification (familiar with equipment)

Risk mitigation verification

Pre-flight checklist (GPS calibration, compass verification, battery test)
Real-time monitoring (wind speed anemometer at site)
Post-flight inspection (parachute system integrity, battery health)

SORA 2.5 Application Process

Timeline: 4-8 Weeks

Phase	Duration	Activities
Preparation	1-2 weeks	Write operational manual, risk assessment, crew training
Submission	—	Submit to ILT (online portal)
ILT Review	2-3 weeks	ILT reviews, requests clarifications/revisions
Resubmission	1 week	Address ILT feedback, resubmit
Approval/Test	1-2 weeks	ILT grants conditional approval, schedules test flights
Test Flights	1 week	Operator conducts supervised test flights (ILT observer present)
Final Approval	—	ILT issues Special Flight Authorization (SFA) certificate

ILT Feedback Rounds (Typical)

Round 1 Feedback (common issues):

Risk assessment incomplete (missing hazard)
Mitigations insufficient (proposed controls not stringent enough)
Crew qualifications unclear (training logs needed)
Operational procedures vague (need specific step-by-step procedures)

Round 2 Resubmission:

Address feedback, expand operational manual
Provide additional crew training documentation
Clarify specific risk controls

Round 3 Approval (or conditional):

Most applications approved by round 2
Conditional approval: "Approved with conditions" (e.g., "Turbine shutdown mandatory, approved for quarterly inspections only")

Common SORA 2.5 Applications in Netherlands

Use Case	Timeline	Complexity	Cost
BVLOS surveying	6-8 weeks	High (large areas, land navigation)	€4,000-8,000
Agricultural spraying	4-6 weeks	Medium (pesticide handling clear regulations)	€3,000-6,000
Infrastructure inspection	4-6 weeks	Medium (proximity to structures)	€3,000-5,000
Event filming	2-4 weeks	Low-Medium (people buffer zones established)	€2,000-4,000
Delivery trials	8-12 weeks	Very high (package safety, BVLOS, people)	€5,000-15,000

Piyo's Beginner Path 🐣

You have a one-time complex operation (not recurring).

Hire SORA 2.5 consultant – Professional firm specializes in ILT applications (€2,000-5,000)
Provide operation details – Timeline, location, aircraft, crew, risks
Consultant writes manual + risk assessment – (3-4 weeks)
Submit to ILT – Via consultant
Wait for feedback – (2-3 weeks)
Implement revisions – (1 week)
Receive approval + conduct test flights – (1-2 weeks)
Execute operation – Special Flight Authorization in hand

Total cost:

Poppo's Expert Path 🦉

You're scaling with multiple projects/year (pursue Operator Approval instead).

Why?

One-time cost: €5,000-15,000 (comprehensive operational manual)
Per-project cost: €0 (included in OA)
If doing >5 projects/year: OA pays for itself

OA development timeline:

OA approval scope:

Once OA approved:

1-week operational briefing (not full SORA re-assessment)
Site-specific risk assessment (short form, not full manual)
Crew confirmation (same team OK, no retraining if recent)

Common Risk Assessment Mistakes

❌ Mistake 1: Identifying Hazards Incorrectly

Wrong:

Right:

❌ Mistake 2: Over-relying on Single Mitigation

Wrong:

Right:

❌ Mistake 3: Skipping Crew Training Documentation

Wrong:

Right:

❌ Mistake 4: Vague Emergency Procedures

Wrong:

Risk Assessment Templates & Tools

Tool	Cost	Usefulness
ILT SORA 2.5 Form (official)	Free	Required (baseline)
Risk Matrix Template	Free	Helpful (visual)
Operational Manual Template	€500-2,000	High (saves writing time)
Professional SORA Consultant	€2,000-8,000	Very high (faster approval)

Penalties for Inaccurate Risk Assessment

Violation	Fine	Notes
Understating risks (approval granted on false assessment)	€15,000-75,000	If incident occurs, criminal prosecution likely
Operating outside approved envelope (e.g., flying in higher wind than approved)	€10,000-40,000	Regulatory violation
False crew qualifications (claiming training not completed)	€10,000-30,000	Fraud + safety violation

Key Resources

ILT SORA 2.5 Guidance – https://www.ilta.nl/en/sora-operations (comprehensive, detailed)
Risk Matrix Framework – https://www.easa.europa.eu (EASA special conditions, helpful examples)
Dutch Risk Assessment Standards – https://www.nen.nl (technical guidance, ISO 31000)

What MmowW Does for You

MmowW streamlines SORA 2.5 documentation:

✅ Risk matrix templates – Hazard identification, mitigation tracking ✅ Operational manual templates – Pre-formatted sections (customizable) ✅ Crew tracking – Qualifications, training records, certification dates ✅ Weather limits – Auto-calculated go/no-go criteria per operation ✅ Test flight logging – Automatic documentation for ILT submission ✅ Post-approval management – Track SFA validity, renewal reminders

Cost:

FAQ

Q: Can I get SORA 2.5 approval without a consultant?

A: Yes, technically. However, first-time approval without consultant: 50-70% rejection rate (ILT feedback loops, delays). Consultant investment (€2,000-5,000) usually saves time (faster approval) and money (fewer feedback rounds).

Q: How many test flights does ILT require?

A: Typically 2-5 supervised test flights (depending on operation complexity). Budget 1-2 weeks for test flight scheduling and execution.

Q: Can I use SORA 2.5 approval from another EU country in Netherlands?

A: No. ILT approvals are Netherlands-specific. However, your operational manual from another EU country provides a template (speeds up ILT application if similar operation).

Q: What happens if conditions change after SORA 2.5 approval?

A: Inform ILT immediately. Example: Wind turbine location changes, or crew member leaves company. Depending on change severity: approval may be suspended pending amendment.

Q: Is SORA 2.5 approval valid internationally?

A: No. SORA 2.5 issued by ILT is valid in Netherlands only. To operate in Germany/France/etc., you need approval from that country's authority.

Q: How often must I renew SORA 2.5 approval?

Last updated:

Next review:

Contact MmowW for SORA 2.5 consulting.