Does standard commercial drone insurance cover BVLOS operations automatically?

Not typically. Most standard commercial drone policies are written with VLOS operations as the baseline risk. BVLOS flight introduces autonomy, extended datalink dependency, and a higher regulatory threshold — all of which require specific underwriter agreement. Operators should not assume BVLOS is covered unless the policy schedule or an endorsement explicitly confirms it, and the approved ConOps is on file with the insurer.

What CAA documentation do I need before approaching an underwriter?

At a minimum, you should have your draft or approved Operational Authorisation, your ConOps, and your SORA output or equivalent risk assessment. If your OA has not yet been granted, underwriters can often provide indicative terms based on draft documentation — this is preferable to waiting, as it allows wording issues to be resolved before the OA is finalised. Article 16 operators should also provide the specific conditions attached to their authorisation.

Are there eligibility requirements that could prevent a BVLOS operator from obtaining cover?

Yes. Underwriters will assess pilot qualifications, hours on type, the operator's safety management system, and loss history. Operations in high-density corridors, over critical national infrastructure, or using experimental detect-and-avoid systems may face restricted appetite in the standard market and require placement in the specialist or excess-and-surplus lines market. Full disclosure of the operational profile at submission stage is essential — material non-disclosure can void cover entirely.

How does the policy territory clause interact with a CAA Operational Authorisation?

The OA defines where you are legally permitted to fly; the policy territory clause defines where the insurer agrees to cover you. These two boundaries must align. If your OA corridor extends into controlled airspace or near restricted zones, confirm that the policy wording does not contain airspace-classification exclusions that would leave those segments uninsured. Cross-border operations require separate confirmation that the policy extends to the relevant foreign jurisdiction.

What is the broker workflow for placing a BVLOS programme through BVLOS Insure?

Submit the aircraft specification, ConOps, SORA output, pilot credentials, and any existing loss history to our underwriting team. We will review the submission, identify any documentation gaps, and approach the appropriate Lloyd's syndicate or specialist company market on your behalf. Indicative terms can typically be provided before the OA is finalised, allowing wording to be agreed in parallel with the CAA approval process. Once terms are accepted, we confirm that the policy schedule mirrors the OA conditions before binding.

Does BVLOS insurance cover ground control stations and datalink infrastructure?

Not automatically under a standard drone hull policy. Ground control stations, datalink repeaters, and associated command-and-control equipment are typically scheduled separately or covered under a broader equipment floater. Operators should list all ground support equipment in their submission and confirm with the underwriter whether it is included within the hull section or requires a separate line of cover.

BVLOS Operations Insurance: A Buyer's Guide

Written by the BVLOS Insure editorial team · reviewed by Anton Kuznetsov, founder

Before your aircraft crosses the visual line of sight, your insurance programme needs to have crossed several thresholds first. BVLOS operations insurance is not a straightforward extension of standard drone liability cover — it is a distinct risk class that demands underwriter pre-approval, CAA-aligned operational documentation, and policy wording reviewed against your Operational Authorisation or Article 16 conditions. This guide sets out what brokers and operators must address before binding cover, what underwriters scrutinise, and where programmes commonly fall short.

Why BVLOS Changes the Risk Profile Entirely

Under the UK CAA's three-tier framework — Open, Specific, and Certified categories — virtually all commercial BVLOS flight sits within the Specific category and requires a formal Operational Authorisation (OA). A handful of operations using highly automated, detect-and-avoid-equipped aircraft may migrate toward the Certified category. Either way, the regulatory burden is substantially higher than Open-category VLOS work, and insurers price and structure cover accordingly.

The core underwriting concern is loss-of-control exposure. In VLOS operations the remote pilot can intervene visually; beyond that boundary, situational awareness depends on datalinks, onboard autonomy, and ground-based detect-and-avoid systems. Each of those dependencies introduces a failure mode that standard drone policy wordings were not drafted to address. Premiums scale with hull value and BVLOS exposure distance, and deductibles typically rise on autonomous or highly automated operations.

Payload also matters disproportionately in BVLOS. A survey sensor worth a fraction of the hull value is one risk; a medical-delivery payload or a tethered communications relay over a populated corridor is another. Underwriters will ask for payload descriptions, and some will exclude specific payload types or require endorsements that cap liability sub-limits for third-party payload damage.

Regulatory Triggers That Drive Coverage Requirements

The CAA's Specific category OA process — informed by EASA's SORA (Specific Operations Risk Assessment) methodology, which the UK retained post-Brexit in adapted form — requires operators to demonstrate that residual risk is tolerable. Insurers are not a formal part of the SORA sign-off, but the OA conditions frequently specify minimum third-party liability limits, and some CAA-approved ConOps templates reference insurance as a mitigating measure.

Article 16 authorisations, issued to operators flying under a CAA-approved club or association scheme, carry their own conditions. Brokers placing cover for Article 16 BVLOS operations should confirm whether the authorisation was granted under a standard scenario or a bespoke ConOps, because the permitted operating area, maximum altitude, and population density constraints all affect the liability exposure the underwriter is being asked to accept.

For operators conducting cross-border BVLOS — for example, infrastructure inspection along a pipeline that crosses into another jurisdiction — the regulatory picture becomes multi-layered. UK CAA authority ends at the UK border; operations entering EU airspace require engagement with the relevant National Aviation Authority under EASA's Specific category rules. Brokers should confirm whether the policy territory clause covers the full operational footprint and whether the liability limit currency (typically quoted in GBP for UK-domiciled programmes) is adequate for the foreign jurisdiction's minimum requirements.

What a BVLOS Insurance Programme Should Cover

A well-structured programme for BVLOS operations typically combines hull all-risks, third-party liability, and — depending on the operation — payload cover, grounding liability, and personal accident for remote pilots and visual observers. Each of these elements needs to be reviewed for BVLOS-specific exclusions before the policy is bound.

Hull all-risks wording should be checked for autonomy exclusions. Some market-standard drone policies exclude loss or damage arising from autonomous flight modes or from operations conducted without a remote pilot actively at the controls. BVLOS operations that rely on automated contingency manoeuvres — return-to-home, auto-land, or geofence-triggered descent — may inadvertently trigger these exclusions if the wording has not been negotiated.

Third-party liability limits for BVLOS work over or near populated areas should reflect the realistic consequence of a ground impact event. Underwriters will model this against the aircraft's maximum take-off mass, cruise speed, and the population density of the operating corridor. Operators should present their CAA-approved risk assessment as part of the submission — it demonstrates that the residual risk has been formally evaluated and often supports a more favourable coverage structure.

Hull all-risks: confirm autonomy and datalink-failure exclusions are removed or endorsed out
Third-party liability: verify the limit is denominated in the correct currency and meets any OA-specified minimum
Payload cover: schedule payload separately if its value or nature creates a distinct risk
Grounding liability: relevant where BVLOS operations are conducted under contract with penalties for non-delivery
Personal accident: consider remote pilots, visual observers, and any ground crew within the operational footprint
War and terrorism: check whether the exclusion applies to airspace incursion scenarios relevant to your corridor

The Broker Submission: What Underwriters Need to See

BVLOS submissions require more documentation than standard commercial drone placements. Underwriters need to understand the operation before they can assess the risk — a one-page ACORD-style form is not sufficient. Expect to provide, at minimum, the aircraft technical specification, the approved or draft ConOps, the SORA output or equivalent risk assessment, and the operator's safety management system summary.

Pilot and crew credentials carry significant weight. Underwriters will ask for GVC (General VLOS Certificate) or equivalent qualifications, hours on type, and — for higher-risk corridors — evidence of BVLOS-specific training or simulation. Some underwriters require a minimum number of supervised BVLOS hours before they will offer standalone cover rather than requiring the operation to be added to an existing fleet programme.

Loss history should be disclosed fully, including near-misses and datalink interruptions that did not result in a claim. BVLOS underwriters are building their own actuarial data for a relatively new risk class, and a transparent loss narrative — even one that includes incidents — is generally received better than a submission that appears to have omitted relevant history. Brokers who present a clean, well-documented submission with a credible safety narrative consistently achieve better coverage terms than those who submit minimal information.

Common Coverage Gaps and How to Close Them

The most frequent gap in BVLOS programmes is the mismatch between the approved operational area in the OA and the policy's geographic territory clause. If the OA permits operations within a defined corridor and the policy territory is written as 'United Kingdom', that alignment may appear adequate — but if the corridor includes controlled airspace, restricted zones, or areas subject to temporary restrictions, the policy should be reviewed to confirm that airspace classification does not trigger an exclusion.

A second common gap is the treatment of ground support equipment and command-and-control infrastructure. BVLOS operations depend on ground control stations, datalink repeaters, and sometimes chase vehicles. Standard drone policies rarely extend hull cover to ground equipment automatically; operators should schedule this equipment explicitly or confirm that it falls within a broader equipment floater.

Finally, operators conducting BVLOS under contract should review their policy's contractual liability clause. Many standard wordings exclude liability assumed under contract unless it would have attached in the absence of the contract. Where a client contract imposes indemnity obligations that exceed what the policy would otherwise cover, a contractual liability endorsement is needed. Brokers should flag this during the placement process rather than leaving it to a post-claim dispute.

Placing Cover: Workflow for Brokers

Start the placement process before the OA is finalised, not after. Underwriters can provide indicative terms and identify documentation gaps while the operator is still in dialogue with the CAA. This parallel-track approach avoids the common scenario where an OA is granted and the operator needs cover immediately, leaving the broker with insufficient time to negotiate wording properly.

Engage the specialist aviation market directly. BVLOS operations insurance is not a product that sits comfortably in the general commercial lines market. Lloyd's syndicates and specialist company markets with dedicated UAS underwriting teams have the appetite and the wording flexibility to accommodate BVLOS risks; generalist insurers typically do not. Brokers without direct Lloyd's access should work through a wholesale MGA with a demonstrated BVLOS book.

Once terms are agreed, confirm that the policy schedule accurately reflects the approved ConOps — aircraft registration, permitted operating area, maximum MTOM, and any specific conditions attached to the OA. A policy that does not mirror the OA conditions creates an ambiguity that will surface at the worst possible moment: a claim.

Frequently asked questions

Does standard commercial drone insurance cover BVLOS operations automatically?: Not typically. Most standard commercial drone policies are written with VLOS operations as the baseline risk. BVLOS flight introduces autonomy, extended datalink dependency, and a higher regulatory threshold — all of which require specific underwriter agreement. Operators should not assume BVLOS is covered unless the policy schedule or an endorsement explicitly confirms it, and the approved ConOps is on file with the insurer.
What CAA documentation do I need before approaching an underwriter?: At a minimum, you should have your draft or approved Operational Authorisation, your ConOps, and your SORA output or equivalent risk assessment. If your OA has not yet been granted, underwriters can often provide indicative terms based on draft documentation — this is preferable to waiting, as it allows wording issues to be resolved before the OA is finalised. Article 16 operators should also provide the specific conditions attached to their authorisation.
Are there eligibility requirements that could prevent a BVLOS operator from obtaining cover?: Yes. Underwriters will assess pilot qualifications, hours on type, the operator's safety management system, and loss history. Operations in high-density corridors, over critical national infrastructure, or using experimental detect-and-avoid systems may face restricted appetite in the standard market and require placement in the specialist or excess-and-surplus lines market. Full disclosure of the operational profile at submission stage is essential — material non-disclosure can void cover entirely.
How does the policy territory clause interact with a CAA Operational Authorisation?: The OA defines where you are legally permitted to fly; the policy territory clause defines where the insurer agrees to cover you. These two boundaries must align. If your OA corridor extends into controlled airspace or near restricted zones, confirm that the policy wording does not contain airspace-classification exclusions that would leave those segments uninsured. Cross-border operations require separate confirmation that the policy extends to the relevant foreign jurisdiction.
What is the broker workflow for placing a BVLOS programme through BVLOS Insure?: Submit the aircraft specification, ConOps, SORA output, pilot credentials, and any existing loss history to our underwriting team. We will review the submission, identify any documentation gaps, and approach the appropriate Lloyd's syndicate or specialist company market on your behalf. Indicative terms can typically be provided before the OA is finalised, allowing wording to be agreed in parallel with the CAA approval process. Once terms are accepted, we confirm that the policy schedule mirrors the OA conditions before binding.
Does BVLOS insurance cover ground control stations and datalink infrastructure?: Not automatically under a standard drone hull policy. Ground control stations, datalink repeaters, and associated command-and-control equipment are typically scheduled separately or covered under a broader equipment floater. Operators should list all ground support equipment in their submission and confirm with the underwriter whether it is included within the hull section or requires a separate line of cover.

Submit your BVLOS operation details to our underwriting team at BVLOS Insure. We work directly with Lloyd's and specialist company markets to structure hull and liability programmes that align with your CAA Operational Authorisation — contact us to begin your submission.