BVLOS Drone Insurance for Automated Beyond Visual Operations

Regulatory Context: Where BVLOS Sits in the UK Framework

In Great Britain, drone operations are governed by the CAA under the framework established by the Air Navigation Order 2016 as amended and the UK-retained version of Commission Delegated Regulation (EU) 2019/945 and Implementing Regulation (EU) 2019/947. Operations are classified as Open, Specific, or Certified. BVLOS flight falls outside the Open category entirely; it requires an Operational Authorisation issued under the Specific category, or — for the most complex operations — entry into the Certified category.

The CAA's Specific category pathway requires operators to submit an Operational Risk Assessment, typically following the SORA (Specific Operations Risk Assessment) methodology. The resulting Operational Authorisation defines the approved geographic volume, the UAS class or specific aircraft, the maximum groundspeed, the crew configuration, and any contingency mitigations. Every one of those parameters is material to underwriters. An insurance submission that does not reference the Operational Authorisation number and its conditions will almost always result in a request for further information before terms can be issued.

Automated BVLOS adds a further layer. Where the aircraft executes pre-programmed or AI-directed flight without continuous pilot input, underwriters treat the human-oversight model as a distinct risk variable. The CAA's evolving guidance on remote pilot competency and detect-and-avoid requirements for automated operations is actively tracked by specialist BVLOS underwriters; operators should expect policy conditions to mirror current CAA expectations rather than lag behind them.

What a BVLOS Hull and Liability Programme Should Cover

A correctly structured programme for automated BVLOS operations combines hull all-risks cover for the aircraft and its payload with third-party liability. Both elements require specific endorsements that go beyond a standard commercial drone wording.

Hull all-risks for BVLOS should respond to loss or damage occurring during the full approved operational envelope, including taxi, launch, autonomous transit, and recovery. Critically, the wording must address loss of link and fly-away scenarios — events that are statistically more consequential in BVLOS operations than in supervised VLOS work. Payload cover, where the sensor or delivery package has significant standalone value, is typically scheduled separately with its own sum insured.

Third-party liability limits for Specific category BVLOS operations are set with reference to the aircraft's maximum take-off mass and the nature of the overflown environment. The UK implements ICAO Annex 13 principles and the CAA's own guidance references minimum liability thresholds expressed in Special Drawing Rights as a unit of account. Operators should confirm with their broker that the liability limit stated in their Operational Authorisation conditions is met or exceeded by the policy — and that the policy does not contain an exclusion for autonomous or automated flight that would silently void that cover.

• Hull all-risks: aircraft, permanently attached equipment, and scheduled payload
• Third-party bodily injury and property damage liability
• Loss of link and fly-away cover (confirm it is not excluded)
• Ground equipment and ground control station cover
• Crew personal accident (where the remote pilot is not covered under a separate employer's policy)
• Data liability extension (where the payload collects personal or commercially sensitive data)

Underwriting Triggers Specific to Automated Operations

Underwriters writing automated BVLOS risks apply a materially different assessment process than they use for piloted VLOS work. The key triggers that elevate scrutiny — and affect terms — are the degree of autonomy, the overflown environment, the detect-and-avoid solution in use, and the operator's safety management system maturity.

Degree of autonomy matters because it determines whether a remote pilot can intervene in real time. A pre-programmed corridor flight with a pilot monitoring and able to command a return-to-home is treated differently from a fully autonomous swarm or a machine-learning-directed inspection flight where the aircraft makes routing decisions independently. Underwriters will ask for a plain-English description of the decision-making chain and will want to see that the CAA's Operational Authorisation explicitly covers the autonomous mode being used.

Detect-and-avoid is a live underwriting question. Where the operation relies on ground-based radar, ADS-B, or an onboard detect-and-avoid system, underwriters will ask for the system's performance specification and any CAA acceptance letter. Operations that depend solely on airspace segregation or NOTAM-based deconfliction without a technical detect-and-avoid solution will typically attract more restrictive policy conditions.

Safety management system documentation — including occurrence reporting logs, maintenance records, and crew training records — is increasingly a pre-binding requirement rather than a post-loss request. Brokers who present a well-organised risk submission including these documents consistently achieve better terms than those who present the aircraft details alone.

Fleet and Multi-Aircraft Programme Considerations

Operators running multiple aircraft on BVLOS authorisations — whether identical platforms on a single corridor or a mixed fleet across several Operational Authorisations — should consider a fleet programme rather than individual aircraft policies. Fleet programmes allow a single policy schedule to cover all authorised aircraft, with hull values declared per aircraft and liability applying on a per-occurrence basis across the fleet.

Premiums on fleet programmes scale with aggregate hull value, the number and nature of Operational Authorisations held, the operational tempo (flying hours or cycles per year), and the BVLOS exposure as a proportion of total flying. Underwriters will ask for a fleet list with individual hull values, the MTOM of each aircraft, and the Operational Authorisation reference for each BVLOS approval. Where aircraft are added or retired during the policy period, mid-term adjustment clauses should be agreed at inception rather than negotiated at the point of change.

Where a fleet includes aircraft operating under both Open category rules and Specific category BVLOS authorisations, the policy must be structured so that the BVLOS endorsements apply only to the authorised aircraft and operations. A single blanket wording that does not distinguish between categories creates ambiguity that can complicate claims handling.

Broker Workflow: Presenting a BVLOS Risk Correctly

The quality of the risk submission is the single largest controllable factor in achieving competitive terms for automated BVLOS operations. Underwriters in this segment receive relatively few submissions and can afford to decline risks that are poorly documented. A complete submission materially reduces the time to indicative terms and the likelihood of exclusions being applied as a substitute for information.

Brokers should assemble the following before approaching the market: the operator's CAA Operator ID, the current Operational Authorisation document including all conditions and approved geographic volumes, the aircraft manufacturer's technical datasheet for each BVLOS-authorised type, the operator's safety management system summary or operations manual, a statement of flying hours or cycles in the preceding twelve months, and details of any previous losses or incidents whether or not a claim was made.

Where the operation is new and no loss history exists, underwriters will place greater weight on the operator's safety management system maturity, the qualifications of the remote pilot in command, and the robustness of the detect-and-avoid solution. A new operator with a well-documented SMS and a CAA-accepted detect-and-avoid system will typically achieve better terms than an experienced operator with a thin submission.

Renewal submissions should include an updated loss run, any changes to the Operational Authorisation since the previous policy period, and a note of any changes to the aircraft configuration or autonomous systems. Mid-term changes to the Operational Authorisation — which the CAA may require following an occurrence or a change in operational scope — must be notified to underwriters promptly; failure to do so can affect the validity of cover.

• CAA Operator ID and current Operational Authorisation document
• Aircraft technical datasheets for each BVLOS-authorised type
• Operations manual or safety management system summary
• Flying hours or cycles in the preceding twelve months
• Full loss and incident history, including uninsured occurrences
• Detect-and-avoid system specification and any CAA acceptance documentation

Policy Conditions and Ongoing Compliance

BVLOS policies for automated operations routinely carry conditions that require the insured to maintain compliance with the Operational Authorisation at all times. A flight conducted outside the approved geographic volume, above the approved MTOM, or in an autonomous mode not covered by the Operational Authorisation will typically trigger a condition precedent to liability, meaning the insurer may decline to indemnify that loss even if the aircraft and crew are otherwise covered.

Operators should read the policy's definition of 'authorised operation' carefully and confirm that it references the Operational Authorisation by document rather than by a generic description of BVLOS flight. Where the CAA issues a variation to the Operational Authorisation — whether to expand or restrict the approved scope — the broker should be notified immediately so that the policy schedule can be updated.

Deductibles on automated BVLOS operations typically rise relative to equivalent piloted VLOS work, reflecting the reduced opportunity for real-time human intervention. Operators should model the deductible against their hull values and operational tempo when comparing programme options, rather than focusing solely on the premium. A lower premium with a high deductible may represent a worse economic outcome for an operator flying high-value aircraft at scale.

Frequently asked questions

Does a standard commercial drone policy cover BVLOS operations?

Not reliably. Most standard commercial drone wordings are designed for Open or lower-risk Specific category VLOS operations. They frequently contain exclusions for autonomous flight, loss of link, or operations outside visual range that would prevent a valid claim arising from a BVLOS incident. A policy written specifically for your CAA Operational Authorisation — with those exclusions either removed or replaced by BVLOS-specific conditions — is required for automated beyond visual line of sight work.

What CAA authorisation do I need before I can obtain BVLOS insurance?

You need a current Operational Authorisation issued by the CAA under the Specific category, explicitly permitting BVLOS flight for the aircraft type and operational area you intend to insure. Underwriters will not write BVLOS cover for operations that have not yet received CAA authorisation. If your authorisation is in progress, brokers can approach the market for indicative terms, but binding cover requires the authorisation document to be in place.

What information does a broker need to place a BVLOS hull and liability programme?

At minimum: your CAA Operator ID, the full Operational Authorisation document including all conditions and approved volumes, technical datasheets for each aircraft type, your operations manual or safety management system summary, flying hours or cycles for the preceding twelve months, and a complete loss and incident history. For automated operations, underwriters will also ask for the specification of your detect-and-avoid system and any CAA acceptance documentation for that system. A complete submission at first approach materially reduces the time to binding terms.

What happens to my cover if the CAA varies my Operational Authorisation mid-policy?

A variation to your Operational Authorisation is a material change that must be notified to your insurer promptly. Most BVLOS policies contain a condition requiring the insured to maintain compliance with the Operational Authorisation as it stands at the time of each flight. If the CAA restricts your authorisation and you continue to fly under the previous scope, or if the CAA expands your authorisation and you fly the new scope without updating the policy, you risk operating outside the terms of your cover. Notify your broker of any CAA variation as soon as it is received.

Are payload and ground control station equipment covered under the same policy?

They can be, but they should be scheduled explicitly. Payload — sensors, cameras, delivery equipment — is typically listed as a separate item with its own sum insured rather than treated as part of the aircraft hull value. Ground control stations, remote pilot stations, and communications equipment can be included under a ground equipment section. Confirm with your broker that each item is scheduled and that the sum insured reflects current replacement value, particularly for high-value sensor payloads where the payload may be worth more than the aircraft itself.

Does the policy respond if my aircraft causes a loss during a fully autonomous flight with no remote pilot actively monitoring?

This depends entirely on the policy wording and the scope of your CAA Operational Authorisation. If your Operational Authorisation explicitly covers fully autonomous flight without continuous remote pilot monitoring, and the policy wording does not contain an exclusion for unmonitored autonomous operations, then the policy should respond. However, many standard wordings include a requirement for a qualified remote pilot to be 'in command' at all times, which can create ambiguity for fully autonomous missions. This is a specific point to resolve with your underwriter before binding cover, not after a loss.