Public Body Drone Insurance UK: Police, MoD & Sub-Contractors

Why public-body operations are a distinct insurance class

Police forces, the MoD, and their supply chains do not operate drones under the same risk profile as a commercial aerial-photography firm. Operational environments routinely include congested urban airspace, night-vision BVLOS sorties, payload carriage (thermal, LiDAR, or specialist sensors), and flights over or near critical national infrastructure. Each of those factors shifts the CAA risk classification upward and, in turn, the coverage requirements that a broker must address.

Under the UK Drone and Model Aircraft Code and the Air Navigation Order 2016 (as amended), operators in the CAA's Specific category — which covers the majority of professional public-body and sub-contractor missions — must hold a valid Operational Authorisation from the CAA. That authorisation does not itself mandate a minimum insurance limit, but it does require the operator to demonstrate that third-party liability cover is in place commensurate with the risk. For public-body contracts, the procuring authority almost always specifies a minimum limit in GBP within the contract schedule, and that figure routinely exceeds what a standard Open-category policy provides.

The MoD additionally operates under Defence Infrastructure Organisation (DIO) and JSP frameworks that impose their own airworthiness and insurance attestation requirements on contracted operators. A sub-contractor who holds a CAA Operational Authorisation but cannot produce an insurance certificate that satisfies the DIO schedule will be stood down before the first sortie. Brokers placing these programmes need to understand both the CAA layer and the procurement layer simultaneously.

CAA category framework and the coverage triggers it creates

The CAA's three-tier framework — Open, Specific, Certified — determines the regulatory obligations that attach to an operation, and those obligations cascade directly into insurance requirements. Open-category operations (sub-250 g or within the A1/A2/A3 subcategories) carry lighter regulatory burdens, but public-body missions almost never remain in Open. The moment an operator flies beyond visual line of sight, carries a payload above the Open-category mass threshold, operates over an assembly of people, or works within a restricted zone, the operation moves into Specific or Certified.

Specific-category operations require a CAA Operational Authorisation or, where a published standard scenario (STS) applies, compliance with that STS. Police air support units and MoD-contracted operators frequently work under bespoke Operational Authorisations that include geographic and operational conditions. Each condition — night operations, BVLOS, flights over crowds — is a coverage trigger that the policy wording must address explicitly. A policy that excludes BVLOS or autonomous flight modes will not respond to the majority of serious public-body missions.

Certified category, which applies to operations over people at scale or with higher-risk aircraft, brings the closest alignment to manned-aviation certification standards. While most current police and MoD drone programmes sit in Specific, the trajectory of the sector — larger platforms, heavier payloads, urban air mobility integration — means brokers should be structuring programmes that can accommodate a Certified-category endorsement without a full re-underwrite.

• Open category: limited applicability to public-body ops; standard third-party liability may suffice for low-risk training sorties only
• Specific category: CAA Operational Authorisation required; policy must align with the authorisation's operational conditions
• Certified category: emerging for heavier or crewed-adjacent ops; requires underwriter familiarity with CAA Certified-category airworthiness expectations
• MoD/DIO contracts: additional attestation layer beyond CAA; insurance certificate must reference the contract schedule's limit and scope
• Police procurement frameworks: often routed through Crown Commercial Service or force-specific standing offer arrangements, each with their own insurance schedule

Sub-contractor liability: where the coverage gap most often appears

The most common coverage failure in public-body drone programmes is not at the prime-contractor level — it is in the sub-contractor chain. A constabulary may engage a prime integrator who in turn deploys a specialist BVLOS operator or a thermal-imaging sub-contractor. The prime's policy may carry adequate limits, but if the sub-contractor's own policy excludes the specific operation type, or if the sub-contractor is not named or scheduled on the prime's policy, a gap exists that neither party's insurer will fill without a dispute.

Brokers placing sub-contractor cover should obtain the prime contract's insurance schedule before binding. The schedule will specify whether the sub-contractor must carry standalone cover or whether they may rely on the prime's policy, and it will state the minimum limit, the required endorsements (typically including public liability, products liability, and professional indemnity for data-processing operations), and any waiver-of-subrogation requirements. Attempting to place cover without that schedule is placing cover blind.

Hull cover for sub-contractor platforms deserves equal attention. Public-body operations often involve expensive specialist payloads — thermal cameras, multi-spectral sensors, LiDAR units — that are not part of the airframe manufacturer's standard configuration. A hull policy that covers the airframe at agreed value but excludes detachable payloads will leave the operator exposed to a significant uninsured loss if the platform is damaged or destroyed on a sortie. Agreed-value hull cover that schedules the payload separately, with a clear definition of what constitutes the insured system, is the appropriate structure.

Operational scenarios that require specific policy endorsements

Night operations are standard for police drone units and are increasingly common in MoD-contracted surveillance work. Many general-aviation drone policies include a daylight-hours restriction as a default condition. Operators and brokers must confirm that the policy either has no such restriction or carries an explicit night-operations endorsement that aligns with the CAA Operational Authorisation's night-flying permission.

BVLOS operations — whether flown with a ground-based observer network, via detect-and-avoid technology, or under a specific CAA BVLOS permission — represent a materially different risk profile from standard VLOS commercial work. Premiums scale with hull value and BVLOS exposure, and deductibles typically rise on autonomous or semi-autonomous operations. The policy wording must confirm that BVLOS is not an excluded mode of operation and that the insurer has been notified of the specific BVLOS methodology.

Data-capture operations for law enforcement or defence purposes introduce a professional indemnity dimension that pure hull-and-liability programmes do not address. If the operator is contracted to deliver processed imagery, geospatial data, or surveillance outputs, and that data is used in an operational decision that subsequently results in a claim, the liability may fall on the data provider rather than the platform operator. A combined hull, liability, and professional indemnity programme — structured as a single schedule rather than three separate policies — reduces the risk of coverage disputes between insurers.

• Night operations: confirm no daylight restriction in policy conditions; obtain explicit endorsement if required
• BVLOS: verify the specific BVLOS methodology is disclosed to underwriters and not excluded
• Autonomous or AI-assisted flight: disclose to underwriters; some wordings exclude fully autonomous modes
• Payload carriage: schedule detachable payloads separately at agreed value
• Data and surveillance outputs: consider professional indemnity alongside hull and liability
• Flights over critical national infrastructure: notify underwriters; may require specific endorsement or sub-limit review

Broker workflow for placing public-body and sub-contractor programmes

The submission to underwriters should lead with the CAA Operational Authorisation reference number and the operational conditions attached to it. Underwriters writing public-body drone business need to understand the regulatory envelope before they can assess the risk — a submission that omits the OA conditions forces the underwriter to make assumptions that will not favour the operator at claims stage.

Alongside the OA, the broker should provide the prime contract's insurance schedule (or the relevant extract), the platform and payload schedule at agreed values, the operator's safety management system summary, and the incident history for the preceding three years. For MoD-contracted operators, the DIO or JSP compliance attestation should be included where available. This is not a standard commercial drone submission; it is a specialty programme that requires a specialty underwriter.

Policy inception should not be confirmed until the broker has verified that the policy wording responds to each operational condition in the CAA OA and each requirement in the contract schedule. A checklist approach — mapping each OA condition and contract requirement to a specific policy clause or endorsement — is the most reliable way to demonstrate due diligence and to defend the placement if a coverage dispute arises.

Frequently asked questions

Does a police force or MoD unit need commercial drone insurance, or does Crown immunity apply?

Crown immunity does not eliminate the need for insurance in the sub-contractor chain. While a constabulary or MoD unit operating its own platforms under its own authorisation may self-insure through government indemnity arrangements, any private-sector operator — including a specialist sub-contractor embedded in a police or MoD operation — must carry commercial third-party liability cover. The CAA's Specific-category framework requires the operator holding the Operational Authorisation to demonstrate that cover is in place, regardless of who the end client is.

What does a public-body drone policy typically cover, and what is commonly excluded?

A well-structured programme for this sector covers third-party liability (bodily injury and property damage), hull loss or damage at agreed value (including scheduled payloads), and — where the operator delivers data or processed outputs — professional indemnity. Common exclusions to watch for include BVLOS operations, night operations, autonomous flight modes, and flights over restricted or prohibited zones. Each of these exclusions is operationally significant for police and MoD work, and each should be addressed by endorsement or confirmed as not applicable before inception.

How does the CAA Operational Authorisation affect what the insurer will cover?

The Operational Authorisation defines the envelope within which the operator is legally permitted to fly — including geographic limits, operational conditions, and any specific permissions such as BVLOS or night operations. Underwriters writing Specific-category cover will align the policy to that envelope. If an operator flies outside the OA conditions, the insurer may decline to respond to a claim on the basis that the operation was not authorised. Brokers must ensure that the policy wording and the OA conditions are consistent, and that any change to the OA is notified to underwriters promptly.

What information does a broker need to submit a public-body sub-contractor programme?

At minimum: the CAA Operational Authorisation reference and its attached conditions; the prime contract's insurance schedule or the relevant extract specifying limits and required endorsements; a platform and payload schedule with agreed values; a summary of the operator's safety management system; and three years of incident or claims history. For MoD-contracted operators, any DIO or JSP compliance documentation should be included. Submissions that omit the OA conditions or the contract schedule will be treated as incomplete by specialist underwriters.

Are there regulatory triggers that make commercial cover mandatory mid-contract?

Yes. If an operator's scope of work expands during a contract — for example, moving from VLOS daylight operations to BVLOS or night sorties — the CAA Operational Authorisation must be updated to reflect the new conditions. That update is a regulatory trigger that requires the broker to notify underwriters and confirm that the policy responds to the revised operational envelope. Failure to notify can result in a coverage gap for the period between the OA amendment and the policy endorsement. Brokers should build a mid-term review process into any public-body programme for this reason.

Can a sub-contractor rely on the prime contractor's policy rather than holding their own cover?

Only if the prime contract's insurance schedule explicitly permits it and the prime's policy names or schedules the sub-contractor in a way that the insurer will recognise at claims stage. In practice, most public-body procurement frameworks require each operator in the chain to hold standalone cover, because the prime's insurer will seek to subrogate against the sub-contractor if the sub-contractor's negligence caused the loss. A waiver-of-subrogation endorsement on the prime's policy can address this, but it must be specifically requested and confirmed in writing before the sub-contractor begins operations.