BVLOS & the Civil Aviation Authority: 2026 Guide

How the CAA Categorises BVLOS Operations

Great Britain retained the EU's Open / Specific / Certified category structure after the transition period, administered domestically by the CAA under the Air Navigation Order 2016 as amended and the UK UAS Regulations 2020. BVLOS flight sits almost entirely within the Specific category, meaning the operator must hold either a CAA-issued Operational Authorisation or operate under a published CAA Acceptable Means of Compliance or Light UAS Operator Certificate (LUCA) where one exists for the relevant scenario.

Within the Specific category, the CAA applies a Specific Operations Risk Assessment — the UK variant of the JARUS SORA methodology. The SORA assigns a Ground Risk Class and an Air Risk Class, combines them into a final risk level, and maps that level to a set of Operational Safety Objectives the operator must satisfy. Underwriters use the same risk architecture: a higher SORA risk level typically triggers additional endorsements, higher deductibles on autonomous or automated legs, and closer scrutiny of the operator's Concept of Operations document.

Operators targeting the Certified category — relevant for larger BVLOS platforms operating in non-segregated airspace or carrying passengers — face a materially different regulatory burden, including potential aircraft certification and crew licensing requirements analogous to manned aviation. Brokers should confirm the applicable category in writing before binding, because Certified-category exposures are not adequately addressed by standard Specific-category policy wordings.

The Authorisation Document and What It Means for Cover

The CAA Operational Authorisation issued under the Specific category is a live document. It states the approved geographic area, maximum operating altitude, aircraft type and registration, crew competency requirements, and any special limitations such as segregated airspace corridors or daylight-only conditions. Every material condition in that document is a potential policy condition. If the operator deviates — flying outside the approved corridor, using an unregistered aircraft, or deploying a remote pilot whose competency certificate has lapsed — cover may be voided.

Brokers should request a copy of the current Operational Authorisation at inception and at each renewal. Where an operator holds a LUCA or a National Qualified Entity approval, obtain the underlying scenario document as well. Underwriters writing BVLOS hull and liability programmes will typically require these documents as part of the submission, and some will attach them as scheduled exhibits to the policy. Any mid-term amendment to the authorisation — which the CAA can require if it identifies a safety concern — should trigger a notification obligation under the policy.

Operators running multiple BVLOS programmes under a single fleet policy should confirm that each authorisation is listed. A blanket 'BVLOS permitted' endorsement without reference to specific authorisation numbers creates ambiguity at claims stage, particularly where one authorisation covers a low-risk corridor survey and another covers a higher-risk urban logistics trial.

Hull Cover Considerations for BVLOS Platforms

BVLOS platforms tend to carry higher hull values than standard VLOS commercial drones, and their loss profiles differ. Extended range, reduced pilot situational awareness, and greater reliance on automated flight systems mean that hull losses — when they occur — are more likely to involve total loss rather than repairable damage. Agreed-value policies are therefore preferable to market-value policies for most BVLOS hull programmes, because depreciation disputes at claims stage are eliminated.

Premiums scale with hull value, BVLOS exposure as a proportion of total flight hours, and the nature of the operating environment. Flights over open rural terrain under a well-defined CAA corridor carry a different risk profile from urban BVLOS trials or flights over critical national infrastructure. Underwriters will also assess the detect-and-avoid or command-and-control technology fitted to the aircraft, because these systems directly affect the probability and severity of a loss.

Where operators lease or finance their aircraft, lenders will typically require hull cover as a condition of the finance agreement and will want to be noted as loss payees. Confirm the lender's minimum requirements early — some institutional lenders specify policy conditions that go beyond standard MGA wordings and require manuscript endorsements.

Third-Party Liability: Regulatory Minimums and Market Practice

The UK UAS Regulations 2020 mandate third-party liability insurance for commercial UAS operations, with the required minimum limit linked to the maximum take-off mass of the aircraft. The regulation references the unit of Special Drawing Rights as the basis for minimum limits, consistent with the Montreal Convention framework applied to manned aviation. Brokers should verify the current SDR-denominated minimum with the CAA's published guidance and convert to GBP at the prevailing rate — limits are quoted in GBP in the domestic market.

Market practice for BVLOS operations routinely exceeds the regulatory minimum. Operators flying over populated areas, critical infrastructure, or in proximity to manned aircraft will find that counterparties — local authorities, infrastructure owners, airspace managers — contractually require limits well above the statutory floor. Brokers should review all operational contracts before recommending a limit, because an inadequate limit discovered after a loss is a professional liability exposure for the broker.

Liability wordings for BVLOS programmes should be reviewed for exclusions relating to autonomous or automated flight, cyber-induced loss of control, and electromagnetic interference. These exclusions, which are common in standard aviation liability forms, can strip cover from the scenarios most likely to produce a BVLOS liability claim. Manuscript endorsements reinstating cover for these perils — subject to agreed conditions — are available in the specialty market.

Broker Workflow: Placing a BVLOS Programme

A clean BVLOS submission to the specialty market requires more documentation than a standard VLOS commercial programme. Assembling the following before approaching underwriters reduces turnaround time and demonstrates operator competence, which itself influences underwriter appetite.

Once the submission is complete, brokers should approach underwriters with genuine BVLOS appetite rather than routing through standard aviation facilities that treat BVLOS as an endorsement to a VLOS base. The risk architecture is sufficiently different that standard-form policies frequently contain conditions incompatible with BVLOS operations. Specialist MGAs with dedicated BVLOS wordings can bind more quickly and with fewer exclusions.

At renewal, re-underwrite rather than roll. BVLOS technology, CAA authorisation conditions, and the operator's loss history all change materially year on year. A renewal that simply extends the expiring programme without reviewing the current Operational Authorisation and any CAA correspondence risks leaving the operator underinsured or in breach of a policy condition.

• Current CAA Operational Authorisation or LUCA scenario document
• Concept of Operations (ConOps) submitted to the CAA
• Aircraft registration certificates and hull valuations
• Remote pilot competency certificates (GVC or equivalent)
• Fleet schedule with MTOM, hull value, and annual flight hours per aircraft
• Details of detect-and-avoid, C2 link redundancy, and emergency procedures
• Any prior loss history, including incidents reported to the CAA under MOR obligations

Regulatory Developments Affecting BVLOS Cover in 2026

The CAA's Future of Flight programme and the associated airspace modernisation work continue to expand the scenarios in which BVLOS operations are practically achievable. The CAA's U-space framework, being implemented in designated U-space airspace, introduces new actors — U-space service providers — whose liability exposure and contractual relationships with operators create coverage questions that standard aviation policies do not address. Brokers placing programmes for operators active in U-space should seek specific underwriter guidance on how U-space service provider interactions are treated.

The CAA has also been developing updated Acceptable Means of Compliance for higher-risk Specific-category operations, which may reduce the bespoke SORA burden for some BVLOS scenarios while introducing standardised operational constraints. Where an operator migrates from a bespoke Operational Authorisation to a standardised AMC-based route, the policy should be reviewed to confirm that the new authorisation structure is still captured by the scheduled documents.

Internationally, operators conducting BVLOS flights that cross into EU airspace — relevant for operators near the Irish land border or for maritime operations — must comply with EASA's Specific category framework as implemented by the relevant national competent authority. The CAA and EASA frameworks are broadly aligned but not identical, and dual-jurisdiction operations require careful policy drafting to avoid territorial gaps.

Frequently asked questions

Does a standard commercial drone policy cover BVLOS operations automatically?

No. Most standard commercial UAS policies contain an express exclusion for BVLOS flight, or limit cover to operations conducted within visual line of sight as defined in the UK UAS Regulations 2020. BVLOS cover requires either a specific endorsement to a base policy or a dedicated BVLOS programme. Brokers should check the base policy definition of 'visual line of sight' carefully — some wordings use a narrower definition than the CAA's regulatory text, which can create gaps even for operations the CAA considers VLOS.

What CAA documents does an underwriter need to assess a BVLOS submission?

At minimum: the current CAA Operational Authorisation (or LUCA scenario document), the Concept of Operations submitted as part of the authorisation application, and any CAA correspondence amending or conditioning the authorisation. Underwriters may also request the operator's SORA working document and the emergency response procedures referenced in the ConOps. Providing these upfront materially accelerates the underwriting process.

What happens to cover if the CAA amends or suspends the Operational Authorisation mid-term?

Most BVLOS policy wordings include a condition requiring the operator to notify the insurer of any material change to the regulatory authorisation. A CAA amendment that restricts the approved operating area or imposes new conditions is a material change. Failure to notify may give the insurer grounds to avoid a claim arising after the amendment. Operators should treat any CAA correspondence about their authorisation as a potential notification trigger and contact their broker promptly.

Are there eligibility requirements operators must meet before a BVLOS programme can be bound?

Underwriters typically require the operator to hold a valid CAA Operational Authorisation specifically permitting the BVLOS operations to be insured — a pending application is not sufficient. Remote pilots must hold the General Visual Line of Sight Certificate (GVC) or an equivalent qualification accepted by the CAA for the relevant operation. For higher-risk SORA levels, additional crew qualifications or operational mitigations specified in the ConOps may be required before underwriters will bind. Some underwriters also require a minimum period of documented VLOS commercial operating history before writing a first BVLOS programme.

How does U-space affect BVLOS liability cover?

U-space introduces U-space service providers (USSPs) as intermediaries between operators and airspace managers. Liability for incidents involving USSP data — such as incorrect traffic information or a failed geo-awareness service — may fall on the USSP, the operator, or both, depending on contractual terms and the nature of the failure. Standard aviation liability policies are not drafted with USSP relationships in mind. Operators active in designated U-space airspace should confirm with their broker that the policy responds to incidents involving USSP-provided services and that no exclusion for third-party navigation or traffic data applies.

Does a BVLOS hull policy cover the ground control station and data links as well as the aircraft?

It depends on the policy wording. Some BVLOS hull policies define 'aircraft' to include the ground control station, command-and-control data links, and payload as a single insured system. Others cover only the airframe and require separate property cover for ground equipment. Given that ground control stations and C2 infrastructure for BVLOS operations can represent a significant proportion of total system value, brokers should confirm the scope of the hull definition at placement and arrange separate cover for any ground assets excluded from the aviation policy.