Drones over UK prisons stopped being a curiosity years ago. This guide collects what is publicly known about the scale of the problem, what detection technology can and cannot do about it, and how we think a prison should approach its first deployment — with the honest caveats in place from the start.
The scale, in numbers we can source
The UK government has reported 1,712 drone incidents at prisons in a single year — a 43% rise on the previous period — covering sightings, disruptions and confirmed contraband attempts. (Source: GOV.UK prison drone statistics; vendor- and government-reported, checked September 2026.) Behind the number sits a simple economics problem: a drone can deliver contraband worth thousands of pounds in a thirty-second hover, and the alternative — corrupted staff or elaborate smuggling — costs more and carries more risk for the criminals.
What detection can actually see
A prison is a mixed-threat airspace, and that is the crux. Machines flown by organised groups are often home-built FPV quads: no Remote ID broadcast, no registration, nothing a standard receiver can hear. Consumer drones doing opportunistic flights — photography, curiosity — usually do broadcast. Our working numbers, all vendor-reported and documented on the receiver comparison: Remote ID receivers start around $129 per node; RF-spectrum sensors, which hear the FPV traffic, start around $3,500. Radar exists for full coverage and costs an order of magnitude more.
How we evaluated approaches
We have not installed detection at a prison ourselves — our role is selection advisory, and this guide is a synthesis of published incident data, vendor documentation and the survey discipline described in our site survey checklist. Everything we recommend below is buildable by an in-house team; the pilot criteria are the same ones we would accept in a procurement.
A staged deployment that holds up
- Phase 1 — baseline (weeks 1–4): one RID receiver on the main approach, logging 24/7. Cost: low. Purpose: learn what your airspace actually contains — most sites are surprised.
- Phase 2 — RF layer (months 2–3): add RF-spectrum monitoring on the approach corridors if the baseline shows silent traffic or if the threat assessment says it will.
- Phase 3 — response integration: alerts into the existing control room workflow, correlation across nodes, and a documented protocol for what happens on a confirmed detection.
- Phase 4 — validation: an authorised walk-test with a known drone on a planned grid, detection logged against GPS truth, gaps on the map. No deployment is “done” without it.
The failure modes to design out
Detections without a response protocol become noise within weeks. Systems bought on coverage promises collapse at the first wall. Budgets that cover hardware but skip validation leave you unable to prove the system works on the day it matters. And a procurement that ignores the silent-FPV problem — because a datasheet said “drone detection” — is the most expensive failure of all, because it feels solved until the night it is not.
Where to go next: our prison detection page carries the full scenario breakdown, the deployment guide covers siting and validation, and the free screening is the fastest way to test our judgement before any money moves.
Content last reviewed: 2026-09-11. Sources: GOV.UK prison incident statistics (1,712 / +43%); vendor documentation, checked September 2026. Not legal advice.