Structured Risk Assessment for Advanced RPAS Operations
Enable Complex Operations Through Structured Risk Design
As drone operations move beyond standard operating conditions, traditional risk assessment approaches are no longer sufficient.
Advanced operations—such as:
- BVLOS
- Long-range infrastructure inspection
- Remote and scalable operations
- Complex or high-risk environments
require a formal, structured risk assessment methodology.
The Specific Operations Risk Assessment (SORA) provides this framework.
Uncrewed Approvals supports operators and organisations in developing SORA submissions aligned with both:
- JARUS SORA 2.5
- CASA’s Australian contextualised version, AUS-SORA
What is SORA?
SORA is a methodology developed by the Joint Authorities for Rulemaking on Unmanned Systems (JARUS) to assess and manage the risk of specific RPAS operations.
It provides a structured approach to:
- Identifying operational risk
- Defining mitigation strategies
- Demonstrating acceptable levels of safety
Rather than applying fixed rules, SORA evaluates:The operation itself — its environment, system, and risk profile
JARUS SORA 2.5 and AUS-SORA
We develop SORA assessments in line with:
JARUS SORA 2.5
- Internationally recognised methodology
- Provides the baseline framework for risk assessment
- Used globally for advanced RPAS approvals
AUS-SORA (CASA Contextualised Version)
- Adapted for the Australian regulatory environment
- Aligns with CASA expectations and approval pathways
- Incorporates local airspace, operational, and regulatory considerations
When is a SORA Required?
SORA is typically required for operations that cannot be assessed using standard frameworks.
This includes:
- BVLOS operations
- Operations above standard altitude limits
- Complex airspace environments
- Large-area or scalable operations
- Multi-RPA or integrated system operations
What SORA Assesses
SORA evaluates risk across multiple dimensions:
Ground Risk (GRC)
- Risk to people on the ground
- Population density
- Operational area characteristics
Air Risk (ARC)
- Interaction with other airspace users
- Airspace classification
- Traffic environment
Mitigation Measures
- Strategic mitigations (planning and design)
- Tactical mitigations (real-time controls)
- Technical mitigations (systems and equipment)
Operational Safety Objectives (OSOs)
- Defined safety requirements
- Evidence that mitigations are effective
What a SORA Requires
A successful SORA submission requires:
Concept of Operations (ConOps)
- Clear definition of the operation
- Mission profile and environment
Risk Assessment
- Structured analysis using SORA methodology
- Identification and mitigation of hazards
System Understanding
- Aircraft capabilities
- Command and control systems
- Operational limitations
Supporting Evidence
- Documentation
- Procedures
- System capabilities
Our Approach
SORA is not a template — it is a designed assessment.
1. Feasibility Assessment
We assess whether your operation is suitable for a SORA-based approval.
2. ConOps Development
We define a clear and defensible Concept of Operations.
3. SORA Development
We develop the full SORA assessment in line with:
- JARUS SORA 2.5
- AUS-SORA requirements
4. Mitigation Design
We define:
- Operational controls
- Technical mitigations
- Procedural frameworks
5. Submission Support
We support:
- Engagement with CASA
- Iteration and refinement
What You Get
- A complete SORA assessment
- ConOps development
- CASA-aligned documentation
- Structured risk mitigation framework
- Support through the approval process
Why Uncrewed Approvals
SORA development requires more than regulatory knowledge — it requires operational design capability.
We bring:
- Deep understanding of advanced RPAS operations
- Experience across complex approval pathways
- Alignment with both international and Australian frameworks
- A focus on practical, achievable outcomes
We don’t just produce a SORA — we help you:Design an operation that can be approved and operated
Common Challenges We Solve
- Difficulty understanding SORA methodology
- Misalignment between ConOps and risk assessment
- Overly complex or unachievable mitigation strategies
- Lack of supporting evidence
- Delays in approval due to incomplete submissions
From Concept to Approval
SORA is often the pathway to:
- BVLOS operations
- Large-scale deployment
- Enterprise-level RPAS capability
A well-developed SORA provides a clear, defensible pathway from concept to approval.
Frequently Asked Questions
Is SORA required for all operations?
No — SORA is typically required for complex or higher-risk operations that fall outside standard approval frameworks.
Is SORA difficult to develop?
It is structured and detailed, but achievable with the right approach and operational design.
Can SORA be used for BVLOS?
Yes — SORA is commonly used as the framework for BVLOS approvals.
How long does the process take?
Timeframes vary depending on complexity and readiness.
Develop Your SORA
If you are planning a complex or advanced RPAS operation, a structured SORA is the first step.
