Does a standard commercial drone policy cover BVLOS flights?

No. Standard commercial drone policies are written for Open Category or lower-risk Specific Category operations and typically exclude BVLOS explicitly, or contain conditions — such as requiring the pilot to maintain unaided visual contact — that a BVLOS operation cannot satisfy. A dedicated BVLOS programme, placed against the operator's CAA Operational Authorisation, is required.

What regulatory document triggers the need for BVLOS-specific insurance?

The CAA Operational Authorisation for Specific Category BVLOS operations is the trigger. The authorisation sets the operational parameters — airspace, MTOM, detect-and-avoid requirements, lost-link procedures — that underwriters use to assess and price the risk. Operating BVLOS without a valid authorisation also voids any insurance cover, so the two documents are interdependent.

Can an operator be covered for both VLOS and BVLOS flights under one policy?

Yes, provided the policy is structured to reflect both operating modes. The BVLOS element will carry its own conditions, and underwriters will want the flight-hours split between VLOS and BVLOS declared at inception. If the balance shifts materially during the policy period — for example, if a new contract significantly increases BVLOS hours — the operator should notify the broker promptly to avoid a coverage gap.

What is the broker's responsibility when an operator's CAA authorisation is amended mid-term?

The broker should treat a material amendment to the Operational Authorisation — such as an extension of the operating area, an increase in MTOM, or the addition of new aircraft types — as a mid-term change requiring underwriter notification. Most BVLOS policies contain a condition requiring the insured to notify the insurer of any change to the authorisation. Failure to do so can prejudice a claim.

Are payload and data liabilities automatically included in a BVLOS hull and liability programme?

Not automatically. Hull and third-party liability are the core covers; payload physical damage, data liability, and cyber extensions are typically added by endorsement. Brokers should establish at submission stage what the operator's contractual obligations to end clients require, and whether the operator's existing cyber programme — if any — extends to UAS-collected data. Gaps between the drone policy and the cyber policy are a common source of uninsured exposure.

How does the SORA SAIL level affect eligibility for cover?

SAIL level is a key underwriting input, not an eligibility threshold. Operations at lower SAIL levels — typically shorter-range, lower-altitude, over sparsely populated areas — are more straightforwardly placed. Higher SAIL levels, particularly those involving operations over populated areas or in controlled airspace, require more detailed submission information and may attract additional conditions or exclusions. Very high SAIL operations may require Lloyd's specialist capacity or a manuscript wording. No SAIL level is automatically uninsurable, but the placement process becomes more bespoke as SAIL rises.

Beyond Visual Line of Sight (BVLOS) Fact Sheet

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

Operating a drone beyond visual line of sight in Great Britain requires a CAA Specific Category authorisation before a single flight departs — and a hull/liability programme structured around that authorisation before underwriters will bind cover. This fact sheet sets out what operators and brokers need to know about the regulatory framework, the coverage architecture, and the underwriting variables that determine whether a BVLOS programme is placed cleanly or returns with exclusions.

Regulatory Framework: Where BVLOS Sits in the UK Drone Rules

The UK retained the EU's three-tier structure — Open, Specific, Certified — after the transition period ended, but the CAA now administers it independently of EASA. BVLOS operations fall squarely in the Specific Category because they exceed the risk envelope that the Open Category permits. An operator must hold either a CAA-issued Operational Authorisation or, for higher-risk scenarios, a Light UAS Operator Certificate (LUOC) with BVLOS permissions appended.

The CAA uses a Specific Operations Risk Assessment (SORA) methodology to evaluate applications. SORA assigns a Ground Risk Class and an Air Risk Class, combines them into a final SAIL level (I–VI), and the SAIL level determines the Operational Safety Objectives the operator must meet. Underwriters read the SAIL level as a proxy for exposure: a higher SAIL signals more demanding airspace, heavier aircraft, or operations over populated areas — all of which affect how a programme is structured.

From 2026, the CAA has signalled continued progress on its BVLOS Sandbox outcomes and the integration of U-Space service providers in designated zones. Operators planning corridor or urban BVLOS work should expect authorisation timelines to reflect U-Space coordination requirements, and brokers should confirm that policy wording does not inadvertently exclude U-Space-managed airspace as a non-standard operating environment.

What a BVLOS Hull and Liability Programme Must Cover

A standard Open Category policy is not fit for BVLOS. The coverage architecture for a Specific Category operation needs to address the expanded risk profile across three dimensions: the aircraft itself, third-party liability, and the payload or data product.

Hull cover for BVLOS platforms typically needs to reflect the full replacement value of a system that may carry redundant flight controllers, detect-and-avoid sensors, and mission-specific payloads. Agreed-value hull wordings are strongly preferred over market-value wordings because BVLOS platforms depreciate unevenly and replacement parts can carry long lead times. Operators should confirm whether ground equipment — ground control stations, data links, launch and recovery systems — is scheduled separately or bundled.

Third-party liability limits are quoted in GBP and must meet the minimum required under UK Retained Regulation (EU) 785/2004 for the MTOM of the aircraft. For heavier BVLOS platforms, those minimums are expressed in Special Drawing Rights (SDRs) as the unit of account; the GBP equivalent fluctuates with exchange rates, so policies should be reviewed at renewal for adequacy. Operators working under contract to infrastructure owners, utilities, or public authorities will almost always face contractual liability requirements that exceed the regulatory minimum.

Payload liability and data liability are increasingly relevant for BVLOS operations delivering inspection, survey, or logistics services. If the drone carries sensors that capture personal data, the operator is a data controller under UK GDPR, and a cyber or data-liability extension may be required by the end client. Brokers should ask whether the operator's existing cyber programme extends to UAS-collected data or whether a standalone extension is needed.

Hull: agreed-value, all-risks, including ground equipment and data links
Third-party liability: GBP limits meeting UK Retained Reg 785/2004 SDR thresholds as a minimum
Payload and sensor cover: physical damage to attached equipment
Data and cyber liability extension: where the operation captures personal or commercially sensitive data
Grounding and loss-of-licence extensions: available on larger fleet programmes

Underwriting Variables Specific to BVLOS

Underwriters assess BVLOS submissions differently from standard commercial drone risks. The CAA Operational Authorisation document — including the Operations Manual and the SORA output — is the primary underwriting document, not a certificate of airworthiness or a pilot licence. Brokers should submit the full authorisation pack at inception, not a summary.

Premiums scale with hull value, MTOM, SAIL level, and the proportion of flight hours conducted in BVLOS mode versus VLOS. An operation that is predominantly VLOS with occasional BVLOS sorties carries a different risk profile from a dedicated BVLOS corridor service. Underwriters will ask for a split of planned annual flight hours and will want to understand whether detect-and-avoid technology is fitted and what its certification status is.

Deductibles typically rise on autonomous or highly automated operations where pilot intervention is limited or delayed. The rationale is straightforward: the window to prevent a loss narrows when a remote pilot cannot immediately override the aircraft. Operators should expect underwriters to ask detailed questions about command-and-control link redundancy, lost-link procedures, and contingency management systems as documented in the Operations Manual.

Fleet programmes covering multiple BVLOS platforms benefit from aggregated underwriting, but each platform's authorisation scope must be individually confirmed. A fleet policy that inadvertently covers a platform operating outside its authorised parameters creates a coverage gap that will surface at claims stage.

Broker Workflow: Placing a BVLOS Programme

The submission package for a BVLOS programme is more document-intensive than a standard commercial drone placement. Assembling it correctly at the outset reduces the number of underwriter queries and shortens the time to bind.

At a minimum, brokers should gather: the CAA Operational Authorisation (including all conditions and limitations), the current Operations Manual, a schedule of all insured aircraft with MTOM and hull values, a statement of planned annual flight hours split by BVLOS and VLOS, details of detect-and-avoid systems fitted, and the operator's incident and claims history for at least three years. Where the operator is a new entrant without claims history, underwriters will place greater weight on the quality of the Operations Manual and the operator's safety management system.

Renewal submissions should be treated as new placements if the scope of authorisation has changed — for example, if the operator has extended from a single corridor to a network of routes, or has moved from a lower SAIL level to a higher one. Brokers who roll over a BVLOS programme without updating the submission risk placing cover that does not match the current authorisation.

Market capacity for BVLOS in GB is concentrated among a small number of specialist Lloyd's syndicates and company-market underwriters. Brokers without a direct Lloyd's relationship should work through a specialist MGA or wholesale broker with demonstrated BVLOS placement experience. Attempting to place BVLOS risk through a standard aviation or commercial lines market is likely to result in either a declination or a policy with exclusions that render it unfit for purpose.

CAA Operational Authorisation including all conditions
Current Operations Manual (version-controlled)
Aircraft schedule: MTOM, hull values, detect-and-avoid equipment
Annual flight hours split: BVLOS vs VLOS
Three-year incident and claims history
Contractual liability requirements from end clients

2026 Market Signals Brokers Should Monitor

The CAA's ongoing BVLOS programme development — including outcomes from the Project Zenith and Project Xcelerate initiatives — is expected to produce more standardised authorisation pathways for lower-risk BVLOS operations. If standardised scenarios emerge, underwriters may develop more streamlined wordings for operations that fit within them, potentially improving market access for operators who currently face bespoke placement processes.

U-Space implementation in designated zones introduces a new layer of operational data — flight plans, real-time tracking, deconfliction records — that underwriters are beginning to treat as underwriting information. Operators participating in U-Space services should expect insurers to ask for access to operational data logs at claims stage, and policy wordings are starting to reflect this. Brokers should review manuscript wordings for U-Space data obligations before binding.

The convergence of BVLOS drone operations with Advanced Air Mobility (AAM) — including electric vertical take-off and landing aircraft operating under Certified Category rules — is beginning to influence how reinsurers think about accumulation exposure. While most commercial BVLOS operators are not yet in AAM territory, brokers advising operators with growth ambitions in that direction should begin conversations with underwriters about how a programme would need to evolve as the aircraft type and regulatory category change.

Frequently asked questions

Does a standard commercial drone policy cover BVLOS flights?: No. Standard commercial drone policies are written for Open Category or lower-risk Specific Category operations and typically exclude BVLOS explicitly, or contain conditions — such as requiring the pilot to maintain unaided visual contact — that a BVLOS operation cannot satisfy. A dedicated BVLOS programme, placed against the operator's CAA Operational Authorisation, is required.
What regulatory document triggers the need for BVLOS-specific insurance?: The CAA Operational Authorisation for Specific Category BVLOS operations is the trigger. The authorisation sets the operational parameters — airspace, MTOM, detect-and-avoid requirements, lost-link procedures — that underwriters use to assess and price the risk. Operating BVLOS without a valid authorisation also voids any insurance cover, so the two documents are interdependent.
Can an operator be covered for both VLOS and BVLOS flights under one policy?: Yes, provided the policy is structured to reflect both operating modes. The BVLOS element will carry its own conditions, and underwriters will want the flight-hours split between VLOS and BVLOS declared at inception. If the balance shifts materially during the policy period — for example, if a new contract significantly increases BVLOS hours — the operator should notify the broker promptly to avoid a coverage gap.
What is the broker's responsibility when an operator's CAA authorisation is amended mid-term?: The broker should treat a material amendment to the Operational Authorisation — such as an extension of the operating area, an increase in MTOM, or the addition of new aircraft types — as a mid-term change requiring underwriter notification. Most BVLOS policies contain a condition requiring the insured to notify the insurer of any change to the authorisation. Failure to do so can prejudice a claim.
Are payload and data liabilities automatically included in a BVLOS hull and liability programme?: Not automatically. Hull and third-party liability are the core covers; payload physical damage, data liability, and cyber extensions are typically added by endorsement. Brokers should establish at submission stage what the operator's contractual obligations to end clients require, and whether the operator's existing cyber programme — if any — extends to UAS-collected data. Gaps between the drone policy and the cyber policy are a common source of uninsured exposure.
How does the SORA SAIL level affect eligibility for cover?: SAIL level is a key underwriting input, not an eligibility threshold. Operations at lower SAIL levels — typically shorter-range, lower-altitude, over sparsely populated areas — are more straightforwardly placed. Higher SAIL levels, particularly those involving operations over populated areas or in controlled airspace, require more detailed submission information and may attract additional conditions or exclusions. Very high SAIL operations may require Lloyd's specialist capacity or a manuscript wording. No SAIL level is automatically uninsurable, but the placement process becomes more bespoke as SAIL rises.

Submit your BVLOS programme enquiry to BVLOS Insure with your CAA Operational Authorisation and Operations Manual. Our underwriting team reviews Specific Category submissions directly and can confirm indicative terms without requiring a full market exercise.