BVLOS Drone Insurance Exclusions: UK Policy Guide

Why BVLOS Exclusions Differ From Standard Drone Policy Wording

Standard Open Category drone policies are written around low-risk, short-range operations with a visual observer present. The moment an operation crosses into Beyond Visual Line of Sight, the risk profile changes across every underwriting dimension: detect-and-avoid capability, command-and-control link integrity, emergency response time, and third-party exposure over populated or congested areas. Underwriters respond by layering exclusions that would not appear in a sub-250 g hobby product.

Maximum Take-Off Mass is one of the first variables an underwriter considers, because MTOM drives both regulatory category and the severity of a potential loss event. Sub-25 kg aircraft operating in the Specific Category face a different exclusions landscape than platforms in the 25–150 kg band, where the consequences of a hull loss or third-party strike are materially greater and underwriting appetite narrows accordingly. Brokers should establish the precise MTOM of every aircraft in the programme before approaching the market, as misclassification at submission is a common source of coverage disputes.

UK Specific Category operations require a CAA Operational Authorisation or, where applicable, acceptance of a Pre-Defined Risk Assessment. Each authorisation carries conditions — altitude ceilings, geographic constraints, crew qualification requirements — and underwriters routinely incorporate those conditions by reference into the policy schedule. Breach of an authorisation condition is therefore simultaneously a regulatory infringement and a policy exclusion trigger. Brokers placing BVLOS programmes should treat the CAA authorisation document, the operator's ConOps, and the policy wording as a three-way alignment exercise.

The Core Exclusion Categories in UK BVLOS Policies

Underwriters active in the UK specialty drone market apply exclusions across several consistent categories. Understanding each category allows brokers to negotiate endorsements or sublimits rather than accepting blanket carve-outs.

Command-and-control link failure is the exclusion that surprises operators most. Many policies exclude loss or liability arising from a C2 link interruption unless the operator can demonstrate that an approved lost-link procedure was filed with the CAA authorisation and was followed at the time of the incident. Policies written on a named-perils basis are particularly strict here.

Autonomous and AI-directed flight is increasingly separated from piloted BVLOS in policy wording. Where an aircraft executes a mission segment without real-time pilot input — even within a pre-approved corridor — some underwriters treat that segment as an autonomous operation and apply a separate, often more restrictive, exclusion clause. Operators using machine-learning-based path planning should disclose this at placement, not at renewal.

• Regulatory non-compliance: any flight conducted outside the scope of the CAA Operational Authorisation, including altitude, geographic, or crew credential breaches
• Unqualified remote pilot: operations flown by a pilot who does not hold the qualification specified in the Operational Authorisation — for BVLOS this goes beyond standard VLOS credentials (see qualification section below)
• Unapproved payload: hull policies typically exclude loss arising from payload not declared at inception; liability policies may exclude third-party damage caused by a payload release not covered by the ConOps
• War, cyber, and electronic warfare: standard market exclusions, but BVLOS operations are more exposed to GPS spoofing and jamming than VLOS flights — check whether cyber-physical loss is carved back in
• Intentional acts and criminal use: absolute exclusion in all policies; relevant where a BVLOS corridor passes over critical national infrastructure
• Consequential loss and data liability: hull and third-party liability policies rarely cover loss of data, mission failure costs, or contractual penalties — these require separate professional indemnity or cyber cover

Regulatory Triggers That Activate Exclusions

The CAA's Specific Category framework, set out in CAP 722 and the associated CAP 2012 guidance, requires operators to conduct a risk assessment — typically following a SORA-style methodology — for non-standard BVLOS operations. The UK CAA has developed its own post-Brexit approach to this framework and does not mandate SORA verbatim; operators should work from current CAA guidance rather than assuming direct equivalence with EASA processes. The ground risk class and air risk class outputs from that assessment determine the operational mitigations required, and underwriters use those same outputs to set coverage conditions. A change in operational scope that would require a revised risk assessment also triggers a material change notification obligation under the policy.

Pre-Defined Risk Assessments published by the CAA provide a structured route to authorisation for operations that fit a defined scenario. UK PDRA-G03, for example, covers certain BVLOS operations in a specific risk envelope — operators flying under a named PDRA should confirm with their broker that the policy wording is aligned to that PDRA's specific conditions, because an exclusion drafted for a bespoke authorisation may not map cleanly onto a PDRA scenario.

Article 16 of the retained UK UAS regulation allows certain operations to be conducted under schemes administered by CAA-approved organisations, where those organisations have been granted authority to issue authorisations within defined parameters. Operators flying under an Article 16 scheme who deviate from the scheme's standard scenario — for example, by operating over a higher population density than the scheme permits — will typically find that both the authorisation and the policy coverage are simultaneously invalidated.

Some underwriters are beginning to include Remote ID compliance as a policy condition in BVLOS wordings, particularly where the Operational Authorisation requires Remote ID broadcast. This is an emerging development rather than a universal market standard, but brokers should check the conditions schedule of any new wording for Remote ID language and advise operators accordingly.

Pilot Qualifications and MTOM Bands: Underwriting Eligibility

BVLOS remote pilot qualification requirements go materially beyond those needed for VLOS commercial operations. A General Visual Line of Sight Certificate demonstrates competency for VLOS flight and is not sufficient on its own to satisfy underwriter eligibility requirements for BVLOS programmes. The CAA Operational Authorisation for a BVLOS operation will typically specify a bespoke qualification, additional training evidence, or a competency framework accepted by the CAA for that specific operation type. Underwriters will require sight of those qualification records at submission, and a pilot who holds only a GVC for a BVLOS programme is likely to trigger the unqualified-pilot exclusion.

MTOM bands are a primary underwriting filter. Sub-25 kg Specific Category operations attract the broadest market appetite, though exclusions still apply in full. Platforms in the 25–150 kg band face a narrower panel of underwriters, higher scrutiny of detect-and-avoid systems, and exclusions that are less negotiable — particularly around autonomous segments and overwater operations. Platforms above 150 kg move toward the Certified Category, where airworthiness requirements and crew licensing obligations change the coverage structure entirely.

Certain submission characteristics will result in an outright declination rather than a quoted programme with exclusions. Brokers should pre-qualify submissions against common declination triggers before approaching the market, as a declined submission can affect future placement.

• No prior VLOS commercial operating history: underwriters typically require a demonstrable track record of compliant VLOS operations before extending BVLOS coverage
• No detect-and-avoid system fitted or declared: for operations in non-segregated airspace, absence of a DAA system is a common hard declination criterion
• Operational Authorisation not yet issued or under appeal: coverage cannot be bound against an authorisation that is not in force
• Loss history showing repeated regulatory non-compliance incidents: pattern of authorisation breaches signals systemic risk that most underwriters will not accept
• Aircraft MTOM not verifiable from manufacturer documentation: unverified MTOM creates category ambiguity that underwriters will not carry

Third-Party Liability: Regulatory Minimums and Overwater Exclusions

Minimum third-party liability insurance requirements for commercial UAS operations in the UK are grounded in the Air Navigation Order 2016 and associated statutory instruments, which impose obligations on operators of aircraft — including unmanned aircraft — to hold insurance against third-party liability. Operators should confirm with their broker that the liability limit is denominated in GBP and is sufficient to meet any contractual minimum imposed by the landowner, local authority, or infrastructure operator, as contractual minimums frequently exceed the regulatory baseline.

Overwater BVLOS operations introduce salvage and wreck removal liability that standard drone policies exclude. Where an aircraft comes down in waters under harbour authority jurisdiction or subject to Maritime and Coastguard Agency oversight, the operator may face obligations under the Merchant Shipping Act 1995 or harbour authority bylaws. This exposure is specific to those jurisdictional contexts and does not arise for all overwater operations — operators should map their corridor against relevant harbour authority boundaries and MCA-designated waters before assuming the standard policy is adequate. Specialist endorsements covering wreck removal costs are available in the London market but must be requested at placement.

Bodily injury and property damage exclusions for third parties are rarely absolute in commercial policies, but sub-limits and conditions apply. Policies written for operations over uninhabited areas may contain a populated-area exclusion that activates if the flight path deviates into a higher-density zone — a real risk for BVLOS corridors that cross variable terrain. The ground risk class assigned in the SORA-style assessment should be cross-referenced against the policy's geographic and population-density conditions.

Broker Workflow: Placing a BVLOS Programme That Minimises Exclusion Exposure

Effective placement follows a staged workflow. The first stage is an indicative terms exercise: the broker submits a summary of the operation — MTOM, corridor type, authorisation status, detect-and-avoid capability, and pilot qualification level — to establish which underwriters have appetite and what the broad exclusions landscape looks like before investing time in a full submission. Indicative terms are not bindable but allow the broker to identify exclusions that may be deal-breakers and address them before the formal submission.

The firm quotation stage requires a complete submission package. Underwriters will not issue firm terms without the full document set, and incomplete submissions result in broader exclusions, extended turnaround, or declinations. Once firm terms are issued, the broker should conduct a line-by-line exclusions review against the operator's ConOps before recommending binding. Binding without that review is the most common source of coverage disputes at claim stage.

Review exclusions at every renewal, not just at inception. BVLOS technology, CAA authorisation conditions, and underwriter appetite all evolve. An exclusion that was non-negotiable at inception may be endorsable twelve months later as the operator builds a claims-free track record. Equally, a change in the operator's ConOps — new aircraft type, new corridor, new payload, revised MTOM — may trigger exclusions that did not apply to the previous programme and must be notified promptly.

• CAA Operational Authorisation (current, in-force copy including all conditions)
• Full ConOps including lost-link procedure, emergency response plan, and corridor mapping
• SORA-style risk assessment output or PDRA acceptance documentation (e.g. PDRA-G03 acceptance letter)
• Aircraft specifications: manufacturer, model, MTOM, detect-and-avoid system details, and any modifications
• Remote pilot qualification records: all qualifications specified in the Operational Authorisation, not just GVC or A2 CofC
• 12-month loss history (nil returns accepted but must be declared)
• Payload declaration: type, mass, and any release or deployment mechanism

Frequently asked questions

What does a UK BVLOS drone insurance policy typically cover versus exclude?

A UK BVLOS policy typically covers hull loss or damage to the aircraft and third-party bodily injury and property damage arising from an insured flight. Standard exclusions include operations conducted outside the scope of the CAA Operational Authorisation, flights by pilots who do not hold the qualifications specified in the authorisation, undisclosed payload or aircraft modifications, cyber-physical loss unless specifically endorsed, and consequential or data loss. The precise scope depends on whether the policy is written on an all-risks or named-perils basis — all-risks wordings are broader but still subject to the full exclusions schedule.

What pilot qualifications do underwriters require for a BVLOS programme?

BVLOS qualification requirements go beyond those needed for VLOS operations. A General Visual Line of Sight Certificate covers VLOS flight only and is not sufficient on its own for BVLOS eligibility. The CAA Operational Authorisation for a BVLOS operation will specify the required qualification — typically a bespoke qualification, additional training evidence, or a competency framework accepted by the CAA for that operation type. Underwriters require sight of those specific qualification records at submission. Some underwriters impose competency requirements beyond the regulatory minimum, particularly for operations over congested areas or at extended range.

How do MTOM weight bands affect BVLOS insurance eligibility and exclusions?

MTOM is a primary underwriting filter. Sub-25 kg Specific Category platforms attract the broadest market appetite, though exclusions apply in full. Platforms in the 25–150 kg band face a narrower panel of underwriters, closer scrutiny of detect-and-avoid systems, and less negotiable exclusions — particularly around autonomous segments and overwater operations. Platforms above 150 kg move toward the Certified Category, where the coverage structure changes materially. Brokers should confirm MTOM from manufacturer documentation before submission, as unverified MTOM creates category ambiguity that underwriters will not carry.

Which UK regulations set the minimum liability insurance requirements for BVLOS operations?

Minimum third-party liability insurance requirements for commercial UAS operations in the UK are grounded in the Air Navigation Order 2016 and associated statutory instruments, which require operators of aircraft — including unmanned aircraft — to hold insurance against third-party liability. The CAA Operational Authorisation may impose additional minimum liability requirements beyond the regulatory baseline. Operators contracting with infrastructure owners, local authorities, or government bodies will often face contractual minimum limits that exceed both the regulatory and policy minimums — the policy limit should be set with reference to the highest of these three thresholds.

Does a change to my CAA Operational Authorisation affect my existing policy?

Yes. Most BVLOS policies incorporate the CAA Operational Authorisation by reference, either explicitly in the schedule or through a regulatory compliance condition. A material change to the authorisation — new aircraft type, revised corridor, changed crew requirements, revised MTOM — constitutes a material change to the risk and must be notified to the insurer promptly. Failure to notify can result in exclusions applying to claims arising from the changed operation, even if the CAA approved the change.

How does the broker submission and quotation process work for a BVLOS programme?

Placement follows two stages. First, the broker submits a summary of the operation to obtain indicative terms — this establishes underwriter appetite and flags likely exclusions before a full submission is prepared. Indicative terms are not bindable. Second, a complete submission package (Operational Authorisation, ConOps, risk assessment, aircraft specs, pilot qualifications, loss history, and payload declaration) is submitted for firm quotation. Once firm terms are issued, the broker should conduct a line-by-line exclusions review against the operator's ConOps before recommending binding. Turnaround from complete submission to firm quotation varies by underwriter and operation complexity — brokers should allow adequate lead time before the intended inception date.