SORA (Specific Operations Risk Assessment) is the pathway to advanced drone operations in Sweden that exceed open-category restrictions. Whether operating beyond-line-of-sight (BVLOS), over populated areas, or in sensitive airspace, Transportstyrelsen requires comprehensive SORA documentation. This guide covers SORA methodology, assessment frameworks, and approval processes for 2026.
What is SORA?
SORA is the regulatory framework under EASA EU 2019/947 that allows operators to conduct drone flights in complex scenarios with demonstrated risk mitigation:
Core principle: "Acceptable risk level" achieved through proven safety measures, not prohibition. SORA fundamentals:- Comprehensive risk analysis demonstrating hazards and mitigations
- Evidence that acceptable risk level ("Negligible Risk" threshold) achieved
- Regulatory approval valid 12-24 months (renewable with operational data)
- More flexible than open-category but requires professional rigor
EASA Risk Assessment Methodology
Transportstyrelsen requires adherence to EASA operational risk assessment (ORA) principles:
Step 1: Operational Scenario Definition
Operators must clearly define the mission:
Required elements:- Objective: What is the flight operation intended to accomplish?
- Geographical scope: Where will flights occur? (maps, coordinates)
- Temporal scope: When will flights occur? (seasons, hours of operation)
- Flight characteristics: Altitude, speed, duration, payload
- Environmental context: Urban/rural, population density, airspace classification
- Regulatory context: Any special permits/approvals required
"Autonomous delivery flights of 2 kg parcels across Stockholm suburban zones (Nacka, Tyresö districts) during daylight hours (06:00-18:00) at altitude 20-50 meters using Class 2 drones with Remote ID and parachute systems."
Step 2: Hazard Identification
Identify all potential failure modes and hazards:
Technical hazards:- Loss of GPS/navigation
- Power system failure (propeller malfunction)
- Communication link loss (remote pilot signal dropout)
- Sensor failure (collision avoidance system malfunction)
- Payload release (unintended cargo drop)
- Collision with obstacles (trees, buildings, power lines)
- Adverse weather (wind gust, precipitation, visibility loss)
- Airspace intrusion (manned aircraft proximity)
- Bird strikes or wildlife interaction
- Unforeseen obstacles in flight path
- Operator fatigue or loss of attention
- Inadequate pilot training for mission type
- Communication failure with ground personnel
- Inadequate safety procedures or contingencies
- Inadequate maintenance or system verification
Step 3: Risk Impact Assessment
For each hazard, assess consequence severity:
Severity classification:- Catastrophic: Fatality or multiple serious injuries
- Hazardous: Serious injury or significant property damage
- Major: Injury or moderate property damage
- Minor: Light injury or minimal property damage
- Negligible: No injury or damage
Step 4: Probability Estimation
Estimate likelihood of hazard occurrence:
Probability classification:- Frequent: >10% likelihood per flight (unacceptable—requires mitigation)
- Occasional: 1-10% likelihood per flight (requires mitigation)
- Remote: 0.1-1% likelihood per flight (acceptable with mitigation)
- Extremely Remote: 0.01-0.1% likelihood per flight (acceptable)
- Negligible: <0.01% likelihood per flight (acceptable—no special mitigation)
Step 5: Risk Matrix Evaluation
Map impact × probability to identify overall risk level:
Risk acceptance threshold (Transportstyrelsen definition):- Acceptable: Negligible risk (impact × probability <10^-7 per flight hour)
- Conditional: Acceptable with proven mitigation measures in place
- Unacceptable: Risk exceeds threshold even with proposed mitigations (redesign required)
Step 6: Mitigation Measure Documentation
For each unmitigated risk, propose and evaluate mitigations:
Mitigation categories:- Design mitigations: Equipment changes (parachute system, redundant sensors)
- Operational mitigations: Procedural safeguards (operator training, geofencing)
- Administrative mitigations: Documentation, insurance, emergency response plans
- Hardware redundancy: Backup systems (dual navigation, emergency power)
SORA Categories Based on Operation Type
Transportstyrelsen groups SORA operations into complexity tiers:
SORA Category 1: Low-Complexity Operations
Examples:- BVLOS flights in rural areas (no population)
- Delivery flights on approved corridors
- Agricultural spraying on private land
- Infrastructure inspection (bridges, power lines)
SORA Category 2: Medium-Complexity Operations
Examples:- BVLOS flights in semi-urban areas (scattered population)
- Delivery flights in suburban zones
- Over-people operations (crowds 100-500)
- Night operations with full autonomy
- Multi-drone coordinated operations
SORA Category 3: High-Complexity Operations
Examples:- BVLOS flights in dense urban areas (Stockholm/Gothenburg)
- Over-people operations (crowds 500+, festivals/stadiums)
- Night operations over populated areas
- Autonomous swarm operations
- Operations near critical infrastructure
SORA Documentation Requirements
Transportstyrelsen requires standardized documentation formats:
SORA Documentation Package Includes:
1. Executive Summary- 1-2 page overview of operation, risk profile, mitigation overview
- Quick reference for reviewers
- Detailed mission definition (objectives, geography, timeline)
- Drone specifications and payload details
- Airspace classification and restrictions
- Environmental and population context
- Comprehensive hazard identification (20+ potential hazards typical)
- Impact/probability matrix (visual representation of risks)
- Detailed mitigation measures for each unacceptable risk
- Residual risk evaluation (proving acceptable risk after mitigations)
- Evidence that mitigations work as designed
- Test data, pilot training records, equipment certifications
- Operational manual with detailed procedures
- Emergency response protocols and contingency plans
- Operator licensing verification
- Pilot certification details
- Insurance proof (coverage amounts, policy details)
- Approval of any equipment/procedures requiring pre-approval
- Flight route maps with GPS coordinates
- Equipment specifications and failure analysis
- Training curriculum documentation
- Maintenance and inspection procedures
- Waiver/approval letters from relevant authorities
Common SORA Application Mistakes
Mistake 1: Insufficient risk identification- Listing only obvious hazards (GPS loss, communication failure)
- Missing environmental hazards (bird strikes, wind gusts)
- Ignoring operational hazards (operator fatigue, training gaps)
- Solution: Use comprehensive EASA hazard checklists
- Proposing mitigations without testing/evidence
- Claiming design features reduce risk without performance data
- Ignoring secondary failure modes
- Solution: Provide test data, equipment certifications, field trial results
- Underestimating occurrence likelihood without data
- Claiming "negligible" probability without statistical evidence
- Solution: Ground probability estimates in manufacturer data, fleet history, testing
- Claiming training without documented curriculum
- Missing flight hour requirements verification
- Solution: Include pilot certificates, training records, supervised flight documentation
- Missing emergency landing protocols
- Inadequate communication procedures
- No contingency plans for system failures
- Solution: Develop detailed operational manual with step-by-step procedures
SORA Approval Process Timeline
Week 1-2: Application Preparation
- Conduct comprehensive risk assessment
- Develop mitigation measures
- Compile SORA documentation package
- Obtain operator/pilot certifications
Week 2-3: Transportstyrelsen Submission
- Submit complete SORA package to Transportstyrelsen
- Pay application fee (SEK 3,000-5,000)
- Provide contact information for clarifications
Week 3-4: Initial Review
- Transportstyrelsen conducts preliminary assessment
- May request clarifications or additional information
- Identifies missing documentation or risk gaps
Week 4-6: Detailed Assessment
- Technical experts evaluate risk assessment
- May request additional testing or field data
- Coordinates with relevant authorities (airports, police, emergency services)
Week 6-8: Approval Decision
- Conditional approval (requires test flights with oversight)
- Full approval (immediate operational authorization)
- Request for modifications (revise risk assessment and resubmit)
Week 8-10: Test Flights (if conditional)
- Operator conducts supervised demonstration flights
- Transportstyrelsen observer monitors compliance
- Equipment performance verified in real-world conditions
Week 10-12: Final Authorization
- Full approval certificate issued
- Valid 12 months (annual renewal requires operational review)
- Documented mitigation measures become mandatory requirements
SORA Costs and Resources
Professional Assistance Costs
- SORA documentation consulting: SEK 30,000-80,000 (specialized expertise)
- Risk assessment services: SEK 15,000-40,000 (detailed analysis)
- Equipment certification/testing: SEK 20,000-60,000 (if novel systems)
- Transportstyrelsen application fees: SEK 3,000-5,000
MmowW SORA Support Features
- SORA template documentation (starting framework)
- Risk matrix calculation assistance
- Hazard identification checklists
- Mitigation effectiveness evaluation
- Approval tracking and renewal reminders
FAQ: SORA Risk Assessment in Sweden
🐣 Q: Do I need SORA to fly BVLOS (beyond-line-of-sight) in Sweden? A: Yes. All BVLOS operations require SORA authorization. Timeline: 2-4 weeks (rural areas), 4-8 weeks (populated areas). Cost: SEK 80,000-200,000 for documentation and approval. 🦉 Q: What's the difference between SORA "conditional approval" and "full approval"? A: Conditional approval requires supervised test flights (3-10 flights with oversight) before full operations. Full approval grants immediate operational authorization. Conditional takes 8-10 weeks total; full approval is faster but requires strong mitigation documentation. 🐣 Q: Can I use a SORA from another EU country (Germany, Netherlands) for operations in Sweden? A: No. Each country's regulatory authority (Transportstyrelsen in Sweden) requires independent SORA approval. However, documentation from other approvals can inform your Swedish application (reducing preparation time). 🦉 Q: What happens if my SORA operation doesn't go as planned (system fails, near-miss)? A: You must report the incident to Transportstyrelsen within 48 hours. Non-serious incidents may just require documentation. Serious incidents may trigger operational suspension pending investigation. Prevention is critical—rigorous testing before approval. 🐣 Q: Is SORA insurance covered by standard commercial drone liability? A: Not always. Check your policy—some insurers require "SORA operations" endorsement (additional cost: SEK 10,000-20,000 annually). Always verify coverage before submitting SORA application.
Compliance Tools and Services
MmowW streamlines SORA preparation:
- Hazard identification templates — Comprehensive checklists for risk analysis
- Risk matrix calculation — Automated impact/probability evaluation
- Mitigation documentation — Template-driven safety case preparation
- Operational manual generator — Procedure documentation streamlined
- Timeline tracking — Monitor SORA approval process from submission to authorization
- Renewal reminders — Annual SORA renewal alerts with documentation update requirements
Implementation Checklist for SORA Operations
- [ ] Obtain advanced remote pilot certification (if not already held)
- [ ] Define detailed operational scenario
- [ ] Conduct comprehensive hazard identification
- [ ] Develop risk mitigation measures (design, operational, administrative)
- [ ] Gather supporting documentation (certificates, test data, training records)
- [ ] Compile complete SORA documentation package
- [ ] Obtain liability insurance verification (SEK 8,000,000+)
- [ ] Submit SORA application to Transportstyrelsen
- [ ] Address any clarifications requested during review
- [ ] Conduct required test flights (if conditional approval)
- [ ] Receive final authorization certificate
- [ ] Implement mandatory mitigation measures
- [ ] Begin operational flights
Looking Ahead: SORA Evolution (2027+)
Transportstyrelsen is planning:
- Streamlined SORA for proven operators — Fast-track pathway for experienced operators
- Pre-approved SORA templates — Standard operations with pre-defined acceptable mitigations
- Autonomous operations authorization — SORA framework for fully autonomous flights (Class 3+)
- Cross-border SORA harmonization — Aligned Nordic standards reducing duplication
Conclusion
SORA is the regulatory gateway to advanced drone operations in Sweden. While the documentation process is rigorous, operators who invest in comprehensive risk assessment and proven mitigation measures unlock valuable operational opportunities: BVLOS delivery, over-people operations, night flights, and complex urban missions. Understanding EASA principles, developing robust safety cases, and maintaining meticulous compliance will establish your operation as a trusted, professionally managed enterprise.