Annual vs Single-Flight BVLOS Insurance UK

How UK Regulatory Categories Shape the Choice

Under the UK drone regulatory framework — which mirrors the EU Open / Specific / Certified tiering but is administered by the Civil Aviation Authority post-Brexit — virtually all commercial BVLOS operations fall into the Specific category. That means the operator holds either a CAA-issued Operational Authorisation (OA) or operates under an Operational Safety Case (OSC). The permission document itself defines the geographic scope, maximum take-off mass, and risk mitigations in force. An insurance policy that does not map to those parameters is functionally misaligned.

Single-flight policies are issued against a defined mission envelope: a named site, a stated date window, a specific aircraft registration, and the MTOM and risk class declared in the OA or OSC. Annual policies instead establish a rated envelope — typically expressed as a fleet schedule, an aggregate BVLOS hours band, and a set of approved operational categories — within which the operator can conduct multiple missions without rebinding. The CAA does not mandate one form over the other, but the OA conditions frequently require the operator to hold insurance that is 'adequate for the operations authorised', which underwriters interpret as coverage that matches the permission in force at the time of each flight.

From 2026, operators pursuing higher-risk BVLOS corridors — including beyond-visual-line-of-sight flights over congested areas or involving detect-and-avoid technology — are increasingly subject to SORA-influenced risk scoring even within the UK's own OSC framework. Underwriters are responding by requiring SORA Ground Risk Class and Air Risk Class declarations at inception, regardless of whether the policy is annual or single-flight. Brokers should obtain these classifications from the operator before approaching the market.

Annual BVLOS Programmes: Structure and Suitability

An annual programme is rated on the aggregate exposure the operator presents across a policy year. Underwriters assess hull value per aircraft, the BVLOS hours or sorties anticipated, the operational categories covered (infrastructure inspection, precision agriculture, corridor survey, and so on), and the geographic spread of operations. Premiums scale with hull value and BVLOS exposure rather than being fixed at a flat rate — a fleet conducting high-frequency linear-infrastructure surveys will be rated differently from one conducting occasional rural mapping flights, even if the aircraft are identical.

The principal advantage for operators running regular BVLOS programmes is administrative efficiency: a single policy document, a single renewal cycle, and a certificate of insurance that satisfies the CAA OA condition without requiring a new bind for each mission. For brokers, the annual form also allows mid-term endorsements when the operator adds aircraft to the fleet schedule or extends into a new operational category — provided the underwriter agrees the endorsement in advance.

Annual policies typically carry a fleet schedule endorsement mechanism and a reporting obligation. Operators are usually required to notify the insurer when a new aircraft is added, when an OA is materially varied, or when a new operational category is introduced. Failure to notify can create a coverage gap at the point of claim. Brokers should build a mid-term review trigger into their service agreement, particularly where clients are scaling BVLOS operations or moving from OSC to a broader OA.

• Suited to operators with predictable annual BVLOS hours or a standing OA covering recurring mission types
• Hull and liability rated together on a fleet basis; deductibles typically rise on autonomous or beyond-radio-line-of-sight operations
• Mid-term endorsements required when fleet, OA scope, or operational category changes
• Single renewal date simplifies compliance evidence for CAA and client contracts

Single-Flight Policies: Structure and Suitability

A single-flight policy — sometimes called a per-mission or on-demand bind — is underwritten against a specific operational envelope declared at the time of placement. The underwriter prices the risk based on the aircraft, the site coordinates or corridor, the date and duration window, the OA or OSC reference number, and any specific mitigations in place (such as a ground-based observer network or a detect-and-avoid system). Because each bind is discrete, the premium reflects the actual risk of that mission rather than an annualised average.

Single-flight structures are appropriate where BVLOS operations are genuinely infrequent or where each mission presents a materially different risk profile — for example, a one-off survey of a specific infrastructure asset, a demonstration flight for a prospective client, or a research mission conducted under a university OSC. They are also used by operators who hold an annual general-aviation hull policy but need a top-up liability layer for a specific BVLOS authorisation that falls outside the annual policy's scope.

The operational constraint is lead time. Binding a single-flight BVLOS policy requires the broker to present a complete risk submission — aircraft details, OA or OSC reference, site data, crew qualifications, and risk mitigations — typically several working days before the flight window. Last-minute binds are possible through specialist platforms but carry a narrower market and may attract loading. Operators who treat single-flight cover as an on-the-day purchase are routinely uninsured at the point of flight.

• Suited to infrequent, high-value, or geographically unique BVLOS missions
• Each bind priced on the specific mission envelope — no averaging across a portfolio
• Requires complete risk submission in advance; same-day binding is not standard for BVLOS
• Useful as a top-up layer where an annual policy excludes a specific operational category

Coverage Scope: What Both Forms Must Address

Regardless of policy form, a BVLOS programme in the UK must respond to third-party liability arising from bodily injury and property damage caused by the aircraft in flight, including during the BVLOS segment. The CAA's Specific-category OA conditions reference the EU Aviation Safety Agency framework on minimum liability limits — expressed in Special Drawing Rights as a unit of account — and the policy must meet or exceed those thresholds for the MTOM class of aircraft being operated. Brokers should confirm that the policy wording does not contain a BVLOS exclusion that would void coverage the moment the aircraft passes beyond visual line of sight.

Hull coverage under both forms typically addresses total loss and partial damage on an agreed-value or stated-value basis. For BVLOS operations, underwriters frequently distinguish between damage occurring during the BVLOS segment and damage during the VLOS transit to the launch point, applying different deductible structures to each. Payload coverage — cameras, sensors, LiDAR units — is usually written as a separate scheduled item and should be confirmed as included in the BVLOS operational envelope rather than restricted to ground handling.

Operators using detect-and-avoid systems, remote-pilot stations, or automated flight management software should ensure the policy addresses cyber and software failure as a proximate cause of loss. This is an emerging coverage question in the UK market: some wordings exclude losses where an automated system made the operative decision, while others treat the remote pilot as the responsible party regardless of automation level. The distinction matters for BVLOS operations where the pilot's ability to intervene is, by definition, limited.

Broker Placement Workflow for 2026

The submission quality expected by BVLOS underwriters has increased materially as the market has matured. A bare minimum submission for either policy form should include the CAA OA or OSC reference number and its conditions document, the aircraft registration and MTOM, the operator's remote pilot competency evidence (GVC or equivalent), and a description of the BVLOS operational category and mitigations. For annual programmes, underwriters will also want a projected hours or sorties estimate and a fleet schedule. For single-flight binds, GPS coordinates or a corridor description and a specific date window are required.

Brokers placing BVLOS programmes should confirm at the outset whether the operator's OA covers the full scope of intended operations. A common placement error is binding a policy against an OA that has since been varied or that does not yet cover the operational category being insured. The CAA's Operational Authorisation is a live document — it can be amended, suspended, or revoked — and the policy's coverage is contingent on the OA being valid and in scope at the time of each flight.

Where an operator is transitioning from VLOS to BVLOS operations, or scaling from single-site to multi-corridor work, the broker should consider whether an annual programme with a broad operational category endorsement is more appropriate than a series of single-flight binds. The underwriting relationship built through an annual programme typically provides faster endorsement turnaround and access to higher liability limits than the on-demand market can offer for individual missions.

• Obtain OA or OSC reference and conditions document before approaching market
• Confirm SORA Ground Risk Class and Air Risk Class if applicable to the operation
• Verify fleet schedule accuracy and mid-term notification obligations at inception
• Check policy wording for BVLOS exclusions, automation exclusions, and payload scope
• Build a mid-term review trigger into the service agreement for scaling operators

Selecting the Right Structure for Your Operation

The decision between annual and single-flight cover reduces to three operational questions: How frequently does the operator conduct BVLOS missions? How consistent is the risk profile across those missions? And does the operator hold a standing OA that covers the intended scope, or are they operating under a series of site-specific permissions? Frequent, consistent, OA-backed operations point toward an annual programme. Infrequent, variable, or permission-specific operations point toward single-flight binds.

Cost is a factor but should not be the primary driver. Single-flight policies can appear cheaper on a per-mission basis for very low-frequency operators, but the administrative overhead and lead-time constraints can create operational friction that outweighs the premium saving. Annual programmes carry a higher upfront commitment but provide the coverage certainty and endorsement flexibility that commercial BVLOS operations typically require.

Brokers advising clients in 2026 should also consider the direction of regulatory travel. The CAA's ongoing work on BVLOS corridors and urban air mobility frameworks is likely to introduce new operational categories that will require policy endorsements. An annual programme with a responsive underwriter is better positioned to absorb those changes mid-term than a series of single-flight binds that must each be resubmitted against the new regulatory context.

Frequently asked questions

Does a standard commercial drone policy automatically cover BVLOS operations?

No. Most standard commercial drone wordings contain an explicit BVLOS exclusion or restrict coverage to operations conducted within visual line of sight of the remote pilot. A separate BVLOS endorsement or a dedicated BVLOS policy is required. Brokers should check the policy wording's definition of 'visual line of sight' and confirm that the BVLOS segment of a flight is not treated as an excluded operation.

What CAA documentation does an operator need before a BVLOS policy can be bound?

At minimum, the operator must hold a valid CAA Operational Authorisation or an approved Operational Safety Case that covers the intended BVLOS operation. The OA or OSC reference number and the conditions document are required at submission. Underwriters will not bind coverage against an anticipated or pending authorisation. Remote pilot competency evidence — typically a General Visual Line of Sight Certificate or an equivalent qualification accepted under the OA — is also required.

Can a single-flight BVLOS policy be extended if the mission overruns its date window?

Extensions are possible but must be agreed with the underwriter before the original policy period expires. An extension is not automatic and will require a revised risk submission confirming that the operational conditions — aircraft, site, crew, and OA validity — remain unchanged. Operating outside the policy period without a confirmed extension leaves the operator uninsured for that segment of the mission.

How does the policy respond if the operator's CAA Operational Authorisation is suspended mid-term?

A policy does not provide coverage for operations conducted without a valid OA. If the CAA suspends or revokes the OA, the operator must cease BVLOS operations immediately. The policy does not respond to flights conducted in breach of the OA conditions, and a claim arising from such a flight is likely to be declined on the basis that the operation was not authorised. Operators should notify their broker immediately if the OA is varied, suspended, or revoked.

Are payload items such as LiDAR sensors and thermal cameras covered under a BVLOS policy?

Payload coverage is not automatically included in either annual or single-flight BVLOS policies. Sensors, cameras, and other payload items must be scheduled separately and their value declared at inception. Brokers should confirm that the payload is covered during the BVLOS operational segment and not restricted to ground handling or VLOS flight. Some wordings treat payload as part of the hull value; others require a separate payload endorsement.

What is the broker's obligation if the operator adds a new aircraft to an annual BVLOS programme mid-term?

The broker must notify the underwriter and obtain a mid-term endorsement adding the new aircraft to the fleet schedule before that aircraft conducts any BVLOS operations. Operating an unscheduled aircraft under an annual policy is a common coverage gap. The endorsement should confirm the new aircraft's registration, MTOM, hull value, and whether it introduces any new operational categories not already covered by the existing programme.