UK SORA 2.5 · Containment
Containment and Adjacent Areas: A Detailed Example of UK SORA 2.5
Within the UK Specific Operations Risk Assessment (SORA) 2.5 methodology, containment is crucial for safely keeping an Unmanned Aircraft System (UAS) within defined operational boundaries. This article explains how containment and the analysis of adjacent areas, such as adjacent ground area and adjacent airspace, can be practically applied. Special attention is given to developing worst-case scenarios, linking these with operational procedures, and documenting evidence to manage risks in UAS operations.
Visualisation of Operational Boundaries
For a verifiable and credible assessment of containment within UK SORA 2.5, accurately visualising all relevant operational volumes is essential. This requires that the flight geography, contingency volume, operational volume, and ground risk buffer are mapped as distinct, clearly defined layers. The adjacent ground area should also be separately defined based on the operational and safety risk analysis. It is critical to document technical details such as coordinates, altitudes, reference systems, map versions and tolerances applied. These steps ensure transparency, reproducibility, and facilitate review during authorisation processes.
Using precise and up-to-date mapping tools enhances the clarity of the containment assessment, aiding communication with the UK CAA during the Operational Authorisation process.
- Visualise and document distinct operational zones as separate map layers
- Record altitude and coordinate references with associated tolerances
- Apply current, authoritative mapping material as supporting evidence
Development and Analysis of Loss-of-Containment Scenarios
A fundamental part of containment is to thoroughly describe credible worst-case scenarios in which the UAS breaches the planned containment limits. Examples include navigation errors, loss of command and control (C2), fly-aways or system failures resulting in uncontrolled flight. It is crucial to assess which individuals, infrastructure, and sections of airspace within the adjacent ground area and adjacent airspace may be affected.
This analysis must identify both technical and human failure modes and distinguish between likely and conservative flight paths. Clear documentation of assumptions and limitations solidifies the risk assessment, a requirement when submitting a SORA to the UK CAA for Operational Authorisation.
- Analyse technical and human causes for containment loss
- Develop worst-case flight paths including adjacent ground area and airspace
- Determine potentially affected persons and assets outside direct flight area
- Document assumptions and limitations clearly for robust analysis
Integration of Containment into Procedures and Documentation
Containment measures must be integrated within the UAS operation manual (ConOps) and supporting procedures. This includes geofencing, flight termination systems, monitoring mechanisms, and operational safety buffers. The ConOps should clearly describe normal, contingency, and emergency procedures relevant to containment failure scenarios.
Explicit identification of system dependencies and failure consequences is essential, along with defined operator actions in those events. Such comprehensive procedure documentation supports operational resilience and provides evidence during UK CAA audits or when verifying compliance with PDRA01 or other relevant PDRAs under the UK Specific Category framework.
- Describe geofencing and flight termination procedures within the ConOps
- Develop procedures for normal, contingency and emergency containment situations
- Maintain documentation of configuration management, testing, and maintenance
- Record contingency actions for system failure and fallback scenarios
Frequently asked questions
Is geofencing alone sufficient for containment?
Geofencing by itself is not necessarily sufficient. Its effectiveness depends on the system’s reliability, independence, correct configuration and thorough testing in line with the required containment robustness level. Without robust configuration and validation, geofencing should not be the sole containment measure.
Why should adjacent airspace be included in the SORA analysis?
Because loss-of-containment can cause risks beyond the immediate operational volume, potentially affecting air traffic and people on the ground in adjacent areas. Including adjacent airspace explicitly in the risk assessment ensures a comprehensive safety evaluation.
Which documents and procedures are relevant for containment evaluation?
Containment must be documented within the UAS operational manual (ConOps) detailing procedures for normal, contingency, and emergency situations. Supporting documentation such as configuration management records, test reports, maintenance logs and flight briefings serve as evidence of containment system robustness.
How do I define the ground risk buffer and adjacent ground area?
The ground risk buffer is a safety zone around the operational volume designed to reduce risk to people and infrastructure. The adjacent ground area includes zones directly outside the operational volume which may be impacted in worst-case scenarios. Both are defined through operational context and risk assessment.