BVLOS Insurance Exclusions UK Operators Should Know

The Regulatory Foundation Underwriters Build Exclusions On

The UK's UAS regulatory framework is established by the Air Navigation Order 2016 as amended by SI 2020/1476, and by the Unmanned Aircraft (Amendment) (EU Exit) Regulations 2020 (SI 2020/1517). SI 2020/1517 retained the EU's Open, Specific, and Certified category structure into UK domestic law following Brexit, but EASA itself has no jurisdiction in UK airspace. The CAA is the sole competent authority for all UK UAS operations, including BVLOS. Any reference to EASA approvals in a UK policy context is relevant only to operators who also hold EU approvals for operations in EU member states — it is not a UK coverage trigger.

BVLOS flight falls in the Specific category regardless of aircraft mass. The mass threshold matters for a different reason: aircraft above 25 kg MTOM require Specific category authorisation even for standard VLOS operations, but any BVLOS operation — irrespective of how light the aircraft is — requires a CAA Operational Authorisation or a compliant PDRA. Insurers treat the OA or PDRA as the contractual baseline: the policy attaches to the scope of that authorisation, and anything outside it is excluded by definition.

Two PDRA variants are directly relevant to UK BVLOS operators. PDRA-S1 covers lower-risk BVLOS operations in sparsely populated areas with defined ground risk buffers and specific C2 link requirements. PDRA-S2 covers operations with a higher ground risk profile, typically involving flight over or near populated areas, and carries more demanding mitigations including enhanced detect-and-avoid provisions. The PDRA variant an operator holds shapes which exclusions apply: a policy written to PDRA-S1 parameters will not respond to an operation that should have been conducted under PDRA-S2 conditions.

Crew competency is a coverage condition, not a background consideration. The General VLOS Certificate is the baseline UK remote pilot qualification, but BVLOS Operational Authorisations routinely require additional endorsements or operator-specific training evidence that goes beyond the GVC. Where an OA specifies a higher competency standard, the insurer will treat that standard as a condition precedent. A Remote Pilot who holds only a GVC when the OA demands more will find hull and liability coverage unavailable if a loss occurs.

The Most Common BVLOS Insurance Exclusions

Policy exclusions in BVLOS programmes cluster around three themes: regulatory non-compliance, operational scope creep, and technology failure outside agreed parameters. Each theme can void coverage entirely or reduce it to a sub-limit that falls well short of a realistic loss scenario.

Regulatory non-compliance exclusions are the most absolute. If the aircraft is flown without a valid CAA OA, outside the geographic or altitude limits stated in that OA, or by a Remote Pilot who does not hold the competency level the OA requires, the insurer will decline the claim. This is a condition precedent to coverage in most BVLOS wordings, not a discretionary assessment.

Operational scope exclusions address what the aircraft is doing, not just where it is flying. Payload exclusions are common: a policy written for survey operations may exclude agricultural spray, cargo drop, or any payload that changes the aircraft's mass above a declared maximum. Autonomous flight exclusions are increasingly prevalent — if the OA permits supervised autonomy but the policy wording was written for piloted BVLOS, a fully autonomous segment of the flight may not be covered.

• Flying outside the geographic or altitude envelope stated in the CAA Operational Authorisation
• Remote Pilot competency below the level required by the OA (e.g., GVC holder where additional BVLOS endorsements are mandated)
• Command-and-control link operating on a frequency or technology not declared at inception
• Payload mass or type exceeding the declared configuration
• Autonomous or AI-directed flight segments where the policy was written for human-piloted BVLOS
• Operations over congested areas or crowds where the OA does not explicitly permit them
• Failure to maintain required separation from manned aviation where a detect-and-avoid system was a coverage condition
• Cyber or electronic warfare interference — often excluded or sub-limited in standard wordings
• PDRA variant mismatch — conducting an operation that falls within PDRA-S2 parameters under a policy written to PDRA-S1 conditions

Hull-Specific Exclusions Operators Frequently Miss

Hull policies for BVLOS aircraft are valued on an agreed-value or market-value basis, and the exclusions reflect the higher loss-frequency environment of extended-range operations. Wear-and-tear exclusions are standard, but BVLOS operators should pay particular attention to battery and propulsion exclusions: many wordings exclude gradual deterioration of battery cells, which can be difficult to distinguish from a sudden failure that causes a crash.

Maintenance exclusions are another area of exposure. If the aircraft has not been serviced in accordance with the manufacturer's maintenance schedule or the operator's own approved maintenance programme, the insurer may decline a hull claim on the basis that the loss was attributable to a maintenance failure. BVLOS aircraft accumulate flight hours faster than VLOS platforms, so maintenance intervals arrive sooner than operators sometimes anticipate. Underwriters will ask for maintenance records at submission, and gaps in those records can affect both eligibility and the scope of hull coverage offered.

Geofencing and software exclusions are emerging as a distinct category. Where an operator has agreed to fly within a digital geofence as a condition of the OA, a policy may exclude losses that occur because geofencing software was disabled, overridden, or failed to update. Operators should confirm whether their policy treats geofencing as a coverage condition or merely as a risk-management recommendation.

C2 link architecture is increasingly a named coverage condition rather than background information. Underwriters writing BVLOS hull coverage want to know the specific command-and-control link technology — satellite, cellular, licensed spectrum — and may exclude losses arising from link failure on a technology not declared at inception. Operators who upgrade or change their C2 architecture mid-term should notify their broker immediately.

Liability Gaps in BVLOS Programmes

Third-party liability for BVLOS operations is governed by the Air Navigation Order 2016 as amended, which sets out the flight rules and operator responsibilities that frame legal liability exposure. The ANO does not itself set a specific indemnity quantum — operators should confirm with their broker what minimum indemnity level, if any, the CAA has attached as a condition of their specific OA, and ensure the policy limit meets or exceeds that requirement.

Pollution and contamination exclusions are standard in most liability wordings and are particularly relevant to BVLOS operators carrying agricultural or industrial payloads. A spray drone that releases product outside the intended area due to a navigation failure may generate a pollution claim that a standard liability section will not cover. Operators in those sectors should ask their broker to source a policy with a pollution buy-back or a separate environmental liability extension.

Data and privacy liability is excluded in virtually all standard UAS liability policies. BVLOS operations over extended corridors collect significant imagery and sensor data. A claim arising from alleged unlawful surveillance, UK GDPR breach, or misuse of captured data will not be covered under a hull and liability programme — it requires a separate cyber or professional indemnity policy. Operators who are also data controllers under the Data Protection Act 2018 should ensure their insurance programme addresses this gap explicitly.

Structuring a BVLOS Programme That Minimises Exclusion Risk

The most effective way to reduce exclusion exposure is to align the policy wording to the OA before the OA is finalised, not after. Brokers should engage the underwriter at the OA application stage so that coverage conditions and operational parameters are agreed in parallel. A policy issued after the OA is granted may contain exclusions that conflict with operational requirements the operator has already committed to.

Disclosure is the single most important obligation at inception and renewal. The Insurance Act 2015 replaced the Marine Insurance Act 1906 duty of disclosure with a duty of fair presentation, which requires the insured to disclose every material circumstance in a clear and accessible manner. Breach of that duty carries graduated consequences: a deliberate or reckless breach entitles the insurer to avoid the policy and retain the premium; an innocent breach may result in a proportionate remedy or an additional premium charge. For BVLOS operators, material circumstances include OA conditions, C2 link architecture, crew qualifications, payload configurations, and any prior losses or CAA correspondence.

BVLOS operations evolve — new corridors, new payloads, new detect-and-avoid technology, changes to crew. Each material change should be notified to the insurer promptly. Avoidance is a more severe outcome than a declined claim: it unwinds the entire policy from inception.

Fleet programmes covering multiple BVLOS aircraft should confirm that each aircraft's OA is scheduled individually or that the policy contains a blanket BVLOS endorsement covering all aircraft operated under the operator's permissions. A fleet policy written for VLOS operations with a BVLOS endorsement added for one aircraft may not automatically extend to a second aircraft added mid-term. Brokers should also review war, terrorism, and sanctions exclusions — BVLOS operations near critical national infrastructure or in contested airspace may engage exclusions that are standard in aviation markets but rarely discussed with UAS operators.

Broker Workflow: Submission, Placement, and Regulatory Triggers

Placing a BVLOS programme requires a materially more detailed submission than a standard commercial UAS risk. Specialist underwriters — whether Lloyd's syndicates or MGAs operating under delegated authority — will not quote from a generic UAS proposal form. The submission must map directly to the OA conditions and the operational safety case. Brokers should assemble the following before approaching the market:

BVLOS programmes take longer to place than standard UAS risks. Specialist underwriters may require several weeks of lead time to review the operational safety case, assess the C2 link architecture, and agree coverage conditions — compared with the days typically needed for a straightforward commercial VLOS risk. Operators should engage their broker well in advance of the intended start date, and ideally before the OA application is submitted to the CAA, so that insurability questions can be resolved in parallel with the regulatory process.

The CAA has the power to suspend or vary an OA at any time. If an OA is suspended following an incident, some policy wordings suspend coverage automatically on the basis that the operator no longer has a legal right to fly. Operators should check whether their policy contains a regulatory suspension clause and what notice period applies. Any CAA correspondence regarding the OA — including routine variations — should be notified to the broker immediately, as it may constitute a material change requiring underwriter agreement.

Changes to the Air Navigation Order or CAA guidance that affect the conditions under which BVLOS is permitted can create mid-term coverage gaps if the policy wording references a specific regulatory version. Brokers should use language that references the ANO as amended from time to time, rather than a fixed version, to avoid a situation where a regulatory update creates an unintended exclusion.

• Copy of the CAA Operational Authorisation or PDRA approval documentation
• Operational safety case, including ground risk assessment and airspace risk assessment
• Aircraft maintenance records demonstrating compliance with the approved maintenance programme
• Crew licence and logbook evidence, including GVC certificate and any additional BVLOS endorsements or operator-specific training records
• Prior loss history for all UAS operations, not limited to BVLOS
• C2 link architecture diagram specifying link technology, frequency, redundancy provisions, and any handover protocols

Frequently asked questions

Does a standard commercial drone policy cover BVLOS operations in the UK?

No. Standard commercial UAS policies are written for Open or lower-risk Specific category VLOS operations. BVLOS requires a dedicated policy endorsement or a standalone BVLOS programme that references your CAA Operational Authorisation and, where applicable, the specific PDRA variant under which you operate. Flying BVLOS under a standard policy and suffering a loss will almost certainly result in a declined claim on the basis that the operation fell outside the policy's scope.

What eligibility criteria do underwriters apply to BVLOS programmes?

Underwriters typically require a valid CAA Operational Authorisation or PDRA approval, a Remote Pilot holding the competency level specified in that OA (which will usually exceed the baseline GVC), a documented operational safety case, evidence of a maintained detect-and-avoid or conflict-management system where the OA requires one, and current aircraft maintenance records. Eligibility criteria vary by underwriter and by the risk profile of the operation — operators should expect a more detailed assessment for PDRA-S2 or bespoke OA operations than for lower-risk PDRA-S1 profiles.

How does the broker placement process work, and how long does it take?

The broker assembles a detailed submission covering the aircraft schedule, OA conditions, operational corridors, payload types, crew qualifications, maintenance records, C2 link architecture, and prior loss history. This is presented to specialist UAS underwriters — typically Lloyd's syndicates or MGAs with delegated authority — who may request the full operational safety case before quoting. BVLOS placements require meaningfully more lead time than standard UAS risks; operators should engage their broker well before the intended start date, and ideally before the OA application is submitted to the CAA.

How does the Insurance Act 2015 affect BVLOS policy disclosure obligations?

The Insurance Act 2015 replaced the Marine Insurance Act 1906 duty of disclosure with a duty of fair presentation. BVLOS operators must disclose every material circumstance — OA conditions, C2 link architecture, crew qualifications, payload configurations, prior losses, and any CAA correspondence — clearly and accessibly at inception and renewal. A deliberate or reckless breach entitles the insurer to avoid the policy and retain the premium. An innocent breach may result in a proportionate remedy or an additional premium charge. The graduated consequences make thorough disclosure a commercial priority, not just a legal formality.

Which regulatory changes most commonly trigger a mid-term coverage gap?

CAA suspension or variation of an OA is the most immediate trigger — some policy wordings suspend coverage automatically when the authorisation is suspended. Changes to the Air Navigation Order that alter BVLOS conditions, updates to PDRA requirements, and changes to airspace classification in the operational corridor can all affect coverage if the policy wording is tied to a specific regulatory version. Operators should notify their broker of any CAA correspondence regarding their OA as soon as it is received, and brokers should ensure policy language references the ANO as amended from time to time rather than a fixed version.

Does a UK BVLOS policy automatically extend to operations in EU member states?

No. Following Brexit, the UK and EU operate entirely separate regulatory frameworks. SI 2020/1517 retained the Open/Specific/Certified structure in UK domestic law, but EASA has no jurisdiction in UK airspace and UK CAA approvals have no automatic recognition in EU member states. A policy placed in the UK market covers UK airspace unless a geographic extension is explicitly endorsed. Operators flying into EU airspace — including cross-border routes near the Irish border or the English Channel corridor — require either a separate policy placed in an EU market or a territorial extension naming the relevant EU jurisdictions, and will need to satisfy the competent authority requirements of the relevant EU member state.