We use the Specific Operations Risk Assessment (SORA) framework to assess complex drone operations. We may use other assessment methods when appropriate.
The Joint Authorities for Rulemaking on Unmanned Systems (JARUS) developed SORA. SORA helps us measure and manage risks to make sure all drone operations meet consistent safety standards.
JARUS released SORA 2.5 in June 2024. All applications must continue using SORA 2.0 until CASA transitions to SORA 2.5.
Temporary Management Instructions (TMIs)
We publish TMIs to provide extra guidance for complex operations. TMIs support safe, consistent assessments during the transition to CASA's version of SORA 2.5.
SORA 2.0 Ground Risk Assessment – TMI 2024-03
SORA 2.0 ground risk assessment - requirements and alternate criteria - TMI 2024-03 updates how operators calculate and manage ground risk.
It includes:
- new population density bands and qualitative descriptors
- clearer methods to identify ground risk classes
- the option to claim sheltering, in some situations, to reduce risk.
These updates help operators assess ground risk more accurately for their operational area. We recommend using this TMI when preparing SORA documents.
RPA Operations over or near people – TMI 2024-01
RPA Operations over or near people - 2024-01 outlines how we assess applications to fly a drone closer than 30 metres of people. Operators who cannot meet the requirements in this TMI should ask about or apply for Advanced operations.
Broad Area BVLOS Operations – TMI 2025-03
Broad Area BVLOS Operations – TMI 2025-03 sets the limits and criteria for area-based BVLOS approvals. It includes:
- four trial pathways
- clear requirements for population density and mitigation measures
- a framework for responsible person nomination and data reporting.
This TMI supports the Broad Area BVLOS trial and helps operators plan and fly safely over larger areas with fewer approvals and greater flexibility.
RPAS Operations Authorisation Assessment Methodology – TMI 2025-02
RPAS Operations Authorisation Assessment Methodology – TMI 2025-02 outlines how we assess complex RPAS operations. SORA remains the default framework, but CASA may use other approaches when suitable. It also lists estimated dates for our transition to SORA 2.5. This guidance improves transparency around how we apply different assessment pathways.
Webinar and support
We hosted a free BVLOS webinar to help operators apply SORA effectively.
The session covered:
- how to fill out a SORA-based BVLOS application
- using updated population data for risk assessment
- examples of effective mitigations.
Watch the BVLOS webinar on YouTube.
Who should use SORA?
SORA is for drone operators who need approval for operations that have risks not yet fully covered by their risk management processes.
This includes operations like:
Steps in the SORA assessment process
The SORA assessment process includes the following steps:
- Concept of operations (CONOPS) development
- Ground risk class (GRC) assessment
- Air risk class (ARC) assessment
- Specific assurance and integrity level (SAIL) determination
- containment assessment.
Concept of operations
A concept of operations (CONOPS) outlines the planned operation by defining the:
- operational area
- contingency volume
- ground risk buffer.
Together these parts make up the operational volume.
Ground risk class assessment
A ground risk class (GRC) involves a:
- iGRC - the risk to people on the ground before you have considered any safety measures.
- fGRC - the risk to people on the ground after you have implemented safety measures, such as sheltering or parachute recovery systems.
You can work out the fGRC by:
- finding the highest population density in the operational volume, per square kilometre
- cross-referencing the best qualitative descriptor, ensuring it matches your operational area
- using the iGRC table located in TMI 2024-03 to determine the score:
- assessing mitigations such as sheltering (M1) or impact reductions (M2).
Population density
We use the latest Australian Bureau of Statistics (ABS) Census data sets to work out the highest population density per square kilometre.
M1 mitigations
An M1 mitigation refers to the ability to reduce the population within the operational volume.
M2 mitigations
An M2 mitigation refers to reducing the force of the drone when impacting a person.
Air risk class assessment
The air risk class (ARC) assessment looks at the risks to other airspace users and applies measures to reduce that risk.
To identify the ARC for the operational volume, you will need to determine the airspace encounter category (AEC). We base the AEC on the airspace type and likelihood of encounters. You can find a guide to ARC in section 4.4.3. of the Jarus guidelines on SORA.
Applying to reduce the air risk class
You can reduce the ARC in some circumstances.
To reduce ARC, you must show that you have reduced the likelihood of an encounter with another airspace user. We may accept some of the following mitigations to reduce the ARC:
- flight restrictions based on stakeholder engagement
- flying at night to reduce visual flight rules (VFR) traffic
- deconfliction plans.
Stakeholder engagement
Stakeholder engagement is essential for:
- identifying typical flying areas/routes
- understanding local air traffic volumes
- working with local airspace users, emergency services and relevant authorities to find risks
- creating operational restrictions and mitigations to reduce air risk.
Specific assurance and integrity level
SORA uses a risk scale, called a specific assurance and integrity level (SAIL) level (ranging from 1 to 6 in Roman numerals). This rating reflects the potential risks of the flight. Higher ratings mean stricter safety requirements for your:
- drone
- training
- risk management.
Operational safety objectives
SORA uses operational safety objectives (OSOs) to manage risks associated with an out-of-control situation. These are safety goals to prevent those situations from happening. We assess each OSO carefully for:
- integrity: the quality of the safety objective.
- assurance: the level of confidence in reaching the safety objective.
- robustness: the level of robustness combines integrity and assurance represented as four categories; optional, low, medium and high.
Containment
Containment considers the risks to people within the adjacent area if the OSOs fail. The adjacent area is the surrounding space where the operation is expected to end if a loss of control occurs, beyond the ground risk buffer.
Containment includes requirements based on the population at risk within the adjacent area.
Emergency response plan
An emergency response plan controls consequences once the drone is out of control. It details how local authorities, such as fire brigade and air traffic control, will respond. The aim is to limit the residual effects and harm from an out-of-control event such as a drone crash.
BVLOS training areas
We encourage applicants to seek approval of an area for the purpose of training and testing. We will generally issue these approvals for the validity of your ReOC. This allows you to continue to train new staff and maintain competency and currency for all staff operating BVLOS.
We recommend you choose a low-risk location that is only as large as necessary for BVLOS training and testing.
Demonstrating compliance
To show compliance with SORA, operators must:
- submit a complete SORA-based safety case, including the application form and checklist
- give evidence supporting claimed mitigations for ground and air risk
- give evidence or declaration for OSOs at the determined SAIL
- meet the containment requirements for the operational area.
Population density determination
We accept population density maps that use the latest Australian Bureau of Statistics (ABS) Census data to identify the population density for a specific area.
The ABS produce population density maps with the smallest grid size of 1 km by 1 km.
For operations near populated areas, SORA requires:
- higher levels of mitigation, such as sheltering or exclusion zones
- more robust contingency plans
- consideration of dynamic populations, such as crowds and roadways.
Working out drone characteristics and dimensions
To work out the characteristics and dimensions of a drone for the SORA ground risk class:
- use wingspan for aeroplane and powered-lift aircraft
- use blade diameter for single-rotor helicopters
- use the maximum distance between blade tips for multi-rotor helicopters
- ensure the maximum speed reflects the highest possible commanded airspeed.
If there's a mismatch between dimensions and speed, use the higher value to assign your drone category.
We have found certain drones that meet compliance requirements for certain operations.
Documents for an application
If you wish to apply using SORA, you must submit:
- an application form and applicable checklists
- evidence supporting claims and requirements.
We might ask for more documents after the assessment process if required.
For complex operations, we recommend arranging a pre-application meeting.
If you're ready to apply:
- Follow the steps to apply for or renew your BVLOS approval.
- Explore the broad area BVLOS trial to see if your operation qualifies for new streamlined application pathways.
- Check the rules for flying over and near people to see if they apply to your operation.
Incomplete applications
An incomplete application means we have found areas where we need more information or clarification to meet the requirements of regulation 11.030 of the CASR.
Some common challenges operators face when completing a SORA, include:
- miscalculating fGRC or ARC
- lack of supporting evidence for ground risk mitigations
- inadequate mitigations to reduce encounter rate for ARC reduction
- lack of supporting evidence for OSO compliance
- failure to adequately describe the CONOPS.