BVLOS Drone Insurance for Beyond Radio Line of Sight UK

Regulatory Context: CAA Specific Category and BRLOS

UK drone regulation sits across three operational categories — Open, Specific, and Certified — established under UK Retained Regulation (EU) 2019/945 and 2019/947, with the Air Navigation Order 2016 serving as the primary domestic enforcement vehicle. BVLOS and BRLOS operations fall firmly within the Specific category, meaning the operator must obtain a CAA Operational Authorisation before any commercial flight. That authorisation is issued against a completed SORA (Specific Operations Risk Assessment), which scores the operation across ground risk class and air risk class to produce a required level of robustness for each safety objective. The CAA's published guidance document CAP 722 (UAS Flight in UK Airspace) is the operative reference for operators and brokers navigating this process, and the CAA's OSC submission portal is the formal channel through which Operational Safety Cases are lodged.

Within the Specific category, the UK CAA offers two routes to authorisation. The first is a Predefined Risk Assessment (PDRA) — a pre-assessed operational scenario published by the CAA that allows operators to self-declare compliance without a full bespoke SORA, provided their operation fits the PDRA parameters precisely. The second is a bespoke Operational Authorisation supported by a full Operational Safety Case. BRLOS operations almost always require the bespoke route: the loss of real-time radio command-and-control link introduces autonomous contingency behaviours and datalink redundancy requirements that fall outside any currently published PDRA. Brokers should note that the UK CAA has not adopted EASA Standard Scenarios (STS-01, STS-02) as live UK routes; the PDRA framework is the closest UK equivalent, and the two should not be conflated in submission documentation.

The CAA's processing timeline for a bespoke Operational Authorisation — including OSC review — is widely documented in CAA guidance as typically running to several weeks, and can extend further for novel platforms or complex airspace environments. Brokers advising operators on programme timing should build this lead time into the project schedule and engage the insurance market in parallel with, not after, the authorisation process. Submissions that arrive after the authorisation has been issued but with an imminent start date are the most common cause of avoidable delays at binding.

Mandatory Liability Insurance: The Statutory Framework

Third-party liability insurance for commercial UAS operations in Great Britain is mandatory under UK Retained Regulation (EC) 785/2004, which sets minimum liability requirements by reference to the aircraft's maximum take-off mass (MTOM). This regulation — not the ANO 2016 directly — is the statutory source of the insurance obligation, and brokers should cite it accurately when advising operators on compliance. UK Retained Regulation (EU) 2019/947 governs operational categories and the SORA framework; it does not itself establish the insurance mandate.

UK Retained Regulation (EC) 785/2004 establishes MTOM weight bands that determine minimum liability thresholds. The sub-20 kg band and the 20 kg and above band are the two categories most relevant to commercial Specific category UAS operations, with the higher band attracting a materially greater minimum limit. Limits under the regulation are denominated in Special Drawing Rights (SDR) as the unit of account — this is the correct regulatory context for SDR references, applying to the statutory minimum floor only. In practice, most BRLOS operations over infrastructure, populated corridors, or under contractual arrangements with network operators or local authorities will require limits that exceed the regulatory minimum by a significant margin, and those contractual minima will be quoted in GBP. Brokers should confirm both the regulatory floor and any client-specified contractual minimum when structuring the liability layer.

Where a BRLOS operation involves a ground-based observer network or a remote pilot station with multiple crew, the policy should confirm that all authorised remote pilots and observers are covered as insured persons for liability arising from their operational role. Policies that restrict cover to a named pilot will create gaps in a multi-crew BRLOS deployment. Payload liability — covering damage caused by a sensor, camera, or delivery item rather than by the aircraft itself — is not automatically included in standard hull and liability wordings and should be confirmed as an endorsement where the payload value or risk profile warrants it.

Hull Coverage: What Changes at BRLOS

Hull insurance for BVLOS and BRLOS platforms is agreed value cover on the airframe, payload, and ground control station. Premiums scale with hull value, the degree of autonomous operation, and the BRLOS exposure as a proportion of total flight hours. A platform flying occasional BVLOS sorties under a mixed authorisation will attract different terms than a dedicated BRLOS asset flying daily corridor missions.

Deductibles typically rise on autonomous operations because the absence of real-time pilot intervention increases the severity of a loss event. Underwriters will examine whether the aircraft carries a flight termination system, whether the ConOps includes a defined safe-state behaviour on datalink loss, and whether the operator has demonstrated the system in a controlled environment. For novel BRLOS platforms, the CAA may require a Flight Test Report or evidence of system qualification as part of the OSC — and underwriters will look for the same documentation. Evidence of manufacturer flight test data and operator acceptance testing materially supports the submission and can influence both the deductible structure and the breadth of autonomous operations cover.

Fleet programmes covering multiple BRLOS-capable platforms should be presented with a schedule that distinguishes BVLOS-authorised airframes from those operating only within VLOS. Bundling all assets under a single description without that distinction will slow the underwriting process and may result in blanket exclusions being applied to the BVLOS exposure.

Key Underwriting Triggers for a BRLOS Submission

Underwriters assessing a BRLOS risk will focus on a defined set of operational and technical factors. Presenting these proactively in the submission reduces turnaround time and avoids mid-process queries that delay binding.

The following factors are assessed on every BRLOS submission:

• CAA Operational Authorisation — confirmed scope, geography, and expiry date
• Completed and CAA-accepted SORA, including ground risk class and air risk class determination, submitted via the CAA OSC portal
• Confirmation of whether the authorisation was obtained via a PDRA or a bespoke OA route — BRLOS will almost always be bespoke
• ConOps document covering datalink loss procedures, flight termination system specification, and safe-state behaviours
• Platform MTOM and applicable weight band under UK Retained Regulation (EC) 785/2004
• Flight Test Report or system qualification evidence for novel BRLOS platforms, where required by the CAA as part of the OSC
• Detect-and-avoid system type and certification status (e.g. ADS-B in, FLARM, or proprietary DAA)
• Operator experience record — total BVLOS flight hours, incident history, and previous authorisation history
• Third-party contracts or airspace agreements specifying liability minima in GBP
• Whether operations are flown over congested areas, near aerodromes, or within controlled airspace under a Letter of Agreement

Broker Workflow: Placing a BRLOS Programme

Start the submission process before the CAA Operational Authorisation is finalised. Some underwriters will issue indicative terms against a draft SORA, allowing the operator to budget for insurance costs during the authorisation process. Binding is conditional on the final authorisation being provided, but early engagement avoids the common problem of an operator receiving their CAA authorisation and then discovering the insurance market needs several weeks to assess a complex BRLOS risk. Given that the CAA's own OSC review process runs to multiple weeks for bespoke authorisations, parallel-tracking the insurance placement is straightforward to plan.

Prepare a single submission pack containing the authorisation, SORA summary, ConOps, platform specification sheet, Flight Test Report where applicable, and a completed proposal form. Reference CAP 722 compliance in the submission narrative — underwriters familiar with the UK market will recognise it as a signal that the operator has engaged properly with the regulatory process. Fragmented submissions slow the process and can result in the risk being declined before it is properly assessed. If the operator is transitioning from a VLOS programme to BVLOS, include the prior policy schedule and loss history to demonstrate continuity.

Once terms are agreed, confirm that the policy schedule accurately reflects the authorisation scope. A policy that covers BVLOS but does not explicitly reference BRLOS, or that limits cover to operations within radio line of sight, will leave the operator uninsured for the specific missions the authorisation permits. This is a common source of coverage disputes and should be resolved at inception, not at the point of claim.

Programme Structures for Ongoing BRLOS Operations

Annual programmes are the standard structure for operators with a defined operational calendar. Where BRLOS missions are seasonal or project-based, some underwriters will consider a project-specific endorsement to an existing annual policy rather than a standalone placement. This approach can be more efficient for operators who fly BVLOS only for specific infrastructure contracts.

Operators scaling from single-platform to multi-platform BRLOS programmes should review their policy structure at each renewal. Fleet arrangements that aggregate hull values and share a single liability limit can produce coverage gaps if one platform operates under a different authorisation scope or in a higher-risk environment than the others. A layered programme — primary liability with an excess layer for higher-value contracts — is worth considering once the fleet and contract profile justifies the additional structure.

Data and cyber coverage is increasingly relevant for BRLOS operations where the aircraft transmits sensitive survey or inspection data via encrypted datalink. While this is a separate product line from hull and liability, brokers placing BRLOS programmes should flag the exposure to the operator and confirm whether it is addressed elsewhere in their insurance portfolio.

Frequently asked questions

What does a BVLOS drone insurance policy actually cover?

A BVLOS hull and liability policy typically covers physical loss or damage to the airframe, payload, and ground control station on an agreed value basis, combined with third-party liability for bodily injury and property damage arising from the operation. Coverage should explicitly extend to BVLOS and BRLOS missions as defined in the CAA Operational Authorisation. Additional endorsements may be required for payload liability, multi-crew liability, and data or cyber exposure. The policy wording should be checked against the ConOps to confirm there are no operational exclusions that conflict with the authorisation scope.

Is a CAA Operational Authorisation required before I can obtain BVLOS insurance?

Most underwriters require a confirmed CAA Operational Authorisation before binding final terms, because the authorisation and the associated SORA define the risk they are accepting. Some underwriters will provide indicative terms against a draft SORA to support budgeting during the authorisation process, but binding is conditional on the final authorisation. Operating BVLOS without a valid Operational Authorisation is a breach of UK Retained Regulation (EU) 2019/947 Article 5, which prohibits Specific category operations without a valid OA, and will void most aviation liability policies regardless of what the schedule states.

How does the broker submission process work for a BRLOS risk?

Prepare a single submission pack containing the CAA Operational Authorisation, SORA summary, ConOps, platform specification, Flight Test Report where the CAA required one as part of the OSC, completed proposal form, and prior loss history if applicable. Submit this to the specialist market — generalist brokers without aviation binding authority will need to approach a specialist MGA or Lloyd's coverholder. Allow sufficient lead time before the operation commences; the CAA's own OSC review for bespoke BRLOS authorisations runs to multiple weeks, and underwriters need comparable time to assess complex risks. Early engagement, before the authorisation is finalised, is strongly recommended.

What is the statutory basis for mandatory drone liability insurance in the UK, and how does MTOM affect the required limit?

Mandatory third-party liability insurance for commercial UAS operations in Great Britain flows from UK Retained Regulation (EC) 785/2004. The regulation sets minimum liability thresholds by MTOM weight band — the sub-20 kg and 20 kg and above bands are the most relevant for Specific category commercial operations, with the higher band requiring a greater minimum limit. The statutory minimums are expressed in SDR units within the regulation itself. In practice, BRLOS operations over infrastructure or under commercial contracts will typically require limits well above the regulatory floor, and those contractual minima will be specified in GBP. Brokers should confirm both the regulatory minimum and any client-specified contractual requirement when structuring the liability layer.

What regulatory documents trigger a change in insurance terms?

Any change to the CAA Operational Authorisation — including an extension of geographic scope, an increase in MTOM moving the platform into a higher weight band under UK Retained Regulation (EC) 785/2004, a change in operating environment from rural to congested, or the addition of BRLOS capability to a previously VLOS-only authorisation — is a material change that must be notified to underwriters. Failure to notify can result in claims being declined on the basis of non-disclosure. Similarly, if the SORA is revised and resubmitted to the CAA via the OSC portal, the updated version should be provided to the insurer promptly.

Does standard drone insurance cover operations beyond radio line of sight specifically?

Standard Open category or lower-risk Specific category drone policies almost always exclude BVLOS and BRLOS operations. The exclusion is typically worded by reference to visual line of sight or radio line of sight limitations, or by restricting cover to operations within a PDRA scope that does not extend to BRLOS. Operators who have obtained a bespoke Operational Authorisation for BRLOS must ensure their policy is specifically endorsed to cover that authorisation scope. If the policy schedule does not reference BRLOS or the specific authorisation number, the operator should seek written confirmation from the insurer before flying.