BVLOS Detect and Avoid: UK Insurance Implications

What the CAA Expects from DAA in BVLOS Operations

Under the UK's Open / Specific / Certified category framework, any operation beyond visual line of sight that cannot be contained within a segregated or controlled volume will typically require a Specific category Operational Authorisation (OpA) from the CAA. The safety case submitted for that authorisation must demonstrate that the UAS can detect conflicting traffic — manned and unmanned — and initiate an appropriate avoidance response without relying on a remote pilot's direct visual observation.

The CAA's Operational Safety Case guidance draws heavily on the SORA (Specific Operations Risk Assessment) methodology. SORA assigns an Air Risk Class (ARC) to the operation based on airspace type and traffic density, and then requires the operator to demonstrate that the DAA solution achieves a sufficient level of robustness to bring residual air risk to an acceptable level. The higher the ARC, the more demanding the DAA performance evidence the CAA will expect to see.

Operators should note that 'detect and avoid' in the regulatory sense encompasses both the detection element — radar, ADS-B In, FLARM, acoustic sensors, or camera-based systems — and the avoid element, which may be cooperative (relying on other aircraft broadcasting position) or non-cooperative (detecting non-broadcasting traffic). The CAA does not currently mandate a single technology standard, but the chosen solution must be justified within the safety case and, critically, must be accurately described to insurers.

How DAA Capability Shapes the Underwriting Assessment

Underwriters treating a BVLOS submission will examine the DAA architecture as part of the overall risk profile, alongside operator experience, maintenance records, and the operational environment. A well-documented, independently validated DAA system that has been accepted by the CAA as part of a live OpA provides underwriters with a degree of regulatory endorsement that a prototype or self-certified solution does not.

The distinction between cooperative and non-cooperative DAA matters to liability underwriters in particular. An operation that relies solely on ADS-B In or FLARM will only detect aircraft that are actively broadcasting. If a mid-air conflict occurs with a non-broadcasting aircraft — a glider, a microlight, or a military fast jet operating under radio silence — the question of whether the operator's DAA solution was fit for the declared airspace environment will be central to any coverage dispute. Brokers should ensure the submission clearly maps the DAA sensor suite to the traffic types present in the operational area.

Hull underwriters will assess DAA reliability as a factor in the probability of a loss event. Premiums scale with hull value and BVLOS exposure, but the quality and redundancy of the DAA system can influence how underwriters view the frequency component of that exposure. An aircraft with a single-point-of-failure DAA architecture will attract more scrutiny than one with layered, dissimilar sensor inputs and an independent flight termination system.

Deductibles typically rise on autonomous operations where the remote pilot's ability to intervene is limited. If the DAA system is operating in an automated avoid mode — executing manoeuvres without real-time pilot command — underwriters will want to understand the logic, the failure modes, and whether the system has been flight-tested to the performance envelope declared in the OpA.

Material Facts, Disclosure, and Policy Conditions

UK insurance law places a duty of fair presentation on the insured under the Insurance Act 2015. For a BVLOS operator, the DAA system specification is almost certainly a material fact: a prudent insurer would want to know the sensor types, the detection range, the avoidance logic, and whether the system has been independently validated. Failure to disclose a material change — for example, swapping a radar-based DAA for a camera-only system between renewal cycles — can give the insurer grounds to avoid the policy or reduce a claim payment.

Brokers should build DAA disclosure into their standard BVLOS submission template. This means collecting the system make and model, the operational design domain for which it has been validated, any CAA acceptance documentation, and the maintenance and software update schedule. Where the DAA system is bespoke or in development, a technical summary from the manufacturer or the operator's airworthiness team should accompany the submission.

Policy wordings for BVLOS programmes will often include a condition requiring the operator to maintain the aircraft and its systems in the configuration described at inception. A DAA software update that materially changes avoidance behaviour, or a sensor that is temporarily disabled for a specific flight, may trigger a notification obligation. Operators and brokers should review these conditions carefully and establish a process for mid-term notifications.

Third-Party Liability Limits and Airspace Risk

The Air Navigation Order 2016, as retained and amended in UK law, requires that UAS operations carry third-party liability insurance meeting minimum limits set by reference to the aircraft's maximum take-off mass. Limits are quoted in GBP for UK-registered operations, though operators flying internationally under bilateral arrangements may need to satisfy requirements expressed in EUR, USD, or AED depending on the jurisdiction.

For BVLOS operations, the relevant liability exposure extends beyond ground third-party risk to include the risk of a mid-air collision with a manned aircraft. This is a qualitatively different risk from a low-altitude VLOS operation over an open field, and underwriters will price and structure limits accordingly. The adequacy of the DAA system is directly relevant to the probability of that collision event occurring, and a robust, well-documented DAA solution supports the case for competitive limit structures.

Where an operator is flying under a CAA OpA that specifies particular DAA performance requirements as a condition of the authorisation, any deviation from those requirements — even temporarily — may constitute a breach of the OpA. Operating outside the terms of a regulatory authorisation is typically an exclusion trigger in specialty aviation liability wordings. Brokers should ensure operators understand that the insurance and the regulatory authorisation are interdependent: losing one can effectively void the other.

Building a Submission That Underwriters Can Assess

A complete BVLOS submission for a DAA-equipped operation should give underwriters everything they need to assess both the hull and liability exposure without having to request multiple rounds of additional information. Delays in the submission process often trace back to incomplete DAA documentation rather than hull value or operator experience.

The following elements should be included as standard in any BVLOS submission where DAA is a feature of the operation:

Underwriters will also want to understand the operator's incident reporting and safety management system. A mature SMS that includes DAA performance monitoring — logging detection events, near-miss data, and system alerts — demonstrates the kind of operational discipline that supports a favourable underwriting view. Where the operator participates in a CAA-recognised safety reporting scheme, that participation should be noted in the submission.

• CAA Operational Authorisation reference and any DAA-specific conditions attached to it
• DAA system specification: sensor types, detection range, avoidance logic, and operational design domain
• Evidence of independent validation or acceptance testing, including any CAA or third-party airworthiness review
• Software version control records and the process for managing updates
• Maintenance schedule and the qualifications of personnel responsible for DAA system upkeep
• Details of any automated avoidance modes and the conditions under which they activate
• Operational area description mapped to the Air Risk Class assigned in the SORA-based safety case

Emerging Standards and the Road to Certified Category Operations

The UK and EU are both developing technical standards for DAA in non-segregated airspace, with EASA's work on EUROCAE ED-269 and related standards feeding into the longer-term framework for Certified category UAS operations. Although the UK has diverged from EU aviation regulation post-Brexit, the CAA has indicated that it will continue to monitor and draw on international standards development, including ICAO's work on UAS integration.

For operators and brokers, the practical implication is that DAA standards are likely to become more prescriptive over time. Systems that meet today's OpA conditions may require upgrade or re-validation as standards mature. Insurance programmes should be structured with this trajectory in mind: multi-year hull agreements should include provisions for notifying insurers of system upgrades, and liability programmes should be reviewed annually against the current regulatory baseline.

Operators planning to scale from Specific to Certified category operations — for example, those targeting urban air mobility or large-payload logistics corridors — should engage their broker and underwriter early in the development process. The insurance market for Certified category BVLOS is still forming, and early engagement allows underwriters to track the development of the DAA solution alongside the regulatory approval process, rather than receiving a completed submission for a novel risk with no prior underwriting history.

Frequently asked questions

Does my detect-and-avoid system need CAA approval before I can obtain BVLOS insurance?

Not in every case, but CAA acceptance of your DAA solution as part of a Specific category Operational Authorisation significantly strengthens your submission. Underwriters can consider operations where the OpA is in progress, but they will want to see the safety case and DAA validation evidence. Operating BVLOS without a valid OpA is likely to trigger an exclusion in any specialty aviation policy.

What does a BVLOS hull and liability policy typically cover in relation to DAA system failure?

Coverage scope varies by wording, but most specialty BVLOS policies cover physical loss or damage to the aircraft and third-party bodily injury and property damage arising from the operation. A DAA system failure that leads to a collision would generally fall within the scope of a liability claim, subject to the policy conditions being met. Exclusions commonly apply where the operator has deviated from the configuration or operational limits described at inception, or where the operation was conducted outside the terms of the CAA authorisation.

How should a broker present a BVLOS submission where the DAA system is proprietary or still in development?

Transparency is essential. Provide a technical summary from the manufacturer or the operator's airworthiness team, describe the validation testing completed to date, and be clear about what regulatory acceptance has and has not yet been obtained. Underwriters can work with development-stage technology, but they need sufficient information to assess the risk. Incomplete or vague submissions typically result in either declination or restrictive conditions that could have been avoided with fuller disclosure.

What regulatory triggers should operators watch for that would require them to notify their insurer mid-term?

Any change that is material to the risk as described at inception should be notified promptly. For DAA-equipped BVLOS operations, this includes: a change to the DAA sensor suite or avoidance logic; a software update that materially alters system behaviour; suspension or amendment of the CAA Operational Authorisation; expansion of the operational area into a higher Air Risk Class; and any incident in which the DAA system failed to perform as expected. Most specialty wordings include a notification condition — brokers should ensure operators have a process for identifying and acting on these triggers.

Are there differences in how insurers treat cooperative versus non-cooperative DAA systems?

Yes. Cooperative systems — those relying on ADS-B In, FLARM, or similar broadcast-dependent technologies — only detect aircraft that are actively transmitting. Underwriters will assess whether the operational airspace contains non-broadcasting traffic types such as gliders, microlights, or certain military aircraft. Where non-cooperative detection capability is absent, underwriters may apply additional conditions, restrict the operational area, or adjust the liability limit structure. The submission should clearly identify which traffic types the DAA solution is designed to detect and provide evidence that this matches the actual traffic environment.

How does the SORA Air Risk Class assigned to an operation affect the insurance programme structure?

The Air Risk Class reflects the density and type of manned aviation traffic in the operational airspace. A higher ARC indicates greater exposure to mid-air conflict, which flows directly into the liability underwriting assessment. Operations assigned a higher ARC will typically require more robust DAA evidence, may attract higher liability limits as a condition of the OpA, and will receive closer scrutiny on the adequacy of the avoidance logic. Brokers should include the ARC determination and the SORA summary in every submission for Specific category BVLOS operations.