IRELAND · SORA 2.5 · Containment
Containment and Adjacent Areas: Detailed Example of SORA 2.5
Within the Specific Operations Risk Assessment (SORA) 2.5 methodology, containment plays a vital role in ensuring that an Unmanned Aircraft System (UAS) remains within its established operational boundaries. This article outlines the practical application of containment, including the careful analysis of adjacent areas such as the adjacent ground area and adjacent airspace. Emphasis is placed on developing credible worst-case scenarios, linking these scenarios to operational procedures in the Concept of Operations (ConOps), and systematically documenting evidence to effectively manage operational risks under the EASA framework as applied in Ireland.
Visualisation of Operational Boundaries
To achieve a verifiable and credible assessment of containment within the SORA 2.5 framework, it is essential to precisely visualise all relevant operational volumes. This includes rendering the flight geography, contingency volume, operational volume, and ground risk buffer as separate, clearly distinguished map layers. The adjacent ground area must also be defined separately based on operational and safety analysis tailored to the specific operation. Key technical details such as coordinates, altitudes, reference systems (e.g., WGS84), map versions, and tolerance values must be thoroughly documented. These measures ensure that the containment analysis is transparent, auditable, and reproducible by the Irish Aviation Authority (IAA) upon review.
- Visualisation and documentation of distinct operational zones as separate map layers
- Recording altitude and coordinate references with associated tolerances
- Use of up-to-date and authoritative mapping materials as substantiation
Development and Analysis of Loss-of-Containment Scenarios
A crucial element of containment evaluation under SORA 2.5 is the comprehensive description of credible worst-case loss-of-containment scenarios. These include navigation failures, loss of command and control (C2), fly-away incidents, and system malfunctions leading to uncontrolled flight. It is essential to analyse which persons, infrastructure, and airspace segments within the adjacent ground area and adjacent airspace could be affected in such scenarios. This involves identifying both technical and human failure causes while considering both likely and conservative flight path deviations. The analysis supports the assignment of intrinsic Ground Risk Class (iGRC), final Ground Risk Class (final GRC), and facilitates accurate risk mitigation planning.
- Analysis of technical and human causes for loss-of-containment
- Development of worst-case flight paths including adjacent ground area and adjacent airspace
- Identification of potential persons and assets affected outside the immediate flight geography
- Documentation of assumptions and limitations that frame the analysis
Incorporating Containment in Operational Procedures and Documentation
Containment measures must be tightly integrated within the Concept of Operations (ConOps) and operational procedures. This includes clear descriptions of geofencing implementations, flight termination systems, ongoing monitoring mechanisms, and operational safety buffers. The operational manual should detail instructions for normal, contingency, and emergency situations, particularly addressing scenarios where containment may be compromised. Explicitly documenting system dependencies and potential failure impacts is vital, alongside the required mitigative actions the UAS operator must undertake. This thorough approach not only strengthens operational robustness but also provides demonstrable evidence during IAA audits, including assessments related to the Air Risk Class (ARC).
- Inclusion of geofencing and flight termination systems within the ConOps
- Procedures addressing normal operations and emergency containment breaches
- Documentation covering configuration management, testing results, and maintenance
- Clear definition of operator actions upon system failure and fallback scenarios
Frequently asked questions
Is geofencing alone sufficient for containment?
Geofencing alone does not guarantee sufficient containment. Its reliability, independence from other systems, configuration, and testing protocols must meet the containment robustness level required by SORA 2.5. Without demonstrated robustness and validation, geofencing cannot serve as the sole containment mitigation.
Why must adjacent airspace be included in the SORA risk assessment?
Because loss-of-containment events may affect air traffic and persons located outside the defined operational volume, including adjacent airspace. Explicitly assessing adjacent airspace is necessary to understand and mitigate all relevant risks posed to manned aviation and the public.
What documents and procedures are essential for a containment review?
Containment must be formally recorded in the Concept of Operations (ConOps), featuring procedures for normal, contingency, and emergency scenarios. Supporting documentation should include configuration management records, testing and validation reports, maintenance logs, and comprehensive flight briefings to demonstrate operational readiness and safety.
How are the ground risk buffer and adjacent ground area defined?
The ground risk buffer is a protective zone surrounding the operational volume designed to minimize risks to people and infrastructure on the ground. The adjacent ground area includes locations just outside the operational volume that could be impacted under worst-case scenarios. Both are defined through detailed operational context analysis and risk assessments as mandated under SORA.