IRELAND · IAA / EASA · SORA 2.5 · ARC
SORA 2.5: Detailed Example of ARC and Air Risk Mitigations for Drone Operators
Under European UAS regulations applicable in Ireland, the Specific Operations Risk Assessment (SORA) framework is a vital tool for methodically evaluating and managing air risk associated with specific drone operations. The Air Risk Classification (ARC) in SORA 2.5 quantifies the probability of encounters between the UAS and manned aircraft within the operational airspace. Assigning an ARC involves detailed airspace analysis, utilisation of authoritative data sources, and a coherent mitigation strategy combining both strategic and tactical measures to effectively reduce air risk in a demonstrable and controlled manner.
Motivating the Initial ARC: Thorough Airspace and Traffic Analysis
Establishing the Initial ARC is the first step in the air risk assessment process and requires a detailed characterisation of the operational airspace. Operators must identify the applicable airspace classification (for example, Classes C or D), including the lateral and vertical limits where the drone will operate. Furthermore, they should identify nearby aerodromes, controlled airspace zones, and prominent air traffic routes that may intersect or be proximate to the UAS activity.
The traffic density and traffic types using this airspace during intended operation times must be analysed. Data is typically gathered from official sources such as the Irish Aeronautical Information Publication (AIP), IAA-designated geozones specifically established for UAS operations, and information from national air traffic control providers. This comprehensive evidence base must substantiate the choice of Initial ARC category (A to D), covering the entire operational volume and reflecting the most demanding conditions expected during flight. Proper documentation ensures transparency and supports subsequent risk mitigation steps.
- Detailed evaluation of applicable airspace classes and precise operational boundaries
- Assessment of traffic density, including types and peak traffic times
- Utilisation of authoritative data sources: AIP, IAA geozones, ATC information
- Clear documentation of assumptions, uncertainties, and current data sets
Strategic Mitigations and Substantiation of the Residual ARC
Strategic mitigations are preventative actions planned prior to flight to reduce the probability of encounter with manned aviation. Examples include scheduling operations during known periods of low air traffic, restricting the operational area to less congested airspace, or coordinating the activity formally with air traffic control (ATC) or other relevant authorities.
It is crucial that these strategic mitigations are robustly evidenced with reliable operational data and documented proof. Merely aiming for a lower ARC without substantiating the mitigation’s effectiveness is insufficient. Only after the strategic mitigations have been convincingly justified can the Residual ARC be established, representing the remaining level of air risk. This Residual ARC then informs the subsequent operational risk controls.
- Predefined temporal and spatial operational restrictions
- Formal coordination and agreements with ATC and relevant stakeholders
- Supporting evidence from operational data and monitoring records
- Transparent derivation of Residual ARC per SORA 2.5 methodology
Tactical Mitigations and Tactical Mitigation Performance Requirement (TMPR)
Tactical mitigations are active measures implemented during the flight to detect and avoid manned aircraft, including collaborative (e.g., equipped with ADS-B) and non-collaborative traffic. These require effective use of onboard or ground-based detection systems such as radar, ADS-B receivers, or visual lookout by suitably trained observers. Additionally, clear communication procedures and formalised decision frameworks, including avoidance manoeuvres, must be in place.
These mitigations must satisfy the Tactical Mitigation Performance Requirement (TMPR) aligned with the assessed air risk level. Comprehensive documentation detailing used equipment, assigned responsibilities, communication channels, decision-making timelines, and contingency plans for equipment or procedural failure is fundamental. Operator training and scenario rehearsals also contribute to ensuring mission safety and compliance with SORA 2.5 standards.
- Employment of certified detection equipment covering the operational airspace
- Clear and prompt decision-making by trained personnel
- Established communication and deconfliction procedures involving third parties
- Robust failure management strategies with fallback provisions
Frequently asked questions
Is flying at a lower altitude enough to reduce the ARC?
No. Flying at a lower altitude alone does not automatically reduce the ARC. SORA 2.5 requires convincing evidence supporting the effectiveness of strategic mitigations. Without this evidence, a reduction in air risk and corresponding ARC cannot be justified.
What distinguishes Initial ARC from Residual ARC?
The Initial ARC reflects the air risk category based on the raw airspace environment without mitigation. The Residual ARC is established after credible strategic mitigations have been applied, showing the lowered risk of encounters with manned aircraft during the operation.
How can I demonstrate that strategic mitigations are effective?
Effectiveness can be documented through air traffic data, proof of coordination with ATC or other relevant authorities, formal agreements, and monitoring outcomes. Without such verified evidence, mitigations do not justify a lower ARC.
When must tactical mitigations be applied under SORA 2.5?
Tactical mitigations are required when the Residual ARC still indicates a significant risk of encounter with manned aircraft that must be actively reduced during the operation. Compliance with the Tactical Mitigation Performance Requirement (TMPR) is then necessary for detection, communication, and decision-making capabilities.