SORA SAIL III vs SAIL IV: what changes for BVLOS operators

For a BVLOS operator, SAIL III and SAIL IV are not two service tiers to choose between. They are outcomes of a risk assessment under the Specific Operations Risk Assessment (SORA) method. The difference matters: SAIL IV brings a higher assurance bar for applicable operational safety objectives (OSOs), and meeting it can take more evidence, engineering and review. But aiming for IV before the operation has been assessed can add work without reducing the risks that actually drive the case.

What SAIL measures

SORA considers the proposed operation, including its ground and air risks, and the mitigations used to reduce those risks. The assessment produces a Specific Assurance and Integrity Level, or SAIL. It informs the robustness expected for the applicable OSOs: the safety objectives an operator must address to support the operation.

SAIL is not a general grade for an aircraft, an operator or a mission’s ambition. Nor is it a substitute for describing the operation clearly. A BVLOS route over a controlled site and one near people, obstacles or other airspace users may present different hazards. The operating environment, aircraft, procedures and mitigations all matter. The resulting SAIL follows from the assessment; it is not a label an operator can simply select.

What changes between III and IV

The practical distinction is the level of assurance expected. SAIL IV generally calls for more robust substantiation of applicable OSOs than SAIL III. That can put greater demands on evidence that procedures, personnel, aircraft and mitigations are adequate for the operation. The exact work depends on which objectives apply and how the safety case addresses them. There is no single paperwork list that fits every mission.

That higher bar can affect design decisions early. An operator may need to explain how a mitigation works, how it is maintained and how its effectiveness is supported. A statement that a risk is controlled is not the same as evidence that the control is suitable and implemented. At SAIL IV, weak assumptions are more likely to become costly gaps to close if they are left until late in the authorization process.

SAIL III is not a shortcut or a lesser form of safe operation. It still requires the operator to address applicable objectives at the assurance level set by the assessment. Conversely, SAIL IV is not automatically safer in practice just because its assurance requirements are higher. A well-supported case depends on the hazards, the controls and the quality of the evidence—not on the Roman numeral alone.

Regulatory overhead follows the case

Stepping up from III to IV can mean additional analysis, documentation, testing or independent scrutiny, depending on the operation and the means used to demonstrate compliance. It can also affect project time and the coordination needed among the operator, technical contributors and competent authority. Operators should not assume that a SAIL IV case will follow a fixed timetable or require an identical package everywhere.

National implementation and authority review matter. Operators working across borders should confirm the applicable process in each jurisdiction rather than assume a conclusion or approval transfers unchanged. In Norway, EASA requirements sit alongside Norwegian aviation law; the operation’s location and oversight arrangements are part of the planning, not administrative details to postpone.

Choose support by the gap you need to close

Some operators can develop the assessment in-house. That can suit a team with current SORA competence, access to the relevant technical evidence and enough time to coordinate operational and regulatory work. The trade-off is capacity: the same specialists may also be responsible for building and running the operation they are assessing.

A specialist drone operations consultancy can help when the operator needs external support to structure the risk assessment, review mitigations or prepare compliance material. The useful question is not whether a consultant promises a particular SAIL outcome. Ask what work is in scope, what evidence the operator must supply, and who remains responsible for the safety case. For a SAIL IV proposal, establish how the consultant will deal with the greater assurance burden before work begins.

North Sky Aviation Consultancy says it provides drone operations and counter-UAS consulting, risk management and compliance consulting, and regulatory compliance assistance. It works across Norway, Sweden, Denmark and the broader European region, and says it helps organizations navigate EASA regulations and Norwegian aviation law. Those services may be relevant to an operator weighing external support; its published information does not specify a SORA deliverable or promise a SAIL result. Operators should verify scope and experience against their own case.

Build the evidence before choosing the label

Start with the operation as it will actually be conducted: routes, people and assets exposed, airspace context, aircraft limits, contingencies and the mitigations on which the case relies. Then identify the objectives and assurance level that follow from the assessment. If the result is SAIL IV, plan for the evidence and review burden early. If it is SAIL III, do not treat that as permission to leave applicable objectives thinly supported.

For teams connecting an operational safety case with broader management-system processes, the practical work of preparing for an EASA SMS compliance audit offers useful background on document review and operational sampling. The core lesson carries over: make the evidence match the operation, and make responsibilities clear.

The decision between SAIL III and IV is ultimately not a procurement choice. It is the consequence of a defined operation and a defensible risk assessment. Get that case right first; then size the team, assurance effort and regulatory plan to match it.