BVLOS Drone Insurance for Beyond Radio Line of Sight

Regulatory Context: CAA Specific Category, UK Reg 2019/947, and BRLOS Permissions

In Great Britain, UAS operations are governed by two principal instruments that must be read together. UK Regulation 2019/947 — retained and amended in GB law following the UK's departure from the EU — is the primary UAS-specific regulation establishing the Open, Specific, and Certified category framework and the SORA-based risk assessment methodology. The Air Navigation Order 2016 (as amended) sits alongside it, providing the broader airspace and operator obligations framework including the mandatory third-party liability insurance requirement. Brokers advising operators on compliance should direct them to both instruments, and to the CAA's CAP 722 guidance document, which is the primary published source for preparing a Safety Case under the Specific category.

BRLOS operations sit firmly in the Specific category and require an Operational Authorisation issued by the CAA. Operators must submit an Operations Manual and, for higher-risk profiles, a Safety Case aligned with the SORA methodology. The SORA process produces a SAIL — Specific Assurance and Integrity Level — rating on a scale of I to VI. SAIL I represents the lowest residual risk after mitigations are applied; SAIL VI represents the highest. BRLOS operations in segregated or sparsely populated corridors with robust contingency procedures typically attract SAIL III or IV. BRLOS operations over populated areas, near aerodromes, or with complex C2 architectures can reach SAIL V or VI, triggering the most demanding assurance and integrity requirements. Operators and brokers should consult CAP 722 and the CAA's published SORA guidance to understand which SAIL level applies to a specific operation before approaching underwriters.

Beyond radio line of sight is a distinct sub-category of BVLOS. Where standard BVLOS retains a direct radio command link, BRLOS missions rely on satellite datalinks, cellular networks, or mesh relay nodes. The CAA treats the loss of command-link integrity as a critical hazard, and any Operational Authorisation for BRLOS work will specify the contingency procedures — typically an automated return-to-home or controlled descent — that must be demonstrated before the authorisation is granted. Underwriters will ask to see the authorisation document and the associated Operations Manual as part of the submission package.

Operators based in Northern Ireland should seek specific confirmation from the CAA regarding the precise regulatory framework applicable to their operations. The post-Brexit position for Northern Ireland is nuanced and should not be treated as settled without direct CAA guidance. Brokers should flag the jurisdiction at submission and ensure the underwriter is aware, rather than assuming the GB framework applies without qualification.

What the Hull Policy Must Cover for BRLOS Missions

A hull policy written for BRLOS operations needs to address loss or damage scenarios that do not arise in VLOS work. The most significant is a datalink failure leading to a fly-away or an uncontrolled descent outside the operator's visual range. Standard aviation hull wordings often contain exclusions for loss of control where the operator cannot confirm the aircraft's position — a clause that can void cover on the most common BRLOS loss scenario. Brokers should request manuscript wording or a specific endorsement confirming that datalink interruption leading to hull loss is a covered peril.

Autonomous or semi-autonomous mission execution introduces a second hull exposure: software-commanded manoeuvres that result in a collision or ground strike without any pilot input at the moment of loss. Some market wordings exclude losses attributable to autonomous navigation errors unless the operator can demonstrate the software was type-approved or tested to a defined standard. Where detect-and-avoid systems are fitted — increasingly a CAA requirement at higher SAIL levels — the policy should confirm whether sensor malfunction causing a collision is covered under hull or whether it falls to a product liability exclusion. Deductibles typically rise on autonomous operations, reflecting the reduced pilot intervention available to prevent or mitigate a loss.

Payload coverage deserves separate attention on BRLOS programmes. Survey sensors, LiDAR units, and communications relay equipment carried on BRLOS platforms often represent a significant proportion of the total insured value. Brokers should confirm whether payload is included within the hull sum insured or scheduled separately, and whether the policy responds to payload loss during an automated emergency landing outside the planned operating area.

Brokers reviewing standard aviation hull wordings for BRLOS suitability should pay particular attention to the following exclusion categories, which are commonly found in off-the-shelf wordings and frequently require amendment or endorsement for BRLOS risks.

• 'Loss of control' exclusions — check whether these apply where the pilot cannot visually or electronically confirm aircraft position at the moment of loss
• 'Unmanned aircraft' sub-limits — some aviation hull wordings impose a sub-limit on UAS losses that may be inadequate for high-value BRLOS platforms
• Autonomous navigation error exclusions — verify these do not void cover for software-commanded manoeuvres during BRLOS mission execution
• Detect-and-avoid sensor failure — confirm whether this is treated as a hull peril or redirected to a product liability exclusion
• Geographic limits — ensure the policy territory matches the full authorised operating area, including relay node and ground control station locations
• Payload exclusions — confirm whether payload loss during an automated emergency landing is covered or excluded as a consequential loss

Third-Party Liability: Statutory Floor, SORA Ground Risk, and C2 Chain

Third-party liability insurance for commercial drone operations in GB is required under the Air Navigation Order. The mandatory insurance obligation is triggered at a maximum take-off mass of 20 kg: operators of unmanned aircraft at or above this threshold must hold third-party liability cover. For BRLOS operations, the aircraft involved will almost always meet or exceed this threshold, so the statutory floor applies as a baseline. However, the regulatory minimum is rarely the binding constraint on a BRLOS programme — contractual requirements from infrastructure clients, landowners, or airspace authorities typically demand limits well above the statutory floor. Limits are quoted in GBP on GB-domiciled programmes; brokers placing cross-border operations should confirm the currency and jurisdiction of the liability section with the underwriter.

Ground risk is the dominant liability exposure on BRLOS missions. SORA's ground risk class is determined by the operating environment — controlled versus uncontrolled airspace, populated versus sparsely populated areas — and the CAA's Operational Authorisation will reflect the mitigations the operator has accepted. Underwriters will map the authorised operating area against the SORA ground risk class and SAIL level when setting liability terms. Operations at SAIL V or VI over or near populated areas will attract more restrictive conditions and higher minimum limits than equivalent operations in segregated corridors at SAIL III or IV.

Command-and-control infrastructure introduces a liability dimension that is absent from VLOS work. If a ground control station, relay aircraft, or cellular network node contributes to a loss event, questions of contributory negligence and indemnity chain become complex. Brokers should establish at submission whether the operator owns and operates all elements of the C2 chain or whether third-party infrastructure providers are involved, and whether those providers carry their own liability cover that could be called upon before the drone operator's policy responds.

Underwriting Information: What to Prepare Before Submission

BRLOS submissions require more supporting documentation than standard commercial drone placements. Underwriters at a specialist MGA will not be able to quote on the basis of a completed proposal form alone. The core documents are the CAA Operational Authorisation, the Operations Manual (including the emergency response procedures for datalink loss), and the aircraft's technical specification confirming the C2 architecture and any detect-and-avoid fitment. The SORA Safety Case, or a summary of the SAIL determination, should be included where available — it materially accelerates the underwriting review.

Pilot qualification records matter more on BRLOS programmes than on VLOS work because the CAA's Operational Authorisation will specify the competency requirements for remote pilots and, where applicable, for the observers or ground crew supporting the operation. Underwriters will want to see that the operator's training and currency records align with what the authorisation requires. Any deviation — for example, a pilot who has not completed the specific BRLOS type training referenced in the Operations Manual — is a material fact that must be disclosed.

Loss history should be presented in full, including incidents that did not result in a claim. A datalink anomaly that triggered an automated emergency landing but caused no damage is still relevant underwriting information on a BRLOS programme because it speaks to the reliability of the C2 system and the operator's incident reporting culture. Underwriters who specialise in this class will ask for it; brokers who surface it proactively build credibility and typically achieve better terms.

• CAA Operational Authorisation (current, with all conditions and limitations)
• Operations Manual, including C2 failure contingency procedures
• SORA Safety Case or SAIL determination summary
• Aircraft technical specification and C2 architecture diagram
• Detect-and-avoid system documentation if fitted
• Pilot qualification and currency records for all authorised remote pilots
• Five-year loss and incident history, including near-misses and datalink anomalies
• Details of any third-party C2 infrastructure providers and their insurance arrangements

Broker Workflow: From Submission to Bind

Once a broker has assembled the full submission package, the workflow at a specialist MGA follows a defined sequence. On receipt of a complete submission — proposal form, CAA Operational Authorisation, Operations Manual, aircraft schedule, pilot records, and loss history — the underwriting team will typically issue an indicative terms letter within a small number of working days. Indicative terms confirm the coverage structure, key conditions, and the information still required to move to a formal quote; they are not a binding offer.

The formal quote stage follows once any outstanding technical queries are resolved — commonly around C2 architecture details, SAIL level confirmation, or payload valuation. Formal quote to bind can be completed within a further short working-day window provided the broker returns signed acceptance and any outstanding documentation promptly. Brokers with delegated authority arrangements should confirm at the outset whether their binding authority extends to BRLOS risks or whether the risk must be referred to the MGA's underwriting team; most standard drone binding authorities exclude BRLOS as a referred class.

Premiums scale with hull value and payload value, the MTOM profile of the fleet, the SAIL levels authorised under the Operational Authorisation, and the aggregate BRLOS flight hours planned for the period. Underwriters will typically want a mid-term review mechanism if the operator materially changes the operating area, obtains an amended authorisation, or adds aircraft that alter the risk profile. Brokers should build this review trigger into the programme structure at inception rather than treating it as an optional condition.

Programme Structure: Annual, Fleet, and Project-Specific Options

Commercial operators running regular BRLOS missions — pipeline inspection corridors, infrastructure surveys, beyond-horizon delivery trials — are best served by an annual programme that covers all authorised aircraft and operating areas. The programme should be structured to reflect the SAIL levels authorised for each aircraft and operating area, with the liability section sized to meet both the statutory floor and any contractual minimums imposed by clients or airspace authorities.

Project-specific cover suits operators who hold a standard annual VLOS policy and are seeking a one-time or short-term BRLOS authorisation for a defined project. The project policy sits alongside the annual programme and responds only to the BRLOS exposures; brokers should confirm that the two policies do not create a gap or an overlap on the liability side, particularly where the aircraft transitions between VLOS and BRLOS phases within a single flight.

Fleet programmes covering mixed VLOS and BRLOS operations require careful scheduling. Each aircraft should be listed with its authorised operating categories, and the policy should confirm that the BRLOS extensions apply only to aircraft and operations covered by a valid CAA Operational Authorisation. This protects both the operator and the insurer: it prevents inadvertent cover for unauthorised BRLOS activity while ensuring that authorised operations are not inadvertently excluded by a VLOS-only fleet endorsement.

Frequently asked questions

Does a standard commercial drone policy cover BVLOS and BRLOS operations?

Most standard commercial drone policies are written for Open or Specific category VLOS operations and contain exclusions or conditions that are not compatible with BVLOS or BRLOS missions. Common gaps include 'loss of control' exclusions where the pilot cannot visually confirm the aircraft's position, 'unmanned aircraft' sub-limits that may be inadequate for high-value BRLOS platforms, and limitations on autonomous navigation errors. A specialist BRLOS policy or a specific endorsement to an existing programme is required to address these exposures properly. Brokers should review the wording against the checklist in the hull section above before advising a client that their existing policy is adequate.

What CAA permissions must an operator hold before BRLOS cover can be placed?

In Great Britain, BRLOS operations require a Specific category Operational Authorisation from the CAA under UK Regulation 2019/947 (as retained and amended in GB law). The authorisation will reference the SORA risk assessment methodology, specify the SAIL level (on a scale of I to VI), define the permitted operating area, describe the C2 architecture, and set out the contingency procedures for datalink loss. Operators should also consult CAP 722, the CAA's primary published guidance for Safety Case preparation. Underwriters will require a copy of the current authorisation before binding cover. Operations conducted without a valid authorisation are not insurable under a compliant programme.

How does the broker submission process work, and how long does it take?

Brokers should assemble the CAA Operational Authorisation, Operations Manual, SORA Safety Case or SAIL determination summary, aircraft technical specification, pilot qualification records, and a five-year loss and incident history before approaching the MGA. A completed proposal form alone is insufficient for BRLOS risks. On receipt of a complete submission, a specialist MGA can typically issue an indicative terms letter within a small number of working days. Formal quote follows once any outstanding technical queries are resolved, and bind can be completed within a further short working-day window on return of signed acceptance and outstanding documentation. Brokers should confirm at the outset whether their delegated authority covers BRLOS operations or whether the risk must be referred to the MGA's underwriting team.

What triggers a mid-term notification obligation under a BRLOS policy?

Material changes that must be notified mid-term typically include: obtaining a new or amended CAA Operational Authorisation that changes the operating area, SAIL level, or C2 architecture; adding aircraft to the fleet that will operate under the BRLOS authorisation; a change in the remote pilot team that affects the qualifications specified in the authorisation; and any datalink incident or hull loss, whether or not a claim is made. Brokers should review the notification conditions in the policy wording with the operator at inception and build a notification protocol into the operator's safety management system.

Is third-party liability cover for BRLOS operations required by law in GB?

Yes. The Air Navigation Order requires operators of unmanned aircraft at or above 20 kg maximum take-off mass to hold third-party liability insurance. BRLOS platforms will almost always meet or exceed this threshold, so the statutory obligation applies. The CAA's Operational Authorisation may also specify minimum liability requirements as a condition of the authorisation itself, and infrastructure clients or landowners will typically impose contractual minimums above the statutory floor. Operators should check all three sources — the ANO threshold, the authorisation conditions, and any contractual requirements — when determining the minimum limit to place.

Can a BRLOS policy cover operations in multiple countries?

Geographic scope is a key policy condition on any BRLOS programme. A GB-domiciled policy will typically cover operations within GB airspace by default. Coverage for operations in EU member states or other jurisdictions requires a specific territorial extension, assessed case by case. In each territory, the operator must hold the host-country equivalent of a Specific category Operational Authorisation from the relevant national aviation authority before cover can respond. Brokers placing cross-border programmes should confirm the territorial limits, the regulatory compliance conditions, and the currency of the liability section with the underwriter at inception.