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:
  1. Contact ILT for pre-application guidance on your specific operation
  2. Determine SORA level (ask ILT directly)
  3. Identify any airspace coordination requirements

Next 4 weeks:
  1. Draft Operations Manual with SORA 2.5 risk assessment
  2. Develop cyber security plan
  3. Update insurance to SORA 2.5 coverage
  4. Train crew on SORA 2.5 requirements

Week 5:
  1. Finalize all documentation
  2. Conduct internal audit (MmowW checklist)
  3. Submit OA application to ILT

Weeks 6–8:
  1. Respond to ILT questions (expect 1–2 rounds of clarification)
  2. Receive OA certificate
  3. Commence BVLOS operations

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