BVLOS Drone Insurance: Aggregate vs Per-Flight Limits UK

How Aggregate and Per-Flight Limits Are Structured

An aggregate limit is the maximum the insurer will pay across all claims arising during the policy period, regardless of how many separate incidents occur. Once that ceiling is eroded — whether by one large loss or several smaller ones — no further liability cover remains until renewal. For high-frequency BVLOS operations, such as pipeline inspection corridors or logistics routes flown multiple times per week, aggregate erosion is a genuine mid-term risk, not a theoretical one.

A per-flight limit, by contrast, resets the available indemnity for each discrete flight or, in some wordings, each flight day. The aggregate still exists — it caps total exposure for the insurer — but the per-flight sub-limit governs what is available for any single occurrence. This structure is more common in programmes designed around variable operational tempo, where the operator cannot predict in advance whether they will fly ten sorties or two hundred in a given month.

Some BVLOS policies use a hybrid: a per-occurrence limit that is high enough to cover the realistic worst-case for a single flight, combined with an annual aggregate that reflects the insurer's total risk appetite for the portfolio. Brokers placing specialty programmes should read the definitions section carefully — 'occurrence', 'flight', and 'sortie' are not interchangeable across all wordings, and the distinction matters when a single BVLOS mission involves multiple waypoints, relay handovers, or a ground control station transfer.

UK Regulatory Context: CAA Specific Category and Operator Authorisation

In the UK, BVLOS operations sit within the CAA's Specific category under the Air Navigation Order 2016 as amended, and require either a CAA-issued Operational Authorisation (OA) or, for lower-risk profiles, a declaration against a CAA-approved standard scenario. The Specific category does not prescribe a minimum liability limit in the way that the Open category's 250 g threshold triggers different requirements — instead, the CAA expects the operator's risk assessment and Operations Manual to demonstrate that the insurance programme is commensurate with the risk.

That 'commensurate with risk' standard is where aggregate versus per-flight architecture becomes a regulatory, not just a commercial, question. An operator flying a fixed daily inspection route over a low-population corridor faces a different aggregate erosion profile than one flying ad hoc urban logistics sorties. The CAA's SORA-derived risk methodology — which underpins most Specific category OA applications — scores ground risk class and air risk class separately; your policy structure should mirror that risk stratification.

Operators holding a CAA Operational Authorisation are required to maintain valid third-party liability insurance throughout the authorisation period. A policy that lapses into an exhausted aggregate mid-term is not compliant, even if the premium has been paid. Brokers should build mid-term aggregate monitoring into their service model for any BVLOS client flying at volume.

Which Structure Fits Which BVLOS Operation

Per-flight or per-occurrence structures tend to suit operations where individual sorties carry high, variable third-party liability exposure — urban air mobility trials, beyond-visual-line-of-sight cargo delivery over populated areas, or crewed-uncrewed integration corridors. In these scenarios, the operator needs certainty that the full limit is available for the worst-case single event, and the insurer prices accordingly.

Aggregate-only structures are more common in lower-frequency, lower-density operations: agricultural survey programmes, offshore energy asset inspection, or linear infrastructure monitoring in sparsely populated terrain. Here, the probability of multiple large losses in a single policy year is lower, and the aggregate ceiling is unlikely to be meaningfully eroded before renewal.

Fleet operators running multiple aircraft simultaneously — a configuration increasingly common in corridor-based BVLOS approvals — need to address whether the limit applies per aircraft or per fleet. Some wordings treat a simultaneous multi-aircraft incident as a single occurrence; others treat each aircraft as a separate occurrence. This distinction can materially affect recovery in a scenario where a comms failure grounds or crashes several aircraft at once.

• High-frequency urban BVLOS: per-occurrence limit with a separately stated aggregate is the preferred structure
• Low-frequency rural or offshore inspection: aggregate-only may be adequate if the annual sortie count is modest
• Multi-aircraft simultaneous ops: confirm whether 'occurrence' is defined per aircraft or per event
• Corridor or hub-and-spoke logistics: model aggregate erosion against projected annual sortie volume before binding
• Crewed airspace integration: check whether the policy responds to mid-air proximity events as well as ground impact

Hull Cover: Total Loss, Partial Loss, and BVLOS-Specific Exclusions

Hull cover for BVLOS aircraft is typically written on an agreed value basis, which avoids disputes about market value depreciation at the point of a total loss. Premiums scale with hull value, the aircraft's autonomy level, and the degree of BVLOS exposure — a fully autonomous beyond-visual-line-of-sight operation carries a different risk profile than a remotely piloted flight with a visual observer at the far end.

Deductibles typically rise on autonomous operations and on flights conducted without a remote pilot in active control. Operators should check whether the hull wording responds to a loss caused by a command-and-control link failure — one of the most common BVLOS loss scenarios — or whether that is carved out as a navigation or systems exclusion. Some wordings exclude losses arising from flight outside the approved operational volume defined in the CAA Operational Authorisation; flying outside your OA boundaries can void hull cover as well as breach your regulatory approval.

Payload cover is usually written separately or as an endorsement. For BVLOS operations carrying sensors, cameras, or cargo, confirm whether the payload limit is sublimited within the hull section or stands alone, and whether it responds to loss during transit as well as during flight.

Broker Workflow: Placing a BVLOS Programme Correctly

Before approaching the market, assemble the operator's CAA Operational Authorisation (or the standard scenario declaration), the current Operations Manual, the SORA or equivalent risk assessment, and a twelve-month projected sortie log. Underwriters writing BVLOS business will ask for all of these; presenting them upfront compresses the quote turnaround and signals that the operator runs a compliant programme.

Specify the limit structure you are seeking — per-occurrence, aggregate, or hybrid — in the submission rather than leaving it to the underwriter to default. If the operator's OA covers multiple aircraft types or multiple operational volumes, list each separately. Underwriters price BVLOS exposure by aircraft type, operational area, and autonomy level; a bundled submission that obscures these variables will produce a less competitive quote.

At renewal, review aggregate utilisation for the expiring period. If the operation has grown in sortie volume or expanded its OA, the prior year's limit structure may no longer be adequate. A programme that was correctly sized at inception can become structurally inadequate within twelve months if the operator scales without a corresponding policy review.

• Submission documents: CAA OA or standard scenario declaration, Operations Manual, SORA, projected sortie log
• Specify limit structure (per-occurrence / aggregate / hybrid) explicitly in the submission
• List each aircraft type and operational volume separately
• Review aggregate utilisation at mid-term for high-frequency operations
• Confirm payload, ground equipment, and data liability are addressed as separate lines or endorsements

Cross-Border and Multi-Jurisdiction BVLOS Considerations

UK-registered operators conducting BVLOS flights in EU member states post-Brexit must satisfy both CAA requirements and the EASA Open/Specific/Certified framework as implemented by the relevant national competent authority — in Germany, for example, the Luftfahrt-Bundesamt (LBA) administers EASA rules at national level. A UK policy wording that references only UK airspace and CAA authorisations may not respond to a loss occurring in EU airspace without a specific territorial extension.

For operators with global programmes — including those flying in the UAE under GCAA jurisdiction, where a SORA-style risk classification system governs BVLOS approvals — the territorial scope of the liability wording and the governing law clause both require careful review. Limits quoted in GBP may need to be converted or restated in the local currency required by the relevant authority. Brokers placing multi-jurisdiction BVLOS programmes should confirm with the underwriter whether a single policy can be endorsed to cover all operational territories or whether separate local policies are required.

Frequently asked questions

Does my CAA Operational Authorisation specify the minimum liability limit I must carry?

The CAA's Specific category framework does not prescribe a fixed minimum liability limit in the way that some other jurisdictions do. Instead, the CAA expects the operator's risk assessment — typically conducted using the SORA methodology — to demonstrate that the insurance programme is commensurate with the identified ground and air risk. In practice, underwriters and brokers use the SORA risk class outputs to guide limit selection, and the CAA may query a programme it considers inadequate during an OA review.

What counts as a 'flight' for the purpose of a per-flight limit?

The definition varies by wording. Some policies define a flight as a single take-off-to-landing sequence; others define it as a continuous period of airborne operation under a single flight plan or ATC clearance. For BVLOS operations involving relay handovers between ground control stations, or multi-segment corridor flights with intermediate waypoints, the definition can determine whether a single mission constitutes one flight or several. Always read the definitions section before binding and, if the wording is ambiguous, seek a written clarification from the underwriter.

Can aggregate erosion mid-term leave my operation non-compliant with my CAA OA?

Yes. A CAA Operational Authorisation requires the operator to maintain valid third-party liability insurance throughout the authorisation period. If aggregate limits are exhausted before renewal — whether through one large claim or several smaller ones — the policy no longer provides the cover the OA requires. Operators flying at high sortie volumes should ask their broker to build mid-term aggregate monitoring into the service arrangement, and should consider whether a reinstatement of aggregate clause is available on their programme.

What information does an underwriter need to quote a BVLOS hull and liability programme?

A complete submission typically includes: the CAA Operational Authorisation or standard scenario declaration; the current Operations Manual; the SORA or equivalent risk assessment; a description of each aircraft type, its hull value, and autonomy level; the operational area or corridor; and a projected annual sortie volume. Underwriters writing BVLOS business will also ask about command-and-control link technology, detect-and-avoid capability, and whether the operation involves simultaneous multi-aircraft flights. Presenting these documents upfront produces faster and more accurate quotes.

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

Not automatically. Post-Brexit, UK airspace and EU airspace are governed by separate regulatory frameworks. A policy written against CAA authorisations may not respond to a loss occurring in EU airspace unless the wording includes an explicit territorial extension. Operators conducting BVLOS flights in EU member states must also satisfy the EASA Specific category requirements as administered by the relevant national competent authority — for example, the LBA in Germany. Brokers should confirm territorial scope and governing law with the underwriter before the operator commences cross-border flying.

Is payload covered under a standard BVLOS hull policy?

Payload cover is not always included within the hull section as standard. Some wordings include a sublimit for attached payload; others require a separate endorsement or a standalone payload policy. For BVLOS operations carrying high-value sensors, specialist cameras, or third-party cargo, brokers should confirm whether the payload limit is adequate for the replacement cost of the equipment, whether it responds to loss during transit as well as during flight, and whether third-party cargo liability is addressed separately.