BVLOS Drone Insurance & Employer Liability for UK Operators

Why BVLOS Changes the Liability Picture

Standard Open-category drone policies are written around a pilot who can see the aircraft and intervene instantly. The moment an operation moves into Specific-category BVLOS — whether under a CAA Operational Authorisation, a Light UAS Operator Certificate (LUC), or a standard scenario such as PDRA-01 — the risk model shifts. The pilot-in-command may be kilometres from the aircraft, ground crew may be stationed along the route, and automated contingency manoeuvres may execute without direct human input. Each of those factors widens the gap between a standard hull-and-third-party policy and the cover the operation actually needs.

Employer liability is the layer most commonly underestimated at placement. Under the Employers' Liability (Compulsory Insurance) Act 1969, any GB-registered business with employees — including labour-only subcontractors who meet the statutory definition — must carry a minimum statutory limit of indemnity of £5 million per occurrence. BVLOS operations routinely involve remote pilots, visual observers, payload operators, and ground-based command-and-control technicians. All may qualify as employees for EL purposes. A policy that covers the drone but not the crew is not a compliant programme.

Insurers underwriting BVLOS EL assess the same risk factors as conventional aviation EL — crew training records, emergency procedures, site-specific risk assessments — but they add BVLOS-specific scrutiny: the ConOps submitted to the CAA, the robustness of the C2 link loss procedure, and whether the operation uses detect-and-avoid technology. Operators who present a well-documented Safety Case will consistently achieve better terms than those who cannot evidence their CAA submission.

CAA Regulatory Framework and What It Triggers at Placement

The UK drone regulatory framework — retained from EU Regulation 2019/947 and administered by the Civil Aviation Authority — divides commercial UAS operations into Open, Specific, and Certified categories. BVLOS flight sits almost entirely within Specific category, requiring either a standard scenario authorisation where one exists, a bespoke Operational Authorisation, or an LUC that grants self-authorisation rights. Each route produces a different document set, and underwriters will ask to see the relevant authorisation before binding.

PDRA-01 is the CAA standard scenario most relevant to lower-risk BVLOS operations, providing a defined operating envelope that reduces the burden of a full bespoke risk assessment. Where an operation falls outside any published PDRA — due to airspace class, population density, MTOM, or operational complexity — the operator must obtain a bespoke Operational Authorisation supported by a full SORA-style risk assessment. Underwriters treat the boundary between PDRA and bespoke OA as a material risk differentiator: bespoke OA risks attract closer scrutiny and, typically, longer quote turnaround.

UK Article 16 transitional authorisations were issued under the CAA's post-Brexit transitional arrangements to allow certain legacy operations to continue. Most of these authorisations have now expired or been superseded by full Operational Authorisations under the current framework. Operators still citing an Article 16 document should verify its current validity directly with the CAA before relying on it at renewal. Brokers should flag any client still holding an Article 16 reference as a potential renewal risk and prompt them to confirm their current authorisation status.

Operators must also be registered through the CAA's Drone and Model Aircraft Registration and Education Service (DMARES). The DMARES registration number is a mandatory field on the policy schedule; underwriters will not bind cover without it. Confirm the registration number is current and matches the operator entity named on the policy.

• Open category: VLOS only; the C1-class weight threshold under UK retained regulation is 250 g MTOM; CE marking carries a defined transitional acceptance period under UKCA transition rules and should not be treated as equivalent to UKCA marking without confirming current transitional status
• Specific category: most commercial BVLOS; standard scenarios (including PDRA-01) where applicable, otherwise bespoke Operational Authorisation required; specialist policy wording essential
• Certified category: manned-aviation equivalence; applies to larger UAS or operations over people at scale; full aviation hull and liability programme required
• Article 16: largely expired or superseded; operators holding these documents must verify current validity with the CAA

Structuring the Hull and Third-Party Liability Programme

Hull cover for BVLOS aircraft should reflect replacement value, not depreciated book value. BVLOS platforms — fixed-wing survey aircraft, multi-rotor inspection drones with specialist payloads, hybrid VTOL units — carry hull values that can be significant, and a total-loss event during an autonomous contingency manoeuvre is not a theoretical scenario. Agreed-value hull wordings are preferable to market-value wordings for this asset class; brokers should negotiate this at placement rather than at claim.

Third-party liability limits for Specific-category BVLOS operations are not set by the CAA, applying UK Retained Regulation (EU) 2019/947, at a fixed GBP figure. The appropriate limit for a given operation is agreed between broker and underwriter based on operational risk factors: the airspace environment, the population density overflown, the nature of the payload, and the complexity of the approved ConOps. A BVLOS survey flight over open moorland carries a different third-party exposure than a corridor inspection over a live railway. Premiums scale with hull value, BVLOS exposure, and ConOps complexity — the broker, not this page, is the right source for specific figures.

Payload cover is frequently written as a separate section or endorsement. Thermal cameras, LiDAR units, and hyperspectral sensors represent a material proportion of total asset value on many BVLOS platforms. Confirm with the insurer whether payload is included in the hull sum insured or requires separate scheduling, and whether payload liability — damage caused by the payload rather than the airframe — is within scope.

Employer Liability: Scope, Crew Classification, and Common Gaps

The 1969 Act applies to employees working under a contract of service or apprenticeship. Courts and the Health and Safety Executive apply a multi-factor test to determine employment status, and BVLOS operations frequently involve arrangements that sit in a grey zone: freelance remote pilots engaged on a per-mission basis, visual observers supplied by a third-party ground-crew agency, and data-link technicians who are nominally self-employed but work exclusively for one operator. Brokers should advise clients to obtain a formal employment-status assessment from their legal team and share the outcome with the insurer at placement.

EL cover must be in place before the first employee is engaged, not after the first incident. For BVLOS operators scaling from a single-pilot VLOS operation to a multi-crew BVLOS programme, the transition point — when the first additional crew member is engaged — is the trigger. Waiting until the CAA Operational Authorisation is granted before arranging EL cover creates an uninsured window that the 1969 Act does not permit.

The statutory minimum limit of indemnity under the 1969 Act is £5 million per occurrence, as documented by the HSE. Policies must meet this threshold; sub-limits that fall below it are non-compliant. Common gaps in BVLOS EL programmes also include: failure to extend cover to crew operating ground control stations at remote locations; exclusions for crew injury arising from C2 link failure events where the aircraft enters an autonomous contingency manoeuvre; and failure to schedule all qualifying crew on the policy. Review the policy schedule against the full crew manifest, not just the named remote pilot.

• Confirm employment status of all crew before placement — freelance does not automatically mean outside the 1969 Act
• EL must be in force before the first qualifying employee is engaged
• Check that ground-station operators and visual observers are within the policy's definition of 'employee'
• Verify the limit of indemnity meets the £5 million statutory minimum per occurrence
• Ensure no exclusion applies to autonomous contingency manoeuvre events
• Confirm DMARES registration number is recorded on the policy schedule

Broker Workflow: From ConOps to Bound Cover

Placing a BVLOS programme efficiently requires assembling the right document set before approaching underwriters. Incomplete submissions result in extended quote turnaround and, in some cases, declinations that could have been avoided. The minimum submission pack for a Specific-category BVLOS risk should include the CAA Operational Authorisation or LUC, the ConOps summary, the operator's GVC or A2 CofC as baseline competency evidence (with any PDRA-specific qualification where applicable), the aircraft maintenance records, the DMARES registration number, and a crew manifest with employment-status confirmation.

Specialist BVLOS underwriters typically require five to ten working days to assess and quote a bespoke OA risk. Where the SORA documentation underpinning the CAA submission is incomplete or has not been shared with the broker, turnaround will extend further. Brokers should set this expectation with clients at the outset of the placement process — last-minute submissions against an imminent operational start date are the most common cause of coverage gaps on BVLOS programmes.

Underwriters will also want to understand the data-link architecture — whether C2 operates over licensed spectrum, the redundancy arrangements, and the detect-and-avoid solution in use. Operations using 4G/5G C2 links should be prepared to evidence network resilience testing. These are not bureaucratic requests; they are the underwriter's proxy for assessing the probability and severity of a C2 loss event, which is the primary loss scenario in BVLOS hull and liability claims.

Mid-term changes — new aircraft added to the fleet, extension of the approved operating area, addition of new crew members, or receipt of a CAA variation to the Operational Authorisation — should be notified to the insurer promptly. BVLOS policies are typically written on a scheduled-aircraft basis, and an unscheduled aircraft operating under the policy is an uninsured aircraft. Build a notification protocol into the operator's change-management process at programme inception.

• CAA Operational Authorisation or LUC documentation
• ConOps summary (full document or executive summary acceptable to most underwriters)
• Remote pilot competency evidence: GVC or A2 CofC as baseline; PDRA-specific qualification where the standard scenario applies
• Aircraft maintenance records and airworthiness documentation
• DMARES registration number (mandatory for policy schedule)
• Crew manifest with employment-status confirmation
• C2 link architecture summary and detect-and-avoid solution description
• SORA risk assessment where a bespoke OA is in place

Frequently asked questions

What does a BVLOS drone insurance policy cover that a standard commercial drone policy does not?

A standard commercial drone policy is typically written for Specific-category VLOS operations: the pilot can see the aircraft, intervene immediately, and the risk envelope is relatively contained. A BVLOS policy extends cover to operations conducted beyond the remote pilot's unaided visual range under a CAA Operational Authorisation, an LUC, or a standard scenario such as PDRA-01. The hull wording must respond to autonomous contingency manoeuvre events, the third-party liability section must reflect the wider geographic footprint of the flight, and the policy must accommodate the multi-crew structure that BVLOS operations require. Payload cover, ground-equipment cover, and employer liability are typically written as additional sections rather than assumed within a standard wording.

Is employer liability compulsory for BVLOS drone operators in Great Britain, and what is the minimum limit?

Yes. The Employers' Liability (Compulsory Insurance) Act 1969 requires any GB-registered business with one or more employees to hold a policy meeting the statutory minimum limit of indemnity of £5 million per occurrence, as documented by the HSE. The definition of 'employee' extends beyond permanent staff to include individuals who work under the operator's direction and control, even if they are nominally self-employed. BVLOS operations routinely involve remote pilots, visual observers, payload operators, and ground-station technicians who may meet this definition. Failure to hold compliant EL cover exposes the operator to fines under the Act and leaves crew without statutory protection.

Which CAA authorisation documents does an underwriter need before binding a BVLOS policy?

At a minimum, underwriters require the CAA Operational Authorisation or, where the operator holds a Light UAS Operator Certificate, the LUC itself along with the scope of privileges it grants. Where the operation is conducted under PDRA-01, the relevant standard scenario declaration should be provided. The ConOps — or a structured summary — is also required because it defines the approved operating envelope that forms the policy boundary. Operators who previously held Article 16 transitional authorisations should confirm with the CAA that their current authorisation is valid, as most Article 16 documents have now expired or been superseded by full OAs. The DMARES registration number must also be provided for inclusion on the policy schedule.

What happens to cover if the operator flies outside the parameters of their CAA Operational Authorisation?

Flight outside the approved operating envelope — whether that means exceeding the authorised range, operating in an airspace class not covered by the authorisation, using an aircraft not listed on the authorisation, or flying with crew who do not hold the required competency — is likely to constitute a material change in risk. Most BVLOS policy wordings contain a condition requiring the operator to maintain their regulatory authorisation and to notify the insurer of any variation. A claim arising from flight outside the authorised parameters may be declined on the basis that the risk presented at placement no longer existed at the time of the loss. Operators should treat their CAA authorisation and their insurance policy as parallel documents that must remain aligned.

Can hull, third-party liability, and employer liability be placed under a single BVLOS programme?

Most specialist BVLOS underwriters — including those on the BVLOS Insure panel — can write hull, third-party liability, and employer liability within a single combined policy or as a coordinated programme with a single point of claims contact. This is preferable to placing EL with a general commercial insurer and hull/liability with an aviation specialist, because split programmes create coverage gaps at the interface: an incident involving both aircraft damage and crew injury may produce a coverage dispute between two insurers applying different definitions of the same event. A single programme with a specialist underwriter who understands the BVLOS risk eliminates that gap.

How long does it take to place a BVLOS programme, and what causes delays?

Specialist BVLOS underwriters typically require five to ten working days to assess and quote a bespoke Operational Authorisation risk from the point of receiving a complete submission. The most common cause of delay is incomplete SORA documentation — where the risk assessment underpinning the CAA submission has not been shared with the broker, underwriters cannot properly assess the approved operating envelope and will request it before quoting. Operations conducted under PDRA-01 may move more quickly because the standard scenario provides a defined risk framework. Brokers should build the five-to-ten working day window into the client's operational planning timeline and avoid last-minute submissions against an imminent start date.