Detected, Not Stopped: What a Prison Drone Drop Says About Perimeter Programs
A reported drone delivery into a Quebec prison shows why a detection rate is not a stop rate. Perimeter programs need a measured chain from alert to outcome.
A delivery that exposed a gap
A reported drone delivery at a Quebec correctional facility illustrates the difference between detecting an aircraft and preventing a delivery. The Canadian Press reported that a drone delivered food and alcohol to an inmate at the Regional Reception Centre. A correctional officers' union representative said cameras and counter-drone technology did not capture the intrusion. Correctional Service Canada told the outlet it was implementing physical mitigation measures including nets.
A detection rate is not a stop rate
In its 2024 response to the Correctional Investigator, Correctional Service Canada said its institutions had drone detection systems and that 98 percent of drones were detected among 290 incidents in the first half of 2024. Detection, however, is an alert, not proof that a payload was intercepted. Measures should be evaluated across the full sequence from alert to response and outcome.
Plan the response as a system
For an authorized security operation, identify who receives an alert, who makes the decision, what response is permitted and how it is recorded. Test the process against site-specific conditions and record the time between notification and action. Physical measures, procedures and authorized technology all have a role, but a detection statistic alone cannot measure the complete response.
Any drone operations near an active security site also require coordination with the facility and applicable authorities. A 2025 federal statement describes a limited exemption for correctional employees to conduct jammer-related activities at federal facilities and Quebec provincial facilities. It is not a general authorization for contractors. Operators should coordinate with the site, understand potential interference and brief lost-link procedures.
The record outlasts the incident
A useful incident record identifies what was observed, when an alert was received, who authorized the response and what action followed. Preserve relevant imagery and metadata, separate authorized flights from unrecognized aircraft, and document any coverage limitations.
The practical lesson is to measure detection, response and outcome separately. A security program can then see where its process needs improvement rather than treating an alert as a completed intervention.
Related reading
Continue the thread.
Related posts are pulled from the same primary topic as the current article.
An airport emergency exercise now starts with a paperwork request
Drones have become a normal part of airport emergency exercises. The FAA has now spelled out who requests airspace access, and how far ahead of the drill it has to happen.
Connecticut Wired a Drone Purchasing Rule Into Public Contracts
The October 1 stage of Connecticut's drone act reaches contractors and any purchase made with state or federal money, while the state's 250 foot critical infrastructure rule has been in force for a year.
Drone Delivery's National Shortcut Is Now a Court Case
A multistate petition filed September 28 targets the single environmental document that now stands in for site-by-site review of drone package delivery. Operators should read the noise data clause and start keeping per-site records.