C2 Link Reliability BVLOS Drone Insurance | BVLOS Insure

Why C2 link reliability sits at the centre of BVLOS underwriting

In a standard VLOS operation the pilot's eyes serve as a continuous, low-latency feedback loop. Remove that loop and the command-and-control datalink becomes the only real-time connection between the remote pilot and the aircraft. Any degradation — interference, spectrum congestion, terrain masking, or hardware fault — can render the aircraft uncontrollable within seconds. Underwriters price and structure cover around that single point of failure more than almost any other technical variable.

UK BVLOS operations fall under the CAA's Specific category framework. Operators must hold a valid Operational Authorisation issued under UK Regulation (EU) 2019/947 as retained in UK law, and the CAA's SORA-derived risk methodology explicitly evaluates the robustness of the C2 architecture as part of the Ground Risk Class and Air Risk Class assessment. An underwriter reviewing a BVLOS submission will cross-reference the declared C2 setup against what the CAA has already accepted in the operator's ConOps — inconsistencies between the two documents are a common reason for referral.

The practical consequence is that C2 link reliability is not just a technical specification; it is a compliance artefact. Operators who treat it as the former but not the latter arrive at the insurance market without the documentation underwriters need to confirm that the CAA-accepted risk mitigations are actually in place.

Technical standards underwriters expect to see documented

Underwriters do not typically prescribe a single radio technology or frequency band, but they do require evidence that the chosen solution has been assessed against a recognised standard. For UK operators the most commonly cited frameworks are ETSI EN 303 717 for the radio link itself and, where the operation uses a mobile network, the operator's own link budget analysis demonstrating adequate coverage along the planned route. Submissions that reference only the drone manufacturer's default telemetry system without independent analysis are routinely queried.

Redundancy architecture is the next layer of scrutiny. A single-link C2 system with no fallback is treated very differently from a dual-link setup combining a primary dedicated radio channel with a secondary LTE or satellite path. Underwriters will ask whether the redundancy is active-active or active-standby, what the switchover latency is, and whether the aircraft's lost-link procedure activates before or after the secondary link is declared failed. These are not abstract questions — they map directly to the probability and severity of a loss-of-control event.

Latency and link margin are equally important. A C2 link that is technically available but operating near its minimum acceptable signal level across significant portions of the route introduces a reliability risk that may not appear in a simple coverage map. Operators should be prepared to provide route-specific link margin analysis, not just a general statement that the link has been tested.

• Spectrum authorisation or licence reference (Ofcom assignment or licence-exempt band declaration)
• Link budget analysis covering the full planned route, including worst-case terrain and atmospheric conditions
• Redundancy configuration: primary and secondary link technologies, switchover logic, and latency figures
• Lost-link procedure documented in the ConOps and consistent with the CAA Operational Authorisation
• Evidence of pre-flight link checks and any in-flight monitoring capability
• Maintenance and inspection schedule for C2 hardware, including antenna systems

How the CAA Operational Authorisation shapes the insurance submission

The CAA issues Operational Authorisations under the Specific category after reviewing a SORA-based ConOps. That ConOps will contain a section on the C2 link, including the declared Operational Safety Objectives and any Specific Assurance and Integrity Levels assigned to the communication system. Underwriters treat the CAA-accepted ConOps as the baseline risk document — if the actual equipment or procedures differ from what was submitted to the CAA, the operator is potentially flying outside their authorisation, which is a material fact that must be disclosed.

Brokers placing BVLOS programmes should request a copy of the current Operational Authorisation and the associated ConOps as standard. The C2 section of the ConOps will tell an experienced underwriter more about the operator's risk management maturity than any number of general statements about 'robust communications'. Where the ConOps is redacted for commercial sensitivity, underwriters may accept a summary prepared by a qualified UAS safety consultant, but this adds friction to the placement process.

Operators who are still in the process of obtaining their Operational Authorisation can approach the market for indicative terms, but binding is almost always conditional on the authorisation being granted and the final ConOps being reviewed. Some underwriters will issue a conditional binder; others will not engage until the CAA process is complete. Brokers should clarify this with the market before raising client expectations.

Coverage structure and common exclusions linked to C2 failures

Hull and liability policies for BVLOS operations are typically structured to cover losses arising from the operation as authorised. A C2 link failure that results in a lost-link event and subsequent hull loss will generally be covered if the lost-link procedure was correctly followed and the aircraft behaved as declared in the ConOps. The exclusion risk arises when the failure mode was foreseeable and undisclosed — for example, operating in a known interference environment without declaring it, or using a C2 system that had not been maintained in accordance with the manufacturer's schedule.

Underwriters frequently attach conditions rather than exclusions to C2-related risks. A condition might require the operator to conduct a route survey before each flight series, to maintain a log of link quality metrics, or to notify the insurer before extending operations into new geographic areas not covered by the original link budget. Breach of a condition does not automatically void the policy, but it can give the insurer grounds to reduce or refuse a claim where the breach is causally connected to the loss.

Autonomous operations — where the aircraft executes a pre-programmed mission with minimal real-time C2 interaction — introduce a distinct underwriting question. Some underwriters treat reduced C2 dependency as a positive risk factor; others view it as increasing the severity of any failure because there is no pilot input to interrupt a developing incident. Deductibles and sub-limits on autonomous BVLOS operations vary accordingly, and brokers should not assume that a policy written for piloted BVLOS will respond in the same way to an autonomous mission.

Preparing a submission that will bind first time

The single most effective thing a broker can do is front-load the C2 documentation. A submission that arrives with the Operational Authorisation, the ConOps C2 section, a route-specific link budget, and a clear description of the redundancy architecture will move through underwriting significantly faster than one that requires multiple rounds of questions. Underwriters working on BVLOS risks are not generalists — they will read the technical documents, and gaps will be identified.

Operators should also be prepared to describe their C2 failure history honestly. A record of minor link dropouts that were handled correctly by the lost-link procedure is not a disqualifying factor — it is evidence that the system works as designed. Concealing a history of C2 incidents is a material non-disclosure that can void cover entirely. The market is more sophisticated than it was even a few years ago, and underwriters are increasingly asking for flight data logs as part of the submission process.

Where an operation involves novel C2 technology — mesh networking, satellite-primary links, or software-defined radio — brokers should engage the underwriter in a pre-submission conversation rather than submitting a standard proposal form. Novel technology is not uninsurable, but it requires a different underwriting process, often involving input from a technical specialist retained by the insurer. Building that time into the placement timeline avoids last-minute delays.

Frequently asked questions

What does a BVLOS hull and liability policy actually cover in relation to C2 link failures?

A correctly structured BVLOS policy covers hull loss and third-party liability arising from the operation as authorised, including losses that result from a C2 link failure provided the declared lost-link procedure was followed and the failure mode was not a foreseeable, undisclosed risk. Coverage can be reduced or declined where the operator was using a C2 system that differed from the one described in the CAA-accepted ConOps, or where maintenance obligations had not been met.

Does my CAA Operational Authorisation need to be in place before I can get BVLOS insurance?

Most underwriters require the Operational Authorisation to be in place before binding, because the CAA-accepted ConOps is the primary risk document they underwrite against. Some markets will issue indicative or conditional terms during the authorisation process, but the final binding is almost always conditional on the authorisation being granted and the ConOps being reviewed. Brokers should confirm this position with the specific underwriter before making commitments to clients.

What documents should a broker include in a BVLOS submission to avoid referral?

At minimum: the current CAA Operational Authorisation, the C2 section of the ConOps, a route-specific link budget analysis, a description of the redundancy architecture including switchover logic and latency, the Ofcom spectrum authorisation or licence-exempt band declaration, and the C2 hardware maintenance schedule. For autonomous operations, include the mission management system documentation and any relevant software assurance evidence. Submissions that arrive without these documents are routinely referred for additional information, which delays binding.

Are there regulatory triggers that require me to notify my insurer about changes to my C2 setup?

Yes. Any change to the C2 system that would require an amendment to your CAA Operational Authorisation — such as switching from a dedicated radio link to a mobile network primary, or extending operations into a new geographic area with a different link budget — is a material change that must be disclosed to your insurer. Operating with an amended C2 setup that has not been notified to both the CAA and your insurer simultaneously risks flying outside your authorisation and outside your policy cover.

How does the underwriting process differ for autonomous BVLOS operations compared to piloted BVLOS?

Autonomous operations are assessed differently because the real-time C2 interaction is reduced or absent during the mission execution phase. Some underwriters view this as reducing the probability of pilot error; others focus on the increased severity risk if the mission management system fails without a pilot able to intervene. The policy structure — including deductibles, sub-limits, and conditions — may differ from a piloted BVLOS programme. Brokers should not assume that an existing piloted BVLOS policy extends automatically to autonomous missions and should seek explicit confirmation from the underwriter.

What happens if my C2 link has experienced dropouts in the past — will that affect my eligibility?

A history of C2 link dropouts that were correctly handled by the lost-link procedure is not automatically disqualifying. Underwriters increasingly request flight data logs as part of the submission, and a well-documented record of minor incidents handled correctly can actually demonstrate risk management maturity. What underwriters treat as a serious concern is undisclosed C2 incidents, particularly those that resulted in uncontrolled flight or near-misses. Full disclosure at submission is essential — material non-disclosure can void cover entirely.