Transport Canada's Specific Operations Risk Assessment (SORA) framework has become the standard methodology for evaluating the safety of advanced drone operations. In 2026, SORA analysis is mandatory for any Special Flight Operations Certificate (SFOC) application and represents the foundation of Transport Canada's risk-based approach to drone regulation. This guide walks through the complete SORA process, from hazard identification to risk mitigation strategy development.

Understanding SORA: Purpose and Framework

SORA is a structured, evidence-based methodology for assessing the safety of drone operations and developing proportionate mitigation strategies.

Core Principle:

Rather than applying one-size-fits-all rules, SORA allows operators to propose customized flight operations with tailored safety measures that demonstrate acceptable risk levels.

Benefits of SORA Approach:
  • Enables innovative operations (BVLOS, over water, etc.) previously prohibited
  • Reduces unnecessary restrictions for low-risk operations
  • Encourages operator responsibility and safety culture
  • Provides clear approval pathway for emerging use cases

SORA vs. Traditional Rules:
  • Traditional Approach: "You cannot fly beyond visual line of sight" (blanket prohibition)
  • SORA Approach: "You may fly BVLOS if you demonstrate through risk analysis that you can maintain safety through specific mitigation measures"

SORA Process Overview: Five Steps

Transport Canada's SORA framework follows five sequential steps:

Step 1: Operational Environment Assessment

Characterize the airspace, terrain, and external factors affecting flight safety.

Airspace Classification:
  • Class A (Controlled): Strict airspace access, separation requirements, continuous ATC service
  • Class B (Controlled): Commercial traffic, approach/departure corridors, ATC service
  • Class C (Controlled): Moderate traffic, controlled access, ATC service
  • Class D (Controlled): Airport traffic patterns, local training, ATC service
  • Class E (Controlled): High-altitude structure (above 700 feet AGL), some locations
  • Class F (Uncontrolled): Rural/remote airspace, low traffic typically
  • Class G (Uncontrolled): Uncontrolled airspace, no ATC service

Terrain Assessment:
  • Urban (dense buildings, infrastructure)
  • Suburban (moderate building density, utility infrastructure)
  • Rural (sparse buildings, agricultural lands)
  • Remote (minimal structures, natural terrain)
  • Over water (lakes, rivers, ocean)

Environmental Factors:
  • Population density (person count per square kilometer)
  • Obstacle density (trees, buildings, utility poles)
  • Wind patterns and seasonal variations
  • Weather frequency (thunderstorms, fog, high winds)
  • Manned aircraft activity (nearby airports, flight training schools)

Step 2: Hazard Identification

Systematically identify all potential safety risks for the proposed operation.

Standard Hazard Categories (Transport Canada):

Hazard Description Severity Level
Collision with manned aircraft Undetected drone in manned aircraft flightpath Catastrophic
Collision with persons Impact with persons on ground or water Critical
Collision with obstacles Impact with buildings, structures, terrain Major/Critical
System failure Motor failure, battery depletion, control link loss Major
Loss of containment Propellers/parts separating during flight Major
Weather encounter Wind, icing, lightning, low visibility Major
Operator error Misjudgment, misunderstanding, fatigue Variable
Third-party interference Jamming, hacking, hostile action Major

Hazard Characterization Format:

Each identified hazard is documented with:

  • Hazard description (specific failure mode or event)
  • Probability (how likely the hazard is to occur)
  • Severity (consequence if hazard occurs)
  • Current risk level (product of probability ร— severity)

Step 3: Societal Risk Assessment

Evaluate the potential impact of hazards on people in the operational area.

Population at Risk Assessment:
  • Airspace users (manned aircraft, other drones)
  • Ground users (persons, vehicles, property)
  • Sensitive areas (hospitals, schools, critical infrastructure)

Severity Categories (Transport Canada):
  • Negligible: No injury or minimal property damage (< CA$1,000)
  • Minor: Minor injury, limited property damage (CA$1,000-CA$10,000)
  • Major: Serious injury, significant property damage (CA$10,000-CA$100,000)
  • Critical: Fatality or multiple serious injuries, major property damage (CA$100,000+)

Acceptable Risk Threshold (Transport Canada):
  • Probability of critical event: < 1 per 10,000,000 flight hours
  • Probability of major event: < 1 per 1,000,000 flight hours
  • Probability of minor event: < 1 per 100,000 flight hours

Step 4: Risk Mitigation Strategy Development

Design specific measures to reduce identified risks to acceptable levels.

Mitigation Categories: Technical Measures:
  • Redundant systems (dual control link, automated failsafe)
  • Detection systems (sense and avoid, traffic collision avoidance)
  • Operational limits (altitude cap, geofencing, speed limits)
  • Monitoring systems (real-time flight telemetry, tracking)

Operational Measures:
  • Training and certification (pilot qualifications, recurrent training)
  • Procedures (pre-flight checklists, emergency protocols)
  • Personnel (safety observers, ground coordinators)
  • Communications (air-ground coordination, airspace notifications)

Administrative Measures:
  • Insurance (minimum liability coverage, professional indemnity)
  • Approvals (airspace access, environmental clearances)
  • Reporting (incident documentation, regulatory filing)
  • Record-keeping (flight logs, maintenance history)

Example Mitigation Strategy (BVLOS Delivery):

Hazard Risk Level Mitigation Measure Residual Risk
Collision with manned aircraft Critical Network Remote ID, continuous ATC coordination, automated altitude limit (400 ft) Major
Loss of command link Major Redundant control link (cellular + backup RF), automated return-to-home Minor
Battery depletion Major Continuous battery monitoring, reserve power calculation, no-return-point limits Minor
System failure mid-flight Major Pre-flight redundancy testing, real-time health monitoring, emergency landing protocol Minor

Step 5: Risk Acceptance and Approval

Document residual risks and obtain Transport Canada approval for operations to proceed.

Risk Acceptance Criteria (Transport Canada):
  • All identified hazards have documented mitigation strategies
  • Residual risk levels are at or below acceptable thresholds
  • Operator has demonstrated competency to execute mitigations
  • Insurance and liability coverage are adequate
  • Operational procedures are clear and testable

Approval Conditions:
  • SFOC issued with specific operational limitations
  • Operational envelope clearly defined (altitude, speed, area, weather)
  • Approval duration (typically 12 months, renewable)
  • Compliance verification requirements (incident reporting, data logging)

SORA Documentation Structure

Transport Canada requires formal SORA documentation following a specific structure:

Required SORA Document Components

1. Executive Summary:
  • Operation description (one paragraph)
  • Operational environment (airspace, terrain, population)
  • Key hazards and mitigations
  • Recommendation (approval/denial rationale)

2. Operational Description:
  • Detailed operation overview (1-2 pages)
  • Flight area map (marked airspace, altitude envelope, route)
  • Weather minimums and operational windows
  • Expected frequency and duration
  • Pilot and observer qualifications

3. Hazard Analysis:
  • Comprehensive hazard list (15-30 typically)
  • For each hazard:
  • Description and failure mode
  • Probability assessment (frequent, occasional, remote, improbable)
  • Severity assessment (negligible, minor, major, critical)
  • Risk matrix position (probability vs. severity)

4. Mitigation Strategy:
  • Hierarchical list of mitigations (technical, operational, administrative)
  • Traceability matrix (hazard โ†” mitigation linkage)
  • Residual risk assessment after mitigations
  • Verification method (how mitigation effectiveness is confirmed)

5. Supporting Documentation:
  • Aircraft specifications and airworthiness documentation
  • Pilot/operator credentials and training records
  • Insurance certificate and policy summary
  • Operational procedures and emergency protocols
  • Maps and airspace coordination confirmations

Typical Document Length: 20-40 pages (technical, detailed, professionally formatted)

Common SORA Applications in Canada (2026)

Example 1: BVLOS Inspection Over Agricultural Land

Operational Environment:
  • Rural airspace (Class G uncontrolled)
  • Agricultural fields, sparse population
  • Multiple properties across 50+ kmยฒ
  • Daily operations, morning hours preferred

Key Hazards:
  • Collision with manned agricultural aircraft
  • Loss of command link (range limitation)
  • Wind shear and weather changes
  • Encountering unexpected obstacle (wind turbine)

Key Mitigations:
  • Coordination with local agricultural aviation operators
  • Cellular network Remote ID for ground tracking
  • Automated return-to-home with geofencing
  • Weather monitoring with operation suspension criteria
  • Obstacle survey in advance of operations

Example 2: Delivery to Residential Areas

Operational Environment:
  • Suburban/urban airspace (Class E/F near residential)
  • Moderate population density (medium-risk areas)
  • Regular flights to 50+ delivery locations
  • BVLOS operations required

Key Hazards:
  • Collision with person (recipient, bystander)
  • Loss of command link near buildings
  • Unintended landing (battery depletion)
  • Unauthorized interference/jamming

Key Mitigations:
  • Network Remote ID with continuous FAA/Transport Canada tracking
  • Restricted landing zones (geofencing prevents unintended landings)
  • Recipient communication protocol (delivery notification system)
  • Redundant battery management with no-return-point limits
  • Real-time monitoring and ground control station

Example 3: Night Operations for Emergency Response

Operational Environment:
  • Urban/mixed terrain (variable airspace)
  • Emergency conditions (search/rescue, medical)
  • Extended flight duration (4+ hours)
  • High-risk airspace (potential manned response aircraft)

Key Hazards:
  • Collision with manned emergency response aircraft
  • Visual disorientation in darkness
  • Battery depletion during extended search
  • Loss of situational awareness

Key Mitigations:
  • Coordination with emergency services (radio communication)
  • Night lighting (anti-collision lights, autonomous navigation lights)
  • Flight time limiting (return-home trigger at 50% fuel)
  • Dedicated pilot + two safety observers
  • Thermal imaging systems for night visibility

MmowW for SORA Documentation and Compliance

Managing SORA documentation across multiple operations requires systematic tracking and version control:

  • SORA Template Library: Pre-built SORA document templates customizable by operation type; hazard database (common hazards catalogued with mitigation strategies); revision control (version tracking for regulatory submissions)
  • Hazard Management: Automated hazard checklist generation by operation type; risk matrix visualization (probability vs. severity); mitigation traceability (each hazard linked to specific mitigations)
  • Documentation Organization: SORA status tracking (draft, under review, approved, expired); regulatory submission records with Transport Canada reference numbers; approval condition tracking and compliance verification
  • Risk Monitoring: Real-time flight data comparison against approved operational envelope; deviation alerting (altitude, location, speed limits); incident capture and automatic reporting templates
  • Compliance Auditing: Scheduled SORA renewal reminders; operational adherence verification (post-flight analysis); documentation audit trail for Transport Canada inspection

๐Ÿฃ Piyo Questions & Answers

Q1: Do I need to write a SORA for every flight, or just the first one?

๐Ÿฆ‰ Poppo: You write SORA once per operation type/location. The approved SORA covers all similar operations under those conditions (e.g., "BVLOS inspection of agricultural fields in the Ottawa region"). Individual flights don't need separate SORA documentsโ€”they just need to comply with the approved SORA conditions.

Q2: How long should my SORA document be?

๐Ÿฃ Piyo: Typically 20-40 pages including appendices. Transport Canada reviews SORA based on depth and quality of analysis, not page count. A 15-page SORA with thorough hazard analysis is better than a 50-page SORA with boilerplate text.

Q3: What if my proposed operation doesn't fit the Transport Canada SORA examples?

๐Ÿฆ‰ Poppo: Use the five-step SORA methodology regardless. Identify your specific hazards, develop proportionate mitigations, and justify why the residual risk is acceptable. Novel operations often take longer to approve but demonstrate your safety thinking clearly.

Q4: How often do I need to renew my SORA approval?

๐Ÿฃ Piyo: Typically SFOC (and associated SORA) are approved for 12 months. Renewal before expiration requires a new SORA if operations have changed, or may be simplified if operations remain identical. Apply 4-6 weeks before expiration.

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

Conclusion

SORA is not a bureaucratic hurdle but a rigorous safety methodology that enables innovative drone operations while demonstrating responsible risk management. Understanding and executing SORA properly is the pathway to regulatory approval for advanced operations. Use MmowW to systematically develop SORA documentation, track hazards and mitigations, manage approval conditions, and maintain compliance throughout your operation's lifecycle. Build your first SORA-approved operation today at CA$7.70/drone/month.

Ready to develop compliant operations? Let MmowW streamline your SORA process.