SORA 2.5 Explained for Drone Pilots – Practical Guide
Your Complete Handbook for Safe and Compliant UAS Operations in the Specific Category1. Introduction
Big news for drone pilots flying in the specific category! EASA has updated the rules you use to get your operational authorisations. The new decision, called ED Decision 2025/018/R, brings in SORA 2.5—the latest version of the risk assessment method that helps you show your operation is safe.Why should you care? If you fly beyond the “open category” limits—like BVLOS flights, heavier drones, or near populated areas—you need an operational authorisation. The way you prove your operation is safe is through SORA. The new version makes things clearer, adds some simplifications, and aligns with international best practices.
Official Source:
EASA Agency Decisions
2. Background
What is SORA?
SORA stands for Specific Operations Risk Assessment. It’s a step-by-step process that helps you figure out the risks of your flight and what you need to do to reduce them. You use it when your operation doesn’t fit the “open category” rules and you need permission from your national aviation authority.
Why the update?
The old version, SORA 2.0, has been around for a few years. Pilots and authorities found some parts confusing and sometimes too conservative. JARUS (the international group that develops SORA) created version 2.5 to fix these issues. EASA has now adopted it for Europe, with a few tweaks for EU-specific rules.3. Why This Matters for Pilots
If you fly BVLOS, near populated areas, or with heavier drones, you need an operational authorisation. SORA is how you prove your operation is safe. The new version makes things clearer, adds simplifications, and aligns with international best practices. Visual Aid Suggestion:Infographic: “When Do You Need SORA?”
- ▸Open Category → No SORA
- ▸Specific Category → SORA Required
- ▸Certified Category → Different process
4. What’s New in SORA 2.5
- â–¸Easier templates for applications.
- â–¸Clearer definitions of robustness levels.
- â–¸Removal of EVLOS term (now BVLOS with Airspace Observer).
- â–¸Updated OSOs (Operational Safety Objectives).
- â–¸Better guidance on containment and population density.
Comparison Table:
| Feature | SORA 2.0 | SORA 2.5 |
|---|---|---|
| Cybersecurity | Included | Removed (future framework) |
| EVLOS Term | Present | Replaced by BVLOS + AO |
| OSOs | 21 objectives | Streamlined & clarified |
5. How to Apply for Operational Authorisation
Step 1: Check if your operation is in the specific category
- â–¸Does it exceed open category limits?
- â–¸Does it involve BVLOS or flights near populated areas?
Step 2: Perform SORA
- ▸Use EASA’s IAM HUB tool for calculations.
- â–¸Follow the 10 steps of SORA (explained below).
Step 3: Prepare your Operations Manual
- â–¸Include normal, contingency, and emergency procedures.
- â–¸Add diagrams of flight areas and risk buffers.
Step 4: Submit your application to your NAA
- â–¸Include the risk assessment, compliance matrix, and supporting evidence.
Step by step process
1. Start
2. Check category
3. Perform SORA
4. Prepare Operations Manual
5. Submit
6. Get Authorisation
6. Step-by-Step Guide to SORA
Here are the 10 steps you need to follow:
| Step | What You Do | Visual Aid Suggestion |
|---|---|---|
| 1 | Describe your operation | Diagram of flight area (green = flight geography, yellow = contingency volume, red = ground risk buffer) |
| 2 | Calculate ground risk | Table of iGRC values vs population density |
| 3 | Apply mitigations | Checklist for M1(A), M1(B), M1(C), M2 |
| 4 | Assess air risk | Decision tree for ARC assignment |
| 5 | Apply strategic mitigations | Table of ARC reduction options |
| 6 | Tactical mitigations | Diagram of detect-and-avoid system |
| 7 | Determine SAIL | Matrix linking GRC + ARC → SAIL |
| 8 | Containment requirements | Table of containment robustness levels |
| 9 | OSOs | Checklist of OSOs with robustness levels |
| 10 | Compile safety portfolio | Template for compliance matrix |
7. Practical Tips & Common Mistakes
- ▸Tip: Use EASA’s Specific Category guidance for SORA calculations.
- ▸Tip: Start early—collect design evidence from your manufacturer.
- â–¸Mistake: Forgetting to include contingency procedures in your operations manual.
- ▸Mistake: Using outdated population density maps—check your NAA’s guidance.
8. Templates & Checklists
Application Checklist
- ▸✅ Operations Manual
- ▸✅ Risk Assessment
- ▸✅ Compliance Matrix
- ▸✅ Evidence for OSOs
- ▸✅ Flight area diagrams (.kml files recommended)
9. Transition Period Advice
You can still use SORA 2.0 for a few months, but switching to 2.5 is recommended.- â–¸Member States may allow SORA 2.0 for up to 6 months.
- â–¸Authorisations under SORA 2.0 remain valid for 2 years.
10. FAQs
Q: Do I need a DVR for my drone? A: Only if your operation is SAIL IV or higher. Q: What happens if my GRC > 7 ? A: Your operation falls into the certified category—different rules apply.11. Useful Links
- â–¸
- â–¸
- â–¸
EASA Regulatory Compliance Notice
This content is for educational purposes only and is based on EASA regulations current at the time of generation.
Always consult the official EASA documentation and your local aviation authorities for the most current regulations and legal compliance requirements before operating any UAS.