SORA Guide
SORA Guide for Drone Operations: What Is It and How to Apply It?
The Specific Operations Risk Assessment (SORA) is a methodology developed by the Joint Authorities for Rulemaking on Unmanned Systems (JARUS) to classify and mitigate risks associated with drone flights in the Specific Category. This guide provides a step-by-step explanation of how to apply SORA to your drone operations in the UK.
What Is SORA?
SORA is a systematic methodology for identifying and mitigating risks in drone operations that do not fall under standard scenarios (STS) or predefined risk assessments (PDRA) within the UK framework. It assists UAS operators in determining operational boundaries, training requirements, and technical characteristics of drones to enable safe operations.
SORA consists of a series of steps that help the operator evaluate the Ground Risk Class (GRC) and Air Risk Class (ARC) of a planned operation, after which mitigations are established to achieve an acceptable level of operational safety.
- Targeted at operations in the UK Specific Category not covered by STS or PDRA.
- Systematically assesses both ground and air risks.
- Provides input for developing an operational manual (ConOps) and an operational authorisation.
When Is SORA Relevant for UK Drone Operators?
In the UK, drone operators in the Open Category do not use SORA, as this regime automatically permits low-risk operations. For Specific Category operations without a PDRA application, SORA is applicable.
The UK Civil Aviation Authority (CAA) employs the SORA process as part of the application for an operational authorisation in the Specific Category. This is mandatory for drone flights that fall outside standard scenarios and where no PDRA method exists.
Note: The EU STS declaration method is not used in the UK as an operational route; UK operators can choose PDRA or SORA where relevant.
- Essential for high-risk or complex BVLOS operations in the Specific Category.
- Applied to new or deviating drone operations outside standard scenarios and PDRA.
- Forms the basis of an operational authorisation application with the UK CAA.
The 10-Step Approach of SORA for Drone Operations
SORA consists of ten consecutive steps that assist an operator in identifying, classifying, and mitigating operational risks. This begins with describing the operation and ends with formulating an acceptable operational authorisation.
Key steps include determining the Ground Risk Class (GRC), Air Risk Class (ARC), identifying geographical and procedural mitigations, and implementing an operational risk management plan (ConOps).
The operator must incorporate the results of this assessment into the operational manual and the Emergency Response Plan (ERP), which are part of the application to the UK CAA.
- Step 1: Description of the operation (ConOps).
- Steps 2-4: Identification of risk classes (GRC and ARC).
- Steps 5-7: Application of mitigations and corrective factors.
- Steps 8-9: Summarisation of the risk profile (SAIL).
- Step 10: Define operational limitations and training requirements.
Practical Tips for Setting Up SORA Files
Ensure a detailed ConOps that clearly describes the operation, environment, and equipment. This forms the basis for the risk analysis.
Collaborate closely with an official safety adviser or use recognised PDRA schemes where applicable to reduce workload.
Thoroughly document all mitigations and assumptions, including the SORA steps used and associated evidence, which is essential in an application for an operational authorisation with the UK CAA.
Verify that all operational limitations align with the ConOps and that the ERP is adequately prepared for emergency scenarios.
- Complete and clear ConOps documentation.
- Use PDRA methods where available to ease the application process.
- Maintain strict documentation of mitigations and training requirements.
- Include a comprehensive ERP and emergency procedures.
Common Mistakes in SORA Application and What to Watch Out For
A common mistake is insufficiently delineating the operational area and overlooking risks in adjacent areas, which can result in incomplete risk assessments.
There is often underestimation of the technical and organisational mitigations required, despite these being explicitly addressed in the SORA methodology.
Insufficient attention to ensuring coherence between the operational manual, ERP, and ConOps can lead to discrepancies in practice and potential refusal of the operational authorisation by the UK CAA.
- Incomplete or unclear delineation of the operational area.
- Underestimating required mitigations and pilot training levels.
- Poorly linked documentation between ConOps, ERP, and operational manual.
- Failure to adhere to current legal requirements and UK CAA guidance.
Frequently asked questions
What is the difference between SORA and PDRA?
SORA is a comprehensive methodology for assessing risks in complex drone operations that fall outside standard scenarios and predefined risk assessments (PDRA). PDRAs are standardised risk assessments for specific operational situations and are simpler to use. In the UK, a UAS operator can choose between PDRA-based or SORA-based operational authorisations under the Specific Category.
Is SORA mandatory for all drone operators in the UK?
No. SORA is only mandatory for drone operations in the Specific Category that do not fall within the Open Category and for which no standard scenario or PDRA is applicable. For many simple operations in the Open Category, you do not need to conduct a SORA.
Where can I find official information about SORA in the UK?
The UK Civil Aviation Authority (CAA) is the competent authority. Official information about SORA and operational authorisations can be found on the CAA website.
Can I use the EU STS route for my drone operations in the UK?
No. The STS concept (Standard Scenarios) is an EU/EASA route that is not used in the UK. UK operators choose between PDRA or SORA routes where applicable.