BVLOS Drone Insurance Certificate for Client Contracts

Why BVLOS Operations Require a Distinct Certificate

The UK Civil Aviation Authority structures unmanned aircraft operations into three regulatory categories: Open, Specific, and Certified. BVLOS flight sits firmly in the Specific category, requiring either a CAA-issued Operational Authorisation or, for lower-risk scenarios, a declaration against a published standard scenario. Neither route is available to an operator whose insurance policy was written for Open category VLOS work — the insurer's risk appetite, the territorial scope, and the liability sublimits are simply different instruments.

Client contracts in sectors such as infrastructure inspection, utilities corridor survey, and emergency-services support routinely specify that the operator must hold a policy endorsed for BVLOS and must be able to produce a certificate of insurance naming the client as an additional interested party. Procurement teams and their legal advisers treat this as a pass/fail condition. An operator who cannot produce the right document before mobilisation loses the contract regardless of their technical capability.

The certificate itself is a summary document — it evidences the policy, not the policy wording. What matters is that the underlying programme has been underwritten against a BVLOS operational profile, that the territorial limits match the project geography, and that the liability section is structured to respond to third-party bodily injury and property damage arising from autonomous or semi-autonomous flight beyond the pilot's direct line of sight.

What a Compliant Certificate Must Evidence

A BVLOS drone insurance certificate presented under a GB client contract should, at minimum, confirm the following on its face or by reference to a schedule of endorsements. Brokers who issue certificates that omit these elements expose their clients to contract breach and their own practice to professional indemnity risk.

The policy period must cover the full duration of the contracted works, including mobilisation and demobilisation phases. Many BVLOS projects run across financial years; a certificate that expires mid-project is a contractual defect.

Liability limits are quoted in GBP and must meet or exceed the floor set in the client's contract schedule. For operations involving flight over or near people, populated areas, or critical national infrastructure, clients frequently specify limits that exceed the statutory minimum required under UK Air Navigation Order provisions. The certificate must reflect the actual limit on the policy, not a generic statement.

• Named insured: the operator's legal entity as it appears on the CAA Operational Authorisation
• Additional insured or interested party: the client entity, as specified in the contract
• Operation type: BVLOS explicitly endorsed, not merely 'unmanned aircraft operations'
• Aircraft schedule: registration marks or fleet description matching the authorised aircraft
• Territorial scope: Great Britain and any offshore or cross-border extension required
• Liability structure: third-party liability limit, any sublimits for passenger or crew liability where relevant
• Hull cover: agreed value or market value basis, with BVLOS endorsement noted
• Cancellation notice period: typically 30 days, though some contracts demand longer

Regulatory Triggers That Shape the Underwriting

Underwriters assess BVLOS risk against the operator's CAA Operational Authorisation, which itself is grounded in a SORA-style (Specific Operations Risk Assessment) methodology aligned with EASA guidance that the CAA has adopted post-Brexit. The Ground Risk Class and Air Risk Class assigned during the SORA process directly inform the insurer's view of third-party liability exposure. An operation with a high Ground Risk Class — for example, flight over a populated area — will attract different underwriting terms than a low-density corridor survey.

The operator's ConOps (Concept of Operations) document, submitted to the CAA as part of the Operational Authorisation application, is the primary underwriting input. Brokers should obtain a copy before approaching markets. Underwriters will also want to see the operator's Remote Pilot competency evidence (GVC or equivalent), the aircraft's airworthiness documentation, and any detect-and-avoid or command-and-control link redundancy specifications.

Where an operation involves a tethered aircraft, a remotely piloted aircraft system operating in a segregated airspace corridor, or a drone-in-a-box deployment, each configuration carries its own risk characteristics. Insurers may apply specific endorsements or exclusions to each. The certificate must accurately reflect which configurations are covered; a certificate that is silent on configuration can be challenged at claims stage.

The Broker Placement Workflow

Placing a BVLOS programme for a GB operator is a specialty lines exercise. Standard commercial combined or SME package markets do not have the appetite or the policy language to respond correctly. The placement should go to a Lloyd's or London company market underwriter with a dedicated unmanned aircraft account, or to a specialist MGA with binding authority for this class.

The submission should be built around the operator's CAA Operational Authorisation (or draft ConOps if the authorisation is pending), the aircraft schedule with hull values, the operator's claims history, and a description of the specific contract or contracts for which the certificate is required. Where the operator runs a mixed fleet — some aircraft on Open category VLOS work, others on Specific category BVLOS — the programme should clearly delineate coverage by aircraft registration or operational profile to avoid ambiguity at claims stage.

Once terms are agreed, the broker issues the certificate against the bound policy. For client contracts that require the certificate before the policy inception date — common in public sector procurement — the broker can issue a cover note, but this must be followed by the formal certificate before the first flight. Brokers should build certificate issuance timelines into their service agreements with operators, particularly for projects with hard mobilisation deadlines.

Renewal is not automatic in this class. BVLOS programmes are reviewed annually against the operator's updated ConOps, any changes to the CAA Operational Authorisation, and the claims experience of the preceding period. Brokers should initiate renewal discussions at least 60 days before expiry to avoid a certificate gap that could suspend an active contract.

Common Certificate Defects That Fail Contract Review

Procurement teams and their insurers have become more sophisticated in reviewing drone insurance certificates. The most frequent defects that cause a certificate to be rejected are not errors in the liability limit — they are structural omissions in the endorsement language.

A certificate that describes coverage as 'unmanned aerial vehicle operations' without specifying BVLOS will be queried. A certificate that names the operator's trading name rather than its legal entity will not satisfy a contract that requires the legal entity. A certificate issued on a policy with a territorial limit of 'United Kingdom' may be insufficient for a project that includes operations in Northern Ireland under different airspace rules, or for a project with a cross-border element into Irish airspace.

Brokers should treat the client's contract insurance schedule as a checklist and map each requirement to a specific policy provision or endorsement before issuing the certificate. Where the policy does not respond to a requirement, the broker must either seek an endorsement from the underwriter or advise the operator that the contract requirement cannot be met on current terms — not issue a certificate that implies coverage that does not exist.

• Policy describes 'UAV operations' without BVLOS endorsement
• Named insured is a trading name, not the legal entity on the CAA authorisation
• Liability limit stated in a currency other than that specified in the contract
• Certificate omits the additional insured clause required by the client
• Territorial scope does not match the operational geography
• Hull cover basis (agreed value vs market value) not stated, creating valuation ambiguity at claims stage

Frequently asked questions

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

A BVLOS-endorsed certificate evidences a policy underwritten against beyond visual line of sight operational profiles — autonomous or semi-autonomous flight, extended range, detect-and-avoid reliance, and the elevated third-party liability exposure that comes with those factors. A standard Open category policy is written for VLOS flight where the remote pilot maintains direct visual contact and can intervene immediately. The two risk profiles are materially different, and an Open category policy will typically exclude or not respond to BVLOS losses. The certificate must reflect the correct underlying policy to be valid for a BVLOS contract.

Does the operator need a CAA Operational Authorisation before a BVLOS insurance certificate can be issued?

In most cases, yes. Underwriters require evidence that the CAA has assessed and authorised the specific BVLOS operation before they will bind coverage, because the Operational Authorisation is the primary document that defines the risk. Where an authorisation is pending, some underwriters will issue a cover note conditional on the authorisation being granted before first flight. Operators who are still in the SORA process should engage their broker early so that the insurance placement can run in parallel with the CAA application, avoiding a delay between authorisation and mobilisation.

Can a broker add a client as an additional insured on an existing BVLOS policy mid-term?

Yes, provided the underwriter agrees and the operation falls within the scope of the existing Operational Authorisation. The broker requests an endorsement naming the client as an additional interested party or additional insured, and once the underwriter issues the endorsement, a revised certificate is produced. This is routine in project-based contracting. However, if the new contract involves a different aircraft, a different operational geography, or a different risk profile than the authorised ConOps, the underwriter may require a mid-term adjustment to the policy terms before issuing the endorsement.

Which regulatory framework governs BVLOS drone insurance requirements in Great Britain?

In Great Britain, unmanned aircraft operations are regulated by the Civil Aviation Authority under the Air Navigation Order 2016 (as amended) and the UK Retained version of EU Regulation 2019/947. BVLOS operations fall within the Specific category and require a CAA Operational Authorisation based on a SORA-aligned risk assessment. The CAA's approach to SORA methodology is broadly consistent with the EASA framework, though the CAA operates independently post-Brexit. Insurance requirements for Specific category operations are set by the CAA and by the EU Aviation Safety Agency-derived requirements retained in UK law; liability limits must meet the statutory minimums, and client contracts frequently specify higher limits.

What information does a broker need from an operator to place a BVLOS programme?

The core submission documents are: the CAA Operational Authorisation (or draft ConOps if pending), the aircraft schedule with hull values and registration marks, the remote pilot's competency evidence (GVC or equivalent), a description of the intended operations including operational volume and ground risk environment, the operator's claims history for at least three years, and the client's contract insurance schedule specifying the required limits and certificate wording. The more complete the submission, the faster the underwriter can respond with terms. Incomplete submissions — particularly those lacking the ConOps or the aircraft schedule — will be returned for further information, delaying certificate issuance.

What happens if a BVLOS insurance certificate lapses during an active client contract?

A lapsed certificate is a contract breach. Most client contracts include a provision requiring continuous insurance cover throughout the works, and a lapse — whether through non-renewal, cancellation, or a gap between policy periods — gives the client grounds to suspend or terminate the contract and, in some cases, to claim damages. Operators should ensure their policy renewal is completed before the expiry date and that a new certificate is issued and delivered to the client before the old one expires. Brokers should build renewal reminders and certificate delivery confirmations into their account management process for all BVLOS clients.