SORA SAIL Levels Explained for UK Drone Operators

SAIL — the Specific Assurance and Integrity Level — is the central output of the SORA methodology. Once you know your SAIL, you know how much rigour your safety case requires. This guide explains what the SAIL is, how it is derived, and what each level demands.

What SAIL measures

SAIL is not a risk score in itself. It is a measure of the level of confidence — the integrity and assurance — that the authority needs in your operation given its assessed risk. A higher SAIL means more must go right, more must be proven, and the consequences of failure are managed more rigorously.

How the SAIL is derived

The SAIL comes from a simple lookup: you take your final Ground Risk Class (GRC) and your residual Air Risk Class (ARC), and read the SAIL from the intersection in the methodology's table. Both inputs are already the product of mitigation work:

• The final GRC reflects the intrinsic ground risk after M1 and M2 mitigations.
• The residual ARC reflects the air risk after strategic and tactical mitigations.

Because both inputs can be lowered by mitigation, the SAIL is something you can influence by design — not a fixed verdict.

The six SAIL levels

SAIL ranges from I to VI:

• SAIL I–II — lower-risk operations. The Operational Safety Objectives can often be met at low robustness, sometimes by self-declaration with supporting procedures.
• SAIL III–IV — moderate-risk operations. More OSOs apply and at higher robustness; assurance evidence (test results, documented procedures, competency records) becomes more important.
• SAIL V–VI — higher-risk operations. Many OSOs apply at high robustness, often requiring independent verification and design-assurance-level evidence. These approach the rigour seen in certified aviation.

SAIL and the Operational Safety Objectives

The practical effect of the SAIL is felt through the Operational Safety Objectives (OSOs). The methodology provides a matrix: for each OSO, and each SAIL, it states the robustness required — optional, low, medium or high. OSOs cover areas such as:

• Technical reliability of the unmanned aircraft system.
• Crew training and competence.
• Procedures and checklists for normal, contingency and emergency situations.
• Maintenance and configuration management.
• Human factors and external services (such as weather and airspace information).

At low SAIL, many OSOs may be optional or require only basic evidence. At high SAIL, the same OSOs demand rigorous integrity and independent assurance.

Robustness: integrity plus assurance

It is worth restating because it is so often misunderstood. Robustness has two dimensions. Integrity is whether the measure actually achieves its safety aim. Assurance is whether you can prove that it does, to the level expected. A measure can have high integrity but low assurance if you cannot evidence it — and that will limit the credit you receive.

Lowering the SAIL by design

If your initial SORA produces a SAIL that is impractical to satisfy, the methodology invites you to iterate. Shrinking the operational volume, adding a parachute, segregating airspace, or fielding detect-and-avoid can each pull the GRC or ARC down, and with them the SAIL. A well-engineered operation often lands a tier or two lower than the naive first pass.

Practical takeaways

Treat the SAIL as the design target of your safety case. Identify it early, then work backwards: which mitigations get you to a SAIL you can realistically support with evidence? The SAIL/OSO matrices are refined between methodology editions, so always build from the version the CAA currently references and treat older tables as illustrative.

Understood this way, the SAIL is not a barrier but a roadmap — it tells you precisely how much evidence you need and where to focus your effort.