BVLOS Drone Insurance: Fleet Blanket vs Per-Aircraft UK

Regulatory Context: Why BVLOS Changes the Calculus

In the UK, Beyond Visual Line of Sight operations sit within the CAA's Specific category under the UK Retained EU Law UAS Regulation (UK SI 2020/1476). CAA CAP 722 (UAS: Guidance for Operators) provides the overarching operational framework, while CAP 2012 (BVLOS Operations) is the dedicated reference document that underwriters and operators should cite when structuring a BVLOS submission. Operators must hold a valid Operational Authorisation (OA) issued against a Predefined Risk Assessment (PDRA), a full Specific Operations Risk Assessment (SORA), or a bespoke risk assessment. Each OA is aircraft-type-specific: it references the make, model, and often the serial number of the UAS approved for the operation. That regulatory granularity has a direct knock-on for insurance, because underwriters need to confirm that every hull on risk is covered by a corresponding OA before they will pay a BVLOS loss.

Two UK-accepted PDRAs give brokers concrete regulatory anchors. PDRA-G01 covers certain standard VLOS and short-range BVLOS scenarios within defined parameters; PDRA-G02 applies where the operational scope extends beyond PDRA-G01 boundaries. Where neither PDRA fits, operators must complete a full SORA, which produces a SAIL — Specific Assurance and Integrity Level, on a scale of 1 to 6 — that defines the robustness of the safety mitigations required. The SAIL level is a key submission document for underwriters, because it signals the residual risk the operator has accepted and the operational controls in place.

BVLOS operations carry materially different risk profiles from VLOS work — longer range, reduced pilot situational awareness, greater dependency on C2 link integrity, and exposure to airspace that may include manned traffic. A policy that works cleanly for a VLOS inspection fleet may leave gaps the moment the same aircraft crosses into an OA-authorised BVLOS corridor. Operators and brokers must confirm that the policy wording explicitly extends to BVLOS use and that any geographic or altitude endorsements align with the OA's approved area of operation. Importantly, the CAA OA application process for a full SORA-based authorisation is measured in months rather than weeks; brokers advising clients on programme inception timing should factor that lead time into the placement schedule to avoid a gap between OA grant and policy inception.

Fleet Blanket Policies: Structure and Suitability

A fleet blanket policy covers a defined class of aircraft up to an agreed maximum hull value per unit, without scheduling each tail individually. The operator declares the total fleet size and the maximum single-aircraft value at inception; the underwriter sets a blanket limit that applies across the portfolio. Mid-term acquisitions that fall within the declared parameters are automatically covered from the date of purchase, which is operationally convenient for operators who rotate stock frequently or run lease-return programmes. In practice, underwriters tend to favour blanket structures where the fleet exceeds a minimum size threshold or where the aggregate hull value across the portfolio makes individual scheduling administratively disproportionate — brokers should confirm the specific threshold with the underwriter at submission.

The liability side of a blanket fleet programme typically aggregates across all aircraft, meaning the full third-party liability limit is available regardless of which hull is involved in an incident. For BVLOS operators running simultaneous multi-aircraft missions — survey corridors, infrastructure inspection, or logistics trials — this aggregation matters: a single-aircraft limit that looked adequate for VLOS work may be insufficient when two or more aircraft are airborne concurrently under separate OAs.

The trade-off is that blanket structures require accurate fleet declarations. Operators should ensure that declared maximum hull values reflect actual replacement costs, because material discrepancies can affect hull claim settlements. Operators should also confirm whether the blanket extends to ground equipment, payload, and data loss, or whether those are scheduled separately — BVLOS payloads (LiDAR, multispectral sensors, SAR systems) often carry values that dwarf the airframe itself.

• Automatic cover for new acquisitions within declared parameters — no mid-term endorsement required
• Single aggregate liability limit available across all concurrent flights
• Simplified administration for fleets with high turnover or leased aircraft
• Accurate maximum-value declarations are essential to support hull claim settlements
• Payload and ground-equipment cover may need separate scheduling

Per-Aircraft Scheduled Policies: Structure and Suitability

A per-aircraft scheduled policy lists every hull by make, model, serial number, and agreed hull value. Each aircraft is a discrete insured item, and the premium reflects the specific risk characteristics of that unit — its MTOM, its propulsion type, its OA scope, and its operational history. For BVLOS programmes, this granularity is often preferred by underwriters because it maps directly onto the CAA OA, which is itself aircraft-specific. Scheduled structures are typically the underwriter preference where the fleet is small, where each aircraft carries a high individual hull value, or where the operational scope of each platform differs materially.

Scheduled policies give operators and brokers precise control over coverage terms at the aircraft level. A fixed-wing BVLOS platform operating a long-range corridor survey can carry different deductibles, different geographic endorsements, and different payload extensions from a multirotor on the same programme. That flexibility is valuable when the fleet is heterogeneous — mixing VTOL transition aircraft, fixed-wing, and tethered systems under a single master policy but with tailored per-hull terms.

The administrative burden is higher: every acquisition, disposal, or serial-number change requires a mid-term endorsement, and failure to notify promptly can leave a new hull uninsured. For operators running lean operations teams, that overhead is a genuine risk. Brokers placing scheduled programmes should build a notification protocol into the client onboarding process and confirm that the policy wording includes a short discovery period for unreported additions.

• Precise hull-level coverage aligned to each CAA Operational Authorisation
• Tailored deductibles, endorsements, and payload extensions per aircraft
• Direct mapping to OA serial-number requirements simplifies claims evidence
• Mid-term endorsement required for every fleet change
• Higher administrative overhead — notification failures can create coverage gaps

Liability Limits, Aggregation, and BVLOS-Specific Considerations

UK operators in the Specific category must carry third-party liability insurance meeting the minimum requirements set out in the retained EU regulation on insurance requirements for aircraft operators (derived from the EC 785/2004 framework as it applies in UK law). Limits are quoted in GBP and must be commensurate with the aircraft's MTOM and operational risk. The retained framework establishes weight-based liability tiers; the lowest tier covers aircraft up to 500 kg MTOM, with higher tiers applying above that threshold. Commercial BVLOS platforms typically fall within the sub-500 kg tier, but the CAA may specify a higher limit as a condition of the OA where the operation involves populated areas, controlled airspace, or proximity to aerodromes. The appropriate limit should be agreed with the underwriter before the OA application is submitted.

Whether you choose a blanket or scheduled structure, the aggregation clause deserves close attention on BVLOS programmes. If two aircraft are flying simultaneously under separate OAs and both are involved in a single event — a C2 link failure affecting a shared ground station, for example — the policy needs to respond to both losses without exhausting the aggregate. Brokers should confirm whether the policy operates on a per-occurrence or per-aircraft basis for liability, and whether a shared-infrastructure failure constitutes one occurrence or two.

Autonomous and highly automated BVLOS operations introduce an additional underwriting consideration: the boundary between pilot error and product liability. If the aircraft deviates from its planned route because of a flight-management system fault rather than a pilot input, the claim may engage the manufacturer's product liability rather than the operator's third-party liability. Operators should confirm that their policy does not exclude losses attributable to autonomous or AI-driven decision-making, and that the wording is consistent with the level of automation described in their SORA and reflected in the SAIL assigned.

Common BVLOS Policy Exclusions Brokers Must Check

BVLOS wordings contain exclusions that do not routinely appear in standard commercial drone policies. Brokers must review these before binding and, where necessary, negotiate endorsements or seek alternative markets. The exclusions most material to this audience are listed below.

Cyber and C2-link failure exclusions are particularly significant for BVLOS operations, where the command-and-control link is the primary means of pilot intervention. A standard cyber exclusion may void cover for a loss caused by signal jamming, spoofing, or a software-driven loss of link — precisely the scenarios most likely to cause a BVLOS hull loss. Brokers should confirm whether the wording carves back C2-link failure as an insured peril or whether a separate cyber endorsement is required.

Autonomous and AI decision-making carve-outs are increasingly common as underwriters seek to limit exposure to losses where no human pilot input was involved. Operators running supervised-autonomous or fully-autonomous BVLOS missions should treat this exclusion as a priority negotiation point. War, terrorism, and nuclear exclusions are standard across the market and are unlikely to be negotiable, but operators should confirm that the terrorism exclusion does not inadvertently capture signal-interference events in sensitive airspace.

• Cyber and C2-link failure — may exclude the most common BVLOS loss scenario; seek explicit carve-back
• Autonomous and AI decision-making — increasingly standard; negotiate if operating beyond supervised flight
• War and terrorism — market-standard; confirm terrorism exclusion does not capture signal-interference events
• Nuclear — market-standard and non-negotiable
• Payload and data loss — typically excluded from hull sections; requires separate endorsement or standalone cover

Placing the Programme: What Underwriters Will Ask

A complete submission to a BVLOS underwriter should include the CAA Operational Authorisation number and expiry date for each aircraft or aircraft type; the PDRA reference (PDRA-G01, PDRA-G02, or bespoke) or, where a full SORA has been completed, the SAIL level assigned; the ConOps including operational volume, ground risk buffer, and adjacent airspace; a current fleet schedule with make, model, serial number, and hull value for each aircraft; crew competency records and remote pilot licence details; and a three-year loss history. Blanket programmes additionally require a declaration of the maximum fleet size and maximum single-aircraft hull value. CAP 2012 should be referenced in the submission where the operation falls within its scope — underwriters familiar with the UK market will expect to see it cited.

Hull valuations must be defensible. Agreed value policies are standard in the BVLOS market; brokers should obtain manufacturer quotes or recent purchase invoices and include them in the submission to support the declared values. This is particularly important for blanket programmes where the maximum declared value sets the ceiling for any single hull claim.

Renewal is not automatic on BVLOS programmes. OA renewals, fleet changes, operational scope expansions, and incident history all affect the risk profile materially. Brokers should begin the renewal process well in advance of expiry — bearing in mind that a SORA-based OA renewal with the CAA can itself take several months — and confirm that any changes to the SORA, SAIL level, or ConOps since the last binding are disclosed. Non-disclosure of a material change in BVLOS scope is one of the most common grounds for claim avoidance in this class.

Frequently asked questions

Does a fleet blanket policy automatically cover a new BVLOS aircraft added mid-term?

It depends on the policy wording. Most blanket structures include automatic cover for new acquisitions that fall within the declared aircraft class and maximum hull value, from the date of purchase. However, if the new aircraft requires a separate CAA Operational Authorisation — which is almost always the case for BVLOS platforms — the underwriter will need to see that OA before confirming the BVLOS extension applies. Notify your broker immediately on acquisition and do not assume BVLOS cover attaches without confirmation.

What liability limit is required for UK BVLOS operations in the Specific category?

Minimum third-party liability requirements for UK UAS operators derive from the retained EU regulation on insurance requirements for aircraft operators, scaled by the aircraft's maximum take-off mass. The framework establishes weight-based tiers, with the sub-500 kg band covering most commercial BVLOS platforms. BVLOS operations over populated areas, near aerodromes, or within controlled airspace will typically require limits well above the regulatory minimum, and the CAA may specify a higher limit as a condition of the Operational Authorisation. The appropriate limit should be determined by reference to the SORA output and SAIL level assigned, and agreed with your underwriter before the OA application is submitted.

Can a single policy cover both VLOS and BVLOS operations on the same aircraft?

Yes, provided the policy wording explicitly extends to BVLOS use and the underwriter has been informed of both operational modes at inception. Many standard commercial drone policies exclude BVLOS by default or treat it as a rated endorsement. Brokers must confirm that the BVLOS extension is active, that it references the correct OA, and that any geographic or altitude restrictions in the endorsement are consistent with the approved operational volume. A policy that covers VLOS but silently excludes BVLOS will not respond to a loss that occurs beyond visual line of sight.

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

A complete submission should include: the CAA Operational Authorisation number and expiry date for each aircraft or aircraft type; the PDRA reference (PDRA-G01, PDRA-G02, or bespoke) or the SAIL level (1–6) where a full SORA has been completed; the ConOps including operational volume, ground risk buffer, and adjacent airspace; a current fleet schedule with make, model, serial number, and hull value; crew competency records and remote pilot licence details; and a three-year loss history. Blanket programmes additionally require a declaration of maximum fleet size and maximum single-aircraft hull value. Brokers should also note that CAA OA applications based on a full SORA are measured in months, so programme inception timing must account for that lead time. Incomplete submissions are the primary cause of delayed terms in this class.

Does a BVLOS policy cover payload and data loss as well as the airframe?

Hull cover under a standard BVLOS policy typically extends to the airframe and permanently installed equipment. Detachable payloads — LiDAR units, multispectral cameras, synthetic aperture radar systems — are usually scheduled separately and valued independently, because their replacement cost often exceeds that of the airframe. Data loss and mission failure are generally excluded from property sections and require specific endorsements or a separate technology errors and omissions policy. Brokers should confirm the payload and data position explicitly at placement, not at the point of claim.

What triggers a material change notification obligation on a BVLOS programme?

Any change that alters the risk profile described at inception is a potential material change. For BVLOS programmes, common triggers include: a new or amended CAA Operational Authorisation; a change in PDRA category (for example, moving from PDRA-G01 to PDRA-G02 scope) or a revised SAIL level following a SORA update; an expansion of the operational area or altitude ceiling; a change in aircraft type, MTOM, or serial number; a change in the level of automation; a new payload type; a change in crew or remote pilot competency; and any incident or near-miss, whether or not a claim is made. Brokers should build a standing instruction into the client relationship requiring prompt notification of any of these events.