SORA Risk Assessment Canada 2026: Complex Operations Guide

What is SORA?

SORA is a three-step assessment framework:

1. Hazard Identification — List everything that could fail (motor failure, GPS loss, weather, third-party interference)
2. Risk Analysis — Calculate probability × consequence for each hazard
3. Mitigation Strategy — Design controls to reduce risk to acceptable levels

Step 1: Hazard Identification

• How likely is it? (frequency)
• What are consequences? (injury/fatality, property damage, environmental impact)
• Can I prevent it? (design, procedure, training)
• Can I mitigate if it happens? (emergency landing, failsafe, recovery)

Step 2: Risk Analysis (Probability × Consequence)

Risk matrix: Probability vs. Consequence

Probability	Description	Frequency
Remote	Highly unlikely but possible	<1 per 10,000 flights
Low	Unlikely	1–10 per 10,000 flights
Medium	Possible	10–100 per 10,000 flights
High	Likely	>100 per 10,000 flights
Consequence	Description	Example
---	---	---
Negligible	No injury,	Drone hits tree, recovers
Minor	Light injury (bruise, small laceration), CA$5,000–$50,000 property damage	Drone hits person, minor cut
Major	Serious injury (fracture, moderate bleeding), CA$50,000–$500,000 property damage	Drone strikes person, hospitalization
Catastrophic	Fatality or multiple serious injuries, >CA$500,000 property damage	Drone falls into crowd, causes death

Risk = Probability × Consequence Example hazard analysis:

Hazard	Probability	Consequence	Risk Level
Motor failure (single rotor multi-rotor)	Low	Major (emergency landing)	Medium
GPS loss (triggers return-to-home)	Medium	Minor (reduced accuracy, manual recovery)	Low
Pilot fatigue (reduced responsiveness)	Low	Major (potential collision)	Medium
Bird strike	Remote	Major (aircraft damaged)	Low
Third-party aircraft collision	Remote	Catastrophic	Medium

---

Step 3: Mitigation Strategies

For each hazard identified above, design a control:

Example 1: Motor Failure Mitigation

Hazard: Single motor fails during flight. Probability: Low (estimated 1 in 5,000 flights based on manufacturer data). Consequence: Major (aircraft cannot sustain flight, emergency descent). Current risk: Medium (Low × Major). Mitigation options:
• Design control: Use multi-rotor with redundancy (hexa-rotor, octa-rotor). If one motor fails, remaining motors can sustain flight.
• Procedure control: Establish maximum altitude limit (e.g., 50m AGL). If motor fails, descent time is <10 seconds, landing site is clear.
• Monitoring control: Real-time motor current monitoring (software alerts if one motor draws excessive current).
• Recovery control: Emergency descent procedure (activate failsafe landing, descend slowly, land in designated zone).

Example 2: GPS Loss Mitigation

Hazard: GPS signal lost (urban canyon, RFI interference, jamming). Probability: Medium (estimated 5–10 per 1,000 flights in urban areas). Consequence: Minor (position accuracy reduced, but aircraft can navigate via visual/inertial). Current risk: Low (Medium × Minor). Mitigation:
• Design control: Aircraft with inertial measurement unit (IMU) can maintain stability without GPS for short durations (30–60 seconds).
• Procedure control: Require VLOS at all times during GPS loss (pilot visual navigation).
• Training control: Pilot trained on manual control in GPS-denied scenarios.
• Operational control: Conduct flights in areas with confirmed GPS coverage (avoid dense urban canyons).

SORA Documentation: What Transport Canada Requires

1. SORA Report (10–30 pages)

Contents: Section 1: Operational Scenario
• What you're doing (BVLOS delivery, autonomous survey, etc.)
• Where (coordinates, airspace class, populated area?)
• When (time of day, weather conditions)
• How long (duration, frequency)
• Who (crew qualifications)
• What aircraft (model, specifications, redundancy features)

Section 2: Hazard Log
• Comprehensive list of hazards identified
• For each: probability, consequence, risk level
• Prioritized by risk (highest risk first)

Section 3: Mitigation Strategies
• For each hazard: control measures implemented
• Explanation of how each control reduces risk
• Evidence supporting control effectiveness (test results, manufacturer data, historical data)

Section 4: Residual Risk Assessment
• After mitigation, is risk acceptable?
• Compare to Tolerable Risk Level
• If residual risk still too high, propose additional controls

Section 5: Oversight & Monitoring
• How will you monitor compliance during operations?
• What triggers an operation abort?
• Incident reporting procedures

2. Risk Assessment Matrix

Tabular format showing all hazards, probabilities, consequences, controls, and residual risk. Example table:

#	Hazard	Probability	Consequence	Control	Residual Risk	Acceptable?
1	Motor failure	Low	Major	Hexa-rotor redundancy + alt limit	Low	Yes
2	GPS loss	Medium	Minor	IMU backup + VLOS req	Low	Yes
3	Weather deterioration	Medium	Major	Pre-flight wx check, abort triggers	Medium	Requires additional control

---

Real-World SORA Example: BVLOS Delivery Corridor

Scenario: Autonomous drone delivery, rural route (Vancouver → Gulf Islands, 13 km over water).

Hazard Identification

Identified hazards:
1. Motor failure
2. GPS loss
3. Communication link loss
4. Weather deterioration (wind, visibility)
5. Third-party aircraft (manned)
6. Bird strike
7. Propeller icing (in winter)
8. Payload deployment failure (package doesn't release)
9. Return-to-home failure (lands in wrong location)
10. Software/autopilot failure

Risk Analysis

Hazard	Probability	Consequence	Risk	Notes
Motor failure	Low	Major	Medium	Multi-rotor, one motor loss manageable
GPS loss	Low	Medium	Low	Over water, fewer urban RFI sources
Comms loss	Low	Major	Medium	Aircraft auto-returns (failsafe)
Weather deterioration	Medium	Major	High	Winter conditions unpredictable
Third-party aircraft	Remote	Catastrophic	High	Over-water route minimizes manned traffic
Bird strike	Low	Minor	Low	Unlikely over open water
Propeller icing	Low	Major	Medium	Winter risk factor
Payload deployment failure	Low	Minor	Low	Manual override available
Return-to-home failure	Low	Medium	Low	Pilot can override, manual recovery
Autopilot failure	Low	Major	Medium	Software redundancy, manual fallback

Mitigation Strategies

Hazard	Control	Residual Risk
Motor failure	Redundant rotors (hexa-rotor), altitude limit 100m	Low
GPS loss	IMU backup, return-to-home triggers, spotter monitoring	Low
Comms loss	Automated return-to-home, documented path to safe landing	Low
Weather deterioration	Pre-flight weather briefing, abort triggers (wind >35 kph, visibility <3 km)	Low
Third-party aircraft	Over-water route avoids major manned traffic, ADS-B receiver on aircraft alerts pilot	Low
Bird strike	Unlikely over open water; no additional control needed	Low
Propeller icing	Winter operations avoided; if necessary, route limited to warmer hours (avoid dawn/dusk)	Low
Payload deployment failure	Manual override, redundant release mechanism	Low
Return-to-home failure	Pilot standby with manual control, designated landing zone pre-surveyed	Low
Autopilot failure	Firmware redundancy, real-time monitoring, pilot intervention ready	Low

Residual Risk Assessment

SORA Approval Process at Transport Canada

Step 1: Submission (Day 1)

• File SORA report + all supporting documentation
• Transport Canada assigns case manager
• Initial completeness check (1–2 weeks)

Step 2: Detailed Review (Weeks 2–6)

• Engineering team reviews hazard analysis
• Assessment: Are hazards comprehensive? Missed anything?
• Risk calculations: Are probabilities/consequences reasonable?
• Mitigations: Are controls adequate? Documented?

Step 3: Clarifications (Weeks 6–10)

• Transport Canada asks questions (typical: 2–5 major, 10–20 minor)
• You provide additional information/data
• Examples: "Provide test data showing your GPS-loss failsafe works," "Explain how you train spotters on signal-loss procedures"

Step 4: Approval or Denial (Weeks 10–16)

• Transport Canada issues SORA approval letter OR requests major revisions
• If approved: Operational approval issued. You can now operate as planned.
• If denied: Revise SORA, resubmit.

Common SORA Mistakes (And How to Avoid Them)

Mistake	Consequence	How to Avoid
Vague hazard list ("Mechanical failure")	Transport Canada asks for specificity	List component-level hazards (motor bearing failure, prop fracture, etc.)
Unsupported probability estimates	"We think this is 'Low' risk" with no data	Cite manufacturer data, historical accident rates, peer studies
Insufficient mitigations	"We have a pilot, so risk is managed"	Design-level controls (redundancy), procedure controls, training controls
No residual risk statement	Transport Canada approves reluctantly or denies	Explicitly state: "After mitigation, residual risk is [Low/Medium], within TRL"
Missing evidence	Transport Canada can't validate your claims	Provide test reports, certifications, manufacturer specs, precedent cases

---

FAQ: SORA Risk Assessment Canada

Q: Is SORA mandatory for all complex operations?

A: Transport Canada increasingly requires SORA for operations beyond basic RPOC (BVLOS, over people, autonomous flights, complex payloads). For simple operations (photography at low altitude, VLOS), SORA may not be required. Check with TC.

Q: How long should a SORA report be?

A: 10–30 pages depending on operation complexity. Simple operation: 10–15 pages. Complex operation (BVLOS + autonomous + over populated area): 25–30 pages. Quality > quantity.

Q: Can I use someone else's SORA as a template?

A: Yes, SORA frameworks are standardized. But every SORA must be tailored to your specific operation. Don't copy verbatim; customize for your aircraft, crew, location, procedures.

Q: What probability data should I cite?

A: Manufacturer failure rates, FAA accident statistics, peer-reviewed studies, your own historical data (if available). For rare hazards, use expert judgment (justify your estimates).

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

A: Yes, if you're comfortable with technical writing and risk analysis. Many operators hire a SORA consultant (CA$2,000–$5,000 cost) to avoid rejection/rework cycles.

Q: What's the difference between SORA and SFOC?

A: SORA is the risk assessment framework (how you prove safety). SFOC is the regulatory waiver (the approval letter from Transport Canada). You do a SORA analysis, submit to TC, TC approves it, TC issues SFOC.

Q: If my SORA is rejected, can I resubmit?

A: Yes. Transport Canada explains why it was rejected. You revise the SORA (typically addressing their specific concerns), resubmit. Second submission often faster (week 4–8, not 8–16 weeks).

Q: Can I operate while SORA is pending approval?

MmowW SORA Support

MmowW (CA$7.70/drone/month) includes:

• SORA template — Hazard log, risk matrix, mitigation documentation
• SORA checklist — Ensure no hazards missed, all mitigations documented
• Flight logging for SORA data — Automatic incident logging (supports future SORA revisions/approvals)

Summary

SORA is Transport Canada's framework for approving complex drone operations. Three steps:

1. Hazard identification — List everything that could fail
2. Risk analysis — Probability × consequence
3. Mitigation strategies — Design controls to reduce risk

Documentation: 10–30 page SORA report with hazard log, risk matrix, controls, and residual risk assessment. Approval timeline: 8–16 weeks. Cost: DIY (free if self-prepared) or CA$2,000–$5,000 if consultant-assisted.
Last updated: 2026-04-09 | Authority: Transport Canada SORA Framework Guidance, NOP 901.201, EASA SORA Specification (adapted) | Next review: 2026-10-09