SORA Mitigation Measures: Reducing Risk in the UK

Mitigations are the heart of a workable SORA. They are the measures by which you take an operation that looks high-risk on paper and bring it down to a level you can credibly support. This guide explains the main mitigation families, how they earn credit, and why robustness is the deciding factor.

Why mitigations matter

The intrinsic risk of an operation — its starting GRC and initial ARC — is often higher than what you can realistically prove against. Mitigations let you reduce those figures, which lowers the SAIL and therefore the burden of evidence across all your Operational Safety Objectives. Choosing the right mitigations is the single biggest lever you have over the difficulty of an application.

Ground-risk mitigations

Two recognised mitigations reduce the Ground Risk Class:

M1 — reducing the number of people at risk

This mitigation lowers exposure. Approaches include:

• Restricting access to the overflown area so that fewer uninvolved people are present.
• Timing flights to avoid periods of high footfall.
• Using ground observers to confirm and maintain a clear area.
• Shrinking the operational volume and ground-risk buffer so fewer people sit beneath the flight path.

M2 — reducing the effect of ground impact

Where exposure cannot be removed, this mitigation reduces harm if an impact occurs. Examples include parachute recovery systems, frangible or energy-absorbing airframe design, and tethering. The aim is to lower the energy delivered to a person on the ground.

Air-risk mitigations

Two layers reduce the Air Risk Class:

Strategic mitigations

Applied before flight, these reduce the chance of meeting manned aircraft. They include operational restrictions (altitude limits, time windows, confined volumes) and structural measures such as airspace segregation or coordination with other airspace users. Strategic mitigations can lower the initial ARC to a lower residual class.

Tactical mitigations

Applied during flight, these enable collision avoidance once an encounter becomes possible. They include detect-and-avoid systems and, for some operation types, airspace observers. The performance required scales with the residual ARC — a higher residual ARC demands more capable tactical mitigation.

Robustness: the deciding factor

Every mitigation is assessed at a robustness level — low, medium or high — and the credit you earn depends on it. Robustness has two components:

• Integrity — does the mitigation genuinely deliver the claimed risk reduction?
• Assurance — can you demonstrate that it does, with appropriate evidence and, at higher levels, independent verification?

A parachute supported by test data, a maintenance schedule and trigger logic earns far more than one simply fitted and asserted. Mitigations claimed without evidence will be discounted by the assessor.

Common pitfalls

• Overclaiming — assuming high robustness without the evidence to back it.
• Double-counting — trying to take credit for the same effect under more than one mitigation.
• Ignoring failure modes — for example, claiming a parachute mitigation without addressing deployment reliability at low altitude.
• Vague ground-risk buffers — failing to justify the area assumptions that underpin M1.

Designing your mitigation strategy

Start from your intrinsic GRC and initial ARC, identify the SAIL they imply, and decide whether that SAIL is achievable. If not, look for the mitigations that move the needle most for the least cost and risk: often a smaller operating volume (M1) and airspace segregation (strategic) are the cleanest wins, with parachutes and detect-and-avoid reserved for where they are genuinely needed.

The specific reduction values and robustness expectations are refined between methodology editions, so always work from the version the CAA currently references and treat older worked examples as illustrative. Well-chosen, well-evidenced mitigations turn an impossible-looking operation into an achievable one — that is what they are for.