Adding a BVLOS Endorsement to Your UK Drone Policy

Why a Standard Open-Category Policy Does Not Cover BVLOS

UK drone insurance policies are underwritten against a declared operational scope. A policy placed for Open-category operations — where the CAA's framework permits flight within visual line of sight, below 120 m, and within defined sub-category limits — contains implicit and often explicit exclusions for operations that require a CAA Specific-category authorisation or an Operational Authorisation (OA). BVLOS flight sits firmly in the Specific category under the UK's retained EU UAS Regulation framework administered by the CAA.

When an operator crosses into BVLOS, the risk profile changes materially: the pilot can no longer see and avoid conflicting traffic unaided, ground-based observers may be required, command-and-control link integrity becomes a rated factor, and the consequence of a lost-link event is harder to mitigate. Underwriters price and structure cover around the declared operational envelope. Flying outside that envelope without endorsement is a material non-disclosure that can void a claim entirely.

Brokers should treat any client conversation about BVLOS expansion as a mid-term adjustment trigger, not a renewal conversation. The sooner the underwriter is notified, the sooner the operator is protected — and the sooner the broker's own E&O exposure is managed.

Regulatory Prerequisites Before Approaching an Underwriter

Underwriters will not endorse BVLOS cover speculatively. The operator must first demonstrate that the CAA has granted, or is actively processing, the appropriate authorisation. For most commercial BVLOS operations this means either a bespoke Operational Authorisation under the Specific category, or qualification under an approved CAA Operational Safety Case (OSC). Some operators working within a National Infrastructure Operator or a CAA-approved BVLOS corridor framework may present alternative evidence, but the principle is the same: regulatory permission precedes insurance endorsement.

The CAA's Specific-category framework requires operators to submit a SORA-derived risk assessment or an equivalent OSC demonstrating that the operation achieves an acceptable level of safety. The output of that process — the OA document itself, the approved Operations Manual, and any conditions attached — forms the primary underwriting evidence pack. Operators who are mid-application should discuss with their broker whether a conditional endorsement, effective on OA grant, is available from their insurer.

Additional regulatory documents that underwriters typically request include: the operator's GVC (General Visual Line of Sight Certificate) or equivalent remote pilot competency evidence, the UAS operator registration number, the approved Operations Manual with BVLOS-specific procedures, and any CAA-imposed conditions such as observer requirements or geographic restrictions. Where the operation involves flights over or near aerodromes, ATM coordination evidence may also be required.

• CAA Operational Authorisation (OA) or approved OSC
• Approved Operations Manual covering BVLOS procedures
• Remote pilot competency certificates (GVC or higher)
• UAS operator registration number (CAA portal)
• Lost-link and emergency procedures documentation
• Any CAA-imposed operational conditions or geographic limits

What the Endorsement Actually Changes on the Policy

A BVLOS endorsement is not a simple extension of existing limits. Underwriters will review the hull sum insured against the aircraft's actual replacement value in its BVLOS-configured state — which may include command-and-control link hardware, redundant flight termination systems, and payload — and adjust accordingly. Liability limits are similarly reviewed: operations over or near people, infrastructure, or controlled airspace carry higher third-party exposure, and minimum limits may be imposed by the CAA's OA conditions or by the operator's client contracts.

Deductibles typically rise on BVLOS operations relative to VLOS equivalents, reflecting the increased difficulty of pilot intervention during a developing incident. Autonomous or highly automated BVLOS operations — where the remote pilot's real-time control input is reduced — attract additional underwriter scrutiny and may carry higher deductibles or sub-limits on autonomous-mode losses. Brokers should ensure clients understand this distinction before submission.

The territorial scope of the endorsement will be defined precisely. A UK-issued OA is jurisdiction-specific; if the operator intends to conduct BVLOS flights in other jurisdictions — for example under EASA's framework in an EU member state, or under GCAA authorisation in the UAE — separate endorsements or standalone policies will be required. Attempting to extend a UK BVLOS endorsement to overseas operations without underwriter agreement is a common gap that brokers should proactively close.

Structuring the Broker Submission

A well-structured BVLOS endorsement submission reduces turnaround time and demonstrates to the underwriter that the broker has pre-qualified the risk. The submission should open with a clear statement of the change being requested — mid-term endorsement to add BVLOS operations — followed by the regulatory evidence pack, a completed updated statement of fact, and a concise operational narrative describing the specific BVLOS use case: what is being flown, where, at what frequency, and under what CAA authorisation.

Underwriters will want to understand the command-and-control architecture. Submissions that describe the C2 link technology, redundancy arrangements, and lost-link behaviour (return-to-home, loiter, or flight termination) are processed faster than those that leave these questions open. If the operator uses a detect-and-avoid system — whether cooperative (ADS-B in) or non-cooperative — include the system specification. This is not a regulatory requirement for the insurance submission, but it materially affects how underwriters assess the collision risk component.

Fleet operators adding BVLOS capability to one or more aircraft within a larger fleet programme should clarify which tail numbers are being endorsed and whether the BVLOS OA is aircraft-specific or operator-wide. Some CAA OAs are issued at operator level with aircraft-type approval; others are aircraft-specific. This distinction affects how the endorsement schedule is worded and how claims are handled if an unapproved aircraft is used on a BVLOS operation.

• Updated statement of fact reflecting BVLOS operations
• Operational narrative: aircraft type, use case, frequency, geography
• C2 link and lost-link procedure summary
• DAA system specification if applicable
• CAA OA document and any attached conditions
• Approved Operations Manual (BVLOS section at minimum)

Mid-Term Timing, Premium Adjustment, and Renewal Implications

BVLOS endorsements added mid-term generate an additional premium, calculated on a pro-rata or short-rate basis depending on the insurer's terms. Premiums scale with hull value, liability limit, operational frequency, and the nature of the BVLOS exposure — corridor operations over uninhabited terrain carry a different risk profile from urban BVLOS over infrastructure. Brokers should obtain a clear endorsement premium indication before presenting to the client, rather than leaving the figure open until binding.

At renewal, the BVLOS endorsement becomes part of the base programme rather than an add-on. Underwriters will review the claims experience under the endorsement, any changes to the OA conditions, and whether the operator's competency evidence remains current. CAA OAs are typically time-limited and may carry conditions that require periodic review; brokers should diary these dates and confirm OA validity as part of the renewal data-gathering process.

Operators who have conducted BVLOS flights without an endorsement in place — whether inadvertently or otherwise — should be advised to make a full disclosure to their broker before renewal. Underwriters take a more constructive view of proactive disclosure than of gaps discovered at claim. The broker's role here is to facilitate that conversation, not to avoid it.

Frequently asked questions

Does my existing commercial drone policy automatically cover BVLOS once I have a CAA Operational Authorisation?

No. A CAA OA grants regulatory permission to fly BVLOS; it does not extend your insurance cover. Your policy covers the operational scope declared at inception. BVLOS is a material change to that scope and requires a formal endorsement from your insurer before BVLOS flights begin. Flying under an OA without an endorsement in place means you are operating outside your policy's terms, and a claim arising from that flight is likely to be declined.

What types of operation qualify for a BVLOS endorsement under UK rules?

Any operation that takes the remote pilot's unaided visual contact with the aircraft beyond the limits permitted in the CAA's Open category falls into the Specific category and requires a BVLOS endorsement. Common qualifying operations include infrastructure inspection along linear assets, beyond-horizon survey, emergency services support, and logistics trials. The CAA's Specific-category framework, including the SORA-derived risk assessment process, defines the authorisation pathway. Underwriters will ask to see the OA or OSC approval before binding the endorsement.

Can a BVLOS endorsement be added to a fleet policy, or does each aircraft need separate cover?

Both structures are available, but the correct approach depends on how the CAA OA is issued. If the OA is operator-level and covers a defined aircraft type, the endorsement can typically be applied at fleet level with a schedule of approved tail numbers. If the OA is aircraft-specific, the endorsement should mirror that specificity. Brokers should confirm the OA structure with the operator before drafting the endorsement schedule to avoid gaps where an unapproved aircraft is used on a BVLOS operation.

What happens if my CAA Operational Authorisation expires or is varied during the policy period?

An expired or materially varied OA is a change in the risk that must be notified to your insurer promptly. If the OA lapses and BVLOS operations continue, the endorsement is effectively unsupported by the regulatory permission it was written against, and cover may not respond. Brokers should diary OA expiry dates alongside policy renewal dates and confirm OA validity at each renewal. If the CAA varies the OA conditions — for example by restricting geography or imposing new observer requirements — the underwriter should be notified so the endorsement wording can be aligned.

How long does it take to get a BVLOS endorsement bound once I submit the documentation?

Turnaround depends on the completeness of the submission and the complexity of the operation. A well-documented submission — including the OA, approved Operations Manual, C2 link summary, and updated statement of fact — typically allows an underwriter to return a premium indication and draft endorsement wording within a few working days. Incomplete submissions, novel operational profiles, or operations involving controlled airspace or populated areas will take longer as underwriters may need to refer to specialist aviation risk assessors. Brokers should not advise clients to begin BVLOS operations while the endorsement is pending.

Is a BVLOS endorsement on a UK policy valid for operations in other countries?

Not automatically. A UK policy endorsed for BVLOS under a CAA OA covers operations within the territorial scope defined in the policy, which is typically Great Britain and Northern Ireland unless extended. Operations in EU member states fall under EASA's UAS regulation as implemented by the relevant national authority — for example, the LBA in Germany — and require separate authorisation and, in most cases, a separate insurance endorsement or policy. Operations in the UAE require GCAA authorisation. Brokers placing programmes for operators with multinational BVLOS activity should structure the cover jurisdiction by jurisdiction rather than relying on a blanket territorial extension.