BVLOS Drone Fleet Insurance | BVLOS Insure

Regulatory Context: Why BVLOS Changes the Risk Profile

In Great Britain, the Civil Aviation Authority governs unmanned aircraft operations under the framework established by the Air Navigation Order 2016 (as amended) and the UK-retained version of EU regulation 2019/947. Operations are stratified into Open, Specific, and Certified categories. BVLOS — Beyond Visual Line of Sight — sits firmly within the Specific category and requires either a CAA-issued Operational Authorisation or, for higher-risk scenarios, a Light UAS Operator Certificate (LUC) that grants self-authorisation privileges.

The Specific category introduces a formal Operational Safety Case (OSC) process, often structured around a SORA-style (Specific Operations Risk Assessment) methodology. Insurers who understand this framework can align policy conditions to the approved OSC rather than imposing blanket exclusions that contradict the authorised operating envelope. For fleet operators, each aircraft variant and each operational scenario may carry its own authorisation, meaning the insurance programme must be flexible enough to schedule multiple configurations without requiring a mid-term endorsement every time a new tail number is added.

Operators planning progression toward the Certified category — for example, those carrying dangerous goods or operating over congested areas at higher MTOM thresholds — should structure their current Specific-category programme so that coverage architecture can migrate upward without a complete re-underwrite. A specialist MGA will build that headroom in from inception.

What a BVLOS Fleet Programme Must Cover

A fleet programme differs from a single-aircraft policy in two fundamental ways: scheduling flexibility and aggregate limit management. Hull cover must attach to each aircraft at its declared value, with the ability to add, remove, or substitute airframes mid-term as the fleet evolves. For BVLOS operations, hull cover should explicitly address damage occurring outside visual range, including scenarios where the aircraft is operating autonomously or under reduced pilot intervention — conditions that some standard aviation hull wordings quietly exclude.

Third-party liability is the non-negotiable core. UK Regulation (EU) 2018/1139 (as retained) and the ANO require operators in the Specific category to hold liability cover commensurate with the risk. Limits are quoted in GBP and must be sufficient to meet the CAA's requirements for the specific operational authorisation held. For fleet operators conducting infrastructure inspection, logistics, or survey work over or near third parties, the liability exposure scales with payload mass, operational altitude, and population density beneath the flight corridor.

Beyond the statutory minimum, a well-structured programme will address:

• Payload cover — sensors, cameras, LiDAR units, and delivery payloads are typically scheduled separately from hull
• Ground equipment and ground control stations — often the highest-value single item in a BVLOS operation
• Cyber and data-link interference — loss of command-and-control link is a defined BVLOS hazard; some wordings now respond to C2 link failure as a covered peril
• Grounding liability — cover for third-party losses arising from an enforced operational pause following an incident
• Crew and operator liability — personal accident extensions for remote pilots and visual observers operating under the OSC

Fleet Scheduling and Mid-Term Flexibility

Fleet operators rarely operate a static asset register. Aircraft are added as programmes scale, retired after heavy landings, or temporarily grounded for maintenance. A BVLOS fleet policy should include a fleet declaration mechanism that allows the operator to notify additions and deletions within a defined window without requiring underwriter sign-off on each transaction. Premiums scale with hull value and BVLOS exposure, so the rating mechanism must be transparent enough that the operator can model the cost of adding a new airframe before committing to the purchase.

Deductibles typically rise on autonomous operations and on flights conducted at extended range from the ground control station. Brokers placing fleet business should negotiate deductible structures at inception rather than accepting schedule defaults, particularly where the operator's OSC includes contingency procedures that demonstrably reduce loss severity — for example, automated return-to-home protocols or redundant C2 links.

Where a fleet spans multiple aircraft types — fixed-wing for corridor survey, multirotor for close-inspection tasks — the programme should be written on a blanket basis with per-aircraft sub-limits rather than as a series of individual policies. This reduces administrative friction and ensures that aggregate limits are managed coherently across the whole operation.

Broker Workflow: Placing a BVLOS Fleet Programme

Brokers approaching the BVLOS market for the first time should expect a more detailed submission process than standard commercial lines. Underwriters will require the current CAA Operational Authorisation or LUC, the Operational Safety Case or SORA output, the aircraft manufacturer's specifications for each type on the fleet, and a statement of the operator's safety management system. The quality of the OSC is a direct underwriting input — a well-documented risk assessment with defined mitigations will produce a more competitive programme than a bare authorisation with no supporting documentation.

Loss history is relevant but not disqualifying. BVLOS is a maturing sector and many operators have limited claims history by virtue of the technology's relative novelty. Underwriters at a specialist MGA will weight the OSC, the operator's training records, and the maintenance regime more heavily than they would in a mature aviation class. Brokers should present this context proactively rather than waiting for the underwriter to ask.

Renewal cycles for BVLOS fleet programmes should be treated as an opportunity to re-benchmark the coverage architecture against the operator's current authorisation scope. If the operator has expanded into new operational scenarios — urban air mobility trials, BVLOS logistics corridors, or beyond-radio-line-of-sight operations using detect-and-avoid technology — the existing policy wording may not respond correctly without amendment.

Common Coverage Gaps in the BVLOS Market

The most frequent gap identified at claims stage is a mismatch between the approved operational envelope in the OSC and the coverage territory or altitude band in the policy schedule. If the CAA authorisation permits operations up to a defined altitude ceiling and the policy schedule references a lower limit carried over from a previous Open-category policy, the insurer has grounds to dispute a claim arising from an incident at the authorised altitude. Brokers must reconcile the policy schedule against the current authorisation at every renewal.

Autonomous and automated flight modes are a second common gap. Many hull wordings were drafted when BVLOS implied a remote pilot with continuous manual control. Modern BVLOS operations increasingly involve waypoint-following, automated landing, and AI-assisted obstacle avoidance. Wordings that define 'pilot error' without accounting for automated decision-making can create ambiguity at claims stage. Specialist MGAs are beginning to address this explicitly in policy language; brokers should request confirmation that autonomous modes are covered perils, not exclusions.

Finally, regulatory liability — the cost of responding to a CAA investigation or enforcement action following an incident — is rarely covered under standard aviation liability wordings. Operators who hold an LUC are subject to ongoing CAA oversight and face potential suspension of self-authorisation privileges following a serious occurrence. Regulatory defence costs cover is available as an extension and is worth considering for any operator whose business continuity depends on maintaining an active authorisation.

Frequently asked questions

What does BVLOS drone fleet insurance actually cover?

A specialist BVLOS fleet programme combines hull cover for each scheduled aircraft, third-party liability at limits commensurate with the CAA Specific category authorisation, and extensions for payload, ground equipment, and ground control stations. Better wordings also address cyber and data-link interference, autonomous flight modes, and regulatory defence costs. Coverage is structured around the operator's Operational Safety Case, so the policy responds to the authorised operating envelope rather than imposing generic aviation conditions that may conflict with approved procedures.

Which operators are eligible for a BVLOS fleet programme?

Eligibility centres on holding a valid CAA Operational Authorisation for Specific category BVLOS operations, or a Light UAS Operator Certificate with BVLOS scope. Operators in the process of obtaining authorisation can discuss pre-inception terms, but cover will not attach until the authorisation is in force. The fleet must have a documented Operational Safety Case, a named accountable manager, and a maintenance regime aligned to the manufacturer's requirements. There is no minimum fleet size, but the programme is designed for operators running two or more aircraft under a coherent operational framework.

How does the CAA's Specific category authorisation affect policy conditions?

The Specific category requires a formal risk assessment — typically following a SORA-style methodology — that defines the operational scenario, the ground risk class, the air risk class, and the mitigations in place. Underwriters use this document to set coverage conditions, deductible structures, and any operational warranties. If the authorisation is amended — for example, to extend the operational area or add a new aircraft type — the policy must be endorsed to reflect the updated scope. Operating outside the authorised envelope will typically void cover for any incident arising from that deviation.

What information does a broker need to submit for a BVLOS fleet placement?

A complete submission includes: the current CAA Operational Authorisation or LUC certificate; the Operational Safety Case or SORA output document; manufacturer specifications and declared values for each aircraft on the fleet; a description of all operational scenarios (inspection, survey, logistics, etc.); details of the ground control station and C2 link architecture; the operator's safety management system documentation; and any loss history for the past three years. The more complete the submission, the faster the underwriting response and the more accurately the programme can be structured.

What regulatory triggers should prompt a mid-term policy review?

Any change to the CAA Operational Authorisation — including an expanded operational area, a new aircraft type, a higher MTOM threshold, or a change in operational scenario — is a mandatory notification trigger. Beyond regulatory changes, operators should review coverage when they introduce autonomous or AI-assisted flight modes not previously declared, when they begin operations over new ground risk environments (for example, moving from rural to peri-urban corridors), or when they add payload types that materially change the third-party liability exposure. Failure to notify material changes can result in claims being disputed at the point of loss.

Can a single programme cover a mixed fleet of fixed-wing and multirotor aircraft?

Yes. A blanket fleet programme can schedule multiple aircraft types under a single policy, with per-aircraft hull sub-limits and a shared aggregate liability limit. Each aircraft type will be rated on its own risk characteristics — MTOM, operational scenario, autonomy level — but the administrative and aggregate management benefits of a single programme outweigh the complexity of maintaining separate policies. Brokers should confirm at inception that the wording does not restrict coverage to a single aircraft category, as some standard aviation hull forms default to a single type.