IRELAND · IAA / EASA · SORA 2.5 · GRC
Ground Risk Mitigations and GRC: Detailed SORA 2.5 Example for Drone Operators
Within the European Union Aviation Safety Agency (EASA) regulatory framework applied in Ireland, correctly documenting and implementing Ground Risk Mitigations (GRC) is critical for safe unmanned aircraft system (UAS) operations. The Specific Operations Risk Assessment (SORA) 2.5 methodology provides a structured way to identify and mitigate risks during drone missions. This article presents a worked example of an inspection flight over an industrial site, focusing on intrinsic GRC, substantiation of mitigations, and deriving the Final GRC in line with IAA expectations.
Example Operation and Intrinsic GRC (iGRC)
Start by selecting the most appropriate iGRC scenario from the SORA 2.5 tables based on your operation’s data. Always document the table reference, version number, and underlying assumptions for traceability. Include sources and reference dates of environmental and population data to ensure transparency and verification of your risk assessment.
SORA 2.5 is regularly updated; therefore, always consult the latest official edition published by EASA. Using outdated assumptions or GRC values can lead to inaccurate risk evaluations, which may not satisfy the Irish Aviation Authority (IAA) during assessment.
- Maximum Characteristic Dimension (MCD): the largest physical dimension of your UAS, relevant to impact risk assessment in a crash scenario.
- Maximal Speed: impacts the severity of an impact and determines necessary safety buffers.
- Flight Geography: covers the operating location, spatial limitations, and any no-fly zones relevant to the mission.
- Contingency Volume: the airspace volume within which the UAS may move during a failure or emergency situation.
- Ground Risk Buffer: a protective zone on the ground around the UAS to reduce the hazard to uninvolved persons.
- Presence of Uninvolved Persons: identification of areas without persons to minimize risk exposure.
Substantiating Ground Risk Mitigations
For example, a segregation procedure lacking a clear map, defined responsible personnel, access control, and logging does not meet the required integrity and assurance levels. Such elements must be demonstrably and operationally assured within the Operations Manual or relevant Operational Procedures.
Assess the robustness of each mitigation measure. Robustness refers to the degree to which mitigations remain effective under varying operational conditions and contingencies. This builds the IAA’s confidence in your safety management.
- Mitigation measure and the expected reduction in GRC
- Detailed procedure including designated responsible roles and specific decision criteria
- Robustness level: how resilience the mitigation is against operational deviations or failures
- Evidence: references to documents, audits, training records, certificates, including version, owner, and validity period
Deriving and Verifying the Final GRC
Ensure that the calculation and application of the Final GRC is reproducible and aligns with the approved Concept of Operations (ConOps) for your operation. Consistency avoids contradictions and supports obtaining approval from the IAA as the competent national authority for UAS in Ireland.
Store all supporting evidence and calculations securely in DroneManual or an equivalent document management system to provide transparency and facilitate inspection by IAA officials upon request.
- Apply risk reductions only when both integrity and assurance documentation meet the required standards.
- Clearly document calculation methods and all values used within the operational dossier.
- Verify consistency of mitigations across all relevant documentation: ConOps, Operations Manual, flight preparation records, and evidence logs.
- Conduct periodic reviews as part of your Emergency Response Plan (ERP) to incorporate new operational contexts or regulatory changes
Frequently asked questions
Is a segregation procedure automatically a valid Ground Risk Mitigation?
No. Its applicability and effectiveness must be assessed in the specific operational context against the requirements of SORA 2.5. A mitigation lacking sufficient integrity and demonstrable assurance does not comply.
Can I reuse the GRC figure from this example for my own operation?
No. This is an illustrative example showing the correct documentation structure. Each operator must calculate their own GRC based on current facts and the relevant SORA tables.
How often should I review my GRC and mitigations?
Regular reviews are essential, especially when changes occur in operational environment, the UAS used, or regulations. This process should be incorporated in your Emergency Response Plan (ERP).
What is the difference between intrinsic GRC and Final GRC?
Intrinsic GRC represents the baseline ground risk in the operational context before considering mitigations. Final GRC is the residual risk remaining after all valid mitigations have been applied.