BVLOS Operations: Requirements & Waivers | BVLOS Insure

How the UK Regulatory Framework Categorises BVLOS

Great Britain operates a three-tier framework — Open, Specific, and Certified — inherited from EU regulations and retained post-Brexit under the Air Navigation Order 2016 as amended, with CAA guidance published in CAP 722 and CAP 2363. BVLOS flight sits firmly outside the Open category, which is reserved for lower-risk, shorter-range operations conducted within visual range. Almost all commercial BVLOS work therefore falls into the Specific category, requiring an Operational Authorisation from the CAA.

Within the Specific category, operators must complete a risk assessment using the CAA's adopted version of the JARUS SORA methodology — Specific Operations Risk Assessment. SORA assigns a Ground Risk Class and an Air Risk Class to the intended operation, combines them into a final SAIL (Specific Assurance and Integrity Level), and then maps required Operational Safety Objectives (OSOs) to that SAIL. The higher the SAIL, the more demanding the technical, procedural, and insurance requirements become.

Operations that cannot be adequately de-risked within the Specific category — for example, large autonomous platforms flying over dense urban areas at altitude — may be directed toward the Certified category, which imposes aircraft airworthiness certification and, in some cases, licensed remote pilot requirements. Certified-category BVLOS is rare in current GB practice but is the trajectory for urban air mobility and cargo drone networks.

CAA Operational Authorisation: What Operators Must Demonstrate

The CAA will not issue an Operational Authorisation for BVLOS without a completed SORA, an Operations Manual that addresses the specific risk environment, and evidence that the operator holds — or will hold before flight — adequate third-party liability insurance. The insurance requirement is not advisory; it is a condition of the authorisation, and the CAA may specify minimum liability limits in the authorisation document itself.

Beyond the insurance condition, the SORA process requires operators to define their Operational Volume precisely, including the Flight Geography, Contingency Volume, and Ground Risk Buffer. Each of these boundaries affects the underwriting assessment: a tighter Ground Risk Buffer over a populated area raises the Ground Risk Class, which in turn raises the SAIL and the complexity of the insurance submission.

Operators seeking a ConOps (Concept of Operations) approval for a repeatable BVLOS operation — such as a linear infrastructure inspection corridor — should expect the CAA to require a Means of Compliance document demonstrating how each OSO is met. Underwriters reviewing the same submission will look for the same evidence: robust detect-and-avoid capability, reliable command-and-control link architecture, and a tested emergency response procedure.

• Completed SORA with documented Ground Risk Class and Air Risk Class
• Operations Manual covering contingency and emergency procedures
• Evidence of third-party liability insurance meeting CAA-specified limits
• Defined Operational Volume with Ground Risk Buffer calculations
• Detect-and-avoid or equivalent mitigations where operating near other airspace users
• Command-and-control link redundancy documentation

BVLOS Waivers and Exemptions: When They Apply

The term 'waiver' is used loosely in the industry but has a specific meaning in GB practice. The CAA does not issue waivers in the FAA Part 107 sense — where a named regulatory paragraph is waived for a defined period. Instead, the CAA issues Operational Authorisations that permit operations which would otherwise be prohibited under the standard Open category rules. The authorisation is the permission; the SORA is the mechanism by which the CAA satisfies itself that the risk is acceptable.

Exemptions under Article 16 of the retained EU UAS Regulation can apply to certain legacy operators or specific operational models, but these are narrow and do not substitute for a full Operational Authorisation for novel BVLOS work. Operators who have seen references to 'Article 16 exemptions' in European contexts should note that the GB retained framework diverges from the EU framework at points, and CAA guidance should always be the primary reference.

For operators running trials or innovation projects, the CAA's Regulatory Sandbox — operated in conjunction with the Future Flight Challenge and Innovate UK programmes — provides a structured route to time-limited BVLOS permissions with enhanced CAA oversight. Insurance for sandbox operations requires specific endorsements, as the operational parameters may change during the trial period and standard policy wordings may not respond without amendment.

Insurance Triggers Specific to BVLOS

Standard commercial drone liability policies written for VLOS operations will typically exclude BVLOS flight unless specifically endorsed. The exclusion is not a market quirk; it reflects a materially different risk profile. In BVLOS operations, the remote pilot cannot apply the naked-eye see-and-avoid obligation that underpins VLOS safety cases, so the technical mitigations — and therefore the underwriting evidence required — are substantially more demanding.

Hull insurance for BVLOS platforms scales with hull value and BVLOS exposure in ways that differ from VLOS fleets. Autonomous or highly automated operations typically attract higher deductibles than piloted VLOS work, reflecting the reduced opportunity for real-time human intervention. Operators running mixed fleets — some aircraft VLOS, some BVLOS — should ensure their policy schedule clearly delineates which aircraft are endorsed for BVLOS, and that the Operations Manual submitted to the CAA matches the scope of the insurance endorsement exactly.

Third-party liability limits for BVLOS are quoted in GBP and must meet any minimum specified in the Operational Authorisation. Where the CAA specifies a limit, that figure becomes the contractual floor; underwriters may offer higher limits depending on the SORA outcome, the operator's safety management record, and the nature of the overflown environment. Operators should not assume that a limit adequate for VLOS work will satisfy a BVLOS authorisation condition.

Cargo and payload liability is a separate consideration for BVLOS delivery operations. If the platform is carrying third-party goods, the cargo liability exposure sits alongside — not within — the standard third-party liability cover, and must be addressed as a distinct line in the programme.

Broker Workflow: Placing a BVLOS Programme

Brokers placing BVLOS hull and liability programmes should collect the SORA documentation before approaching the market. Underwriters will ask for it; submitting without it delays the quote and signals that the operator may not yet have CAA authorisation in hand. The SORA output — particularly the SAIL level and the list of OSOs the operator has committed to — is the primary underwriting document for a BVLOS submission.

The Operations Manual is the second critical document. Underwriters will check that the emergency procedures, command-and-control architecture, and detect-and-avoid mitigations described in the manual are consistent with the SORA. Inconsistencies between the two documents are a common cause of referral to a senior underwriter or outright declination.

For novel or high-SAIL operations, brokers should expect a manuscript policy rather than a standard form. Manuscript wordings allow the insurer to align the policy conditions precisely with the OSOs the operator has committed to, and to include conditions precedent that mirror the CAA's authorisation conditions. This protects both the operator — who needs certainty that the policy responds — and the insurer, who needs to know the safety case has been maintained throughout the policy period.

• Obtain SORA documentation and SAIL output before approaching underwriters
• Confirm CAA Operational Authorisation status — pending, granted, or in sandbox
• Provide the full Operations Manual, not a summary
• Identify all aircraft to be operated BVLOS and their hull values
• Clarify payload and cargo liability exposure if goods are being carried
• Flag any planned changes to operational parameters during the policy period

Frequently asked questions

Does a standard commercial drone policy cover BVLOS operations automatically?

No. Most standard commercial drone liability and hull policies exclude BVLOS flight unless a specific BVLOS endorsement is added. The exclusion reflects the materially different risk profile of operations conducted outside the remote pilot's direct line of sight. Operators must ensure their policy schedule and endorsements match the scope of their CAA Operational Authorisation before any BVLOS flight takes place.

What regulatory category does BVLOS fall under in Great Britain?

BVLOS operations in Great Britain fall outside the Open category and require a CAA Operational Authorisation under the Specific category, or in some cases the Certified category. The CAA uses the JARUS SORA methodology to assess risk, assigning a SAIL level that determines the Operational Safety Objectives the operator must meet. There is no blanket BVLOS permission; each operation or repeatable ConOps must be individually assessed.

What documents does an underwriter need to quote a BVLOS programme?

At minimum, underwriters require the completed SORA with SAIL output, the full Operations Manual, confirmation of CAA Operational Authorisation status, a schedule of aircraft to be operated BVLOS with hull values, and details of any payload or cargo liability exposure. For novel or high-SAIL operations, additional technical documentation — such as detect-and-avoid system specifications and command-and-control link architecture — is typically requested before terms are issued.

Does the CAA specify the liability limit that must appear on the policy?

The CAA may specify minimum third-party liability limits as a condition of the Operational Authorisation. Where a limit is specified, it becomes the contractual floor for the insurance programme. Operators should share their Operational Authorisation document with their broker so that the policy limit is confirmed to meet or exceed the CAA's condition before the authorisation is relied upon for flight.

How does the SORA SAIL level affect the insurance placement?

A higher SAIL level indicates a more complex risk environment and requires the operator to demonstrate more demanding Operational Safety Objectives. Underwriters use the SAIL output to assess the adequacy of the operator's mitigations, set appropriate deductible levels, and determine whether a standard policy form or a manuscript wording is required. Operations at higher SAIL levels typically involve longer underwriting review periods and may require senior underwriter sign-off.

Can a broker place BVLOS cover for an operator whose CAA authorisation is still pending?

Underwriters can issue indicative terms or a terms letter while an Operational Authorisation is pending, but the policy will not be bound — and BVLOS flight must not commence — until the CAA authorisation is granted. The final policy wording must reflect the conditions of the granted authorisation, so brokers should request a copy of the authorisation document before binding and check that the policy scope aligns with the authorised ConOps.