SORA Risk Assessment New Zealand 2026: Complete Guide

The Specific Operational Risk Assessment (SORA) is the foundation of New Zealand's advanced drone operations framework. If you're planning commercial flights beyond visual line of sight, filming over people, or conducting specialized operations, the CAA requires a SORA demonstrating you've identified hazards and implemented mitigations. Understanding SORA is critical to regulatory compliance and operational safety.

What Is SORA and Why Does CAA Require It?

SORA is a structured risk assessment methodology that answers one question: "What could go wrong, and how will you prevent it?"

CAA's SORA Philosophy:

Default rule is "No"—special operations are prohibited unless proven safe
Operator burden: You must demonstrate mitigations reduce risk to acceptable level
Scalable approach: Low-risk operations (e.g., simple visual inspection) use simplified LROA; high-risk operations (e.g., 1,000-person festival filming) require comprehensive SORA
Living document: SORA must be updated if operational parameters change

When SORA Is Required:

Beyond Visual Line of Sight (BVLOS) operations
Over people or property (not your own)
Night flying
Flights exceeding 120m altitude
Operations in controlled airspace
Heavy aircraft (>7kg) in any scenario
Specialized operations (delivery, spraying, inspection with risk)

When SORA Is Optional (Standard Part 102 Suffices):

Visual line of sight, daytime, 120m altitude maximum
Unpopulated area, no people below
Aircraft <2kg
Simple recreational application

The 5-Step SORA Framework

Step 1: Define Your Operation

Document These Parameters:

Aircraft Type: Model, weight, endurance, payload, redundancy systems
Location: GPS coordinates, venue description, geographic boundaries
Duration: Expected flight time per mission, total daily operations
Altitude: Typical altitude AGL, maximum altitude planned
Personnel: Who operates drone, who observes, crew experience level
Operational Pattern: Frequency (daily, weekly, seasonal), repeatability
Weather Constraints: Min/max wind, visibility, temperature limits

Example Definition:

"Commercial visual inspection of 3-story residential roof using DJI M300 RTK. Single flight 30 minutes duration, 50m maximum altitude AGL, 1km from residential area, daytime operations only, wind <10 knots, visibility >2km minimum. Operated by commercial pilot with 200+ hours experience. Single observer on-site."

Step 2: Identify Hazards

Hazards are potential events that could cause harm. Think systematically:

Aircraft Hazards:

Motor/propeller failure (loss of thrust)
Battery failure (power loss mid-flight)
GPS loss (navigation uncertainty)
Communication signal loss (loss of control)
Structural failure (frame breaks mid-flight)
Sensor failure (camera/thermal stops working)

Environmental Hazards:

Wind gust exceeding aircraft limits
Precipitation (rain, snow, hail)
Lightning/electrical storm proximity
Electromagnetic interference (antennas, power lines)
Extreme temperature affecting battery performance
Turbulence from nearby structures

Operational Hazards:

Pilot fatigue or distraction
Observer losing visual contact
Crew communication breakdown
Inadequate pre-flight briefing
Spectator entering flight path
Unauthorized aircraft in airspace

Consequence Hazards:

Impact with building or structure
Impact with person on ground
Impact with manned aircraft
Fire risk (battery malfunction)
Property damage (expensive equipment below)

Example Hazard List (Residential Roof Inspection):

Motor failure during climb → loss of altitude control
GPS lock loss → navigation uncertainty
Wind gust >12 knots → loss of stability
Propeller strikes nearby tree → damage/loss of control
Communication signal dropout → loss of pilot control
Battery voltage sag → insufficient power for safe descent
Nearby resident objects → spectator in flight path
Power lines on property edge → collision risk

Step 3: Quantify Risk (Probability × Consequence)

For each hazard, assess:

Probability (Likelihood):

Extremely Remote: <1 in 1 million flights
Remote: 1 in 100,000 flights
Low: 1 in 10,000 flights
Medium: 1 in 1,000 flights
High: 1 in 100 flights

Consequence (Severity if Occurs):

Negligible: No injury, minimal property damage
Minor: Minor injury (cuts, bruises), small property damage
Moderate: Serious injury (breaks, hospitalization), significant property damage
Major: Fatality or permanent disability, major property damage
Catastrophic: Multiple fatalities, massive property damage

Risk Rating:

High × Catastrophic = UNACCEPTABLE (must mitigate or stop operation)
Medium × Major = UNACCEPTABLE (must mitigate significantly)
Low × Moderate = ACCEPTABLE WITH MITIGATIONS
Low × Minor = ACCEPTABLE WITH STANDARD CONTROLS
Extremely Remote × Negligible = ACCEPTABLE (baseline operations)

Example Risk Matrix for Hazard "Motor Failure":

Probability: Low (motors fail ~1 in 5,000 flights; quality manufacturers)
Consequence: Major (battery parachute doesn't always deploy; ~50% safe landing rate)
Risk Rating: Moderate × Major = UNACCEPTABLE without mitigation

Step 4: Define Mitigations

For each unacceptable or high-risk hazard, identify how you'll reduce probability OR consequence:

Probability-Reducing Mitigations (Prevent Hazard Occurrence):

Redundant systems (dual motors, dual batteries)
Component quality standards (aviation-grade parts)
Maintenance schedules (pre-flight checks, annual inspections)
Training & certification (pilot competency verification)
Environmental limits (weather minimums, altitude caps)

Consequence-Reducing Mitigations (Limit Harm if Hazard Occurs):

Parachute systems (automatic deployment on power loss)
Geofencing (prevents flights into no-fly zones)
Altitude limits (reduces impact velocity)
Spectator exclusion (fewer people at risk)
Emergency landing zones (safe places to crash)

Example Mitigations for "Motor Failure":

Use commercial-grade aircraft (DJI M300 RTK, not toy-grade)
Install dual-battery system (automatic failover if one fails)
Implement parachute system (deploys automatically on power loss, reduces velocity 80%)
Maintain 50m altitude limit (reduces impact velocity vs. full altitude)
Establish 100m emergency landing zone (clear area if parachute fails)
Monthly motor inspection (visual check for wear/damage)

Step 5: Evaluate Residual Risk

After mitigations, is risk acceptable?

Acceptable Risk Levels (CAA Standard):

Probability: Remote or lower
Consequence: Minor or lower
Combined: Risk acceptable for approval

Process:

Apply each mitigation
Re-estimate probability (often drops 1–2 levels due to redundancy)
Re-estimate consequence (parachute reduces from Major to Moderate)
New rating: Low × Moderate = ACCEPTABLE WITH MITIGATIONS
CAA approval likely

If Still Unacceptable:

Add more mitigations (third-party safety review, additional training)
Reduce operational scope (lower altitude, smaller area, fewer flights)
Consider operation infeasible (accept that SORA approval won't be granted)

Practical SORA Template

Aircraft System Analysis

`` Aircraft: DJI Matrice 300 RTK Weight: 9.1kg (under 25kg threshold) Endurance: 55 minutes nominal Redundancy: Dual batteries, RTK-enabled GPS Failure Mode Analysis:



Primary battery depletion: Automatic failover to secondary
Secondary battery failure: Manual land within 10-minute window
GPS loss: IMU backup provides 2-3 min autonomous flight
Signal loss: Return-to-home triggered automatically at 100m range


Operational Area Definition

` Location: Residential roofing inspection, 15 Oak Street, Auckland Coordinates: -37.0214, 174.7645 Boundaries: Property perimeter ±100m buffer Airspace: Class G (uncontrolled), no proximity to aerodromes Occupied buildings: Single-family residence (residents briefed) `


Hazard Identification & Mitigation




Hazard
Probability
Consequence
Risk
Mitigation
Residual



Motor failure
Low (1:5k)
Major
Unacceptable
Dual motors, parachute
Acceptable


Signal loss
Low (1:10k)
Moderate
Acceptable
RTH trigger, geofence
Acceptable


Weather shift
Medium (1:100)
Minor
Acceptable
Pre-flight weather check
Acceptable


Spectator entry
Medium (1:500)
Major
Unacceptable
Geofence, crew brief
Acceptable

Hazard	Probability	Consequence	Risk	Mitigation	Residual
Motor failure	Low (1:5k)	Major	Unacceptable	Dual motors, parachute	Acceptable
Signal loss	Low (1:10k)	Moderate	Acceptable	RTH trigger, geofence	Acceptable
Weather shift	Medium (1:100)	Minor	Acceptable	Pre-flight weather check	Acceptable
Spectator entry	Medium (1:500)	Major	Unacceptable	Geofence, crew brief	Acceptable


Crew Qualifications

` Pilot: Commercial drone license holder Experience: 250 flight hours, 50 residential inspections Training: Residential roofing safety course (completed 2026-01) Observer: Designated crew member, briefed on procedures `


Insurance & Liability

` Public Liability: NZ$2M (inspection operations) Professional Indemnity: NZ$1M (data accuracy liability) Coverage: Reviewed for residential roof assessment exclusions ``

Common SORA Mistakes

Mistake 1: Inadequate Hazard Identification

Problem: SORA lists 5 hazards; CAA identifies 15 you missed Solution: Use checklist approach. Cover: aircraft, environment, operations, consequence, airspace categories

Mistake 2: Risk Underestimation

Problem: "Motor failure is extremely remote" (unsupported claim) Solution: Use manufacturer MTBF (Mean Time Between Failure) data. Cite sources for probability estimates.

Mistake 3: Mitigations That Don't Reduce Risk

Problem: "Parachute system will deploy" (but no testing/validation data) Solution: Cite system reliability data, test results, independent validation

Mistake 4: Over-Complicated SORA

Problem: 100-page SORA for simple visual inspection Solution: Match SORA complexity to operation. Simple operations = 5–10 pages. Complex operations = 20–40 pages.

Mistake 5: No Residual Risk Evaluation

Problem: SORA identifies mitigations but never concludes whether risk is acceptable Solution: Explicitly state final risk rating post-mitigation. Example: "Residual risk: Low probability × Minor consequence = ACCEPTABLE"

SORA vs. LROA: When to Use Which

Low-Risk Operational Approval (LROA) - Simplified

Use When:

BVLOS range <5km
Low population density
Standard aircraft (no exotic payloads)
Daytime operations
Predictable hazards

Document:

Aircraft specs (1–2 pages)
Operational area (map + description)
Weather limits
Hazard identification (simplified)
Crew qualifications
Insurance proof

Timeline: 4–6 weeks typically Example: Daytime BVLOS inspection of power lines across farmland

Full SORA - Comprehensive

Use When:

Extended BVLOS range (>5km)
Over people or property
Night operations
Specialized equipment (spraying, delivery)
Complex risk environment

Document:

Everything in LROA PLUS:
Detailed hazard analysis (25+ hazards)
Probability/consequence quantification
Independent risk assessment
Third-party review
Airspace coordination plan
Post-flight validation procedure

Timeline: 8–12 weeks typically Example: 1,000-person festival filming with over-people component

Tools & Resources for SORA Preparation

Official CAA Resources

CAA SORA Template: www.caa.govt.nz (downloadable Word document)
Risk Assessment Guidance: AC101-1 Airworthiness Certification
Exemption Application Portal: Online submission system

Third-Party Support

Flight Training Organizations: Can prepare SORA on your behalf (cost: NZ$2,000–8,000)
Safety Consultants: Specialized drone compliance advisors
Insurance Brokers: Help identify risks specific to your operation

Software Tools (Not Required But Helpful)

Pix4D Risk Assessment: Free hazard checklist template
AirMap Airspace Tool: Real-time airspace data for location risk analysis
WeatherOps: Wind/weather forecasting specific to drone operations

Frequently Asked Questions

🐣 Piyo: Can I use a SORA from another operator if our operations are similar?

Not formally, but you can reference it for structure. Your SORA must be specific to your aircraft, crew, location, and risk environment.

🦉 Poppo: How often do I need to update my SORA?

CAA typically accepts SORA for 2 years. If you change aircraft, crew, or operational scope significantly, file amendment (4–6 week process).

🐣 Piyo: What if CAA rejects my SORA? Can I appeal?

Yes. Ask CAA for specific rejection reasons. Revise mitigations addressing concerns. Resubmit (counts as new application, full timeline again).

🦉 Poppo: Is SORA approval a safety guarantee?

No. SORA shows you've thought through risks, but accidents still happen. CAA approval = "acceptable risk per regulatory standard," not "zero risk."

🐣 Piyo: Do I need a safety consultant to prepare SORA?

Not required, but recommended for complex operations (>20 hazards, over-people, specialized aircraft). Simple operations (visual inspection, VLOS) = self-preparation viable.

Automate SORA Management with MmowW

Managing SORA documents, updates, and exemption tracking is administrative overhead. MmowW automates SORA requirement checklists, hazard templates, and exemption deadline tracking at just NZ$8.60 per drone per month. With MmowW, you get:

✅ SORA requirement assessment (operation complexity analyzer)
✅ Hazard identification checklist and template
✅ Risk mitigation documentation framework
✅ Exemption validity tracking and renewal alerts
✅ CAA submission checklist ensuring nothing is forgotten

References: CAA Part 102 SORA Guidance (2026), AC101-1 Risk Assessment Standard, CAA Exemption Template Documentation, New Zealand Airworthiness Certification Framework