SORA 2.5 · GRC
GRC and Ground Risk Mitigations: Detailed SORA 2.5 Example for Drone Operators
In the context of UK regulations for unmanned aircraft systems (UAS), it is essential to correctly document and implement Ground Risk Mitigations (GRC). The Specific Operations Risk Assessment (SORA) 2.5 provides a structured approach for identifying and mitigating risks during UAS operations. This article presents a detailed example of an inspection flight over an industrial area, focusing on intrinsic GRC, the substantiation of mitigations, and deriving the Final GRC.
Example Operation and Intrinsic GRC (iGRC)
Using operational data, select the most relevant intrinsic Ground Risk Mitigation (iGRC) scenario from the SORA 2.5 assessment tables. Always record the table reference, version number, and the foundational assumptions. Additionally, cite sources and reference dates for environmental and population data to ensure your risk assessment is transparent and verifiable.
Keep in mind that SORA 2.5 is regularly updated; always refer to the latest official UK CAA endorsed release or guidance. Relying on outdated assumptions or GRC values may result in inaccurate risk evaluations.
- Maximum Characteristic Dimension (MCD): the largest dimension of the UAS, affecting potential impact risk.
- Maximum Speed: influences impact severity and required risk buffers.
- Flight Geography: encompasses the location, spatial constraints, and no-fly zones relevant to the operation.
- Contingency Volume: the airspace within which the UAS might move during failures or emergencies.
- Ground Risk Buffer: a safety zone established to protect people on the ground.
- Presence of Non-Involved Persons: identifying areas where no uninvolved persons are present to minimise risks.
Substantiation of Ground Risk Mitigations
For example, an exclusion zone procedure lacking a clear map, designated responsible personnel, controlled access measures, and a registration system does not meet required integrity and assurance standards. Such controls must be demonstrably effective and operational, as documented within the Operations Manual or operational procedures.
Assess the robustness of each mitigation measure. Robustness reflects how well a mitigation withstands operational variations or equipment malfunctions and whether it enjoys broad support and systematic enforcement within the operational team. Demonstrating robustness enhances the UK CAA's confidence in the safety arrangements.
- Specify the mitigation and quantify its expected reduction effect on GRC.
- Provide detailed procedures, assigned responsible roles, and clear decision criteria.
- Robustness level indicating resilience against operational deviations and failures.
- Supporting evidence, including documents, audit results, training records, and certificates, complete with versioning, ownership, and validity periods.
Deriving and Verifying the Final GRC
Ensure the calculation and application of the Final GRC are reproducible and consistent with the approved Concept of Operations (ConOps). This alignment prevents contradictions and supports obtaining UK CAA Operational Authorisation.
Maintain all underlying evidence and calculations in a secure management system such as DroneManual or an approved documentation platform, so that inspectors can review them when required.
- Reduce the GRC figure only if documented integrity and assurance meet the required levels.
- Clearly record the computational methods and input data within your operational dossier.
- Verify that mitigation measures are consistently documented across the ConOps, Operations Manual, pre-flight preparations, and evidence registers.
- Perform regular reviews as part of your Emergency Response Plan (ERP) to accommodate changes in operational conditions or regulatory requirements.
Frequently asked questions
Is an exclusion procedure automatically a valid Ground Risk Mitigation?
No. The validity and effectiveness of an exclusion procedure must be assessed based on the specific operational context and SORA 2.5 criteria. Mitigations lacking sufficient integrity and verifiable assurance do not satisfy regulatory requirements.
Can I adopt the GRC value from this example for my own operation?
No. This example is provided to illustrate correct documentation and risk assessment structure. You must perform your own GRC calculation tailored to your operation using up-to-date data and applicable SORA tables.
How often should I review my GRC and mitigations?
GRC and associated mitigations should be reviewed regularly, especially following changes in the operational environment, aircraft, or relevant regulations. Regular review is a crucial part of maintaining an effective Emergency Response Plan (ERP).
What is the difference between intrinsic GRC and Final GRC?
Intrinsic GRC represents the baseline risk inherent in the operation before applying any mitigations. Final GRC is the remaining risk after all valid Ground Risk Mitigations have been applied.