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 is essential to ensure an Unmanned Aircraft System (UAS) remains within its defined operational boundaries. This article explains practical implementation of containment measures and adjacent area analysis, such as adjacent ground areas and adjacent airspace. Special focus is placed on worst-case scenario development, their connection to operational procedures, and documenting evidence to manage risk effectively during UAS operations in Ireland under the EASA framework.
Visualisation of Operational Boundaries
A credible and verifiable containment assessment as required by SORA 2.5 depends on precise visualisation of all relevant operational volumes. These include the flight geography, contingency volume, operational volume, and ground risk buffer, each clearly represented as separate layers on maps. Furthermore, the adjacent ground area should be explicitly defined based on specific operational and safety considerations. Detailed documentation of coordinates, altitude references, geodetic datums, chart versions, and tolerances is crucial. This ensures the analysis is transparent, reproducible, and can be reliably reviewed by the Irish Aviation Authority (IAA).
- Visualise and document distinct operational zones as separate map layers
- Record accurate altitude and coordinate reference systems with tolerances
- Use current and authoritative aeronautical charts for substantiation
Development and Analysis of Loss-of-Containment Scenarios
A thorough containment strategy requires detailed assessment of credible worst-case scenarios where the UAS may breach containment boundaries. Common scenarios include navigation errors, loss of command and control (C2), fly-aways, or system malfunctions causing uncontrolled flight. It is vital to analyse which individuals, structures, and airspace segments within the adjacent ground area and adjacent airspace might be impacted. Identification of both technical and human failure modes helps determine realistic and conservative flight path deviations. This detailed evaluation underpins the risk assessment presented to the IAA for Specific category operations requiring SORA.
- Analyse technical and human causes contributing to loss of containment
- Develop and map worst-case flight paths including all adjacent zones
- Identify potentially affected persons and assets beyond the direct operation area
- Document all assumptions and boundary conditions defining the analysis scope
Integration of Containment into Procedures and Documentation
Containment measures must be integrated seamlessly into the operational manual (ConOps) and operational procedures submitted to the IAA. Systems such as geofencing, flight termination, and real-time monitoring capabilities should be clearly described, including their operational reliability and limitations. The ConOps must include detailed instructions for normal operation as well as contingency and emergency procedures addressing containment failure scenarios. Specifying how system dependencies and failure impacts are managed ensures operational robustness. This documentation is essential evidence during evaluations such as the application for an Operational Risk Assessment (ORA) or Operations Risk Assessment (ORA) required by the IAA.
bullets=[
Describe geofencing and flight termination implementation within the ConOps
Define procedures for normal, contingency and emergency containment scenarios
Maintain records of configuration management, system tests, and maintenance activities
Frequently asked questions
Is geofencing alone sufficient to ensure containment?
No. Geofencing alone may not meet containment requirements unless it is demonstrably reliable, independent, properly configured, and thoroughly tested to the required robustness level. Operators must ensure geofencing complements other measures to form a resilient containment system.
Why must adjacent airspace be considered in a SORA containment analysis?
Because a containment failure could affect air traffic or persons on the ground in areas beyond the intended operational volume. Including adjacent airspace in the assessment is necessary for a comprehensive evaluation of hazards and mitigation measures as expected by the IAA.
What documentation supports a compliant containment evaluation?
Containment must be documented within the operational manual (ConOps) clearly outlining normal, contingency, and emergency procedures. Supporting documentation such as configuration control records, test reports, maintenance history, and briefing materials should be retained to prove system integrity.
How do I define the ground risk buffer and adjacent ground area in my SORA assessment?
The ground risk buffer is a protective zone around the operational volume that limits potential risks to people and infrastructure. The adjacent ground area includes locations directly outside the operational boundary that could be affected under worst-case scenarios. Both should be defined based on your operation's specific risk profile and context, and justified in your risk assessment.