SORA Risk Assessment NZ 2026: Part 102 Application Guide

:::

:::

What Is SORA?

SORA stands for Specific Operational Risk Assessment. It's a structured method for evaluating risks in drone operations and proposing safety mitigations.

SORA vs. SMS

These terms are sometimes confused:

Aspect	SORA	SMS
Purpose	Evaluate risks for specific operations	Document overall safety management procedures
Scope	Targeted to one operation or operation type	Covers all your company operations
Audience	Used internally + submitted with CAA application	Your company's safety manual (living document)
Requirement	Required for Part 102 UAOC application	Required for Part 102 UAOC, updated regularly
Detail Level	Deep hazard analysis for specific risks	Broader procedures, high-level hazard register

Key point: SORA is the risk analysis foundation for your SMS. Your SMS incorporates SORA findings and builds operational procedures around them.

Why SORA Matters

CAA NZ doesn't just approve you to fly anywhere, anytime. They approve you for specific operations with defined limitations. SORA demonstrates:

1. ✅ You've identified hazards – You know what could go wrong
2. ✅ You have mitigations – You have plans to prevent or manage those hazards
3. ✅ Risk is acceptable – Residual risk is low enough for safe operations
4. ✅ You're competent – You've thought deeply about safety, not just compliance

A thorough SORA impresses CAA NZ and leads to faster approvals with fewer questions.

:::

SORA Framework: EASA Methodology (Adapted for NZ)

CAA NZ largely follows EASA (European Union Aviation Safety Agency) SORA methodology, adapted for NZ context.

SORA Components

A complete SORA includes:

1. Operational Description – What operations you'll conduct (aircraft, location, altitude, etc.)
2. Hazard Identification – What can go wrong
3. Risk Analysis – Probability × Severity = Risk Level
4. Mitigations – What you'll do to reduce risk
5. Residual Risk Assessment – Risk after mitigations applied
6. Approval Justification – Why CAA NZ should approve this operation

Risk Matrix (Severity × Probability)

Standard risk assessment uses a matrix: `` CATASTROPHIC HAZARDOUS MAJOR MINOR Frequent RED RED AMBER AMBER Occasional RED AMBER AMBER GREEN Remote AMBER AMBER GREEN GREEN Extremely Rare AMBER GREEN GREEN GREEN ``

Color coding:

• 🔴 RED – Unacceptable risk (must have strong mitigations or reject operation)
• 🟠 AMBER – Acceptable with mitigations (standard risk, manageable)
• 🟢 GREEN – Acceptable risk (low risk, standard safety practices sufficient)

Your goal: Move all hazards to AMBER or GREEN through mitigations.

Building Your SORA: Step-by-Step

Step 1: Define Your Operational Scope

Write out exactly what operations you'll conduct:

Example for surveying company: "Company XYZ will conduct Beyond Visual Line of Sight (BVLOS) orthomosaic surveys using DJI Matrice 300 RTK aircraft in rural NZ. Operations will:

• Cover areas of 50-500 hectares per mission
• Be conducted during daylight hours (30 min after sunrise to 30 min before sunset)
• Be limited to uncontrolled airspace (Class F/G) only
• Maintain minimum 500m distance from residential areas
• Use RTK GPS for navigation (not GPS only)
• Employ two-person crew: Remote Pilot + Ground Observer
• Use automated flight paths with manual override capability
• Never conduct operations over people or populated areas
• Weather limits: wind <8 m/s, visibility >5 km"

Why this matters: Specific scope limits your SORA. Broader scope = more hazards = more complex SORA.

Step 2: Identify Hazards

Brainstorm everything that could go wrong:

Category	Potential Hazards
Aircraft Failure	Propeller failure, motor loss, GPS dropout, gimbal failure, battery fire
Environmental	Wind gust, severe weather, bird strike, lightning
Operational	Pilot error, observer error, navigation error, lost signal
Third-Party	Manned aircraft collision, drone hit bystander, impact on property
Data/Cyber	GPS spoofing, unauthorized control, data loss, malware
Ground Operations	Crew injury during setup, battery malfunction, ground fire

Aim for 30-50 distinct hazards depending on operation complexity. This shows thorough thinking.

Step 3: Analyze Risk for Each Hazard

For each hazard, assess:

Severity: What's the worst case?

• Catastrophic = deaths, major property damage
• Hazardous = serious injury, significant property loss
• Major = injury requiring medical treatment, minor property loss
• Minor = no injury, minimal property impact

Probability: How likely is this hazard?

• Frequent = multiple times per year, >1%
• Occasional = few times per year, 0.1-1%
• Remote = rare, happens across industry, 0.01-0.1%
• Extremely rare = almost never, <0.01%

Risk level: Read from matrix above Example analysis:

Hazard	Severity	Probability	Risk	Notes
Propeller failure mid-flight	Major	Remote	AMBER	Modern drones highly reliable, but single-point failure
Pilot error (wrong waypoint)	Hazardous	Occasional	AMBER	Risk increases with fatigue, inexperience
GPS loss over rural area	Major	Remote	AMBER	RTK fallback to standard GPS degrades accuracy
Bird strike	Hazardous	Remote	AMBER	Rare in rural areas, more likely near coasts/water
Unauthorized interference (remote control jamming)	Major	Extremely Rare	GREEN	Unlikely without intentional adversary

Step 4: Propose Mitigations

For each AMBER/RED hazard, propose mitigation:

Hazard	Mitigation	Risk Reduction
Propeller failure	Pre-flight propeller inspection; reserve aircraft on standby; Maintenance intervals per manufacturer	Reduces Probability: Occasional → Remote
Pilot error	Crew training + annual refresher; Automated flight plan with manual override; Checklist discipline	Reduces Severity: Hazardous → Major; Probability: Occasional → Remote
GPS loss	RTK base station + standard GPS redundancy; Failsafe landing procedure; Avoid dense urban canyons	Reduces Severity: Hazardous → Major
Bird strike	Operate in open areas (reduce bird encounters); Remote Pilot monitor for birds; Altitude limits (stay below typical bird flight)	Reduces Probability: Remote → Extremely Rare

Goal: After mitigations, move all risks to AMBER or GREEN.

Step 5: Residual Risk Assessment

After proposing mitigations, re-assess risk:

Hazard	Original Risk	Mitigations	Residual Risk	Acceptable?
Propeller failure	AMBER	Inspection + maintenance + reserve aircraft	GREEN	✅ Yes
Pilot error	AMBER	Training + checklist + automation	GREEN	✅ Yes
GPS loss	AMBER	Redundancy + failsafe	GREEN	✅ Yes
Bird strike	AMBER	Area selection + monitoring	GREEN	✅ Yes

If any hazard remains RED after mitigations, either:

1. Add more/better mitigations, OR
2. Reject that operation (don't do it)

Step 6: Approval Justification

Write a conclusion paragraph: "After thorough hazard analysis and implementation of robust mitigations, residual risk for BVLOS surveying operations is acceptable. All identified hazards have been reduced to AMBER or GREEN risk levels through:

1. Pre-flight inspections and maintenance procedures (reduces equipment failure risk)
2. Comprehensive crew training and annual refresher requirements (reduces human error)
3. Automated flight paths with manual override (reduces navigation error)
4. Weather limits and operational restrictions (reduces environmental risk)
5. Emergency procedures (reduces consequence of failures)

CAA NZ approval is justified based on: professional crew competency, robust safety management system, operational limitations matched to risk profile, and industry best practices. This operation can be conducted safely within defined limitations."

SORA Documentation Format

Industry-Standard Template

Your SORA should include:

Front Matter:

• Title page (Operation name, date, company, authors)
• Executive summary (1-page overview)
• Table of contents
• Version control (track edits, approvals)

Main Sections:

1. Operational Description (2-4 pages)
2. Aircraft & System Specifications (2-3 pages)
3. Crew & Training Requirements (1-2 pages)
4. Hazard Identification (2-3 pages, list table)
5. Risk Analysis (5-10 pages, detailed matrix)
6. Mitigations (5-10 pages, detailed for each hazard)
7. Residual Risk (2-3 pages, post-mitigation assessment)
8. Approval Justification (1-2 pages)
9. Appendices (checklists, procedures, training records)

Total length: 25-50 pages depending on complexity

Tools & Software

Options for creating SORA:

1. Microsoft Word (free if you have Office, standard format, client-friendly)
2. Google Docs (free, cloud-based, easy collaboration)
3. Specialized SORA software (Corvus Safety, GRC tools) – NZ$500-$5,000, overkill for small ops
4. EASA SORA template (available free online, adapt for NZ CAA)

Recommendation: Start with Word or Google Docs + EASA template. Once you're experienced, upgrade to specialized software if operating fleet-wide.

SORA Development Timeline & Cost

DIY Approach (No Consultant)

Timeline:

• Research & learning: 1-2 weeks (understand SORA methodology, EASA guidance)
• Hazard identification: 1-2 weeks (brainstorm, document, refine)
• Risk analysis: 2-3 weeks (matrix completion, detailed narrative)
• Mitigations: 1-2 weeks (propose, evaluate, refine)
• Residual assessment: 1 week (final validation)
• Editing & formatting: 1 week (professional presentation)
• Total: 7-12 weeks

Cost: NZ$0 (your labor only) Best for: Experienced operators, simpler operations, patient timeline

Consultant-Assisted Approach

Timeline:

• Initial briefing: 2-3 hours (share your operation details)
• Consultant develops SORA: 2-3 weeks (drafts hazard analysis, risk matrix)
• Your review & feedback: 1-2 weeks
• Refinement cycle: 1-2 weeks
• Final review & submission: 3-5 days
• Total: 4-6 weeks

Cost: NZ$5,000-$12,000 (typical consultant rate: NZ$2,000-$3,000/week) Best for: Busy operators, complex operations, faster timeline, lower risk of CAA rejection

When to Hire a Consultant

Consider hiring if:

• ✅ Your operation is complex (BVLOS + over people + night + multiple aircraft types)
• ✅ You're risk-averse (want professional validation before submission)
• ✅ Your timeline is tight (need UAOC within 3-4 months)
• ✅ First-time UAOC applicant (consultant increases approval odds)

Skip consultant if:

• ✅ Your operation is simple (VLOS only, single aircraft, rural areas)
• ✅ You've already developed SMS documents
• ✅ You're patient (6-12 month timeline is fine)
• ✅ You're budget-conscious (willing to DIY, accept slightly higher CAA questions)

Common SORA Mistakes (Learn From Others)

Mistake 1: Over-Scope Operations

❌ Bad: "Company will conduct all drone operations: VLOS, BVLOS, night, over people, delivery, spraying, inspections, etc." ✅ Good: "Company will conduct VLOS surveying of rural farms in daylight hours only, within Class F/G airspace."

Why: Overly broad scopes require massive SORA. Start narrow, add scope later through SMS amendments.

Mistake 2: Insufficient Hazard Identification

❌ Bad: "Hazard list: aircraft failure, human error. Risk: acceptable." ✅ Good: 40+ distinct hazards, each analyzed with severity/probability, specific mitigations per hazard.

Why: CAA NZ sees this as lazy. Thorough hazard identification shows competence.

Mistake 3: Weak Mitigations

❌ Bad: "Mitigation: We will be careful." ✅ Good: "Mitigation: Pre-flight GPS RTK convergence check (minimum 2-minute lock); if convergence not achieved, delay flight by 15 minutes and retry; if still failing, use alternate aircraft with proven RTK performance."

Why: Specific, procedural mitigations convince CAA NZ you've thought deeply.

Mistake 4: Ignoring Residual Risk

❌ Bad: "After mitigations, all risks are GREEN and acceptable." ✅ Good: "Residual risk remains AMBER for bird strike (Occasional probability, Major severity) due to rural environment. This is acceptable because: 1) operations avoid bird migration corridors, 2) daytime only (peak activity), 3) altitude limits reduce encounter probability."

Why: Acknowledging residual risk shows maturity. Saying all risk is GREEN looks naive.

Mistake 5: Vague Crew Qualifications

❌ Bad: "Remote Pilot must be qualified." ✅ Good: "Remote Pilot must hold CAA Remote Pilot License (mandatory), have minimum 50 flight hours in VLOS, and complete annual training refresh in BVLOS procedures."

Why: CAA NZ wants specificity. Define minimum qualifications clearly.

FAQ

Q: Do I need a separate SORA for each operation, or one SORA for all operations?

A: You can have one comprehensive SORA covering all your operations if they're similar (e.g., "all VLOS surveying"), or separate SORAs for distinctly different operations (e.g., "VLOS surveying" vs. "BVLOS delivery"). CAA NZ prefers grouping similar operations.

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

A: Yes! SORA templates are available free. Adapt to your specific operations. Never submit a copy of competitor SORA (unethical, won't match your aircraft/procedures).

Q: What if I discover a new hazard after submitting SORA?

A: Update your SMS (living document) immediately. Minor new hazards don't require SORA revision. Major new hazards or changes in operations require formal UAOC amendment (submitted to CAA NZ).

Q: Does SORA need to be updated yearly?

A: Yes. During CAA NZ surveillance audits (annual), you'll review SORA for relevance. If your operations haven't changed, update the "review date" only. If operations have changed significantly, develop revised SORA.

Q: Who approves SORA—does CAA NZ sign off?

A: CAA NZ doesn't formally "approve" SORA; they approve your UAOC, which incorporates SORA findings. If CAA NZ has issues with your SORA during audit, they'll request revisions before approval.

Q: How detailed should hazard descriptions be?

MmowW for NZ SORA & Risk Management: MmowW helps you track the conditions your SORA describes: weather limits, crew qualifications, flight parameters, hazard mitigation procedures. Every flight is logged against your SORA scope. At NZ$8.60 per drone per month, you maintain a complete operational record proving SORA compliance. Build SORA with rigor. Stay risk-aware. Let MmowW track your safety.