BVLOS Hull Insurance: Buyer's Guide for UK Operators

Written by the BVLOS Insure editorial team · reviewed by Anton Kuznetsov, founder

If you are operating or placing cover for a drone conducting beyond visual line of sight flights in the UK, standard Open-category hull policies will not respond. BVLOS operations sit firmly within the CAA's Specific or Certified category framework, and the insurance programme must match that regulatory reality before a single flight takes place. This guide covers what a BVLOS hull insurance policy needs to contain, the underwriting factors that drive terms, and the broker workflow for getting a programme bound efficiently.

Why BVLOS Changes the Hull Insurance Equation

Visual line of sight operations allow the remote pilot to observe the aircraft directly and intervene in real time. BVLOS removes that safety layer, which is precisely why the CAA requires operators to hold either an Operational Safety Case under the Specific category or, for higher-risk missions, a Certified category approval. Each of those regulatory pathways introduces risk factors that standard drone hull wordings were never designed to price.

Underwriters assess BVLOS hull risk differently from VLOS because the probability and severity of a loss event change materially. Collision avoidance relies on detect-and-avoid technology, datalink integrity, and contingency procedures rather than the pilot's own eyes. A datalink failure at extended range can result in a total loss with no opportunity for manual recovery. Hull policies for BVLOS must therefore address not just physical damage but the specific failure modes that BVLOS introduces.

UK operators should also be aware that the Air Navigation Order 2016 and the retained EU UAS Regulation (2019/947 as it applies in Great Britain) set the legal baseline. The CAA's Operational Authorisation issued under the Specific category will specify the conditions of flight, and your hull wording must not contain exclusions that contradict those authorised conditions — otherwise you may hold a policy that is technically void at the moment of a claim.

What a BVLOS Hull Insurance Policy Should Cover

A fit-for-purpose BVLOS hull policy covers the airframe, payload, and ground control station as a combined insured value, with cover triggering on accidental damage, crash, fire, theft, and — critically — flyaway. Flyaway cover is non-negotiable for BVLOS: if a datalink failure causes the aircraft to depart controlled flight and the hull is never recovered, you need the policy to respond on a total-loss basis without requiring physical evidence of wreckage.

Payload cover deserves separate attention. BVLOS missions frequently carry high-value sensors — LiDAR units, multispectral cameras, or specialist inspection equipment — whose replacement cost can exceed the airframe value. Confirm whether payload is included within the declared hull sum insured or scheduled separately, and ensure the wording covers payload damage caused by a hard landing or crash, not just theft.

Ground equipment, including ground control stations, RF relay nodes, and mobile command vehicles used in extended-range operations, should be listed as insured property. Some wordings restrict cover to the aircraft in flight; others extend to all equipment forming part of the UAS system. Read the definition of 'aircraft' in the policy schedule carefully — a narrow definition can leave significant assets uninsured.

  • Airframe on an agreed-value or replacement-cost basis
  • Payload scheduled at full replacement value
  • Ground control station and relay infrastructure
  • Flyaway / uncontrolled flight total-loss cover
  • Transit and storage cover between operational deployments
  • Temporary replacement aircraft during repair periods

Underwriting Factors That Shape BVLOS Hull Terms

Premiums scale with hull value and BVLOS exposure in ways that differ from VLOS programmes. Underwriters will assess the aircraft manufacturer and model, the detect-and-avoid system fitted, the datalink architecture, and the operator's OSC or Operational Authorisation conditions. A well-documented OSC that demonstrates robust contingency procedures will generally attract more competitive terms than an operation where the risk assessment is thin.

Operational environment matters significantly. Corridor surveys over uninhabited moorland carry a different risk profile from urban infrastructure inspection where a flyaway could result in third-party property damage or bodily injury. Underwriters will want to understand the geographic footprint of operations, the population density beneath the flight path, and whether the operation is conducted under a CAA-issued OSC or a National Qualified Entity-issued standard scenario that includes BVLOS elements.

Deductibles typically rise on autonomous operations compared with remotely piloted VLOS flights, reflecting the reduced ability to intervene. Fleet operators should expect underwriters to request aggregated flight-hour data, maintenance records, and incident history. A clean operational record with documented airworthiness procedures will support better deductible terms than a programme where maintenance is informal or undocumented.

The aircraft's detect-and-avoid capability is increasingly a hard underwriting criterion rather than a rating factor. Some markets will decline to quote BVLOS hull cover entirely if the aircraft lacks a certified or independently validated DAA system. Operators planning BVLOS programmes should confirm DAA requirements with their broker before finalising aircraft procurement.

Regulatory Triggers Brokers Must Verify

Before placing a BVLOS hull programme, brokers must confirm the operator holds the correct CAA authorisation. For Specific category BVLOS, this means either a bespoke Operational Authorisation with an accepted OSC, or a standard scenario that explicitly permits BVLOS — and at the time of writing, no CAA standard scenario covers unrestricted BVLOS, so a bespoke OSC is almost always required. Placing hull cover without verifying the authorisation status exposes both the operator and the broker to a coverage gap.

The policy inception date must align with or follow the date of the CAA Operational Authorisation. A hull policy that incepted before the authorisation was granted may be challenged on the basis that the insured operation was not legally permitted at the time cover attached. Brokers should retain copies of the Operational Authorisation and any associated OSC as part of the placement file.

For operators conducting cross-border BVLOS — for example, survey work that crosses into Northern Ireland airspace or involves flights coordinated with the Irish Aviation Authority — the policy must confirm territorial scope. GB-domiciled policies may restrict cover to Great Britain; operators working in Northern Ireland or with European counterparts should confirm whether the wording extends to EASA member state airspace or requires a separate endorsement.

  • Confirm CAA Specific or Certified category Operational Authorisation is in force
  • Verify OSC acceptance date aligns with policy inception
  • Check territorial scope covers all planned operational areas
  • Confirm the wording does not exclude autonomous or semi-autonomous flight modes used in the operation
  • Retain authorisation documents in the placement file for claims purposes

Broker Workflow: From Submission to Bind

A clean BVLOS hull submission should include the aircraft make, model, and serial number; the declared hull value and payload schedule; a copy of the CAA Operational Authorisation and OSC summary; the operator's flight-hour history and incident record; and a description of the operational environment including typical range, altitude, and population density. Submissions that arrive without the OSC documentation routinely stall at underwriting, adding days to the placement timeline.

Specialist BVLOS markets operate on a manuscript or bespoke wording basis rather than off-the-shelf drone policy forms. This means the broker should expect a dialogue with the underwriter about specific wording requirements — particularly around flyaway, DAA system warranties, and autonomous operation clauses — rather than a simple quote-and-bind process. Build adequate lead time into the placement schedule, particularly for first-time BVLOS programmes.

Once terms are agreed, the policy schedule should explicitly reference the CAA Operational Authorisation number and the OSC version. This creates a clear audit trail and ensures that if the operator's authorisation conditions change — for example, if the CAA issues a revised Operational Authorisation with amended geographic or altitude limits — the broker can review whether the hull wording remains aligned and arrange an endorsement if needed.

Frequently asked questions

Does a standard drone hull policy cover BVLOS operations?
Not typically. Most standard drone hull wordings are designed for Open-category or basic Specific-category VLOS operations and contain exclusions for flights beyond the remote pilot's unaided visual range. A BVLOS hull policy requires a bespoke or manuscript wording that explicitly covers extended-range and autonomous flight modes, flyaway scenarios, and the specific equipment architecture used in BVLOS operations.
What CAA authorisation do I need before a BVLOS hull policy will be issued?
UK operators conducting BVLOS flights require a CAA Operational Authorisation under the Specific category, supported by an accepted Operational Safety Case. No current CAA standard scenario covers unrestricted BVLOS, so a bespoke OSC submission to the CAA is the standard route. Underwriters will require sight of the Operational Authorisation before binding hull cover, and the policy inception date should not predate the authorisation.
Is payload covered under a BVLOS hull policy, or does it need a separate policy?
This depends on the wording. Some BVLOS hull policies include payload within the total insured value of the UAS system; others treat payload as a separate scheduled item or exclude it entirely. High-value payloads — LiDAR units, specialist sensors, or customer-owned equipment — should always be explicitly scheduled with their own agreed or replacement value. Confirm the payload position with your underwriter before inception.
How does the broker submission process differ for BVLOS hull versus standard drone hull?
BVLOS hull placements require significantly more documentation than standard drone programmes. Underwriters will expect the CAA Operational Authorisation, the OSC or a summary of its key risk mitigations, aircraft technical specifications including DAA system details, operational environment data, and the operator's flight-hour and incident history. Manuscript wording negotiation is common, so brokers should allow additional lead time compared with a standard drone hull placement.
Does a BVLOS hull policy cover operations in Northern Ireland or EU member states?
Territorial scope varies by wording. Policies placed on a GB basis may restrict cover to Great Britain, which could leave operations in Northern Ireland — regulated by the UK CAA but geographically separate — or in EASA member state airspace without cover. Brokers should confirm territorial scope at the submission stage and arrange endorsements or separate placements for operations outside the primary policy territory.
What happens to my hull cover if the CAA amends my Operational Authorisation mid-term?
If the CAA issues a revised Operational Authorisation that changes the conditions of your BVLOS operation — for example, amending geographic limits, altitude ceilings, or DAA requirements — you should notify your broker immediately. The hull policy schedule typically references the authorisation number and version; a material change to the authorisation may require a policy endorsement to ensure the wording remains aligned with your legal operating conditions. Failure to notify could affect the validity of a claim.

Submit your BVLOS hull risk to our specialist underwriting team at BVLOS Insure. Upload your CAA Operational Authorisation, OSC summary, and aircraft schedule using the secure submission portal, and we will revert with indicative terms within two working days.

Talk to a specialist

Tell us a few details about the operation and we'll come back with indicative terms within 24 hours.