Beyond Visual Line of Sight Insurance | BVLOS Insure

Why Standard Drone Policies Fall Short for BVLOS

Most commercial drone policies are written against VLOS operations in the CAA Open or lower Specific category. The moment a flight plan removes the requirement for the remote pilot to maintain unaided visual contact with the aircraft, the risk profile changes materially: longer flight paths, reduced pilot reaction time, greater reliance on detect-and-avoid systems, and — critically — a higher probability of third-party exposure over populated or congested areas.

Underwriters treat BVLOS as a distinct risk class, not a simple extension of VLOS cover. A policy that does not explicitly affirm BVLOS operations in its schedule or endorsement wording will almost certainly contain an exclusion — whether express or implied through the 'lawful operation' condition — that voids cover the moment the aircraft crosses the visual threshold.

For brokers, the practical consequence is straightforward: never bind a BVLOS programme on a standard commercial drone wording without written confirmation from the underwriter that the OA scope is covered. Verbal assurances at placement do not survive a claims dispute.

The UK Regulatory Framework Underwriters Follow

The CAA administers drone operations in Great Britain under the UK retained version of EU regulation, structured across Open, Specific, and Certified categories. BVLOS flights — other than the narrow carve-outs permitted under certain Open-category conditions for very low-mass aircraft — require a Specific-category Operational Authorisation issued by the CAA, or flight under a published Pre-Defined Risk Assessment (PDRA) where one exists for the intended operation.

The CAA's SORA-derived methodology (Specific Operations Risk Assessment) assigns a Ground Risk Class and Air Risk Class to each operation, producing a final SAIL (Specific Assurance and Integrity Level) score. Underwriters use the SAIL level, the Operational Safety Objectives, and the Operational Safety Objectives Means of Compliance as primary inputs when assessing liability limits, deductibles, and exclusions. A higher SAIL score — reflecting operations over populated areas or in non-segregated airspace — will attract more restrictive terms.

Operators flying under an OA must also comply with the mandatory third-party liability insurance requirements set out in UK Regulation (EU) No 785/2004 as retained in domestic law. Limits under that regulation are expressed in Special Drawing Rights (SDRs) and scale with maximum take-off mass. Brokers should confirm that the policy limit, quoted in GBP, satisfies the SDR-denominated statutory minimum at the exchange rate prevailing at inception — and that the policy responds to the full scope of the OA, not merely the minimum statutory floor.

• Open category: limited BVLOS carve-outs for sub-250 g aircraft in specific conditions only
• Specific category: OA or PDRA required; SORA methodology determines SAIL level
• Certified category: manned-aviation equivalence; applies to larger or higher-risk BVLOS platforms
• UK Regulation (EU) No 785/2004: statutory liability minima expressed in SDRs, scaled by MTOM

What a BVLOS Hull and Liability Programme Should Cover

A well-structured BVLOS programme is built around four interlocking covers. Third-party liability is the statutory foundation, but hull all-risks, payload liability, and — where relevant — grounding liability for fleet operators each need to be addressed in the same placement to avoid gaps between policies.

Hull all-risks cover for BVLOS aircraft should be written on an agreed-value basis, reflecting the difficulty of establishing market value for bespoke platforms. Deductibles typically rise on autonomous or highly automated operations relative to pilot-in-command BVLOS, because the claims frequency profile differs and the investigative cost of an autonomous-system incident is higher. Brokers should negotiate deductible structures that align with the operator's maintenance regime and redundancy architecture rather than accepting a flat percentage.

Payload cover is frequently underwritten separately or as an extension, and the scope matters: a thermal imaging sensor has a different replacement cost and a different liability profile than a delivery payload or a broadcast-quality camera. Where the payload itself can cause third-party harm — a dropped package, a fuel cell leak — the liability wording must extend to payload-related losses, not merely aircraft-related losses.

Grounding and loss-of-use cover becomes commercially significant for operators running scheduled BVLOS services — corridor inspections, pipeline surveys, logistics routes — where a grounded aircraft generates direct revenue loss. Underwriters will require evidence of contracted revenue and maintenance records before quoting this extension.

• Third-party liability: statutory SDR-based minimum, typically exceeded by commercial programme limits
• Hull all-risks: agreed value, BVLOS-affirmed, autonomous-ops deductible clause where applicable
• Payload liability: extension or standalone, scoped to payload type and drop/release risk
• Grounding / loss-of-use: available for contracted-revenue BVLOS operations
• Crew personal accident: relevant where remote pilots operate in hazardous ground environments

What Underwriters Assess at Submission

A BVLOS submission that arrives without the operator's OA document, SORA, and operations manual will be declined or heavily loaded. Underwriters need to read the approved operational scope — geographic area, altitude band, airspace class, detect-and-avoid system, contingency procedures — before they can price the risk. Brokers who pre-screen submissions against these requirements reduce turnaround time and improve the quality of terms they receive.

Platform specification matters beyond MTOM. Underwriters assess redundancy architecture (dual-IMU, redundant power, parachute recovery), communication link type and range, and whether the aircraft holds a type-certification or is a bespoke build. Bespoke platforms without a recognised type record attract wider pricing bands because loss-adjustment and parts-sourcing costs are harder to model.

Pilot and organisation credentials are scrutinised closely. The remote pilot's GVC (General VLOS Certificate) or equivalent, any additional BVLOS-specific training endorsed by the CAA or a National Qualified Entity, the operator's CAA registration number, and the organisation's safety management system maturity all feed into the underwriting assessment. A first-year operator with a new OA will face different terms than an organisation with a multi-year claims-free track record on similar operations.

Premiums scale with hull value, liability limit, BVLOS exposure hours, geographic scope, and the SAIL level of the approved operation. Autonomous operations — where the remote pilot is monitoring rather than actively controlling — attract additional scrutiny and, in most markets, a loading relative to pilot-in-command BVLOS.

How Brokers Should Structure a BVLOS Submission

Prepare a submission pack before approaching underwriters. The pack should include the operator's current OA (or the PDRA reference and compliance evidence), the SORA or risk assessment, the operations manual, the aircraft technical specification sheet, the remote pilot credentials, and a twelve-month flight-hours forecast broken down by operation type. If the operator is mid-OA application, indicate the expected issue date and provide the draft SORA — some underwriters will offer indicative terms against a draft, which helps operators budget before authorisation is granted.

Approach specialist BVLOS underwriters rather than generalist aviation markets. The Lloyd's and London company markets contain a small number of syndicates and insurers with dedicated drone underwriting teams who understand SORA outputs and OA conditions. Placing BVLOS risk with a generalist aviation underwriter who lacks this specialism increases the probability of coverage disputes at claims stage.

Review policy wording against the OA scope line by line. Confirm that the geographic area of operations, the airspace classes, the autonomous-flight provisions, and the payload types are all explicitly within scope. Where the OA is broad — for example, a corridor authorisation covering multiple airspace classes — ensure the policy does not contain a narrower geographic or airspace limitation that would create an uninsured gap.

Emerging BVLOS Operations and Coverage Considerations

Urban Air Mobility (UAM) corridors, drone delivery networks, and Beyond Radio Line of Sight (BRLOS) operations are pushing BVLOS risk into territory that existing policy wordings were not designed to address. Operators planning these operations should engage underwriters at the design stage — before the OA application is submitted — so that coverage architecture can be built alongside the operational design.

Counter-drone and airspace conflict liability is an emerging exposure for BVLOS operators: if a BVLOS aircraft causes a conflict that triggers a manned-aircraft go-around or emergency procedure, the liability chain is complex. Specialist wordings are beginning to address this, but coverage is not uniform across the market. Brokers should ask underwriters specifically how the policy responds to airspace conflict scenarios that do not result in a physical collision.

Cyber and data-link interference exclusions are increasingly common in aviation policies and can be particularly problematic for BVLOS operations, where the command-and-control link is a critical safety system. If the policy contains a cyber exclusion, brokers should assess whether a standalone cyber extension or a separate cyber policy is needed to cover command-link interference scenarios that result in hull loss or third-party damage.

Frequently asked questions

Does a standard commercial drone policy cover BVLOS flights?

Not automatically. Most commercial drone policies are written against VLOS operations and contain either an express BVLOS exclusion or a 'lawful operation' condition that voids cover if the flight exceeds the scope of the operator's permissions. A BVLOS-affirmed policy — one that explicitly references the operator's Operational Authorisation and confirms cover for the approved BVLOS scope — is required. Always obtain written confirmation from the underwriter before binding.

What regulatory documents does an operator need before applying for BVLOS insurance?

At minimum: a CAA-issued Operational Authorisation (or evidence of a compliant PDRA operation), a completed SORA or equivalent risk assessment, an approved operations manual, and current CAA operator registration. Underwriters will also want the remote pilot's credentials, including GVC or equivalent and any BVLOS-specific training records. Operators mid-application can approach underwriters for indicative terms using draft documentation.

How does the CAA's SAIL level affect insurance terms?

The SAIL level produced by the SORA process is a direct input into underwriting. Higher SAIL levels — reflecting operations over populated areas, in non-segregated airspace, or with reduced contingency margins — indicate greater potential severity of a third-party loss. Underwriters typically respond with higher liability limits requirements, more restrictive deductible structures, and closer scrutiny of the operator's safety management system. A lower SAIL level, achieved through operational design choices such as geographic restriction or reduced altitude, will generally produce more competitive terms.

Are autonomous BVLOS operations covered under the same policy as pilot-in-command BVLOS?

Not necessarily on the same terms. Autonomous operations — where the remote pilot monitors rather than actively controls the aircraft — present a different frequency and severity profile, particularly for hull losses during system-failure scenarios. Most underwriters treat autonomous ops as a distinct sub-class and may apply a loading, a higher deductible, or require additional technical evidence of redundancy architecture. Brokers should declare the degree of autonomy explicitly at submission rather than allowing it to be captured under a general BVLOS description.

What is the broker workflow for placing a BVLOS programme through BVLOS Insure?

Compile a submission pack containing the OA, SORA, operations manual, aircraft technical specification, remote pilot credentials, and a twelve-month flight-hours forecast. Submit to the BVLOS Insure underwriting team via the broker portal or by direct email. Indicative terms are typically issued within five working days for complete submissions. Formal quotation follows receipt of any outstanding documentation. Binding is subject to underwriter sign-off on the final OA scope and any endorsements required to align the policy wording with the authorised operation.

Does BVLOS insurance cover payload liability and cyber or data-link risks?

Payload liability and cyber or data-link risks require specific attention at placement. Payload liability — covering harm caused by a dropped or malfunctioning payload — is not always included in the base wording and may need to be added as an extension scoped to the payload type. Cyber and data-link interference exclusions are increasingly common in aviation policies; if present, a separate cyber extension or standalone cyber policy may be needed to cover command-link scenarios that result in hull loss or third-party damage. Brokers should review both points explicitly with the underwriter before binding.