IRELAND · IAA / EASA · SORA 2.5
SORA 2.5: Step-by-Step Guide for Drone Operators in Ireland
The Specific Operations Risk Assessment (SORA) is a structured process designed to assess the risks associated with planned Unmanned Aircraft System (UAS) operations in the Specific category. On 29 September 2025, the European Union Aviation Safety Agency (EASA) released version 2.5 of the SORA method as part of the AMC/GM to EU Regulation 2019/947. It is essential for UAS operators in Ireland to clearly specify the SORA version applied, ensuring alignment with the Irish Aviation Authority (IAA) expectations and avoiding confusion with earlier versions or other national requirements. This guide outlines the stepwise application of SORA 2.5 adapted to the Irish regulatory environment.
1. Define the Concept of Operations (ConOps) Clearly
The initial stage involves producing a comprehensive ConOps document that precisely details the planned UAS operation. This includes identifying the drone model(s), the operational volume—including its geographic location and altitude limits—the airspace class involved, relevant crew members, communication arrangements, and both standard operating procedures and emergency response procedures (ERP). A clearly established ConOps provides the foundation for a replicable and consistent risk assessment process in line with EASA and IAA expectations.
- Define the operational volume including coordinates and altitude.
- Specify the airspace class and any applicable national airspace restrictions enforced by the IAA.
- Detail the UAS platform, onboard sensors, and control systems employed.
2. Evaluate Ground Risk and Air Risk Using SORA Methodology
Using the ConOps, the operator assesses the risk to people on the ground and to other airspace users. SORA 2.5 applies updated classification schemes and modelling techniques for ground risk, such as Population Density and Vulnerable Areas, and air risk factors like air traffic density and airspace classification. It is critical to document all assumptions, data sources such as Irish Census or national vulnerability maps, and applied risk models transparently. Only mitigations that are implemented, effective and verifiable should be included in the risk estimates to maintain regulatory compliance.
- Apply current EASA-approved methods and IAA-acknowledged data sources for risk quantification.
- Explicitly document all input data sets, including national geographic and statistical references.
- Incorporate only established and demonstrable mitigation measures in the risk modelling.
3. Determine the SAIL Level and Corresponding Operational Safety Objectives (OSOs)
The combination of ground and air risk assessments results in a determination of the Specific Assurance and Integrity Level (SAIL) necessary for the operation. The SAIL corresponds with specified operational safety objectives (OSOs) that must be met to mitigate identified risks. Each OSO should be documented with supporting evidence, the party responsible for compliance, and any pending mitigations or approvals. This step ensures transparent risk governance and accountability under both EASA and Irish national oversight.
- Identify the operation’s SAIL category according to the SORA 2.5 framework.
- Establish applicable OSOs that address system robustness, integrity, and assurance requirements.
- Maintain detailed records of evidence, responsible personnel, and outstanding compliance tasks.
4. Implement Containment Strategies and Finalise Evidence Compilation
Containment entails both technical and procedural measures that ensure the UAS operation remains within predefined operational and contingency volumes, thus constraining risk exposure to acceptable levels. This includes defining the operational volume on the ground and in airspace, alongside the ground risk buffer and contingency volumes as per SORA 2.5 guidance. Thorough evaluation of system dependencies, mitigation robustness, and emergency response protocols (ERP) is essential. The operator must assure that the ConOps, operational manual (OM), ERP, test documentation, and annexes consistently reflect all chosen mitigations and operational limits before presenting the dossier for IAA review.
- Define containment areas integrating operational volume, contingency volume, and ground risk buffer in relation to Irish geography.
- Evaluate and mitigate technical dependencies on navigation, detect-and-avoid, and communication systems.
- Ensure all operational documentation (OM, ERP, test results) align to support the containment and OSO fulfilment.
Frequently asked questions
Is SORA 2.5 the latest version recognised by the IAA?
Yes. EASA introduced SORA 2.5 in September 2025 under AMC/GM to EU Regulation 2019/947. The IAA recognises this as the applicable version for Specific category operations; however, operators should confirm any transitional provisions or national adaptations directly with the IAA.
Can DroneManual provide fully approved SORA risk assessments for the IAA?
No. DroneManual supports the structured development of operational dossiers and evidence gathering but does not provide official approvals. Responsibility for assumptions, calculations, and submission to the IAA rests with the UAS operator or their appointed consultant.
What is the role of containment in the SORA 2.5 methodology?
Containment is key to technically limiting the UAS operation's spatial boundary to keep the risk within acceptable levels. This protects people on the ground and other airspace users by ensuring the operation does not extend beyond safe operational volumes defined via operational volume, contingency volume, and ground risk buffer concepts.
How does SORA 2.5 enhance transparency in risk management?
SORA 2.5 requires operators to document operational safety objectives (OSOs) alongside traceable evidence and assigned responsibilities, creating transparent, auditable risk governance aligned with EASA regulations and IAA oversight.
What distinguishes SORA from PDRA in Ireland’s Specific category?
SORA is a tailored risk assessment process used for complex Specific category operations requiring an individual risk assessment. PDRAs (Pre-Defined Risk Assessments) are standardised risk mitigation packages pre-approved by EASA and accepted by national authorities like the IAA to simplify authorisation for recurrent, lower-risk operations.