BVLOS Drone Operations Netherlands: SORA 2.5 & ILT Pathways

Beyond Visual Line of Sight (BVLOS) operations are the highest value in drone work—autonomous mapping over large areas, infrastructure inspection at distance, delivery routes. But they're also the most heavily regulated. The Netherlands ILT requires an Operational Authority (OA) for BVLOS, and as of April 1 2026, the new SORA 2.5 standard applies. This guide covers the SORA 2.5 transition, OA approval, and how to go from planning to approved BVLOS flights.

🐣

Piyo 🐣 (Beginner Pilot)

Piyo (Regulatory Expert): "SORA 2.5 is live Apr 1 2026. Operators still using old SORA 1–2 standards lose their approvals. Plan the transition now."

:::

🦉

Poppo 🦉 (Compliance Expert)

Poppo (Compliance Officer): "BVLOS isn't just longer-range flying—it's autonomous risk management. The ILT doesn't approve operations; they approve your risk framework."

What Is BVLOS? (Beyond Visual Line of Sight)

VLOS (Visual Line of Sight): Operator sees the aircraft at all times. Max distance ~500m. BVLOS (Beyond Visual Line of Sight): Operator relies on automated systems (GPS, RTK, cameras) to maintain situational awareness. Distance: 500m to several kilometers. BVLOS enables:

Autonomous surveying (orthomosaic mapping of large properties/farms)
Infrastructure inspection (power lines, pipelines, bridges—distances >1 km)
Utility construction (site progress documentation from altitude)
Delivery operations (package routing from depot to customer address)
Agricultural monitoring (crop health, irrigation assessment across 100+ hectares)

BVLOS requires: ILT Operational Authority (OA) approval of your risk assessment and operational procedures.

🐮

Moo 🐮 (MmowW Founder)

Moo (Drone Operator): "So I can't just extend my VLOS operation to 1 km?"

:::

🐣

Piyo 🐣 (Beginner Pilot)

Piyo: "No. That's illegal without OA. The ILT enforces airspace rules. Unauthorized BVLOS = €20,000+ fine + aircraft confiscation."

SORA 2.5: The New Standard (Apr 1 2026)

SORA = Specific Operations Risk Assessment. It's a framework for assessing BVLOS risk and proving you've mitigated hazards.

SORA Levels Explained

SORA Level	Risk Profile	ILT Approval	Example Operation
SORA 1	Very low risk (isolated area, no people/property)	Simple notification	Surveying remote farm, zero population)
SORA 2	Low-to-medium risk (occasional people/property below)	Standard OA approval	Infrastructure inspection near houses, populated areas
SORA 2.5 (NEW Apr 2026)	Medium risk with enhanced safety measures	Enhanced OA approval + cyber requirements	Urban corridor inspection, delivery operations, critical infrastructure
SORA 3	High risk (frequent people/property exposure)	Complex OA, high insurance (€1M+)	Emergency response (wildfire, disaster)

SORA 2.5 Deadline: What's Changing?

Old SORA (Pre-Apr 2026):

Accepted SORA 1–2 approvals
Minimal cyber security requirements
Basic risk documentation sufficient
Insurance: €500k liability standard

New SORA 2.5 (Apr 1 2026 onwards):

Old SORA 1–2 approvals become invalid for new operations
Cyber security assessment mandatory
Risk documentation more rigorous (hazard identification, mitigation proof)
Insurance: €750k–€1M liability (increased)
Geofencing & lost-link recovery procedures mandatory
Real-time monitoring & compliance log mandatory

What this means:

If you have an old OA, you're not automatically revoked, but renewals require SORA 2.5 compliance
New BVLOS approvals (after Apr 1) must use SORA 2.5 framework
Existing SORA 1–2 operators can continue until renewal, but must transition to SORA 2.5 by Dec 31 2026

🦉

Poppo 🦉 (Compliance Expert)

Poppo's Note: SORA 2.5 is ILT's response to increased drone accidents. More operations = higher risk = stricter approval. Start your upgrade now; don't wait until December.

ILT BVLOS Approval Process (4–8 Weeks)

Step 1: Pre-Application (Week 1–2)

Contact ILT airspace team (info@ilta.nl):

Describe planned operation (location, distance, frequency)
Ask which SORA level applies
Request airspace clearance pre-approval (some areas require pre-coordination with military/ATC)

Example pre-app email:

`` Subject: BVLOS Pre-Application Inquiry Dear ILT, We propose BVLOS surveying operations in [area name], conducted:



Aircraft: DJI M350 (max 10 kg)
Distance: up to 2 km from operator
Altitude: 150m AGL maximum
Frequency: 2–3 times/month
Risk profile: SORA 2 (occasional residential structures below route)
 Can you advise on approval pathway and airspace constraints? Best regards, [Your company]

ILT response: Usually within 5 business days, indicating SORA level & preliminary airspace approval.

Step 2: OA Application Submission (Week 2–3)

Prepare full OA application package:

Cover letter (1 page)

Your company details
Proposed operation scope
Timeline for approval

Operations Manual (30–50 pages, see previous article)

Comprehensive BVLOS procedures
Risk Register with SORA 2.5 mitigations
Emergency procedures (lost link, GPS failure, system failure)
Crew training plan

SORA 2.5 Risk Assessment (specific to your operation)

Hazard identification (aircraft failure, GPS loss, obstacle collision, cybersecurity breach)
Mitigation measures (redundancy, procedures, training)
Residual risk acceptance statement
Safety performance targets

Cyber Security Plan (NEW for SORA 2.5)

GPS spoofing detection & response
Aircraft command encryption
Operator credential management (password, 2FA)
Data protection (flight logs, telemetry storage)
Incident reporting (cyber incident → ILT notification within 24 hours)

Insurance Certificate

Proof of €750k–€1M liability coverage
SORA 2.5 explicitly listed as covered operation

Crew Credentials

Remote pilot certificates (A2 minimum for BVLOS)
Medical certificates
BVLOS-specific training records

Aircraft Specifications

Weight, payload, endurance, max speed
Manufacturer BVLOS recommendations
Maintenance schedule

Submit via ILT online portal (www.ilta.nl).

Step 3: ILT Review (Week 3–6)

ILT reviews for:

SORA 2.5 compliance (hazard identification complete?)
Operations Manual quality (procedures detailed? Crew trained?)
Insurance adequacy
Risk assessment credibility (mitigations realistic? Based on evidence?)
Cyber security plan (GPS spoofing detection? Command encryption?)

Possible outcomes:

Approved: OA certificate issued; operations begin immediately
Approved with conditions: OA issued; specific restrictions apply (e.g., "Daytime only," "Max 50 flights/month," "No operations within 500m of residential areas")
Needs revision: ILT requests modifications; resubmit revised sections (add 2–4 weeks)
Rejected: Serious gaps; major revision + reapplication required (start over)

Step 4: OA Granted (Week 6–8)

Upon approval:

ILT issues OA certificate (valid 3 years)
Operations can commence immediately
Annual compliance review required
Incident reporting mandatory

SORA 2.5 Checklist: Key Requirements

[ ] SORA 2.5 risk assessment completed (minimum 10 hazards identified)
[ ] Mitigation strategies documented & evidence-based (e.g., "GPS spoofing detection enabled via DJI OcuSync encryption")
[ ] Cyber security plan addresses GPS spoofing, command encryption, credential management
[ ] Emergency procedures tested & documented (GPS loss recovery, lost link, battery warning)
[ ] Operations Manual includes SORA 2.5 appendix
[ ] Crew trained on SORA 2.5 requirements (minimum 8 hours additional training)
[ ] Insurance updated to €750k–€1M liability with SORA 2.5 endorsement
[ ] Geofencing programmed (aircraft cannot fly beyond airspace bounds)
[ ] Lost-link recovery procedure defined (automatic land, RTH, operator intervention)
[ ] Real-time monitoring system in place (ground crew able to view aircraft telemetry live)
[ ] Compliance log template prepared (flight-by-flight documentation of safety checks)
[ ] Incident escalation protocol documented (cyber incidents → ILT within 24 hours)

🦉

Poppo 🦉 (Compliance Expert)

Poppo's Note: SORA 2.5 isn't about paperwork—it's about proving your operation won't fail catastrophically. Every hazard needs a credible mitigation. "We hope GPS doesn't fail" isn't acceptable. "GPS spoofing detected by DJI system; operator trained on manual recovery; emergency landing protocol programmed" is.

Common BVLOS Scenarios & SORA Levels

Operation	Example	SORA Level	Approval Timeline
Remote farm surveying	100-hectare property, no people on ground	SORA 1	2–3 weeks
Power line inspection	50 km corridor, occasional houses below	SORA 2.5	4–6 weeks
Urban delivery	Residential area, frequent buildings/people	SORA 3	8–12 weeks (complex)
Construction monitoring	Site over populated area, daily flights	SORA 2.5	4–6 weeks
Airport boundary inspection	Perimeter check, nearby controlled airspace	SORA 2.5	6–8 weeks

---

FAQ: BVLOS & SORA 2.5

Q: Can we keep flying under old SORA 1–2 standards until Dec 2026?

A: Yes, if your OA is already approved. But new SORA 1–2 applications are rejected. Existing operations can continue until OA renewal.

Q: What if GPS signal is lost during a BVLOS flight?

A: You must have a defined response: return-to-home (RTH), climb above obstacles, or emergency landing. This must be programmed and tested before approval.

Q: How often do we need to report incidents to ILT?

A: BVLOS incidents within 24 hours. Cyber incidents (GPS spoofing, data breach) within 24 hours. Minor operational deviations (slight airspace crossing) within 7 days.

Q: Can we operate BVLOS near Schiphol with ILT approval?

A: No. Schiphol has a 5 km no-drone radius regardless of OA approval. Operations outside this radius with ILT OA are permitted.

Q: Does MmowW help with SORA 2.5 compliance?

Action Plan: BVLOS Approval Now

This month:

Contact ILT for pre-application guidance on your specific operation
Determine SORA level (ask ILT directly)
Identify any airspace coordination requirements

Next 4 weeks:

Draft Operations Manual with SORA 2.5 risk assessment
Develop cyber security plan
Update insurance to SORA 2.5 coverage
Train crew on SORA 2.5 requirements

Week 5:

Finalize all documentation
Conduct internal audit (MmowW checklist)
Submit OA application to ILT

Weeks 6–8:

Respond to ILT questions (expect 1–2 rounds of clarification)
Receive OA certificate
Commence BVLOS operations

MmowW NL: €6.08/drone/month | SORA 2.5 risk templates | OA documentation tools | Real-time compliance logging included

📝 Update History

2026-04-09 — Initial publication