IRELAND · SORA 2.5 · GRC
Understanding GRC and Ground Risk Mitigations: A Detailed SORA 2.5 Guide for Drone Operators
Under European UAS regulations, including Irish implementation via the IAA, thoroughly documenting and implementing Ground Risk Mitigations (GRC) is critical for safe operations. The Specific Operations Risk Assessment (SORA) version 2.5 provides a methodical process to identify and reduce risks during drone flights. This article uses a practical example of an inspection flight over an industrial facility, detailing intrinsic GRC, mitigation substantiation, and calculation of the Final GRC.
Example Operation and Intrinsic GRC (iGRC)
For your specific operation, identify the most applicable intrinsic Ground Risk Class (iGRC) using the SORA 2.5 reference tables, ensuring you record the table reference, version, and all relevant assumptions. Include clear citations of data sources and dates for environmental and population figures referenced to support the risk assessment. This approach promotes transparency and facilitates regulatory review by the IAA.
Remember that SORA is a living framework regularly updated by EASA. Always use the latest official SORA 2.5 release available on the EASA website to avoid basing your risk assessment on outdated assumptions or mitigation levels, which can lead to erroneous safety conclusions.
- Maximum Characteristic Dimension (MCD): largest drone dimension affecting impact severity.
- Maximum Speed: impacts potential severity of ground impact and size of safety buffers.
- Flight Geography: includes spatial constraints, land use, and no-fly zones relevant to the operation.
- Contingency Volume: airspace volume where the drone may move unexpectedly during failures.
- Ground Risk Buffer: safety perimeter to protect uninvolved persons on the ground.
- Presence of Non-Involved Persons: assessment of whether the operation area includes persons not involved in the operation.
Substantiating Ground Risk Mitigations
For example, a risk mitigation such as an exclusion zone must be clearly defined with documented maps, assigned responsible personnel, access control measures, and a logging system. Lack of these elements undermines the mitigation’s integrity and assurance level. Such mitigations must be clearly integrated and verifiable within your Operations Manual or Standard Operating Procedures.
Assess the robustness of each mitigation carefully. Robustness means the mitigation consistently performs effectively across varying operational scenarios and potential system failures. Robust mitigations strengthen the credibility of your safety case when reviewed by the IAA.
- Definition of the mitigation and the expected GRC reduction it provides.
- Detailed procedures with named responsible roles and decision-making criteria.
- Robustness level indicating resilience to operational variability and failures.
- Supporting evidence such as procedural documents, audits, training records, and certificates, including version control, ownership, and expiry.
Calculating and Verifying the Final GRC
The Final GRC calculation must be replicable and consistent with your approved Concept of Operations (ConOps). Maintaining coherence across your ConOps, Operations Manual, flight preparation documents, and risk mitigation evidence helps avoid inconsistencies and facilitates the IAA’s review and approval process.
Store all supporting documents and calculations securely—using platforms like DroneManual can help structure your documentation—to enable prompt access and transparency during inspections or audits.
- Apply risk reductions only where both the integrity and assurance levels meet or exceed the required thresholds.
- Document the methodology and values used for the Final GRC calculation clearly in your operations dossier.
- Ensure alignment and consistency of mitigations and assumptions across all operational documentation.
- Regularly review your GRC and associated mitigations through an Emergency Response Plan (ERP) or similar process to reflect changes in operational environment, equipment, or regulatory requirements.
Frequently asked questions
Is an exclusion procedure automatically a valid Ground Risk Mitigation?
No. Its applicability and effectiveness must be assessed within your specific operational context and in line with SORA 2.5 requirements. Without sufficient integrity and assurance, an exclusion procedure will not meet regulatory standards.
Can I use the GRC value from this example for my own operation?
No. This example is intended to illustrate correct documentation practice. You must perform a GRC calculation tailored to your operation, based on current data and the latest SORA tables.
How often should I review my GRC and related mitigations?
Regular reviews are essential, especially when there are operational changes, updates to the UAS, or new regulatory guidance. Incorporate these into your Emergency Response Plan (ERP) to maintain continuous safety assurance.
What distinguishes intrinsic GRC from Final GRC?
Intrinsic GRC represents the initial risk without mitigation measures applied. Final GRC is the residual risk after all validated mitigations have been factored in.