Drone Liability Limits — How Much TPL Should a UK Operator Carry?

Why Drone Liability Limits matters in 2026

Drone Liability Limits sits at the intersection of CAA permissions, contractor procurement and underwriter appetite. The way the UK market has evolved post-Brexit means brokers need clear evidence to bind cover at the limits a tier-one principal will actually accept — typically £5m–£10m TPL with hull and payload structured separately.

For UK operators working on infrastructure, energy or media contracts, drone liability limits is rarely the line item that fails a procurement gate. What fails procurement is the absence of evidence: an OA that doesn't cover the planned mission, or a hull schedule that hasn't been updated since the operator added drones to the fleet.

What underwriters look for

An underwriter pricing a UK risk in this segment is reading three things in order: the operating envelope, the loss history, and the principal's contractual demands. None of these is a surprise; what is a surprise, repeatedly, is how often the submission misses one of them.

• Operating envelope — the OA paragraphs that govern actual missions, not the full document
• Loss history — clean 36-month record, or a clean explanation of what happened
• Contractor demand — the limit and indemnity clauses on the largest contract the operator routinely takes on
• Fleet schedule — every airframe with agreed value, year of manufacture, retrofit notes

Where the wholesale facility helps

UK Drone Insurance operates as a wholesale broker into B+ rated paper that has explicit appetite for drone liability limits. We are not cheaper than retail at the bottom of the market; we are bindable when retail won't extend a quote. That is most often the case for fleets above twelve airframes, BVLOS-rated programmes, and missions outside Coverdrone-style pre-baked templates.

If the placement has run aground at retail, send the operator profile, OA excerpt and fleet schedule via the form below. We come back inside 24 hours with indicative terms or a clear "no, here's why" so you can re-route the case quickly.