Drone Insurance for ConOps Submission UK

Why Insurance Is a ConOps Gating Requirement

Under the UK Specific category framework, operators cannot fly without an Operational Authorisation granted by the Civil Aviation Authority. The ConOps is the primary document the CAA uses to assess risk, and it must address how third-party liability exposure is managed. Insurance is the accepted mechanism for that management. A ConOps that references cover which has not been formally bound — or which carries exclusions that contradict the stated operational envelope — will draw a Regulatory Query that stalls the authorisation clock.

The legal baseline for third-party liability is set by UK Regulation (EU) 2018/1139 as retained in domestic law, supplemented by the Air Navigation Order 2016 and the specific provisions of CAP 722 and CAP 722C. These instruments do not prescribe a single minimum limit for Specific-category operations in the way that Open-category hobby thresholds are defined, but they do require that cover is proportionate to the risk class of the operation. Underwriters and brokers therefore need to read the ConOps itself — particularly the SORA-derived Ground Risk Class and Air Risk Class assessments — before recommending a limit structure.

Operators who use a Predefined Risk Assessment (PDRA) route rather than a full SORA still need insurance evidence. PDRAs narrow the operational parameters but do not remove the liability obligation. The policy must reflect the PDRA identifier and the associated operational constraints, or the CAA may treat the cover as non-compliant with the authorisation being sought.

What the Policy Document Must Contain

The CAA does not publish a mandatory policy template, but its authorisation reviewers look for specific elements when they examine insurance evidence. A certificate of insurance alone is rarely sufficient for a Specific-category submission. Operators should request a policy schedule and, where the operation involves novel or elevated risk, a copy of the relevant endorsements.

The named insured must match the operator entity on the ConOps exactly. A mismatch between a trading name and a registered company name is one of the most common causes of a Regulatory Query at the insurance-evidence stage. Brokers should confirm the legal entity name before binding and ensure the schedule reflects it without abbreviation.

The territorial scope must cover Great Britain and, where relevant, Northern Ireland, UK territorial waters, and any offshore or cross-border segments described in the ConOps. Operations that extend into controlled airspace or that involve flights over congested areas require the policy to be explicit about those environments — a standard open-air exclusion or an unendorsed congested-area exclusion will create a gap that the CAA will identify.

Limits are quoted in GBP for most UK programmes. The limit of indemnity should be set by reference to the Ground Risk Class and Air Risk Class outputs from the SORA or PDRA, not by reference to what the operator paid for the aircraft. Hull value and payload value inform the hull section; the liability limit is driven by exposure to third parties on the ground and in the air.

• Named insured matches the CAA operator registration entity precisely
• Territorial scope explicitly covers the operational area in the ConOps
• Third-party liability limit aligned to SORA or PDRA risk class output
• No unendorsed exclusions that contradict the stated operational envelope
• Policy period covers the anticipated Operational Authorisation duration
• Any BVLOS, autonomous, or beyond-visual-line-of-sight endorsements attached where applicable

Hull and Payload Cover in a ConOps Context

Hull insurance is not a CAA requirement for ConOps submission, but it is commercially prudent for any operation where the aircraft or payload carries significant value. More importantly, hull cover affects the overall programme structure: underwriters writing third-party liability on high-value BVLOS platforms will often require hull cover to be placed concurrently, because the hull underwriter's loss-prevention requirements provide a secondary risk-management layer.

Payload cover deserves separate attention in ConOps submissions that involve sensor packages, survey equipment, or delivery cargo. The ConOps should describe the payload category, and the insurance schedule should reflect it. A payload exclusion on a survey programme, or a cargo liability gap on a delivery operation, creates an uninsured exposure that may also indicate to the CAA that the operator has not fully assessed the consequence of a payload-related incident.

Premiums scale with hull value and BVLOS exposure. Operators running autonomous or highly automated missions should expect underwriters to ask detailed questions about redundancy systems, geofencing, detect-and-avoid capability, and the qualifications of the remote pilot or flight supervisor. These questions are not bureaucratic — they directly inform the risk class the underwriter assigns and therefore the terms available.

BVLOS Operations and Elevated Underwriting Scrutiny

Beyond Visual Line of Sight operations sit at the highest end of the Specific-category risk spectrum and, in some configurations, approach the Certified category. The CAA's BVLOS framework, developed through its BVLOS Industry Action Group outputs and reflected in CAP 722C, requires operators to demonstrate a comprehensive safety case. Insurance underwriters mirror this scrutiny: a BVLOS submission without a mature safety case will struggle to attract competitive terms, and some markets will decline to quote entirely.

Deductibles typically rise on autonomous operations compared with manually piloted VLOS flights. Underwriters price the reduced human-in-the-loop factor and the increased consequence severity of a loss event. Brokers placing BVLOS programmes should present the full ConOps, the SORA output, the detect-and-avoid solution, and any relevant airspace integration agreements to underwriters at first submission rather than drip-feeding information through the negotiation.

Operators seeking an Operational Authorisation for BVLOS should engage their broker before the ConOps is finalised, not after. The insurance terms available — particularly any operational restrictions in the policy endorsements — may need to be reflected back into the ConOps to ensure the two documents are consistent. A ConOps that describes a capability the policy excludes creates a compliance gap that neither the CAA nor the underwriter will accept.

Broker Workflow: From ConOps Draft to Bound Cover

The most efficient workflow begins with the broker receiving a draft ConOps alongside the standard risk submission. The ConOps provides the underwriter with the operational envelope, the risk class assessment, the mitigations in place, and the crew qualifications — information that would otherwise require a lengthy supplementary questionnaire. Brokers who submit a ConOps with their first approach to market typically receive faster and more accurate indicative terms.

Indicative terms should be reviewed against the ConOps before the operator submits to the CAA. If the indicative terms contain exclusions or conditions that conflict with the operational scope, those conflicts need to be resolved at the underwriting stage. Attempting to resolve them after the CAA has issued a Regulatory Query adds time pressure and may require a ConOps amendment.

Once terms are agreed, the broker should request a policy schedule and any relevant endorsements in draft before binding. The operator should review the draft schedule against the ConOps checklist above. Binding should be timed so that the policy inception date aligns with the anticipated Operational Authorisation start date — a policy that expires before the authorisation period ends will require a mid-term renewal that creates an unnecessary compliance event.

For fleet operators or operators running multiple ConOps simultaneously, a fleet or blanket programme may be appropriate. Underwriters can structure these to cover multiple aircraft and multiple operational envelopes under a single policy, with endorsements that map individual aircraft registrations to specific ConOps authorisations. This approach reduces administrative burden but requires careful schedule management to ensure each authorisation is correctly reflected.

Regulatory Triggers That Require Policy Updates

An Operational Authorisation is not static. The CAA may impose conditions that change over the authorisation period, and operators who modify their operations — new aircraft type, expanded geographic area, change in payload, move from VLOS to BVLOS — must assess whether the change triggers a ConOps amendment and, if so, whether the insurance policy requires a corresponding endorsement.

Material changes to the operation that are not notified to the underwriter can void cover at the point of a claim. The duty of fair presentation under the Insurance Act 2015 requires the operator and broker to disclose all material facts at inception and to notify the insurer of material changes during the policy period. A change that the CAA would treat as requiring a ConOps amendment is almost certainly a material change for insurance purposes.

Operators who hold a General PDRA authorisation and subsequently seek a Specific authorisation for a higher-risk operation should treat the new authorisation as a new insurance placement, not a mid-term endorsement to an existing policy. The risk profile changes sufficiently that underwriters will want to assess the new operation on its own terms.

• New aircraft type or significant change in MTOM
• Expansion of operational area into controlled airspace or congested areas
• Change from VLOS to BVLOS or introduction of autonomous flight modes
• Addition of new payload categories, particularly hazardous materials
• Change in crew qualifications or remote pilot certification status
• Expiry or amendment of an Air Traffic Management agreement referenced in the ConOps

Frequently asked questions

What insurance evidence does the CAA require for a Specific-category ConOps submission?

The CAA requires evidence that third-party liability cover is in place or conditionally bound and that it is proportionate to the risk class of the operation as assessed through the SORA or applicable PDRA. A certificate of insurance is typically insufficient on its own. Operators should provide a policy schedule confirming the named insured, territorial scope, limit of indemnity, and the absence of exclusions that contradict the operational envelope described in the ConOps.

Does the insurance policy need to reference the specific PDRA or SORA used in the ConOps?

Yes, where the operation is authorised under a named PDRA, the policy or endorsement schedule should reference that PDRA identifier and the associated operational constraints. For full SORA operations, the policy terms should be consistent with the Ground Risk Class and Air Risk Class outputs. Inconsistencies between the ConOps risk assessment and the policy scope are a common source of CAA Regulatory Queries.

Who is eligible to place drone insurance for a ConOps submission?

Any commercial operator registered with the CAA and holding or applying for an Operator ID under the UK drone registration scheme can place a Specific-category programme. The operator entity named on the CAA registration must match the named insured on the policy. Operators using a PDRA route, a full SORA, or seeking a bespoke Operational Authorisation are all eligible, though the underwriting information required and the terms available will differ based on the risk class and operational complexity.

How should a broker present a BVLOS operation to the insurance market?

Brokers should submit the full ConOps draft, the SORA output including Ground Risk Class and Air Risk Class assessments, details of the detect-and-avoid solution, airspace integration agreements, crew qualifications, and the aircraft technical specifications at first approach to market. Presenting this information upfront rather than responding to underwriter questions piecemeal produces faster indicative terms and reduces the risk of exclusions being applied due to incomplete information.

What happens to the insurance policy if the operator amends the ConOps after the Operational Authorisation is granted?

Any amendment to the ConOps that changes the operational envelope — new aircraft, expanded area, change in flight mode, new payload category — is likely to constitute a material change for insurance purposes under the Insurance Act 2015. The operator must notify the broker, who must in turn notify the underwriter. Failure to do so can void cover at the point of a claim. If the CAA requires a ConOps amendment, treat it as an automatic trigger to review the insurance schedule.

Can a single policy cover multiple ConOps authorisations for a fleet operator?

Yes. Underwriters can structure fleet or blanket programmes that cover multiple aircraft and multiple operational envelopes under a single policy, with endorsements mapping individual aircraft registrations to specific Operational Authorisations. This reduces administrative burden for operators running several concurrent ConOps. However, the schedule must be maintained carefully to ensure each authorisation is correctly reflected and that no aircraft or operation falls outside the endorsed scope.