BVLOS Drone Insurance UK Requirements

How the UK Regulatory Framework Defines BVLOS Risk

UK drone operations are governed under the UK retained version of EU regulation, administered by the CAA. The three-tier structure — Open, Specific, and Certified — determines the level of regulatory scrutiny an operation faces. The vast majority of BVLOS flights fall within the Specific category, requiring an Operational Authorisation and a SORA-style risk assessment. Operations involving highly automated or autonomous aircraft that cannot be accommodated within the Specific category framework may escalate to the Certified category, which carries a materially different regulatory and insurance burden.

The Specific Operational Risk Assessment methodology assigns a Ground Risk Class and Air Risk Class to the operation, which together produce a final risk level. That risk level directly informs the minimum robustness requirements for your operational safety case — and insurers use the same risk inputs when underwriting hull and liability cover. An operation with a higher final risk level will face more rigorous policy conditions, higher deductibles on autonomous or automated functions, and potentially sub-limits on certain loss scenarios.

The CAA has published a PDRA-UK series of Predefined Risk Assessments for repeatable, lower-complexity scenarios. It is important for brokers to understand that no current PDRA-UK covers BVLOS operations — the published PDRA-UK assessments, including PDRA-UK01, address VLOS scenarios only. All BVLOS operations therefore require a bespoke Operational Authorisation. There is no predefined pathway that removes the need for a full bespoke OA for BVLOS flights, and submissions to the market should reflect this accordingly.

The Concept of Operations document — the ConOps — is a named submission item for bespoke OA applications. Both the CAA and underwriters treat it as a primary risk-assessment input. A well-structured ConOps that clearly describes the operating environment, contingency procedures, and command-and-control architecture will support both the regulatory application and the insurance placement.

CAA Authorisation Routes: Bespoke OA and Article 16

For BVLOS operations, the standard route is a bespoke Operational Authorisation under the Specific category. The operator submits a full safety case — including the ConOps, SORA documentation, and evidence of remote pilot competency — and the CAA assesses the application against the risk level produced by the SORA methodology. The CAA has published an indicative processing target for bespoke OA applications; operators and brokers should treat this publicly stated window as the planning baseline and factor it into programme timelines. Binding or conditionally binding insurance cover before submission is advisable, since evidence of compliant cover is required as part of the application pack rather than as a post-approval step.

Article 16 of the UK retained UAS regulation provides a separate authorisation pathway for operators who are members of a CAA-approved model aircraft association or who operate under a CAA-recognised scheme. Article 16 authorisations are not a general BVLOS route — they apply to specific operator categories and carry their own conditions. Where an Article 16 authorisation is in place, brokers should confirm whether the scope of the authorisation extends to the BVLOS elements of the operation, since an Article 16 authorisation that does not explicitly cover BVLOS will not satisfy the CAA's requirements for those flights. The insurance submission should reference whichever authorisation route applies and include the relevant CAA reference documentation.

The distinction between a bespoke OA and an Article 16 authorisation matters for underwriting as well as regulation. Underwriters active in the BVLOS space will want to understand which route the operator has taken, since the two pathways carry different risk profiles and different levels of CAA scrutiny. A bespoke OA supported by a full SORA submission gives underwriters a richer risk-assessment dataset than an Article 16 authorisation, and this can affect both the terms available and the speed of the placement.

Mandatory Third-Party Liability Cover: Legal Basis and MTOM Bands

The primary UK instrument governing aviation insurance obligations is UK retained Regulation 785/2004 (as amended), which sets minimum third-party liability floors by maximum take-off mass band, expressed in Special Drawing Rights. The Air Navigation Order operates alongside it but is not the source of the insurance obligation itself. Brokers placing BVLOS programmes must identify the correct MTOM band for each aircraft and ensure the policy limit meets or exceeds the corresponding SDR floor.

The MTOM band structure under UK retained Regulation 785/2004 covers multiple weight categories relevant to commercial UAS operations. The bands include aircraft up to 500 kg MTOM, 500 kg to 1,000 kg, 1,000 kg to 2,700 kg, and further bands above that threshold for heavier aviation. Most commercial BVLOS UAS platforms — including fixed-wing survey aircraft, hybrid VTOL systems, and larger multi-rotor platforms — fall within the sub-500 kg band, but operators should not assume this without confirming the aircraft's certified MTOM. The SDR floor rises at each band boundary, and placing a policy against the wrong band creates a compliance gap that could affect both the OA application and any subsequent claim.

For practical underwriting purposes, the sub-25 kg threshold within the lower bands represents a meaningful internal boundary: aircraft at or above 25 kg MTOM attract a higher SDR minimum floor than lighter platforms. However, the full band structure extends well beyond this point, and brokers should confirm the precise SDR-denominated floor for the relevant band rather than relying on a binary sub-25/25-plus framing. The liability limit placed in the market will often exceed the regulatory floor to satisfy client contracts, landowner requirements, and OA conditions.

The liability limit required also scales with the nature of the operating environment. Operations over populated areas, critical infrastructure, or congested airspace attract higher minimum limits than equivalent flights over sparsely populated terrain. Insurers assess these factors independently of the regulatory minimum, and the policy limit placed in the market should reflect both the SDR floor and the operational risk profile. Brokers should note that the CAA's insurance requirement applies to the operation, not merely the aircraft — if a single OA covers a fleet of aircraft operating BVLOS under one safety case, the policy must respond to any aircraft within that fleet, and fleet endorsements and scheduled-aircraft clauses need to be reviewed carefully to ensure no gaps exist between the OA scope and the insured scope.

Hull Cover, Policy Wording, and Common BVLOS Exclusions

Third-party liability is the regulatory minimum, but hull cover is almost always placed alongside it for commercial BVLOS programmes. Aircraft operating BVLOS tend to be higher-value platforms — fixed-wing, hybrid VTOL, or purpose-built multi-rotor systems with redundant avionics — and the cost of a total loss without hull cover can be operationally catastrophic. Underwriters assess hull risk for BVLOS differently from standard VLOS operations, with key factors including the degree of autonomy, the reliability of the command-and-control link, the detect-and-avoid capability fitted, and whether the aircraft operates with a remote pilot actively monitoring or in a fully automated mission profile. Premiums scale with hull value and BVLOS exposure; deductibles typically rise on autonomous operations where pilot intervention is limited.

Brokers reviewing BVLOS policy wordings should pay close attention to exclusions that are common in this class but not always prominent in standard commercial drone policies. Cyber and command-and-control link failure exclusions appear frequently — some wordings exclude loss or liability arising from any failure, interruption, or unauthorised access to the C2 link, which is a material exposure for BVLOS operations where the C2 link is the primary means of aircraft control. Autonomous-mode sub-limits are also common: where the aircraft operates in a fully automated mission profile without active remote pilot input, some policies apply a reduced hull limit or a higher deductible for losses occurring in that mode. Brokers should identify whether the client's ConOps describes any autonomous segments and ensure the policy wording responds to those segments without a coverage gap.

Payload cover is a separate consideration. Survey sensors, LiDAR units, thermal cameras, and delivery payloads each carry their own replacement cost and may not be included under a standard hull clause. Operators should confirm whether payload is covered on an all-risks basis, whether it is subject to its own sub-limit, and whether cover applies during transit as well as during flight.

For Certified category aircraft, underwriters will require evidence of UK CAA type approval or airworthiness approval under retained UK aviation regulation. UK CAA airworthiness standards apply — EASA standards ceased to have direct effect in the UK following Brexit and do not substitute for UK CAA approval. The absence of a valid UK CAA airworthiness approval for a Certified category platform will typically prevent binding of hull cover. Brokers should confirm the airworthiness status of any Certified category platform before approaching the market.

Eligibility Criteria and What Brokers Need to Submit

Placing BVLOS hull and liability in the London specialty market or with an MGA requires a more detailed submission than a standard VLOS commercial programme. Underwriters need to understand the operational risk before they can quote, and incomplete submissions result in delays or declinations. Eligibility for BVLOS cover is not automatic — underwriters apply gatekeeping criteria that reflect the higher risk profile of beyond-visual-line-of-sight operations.

Common eligibility criteria applied by underwriters include a minimum number of logged flight hours on the specific aircraft type to be insured, a minimum operational track record demonstrating that the operator has conducted similar operations without significant incident, and evidence of a functioning Safety Management System. New BVLOS operators with limited flight hours on type or no established SMS are likely to face restricted terms, higher deductibles, or declination until they can demonstrate an adequate track record. Brokers should assess these criteria before approaching the market and advise clients accordingly — a submission that does not meet the underwriter's eligibility threshold will not produce bindable terms regardless of the quality of the CAA authorisation.

A complete submission allows an underwriter to assess the operation against their own risk appetite and produce terms genuinely aligned to the CAA authorisation in place. Submissions referencing a bespoke OA or an Article 16 authorisation should include the relevant CAA reference documentation so the underwriter can verify the authorisation scope. The ConOps document should be included in full — underwriters use it as a primary risk-assessment input in the same way the CAA does.

• Copy of the CAA Operational Authorisation (bespoke OA or Article 16 authorisation), including any conditions attached
• ConOps (Concept of Operations) document submitted to or accepted by the CAA
• SORA documentation or equivalent risk assessment, including the assigned Ground Risk Class and Air Risk Class
• Aircraft make, model, MTOM, and hull value for each platform to be insured, with aircraft registration(s)
• Details of the command-and-control architecture, including redundancy and fail-safe behaviour
• Detect-and-avoid system specification, if fitted
• Operational geography — typical operating areas, airspace classifications, proximity to populated areas
• Remote pilot competency evidence: GVC or equivalent for VLOS elements, plus CAA-accepted BVLOS competency evidence such as an operator-specific BVLOS competency scheme or a CAA-approved BVLOS training course
• Logged flight hours on type for each remote pilot operating under the OA
• Evidence of a Safety Management System appropriate to the scale and complexity of the operation
• Claims history for the preceding three years across all unmanned aircraft operations
• Details of any sub-contractors or third-party remote pilots operating under the same OA

Placing the Programme: Market Access, Timeline, and Policy Structure

The London specialty market, including Lloyd's syndicates and company market carriers, remains the primary source of capacity for complex BVLOS programmes in the UK. MGAs with delegated underwriting authority can offer faster turnaround for programmes that fall within their binding authority, which is particularly useful for operators with time-sensitive OA applications. Brokers should factor the CAA's published OA processing timeline into the client's programme schedule: the CAA has stated a target processing window for bespoke OA applications, and insurance evidence is required before or at the point of submission rather than after approval. Conditionally binding cover — subject to the OA being granted on terms consistent with the risk declared — is a recognised mechanism for managing this sequencing, but the conditions must be clearly documented and agreed with the underwriter before submission.

Policy structure for a BVLOS programme typically combines a liability section — covering third-party bodily injury and property damage arising from the operation — with a hull section on an agreed-value or market-value basis. Some programmes also include a public liability extension for ground crew activities, a legal expenses section, and cover for regulatory investigation costs. The scope of each section should be mapped against the operator's contractual obligations and the CAA's OA conditions before binding. Any autonomous-mode sub-limits or C2-link exclusions identified during wording review should be resolved at placement rather than discovered at the point of a claim.

Operators working across borders — for example, conducting BVLOS surveys in both the UK and EU member states — will need to confirm that the policy responds in each jurisdiction. Post-Brexit, UK-issued policies do not automatically satisfy EU member state insurance requirements, and a separate EU-admitted policy or a policy with an explicit territorial extension may be required. Brokers should clarify the territorial scope at placement and ensure it is documented in the policy schedule. Any material change to the OA during the policy period — new aircraft, expanded operating area, different payload, or revised conditions — should be notified to the insurer promptly, since operating outside the declared risk profile without notification may give the insurer grounds to decline a claim.

Frequently asked questions

At what point in the CAA OA process is insurance evidence required?

Evidence of compliant third-party liability insurance is required as part of the OA application pack — it is a submission input rather than a post-approval formality. Operators should ensure cover is bound, or conditionally bound with a confirmed limit, before submitting the application so that the evidence requirement can be satisfied without delay. The CAA has published an indicative processing target for bespoke OA applications; brokers should use that publicly stated window as the planning baseline and advise clients to engage the insurance market well in advance of their intended submission date.

What does a BVLOS drone insurance policy actually cover?

A fully structured BVLOS programme typically covers third-party liability for bodily injury and property damage caused by the aircraft or its operation, hull loss or damage on an all-risks basis, and payload cover for sensors or equipment carried. Extensions can include legal expenses, regulatory investigation costs, and ground crew public liability. The minimum liability floor is set by UK retained Regulation 785/2004 according to the aircraft's MTOM band, expressed in Special Drawing Rights — the policy limit placed in the market will often exceed that floor to satisfy client contracts and OA conditions. Brokers should review the policy wording carefully for cyber and C2-link failure exclusions and any autonomous-mode sub-limits, as these are common in BVLOS wordings and can create material coverage gaps.

Can a standard commercial drone policy cover BVLOS operations?

Standard commercial VLOS policies commonly exclude BVLOS operations, either explicitly in the policy wording or through a condition that cover applies only within the pilot's unaided visual line of sight. Operators who conduct BVLOS flights under a VLOS policy risk a coverage gap that would also place them in breach of their OA conditions. A BVLOS-specific endorsement or a policy written from inception to cover the authorised BVLOS scope is required. Brokers should check the territorial and operational scope clauses carefully before binding and confirm that any autonomous-mode segments described in the ConOps are covered without sub-limit or exclusion.

What eligibility criteria do underwriters apply to new BVLOS operators?

Underwriters typically require a minimum number of logged flight hours on the specific aircraft type to be insured, a demonstrable operational track record on similar operations, and evidence of a functioning Safety Management System. New operators with limited hours on type or no established SMS are likely to face restricted terms, higher deductibles, or declination until they can demonstrate adequate experience. Brokers should assess these criteria before approaching the market — a submission that does not meet the underwriter's eligibility threshold will not produce bindable terms regardless of the quality of the CAA authorisation. Pilot competency documentation, including CAA-accepted BVLOS competency evidence beyond the GVC, should be included in every submission.

Does the MTOM of my aircraft determine the minimum liability limit required?

Yes. UK retained Regulation 785/2004 sets minimum third-party liability floors by MTOM band, expressed in Special Drawing Rights. The band structure covers multiple weight categories — including sub-500 kg, 500 kg to 1,000 kg, 1,000 kg to 2,700 kg, and higher bands — with the SDR floor rising at each boundary. Most commercial BVLOS UAS platforms fall within the sub-500 kg band, but brokers should confirm the aircraft's certified MTOM rather than assuming the lowest band applies. Within the lower bands, aircraft at or above 25 kg MTOM attract a higher SDR floor than lighter platforms. Operators' own contractual obligations to clients or landowners will frequently require limits above the regulatory floor regardless of MTOM band.

What is the difference between a bespoke OA and an Article 16 authorisation for BVLOS?

A bespoke Operational Authorisation is the standard route for BVLOS operations under the Specific category. The operator submits a full safety case — including ConOps, SORA documentation, and competency evidence — and the CAA assesses it against the risk level produced by the SORA methodology. An Article 16 authorisation is a separate pathway available to operators who are members of a CAA-approved model aircraft association or who operate under a CAA-recognised scheme; it is not a general BVLOS route and applies only to specific operator categories. Brokers should confirm whether an Article 16 authorisation explicitly covers the BVLOS elements of the operation before treating it as sufficient for insurance and regulatory purposes. Underwriters will want to understand which route applies, as the two pathways carry different risk profiles and different levels of CAA scrutiny.