Counter-UAS in Canada

Counter-UAS — C-UAS — is a category name for the sensors, software, and procedures organizations use to know what is flying above them and, in a narrow set of authorized cases, to do something about it. The category grew up around military and federal-agency use cases; over the past decade it has moved into corrections, critical infrastructure, airports, and public venues. In Canada, that shift accelerated with Bill C-15's royal assent on March 26, 2026, which created — for the first time — a defined federal pathway to authorize interdiction beyond a handful of federal agencies.

The category divides cleanly. Detection observes; mitigation acts. In Canadian civil practice today, most deployed C-UAS is detection-only. Mitigation sits behind the Transport Canada authorization framework, and the implementing regulations are still being developed. Read the Bill C-15 pillar.

RF detection. Passive sensors that listen for the control and video links between a drone and its operator. Basic systems detect and direction-find; advanced systems decode the protocol to extract drone model, serial number, pilot location, and home point. RF is the cheapest per unit of coverage and the only layer that produces operator location — which converts an incident into something police can act on while the pilot is still on-scene. Its blind spots: autonomous drones running silent, fibre-tethered drones, and any airframe whose protocol the library does not yet cover.

Radar. Active RF that detects the airframe itself regardless of emissions. Small-drone radars close the autonomous-drone gap RF-only systems leave open, but they are more expensive, they interact with the site's clutter environment (buildings, trees, moving vehicles), and false-alarm tuning becomes a first-class deployment problem.

Electro-optical and infrared cameras. Slew-to-cue cameras cued by RF or radar provide visual confirmation, payload assessment, and evidence video. Without cueing they are near-useless for detection — a human cannot search the sky manually. With cueing they turn an alert into something an operator, and later a court, can evaluate.

Remote ID. Compliant drones broadcast identifiers over Bluetooth or Wi-Fi. Remote ID ingestion is nearly free once other sensors are in place, and it is the fastest way to sort compliant operators (nuisance, hobbyist, contracted survey) from non-compliant ones (contraband, surveillance, hostile). Its blind spot is obvious: bad actors do not broadcast.

Acoustic. Short-range sensing useful in quiet, low-clutter environments (rural corrections, small event footprints). Range is limited and urban noise degrades performance; it is a supplementary layer, not a primary one.

The technology explainer covers each layer in more depth, with the tradeoffs practitioners weigh in real procurements.

A room full of sensors is not a system. The C2 layer — fusion software — is where multi-sensor detections become a single airspace picture, where classification (drone / bird / aircraft / vehicle) happens, where alerts route into your existing security operations, and where the audit trail lives. Buyers underweight this layer routinely and pay for it later, in the form of operators who stop trusting the system by month two.

Two things separate serious C2 from a demo screen: how it handles false alarms (an operations centre that gets fifty bird alerts a night stops looking), and what its evidence output looks like — time-synced track history, decoded identifiers, and correlated video, in a format your counsel and local police can use. If prosecution is a plausible outcome, this is where the case is won or lost.

Every Canadian C-UAS conversation eventually reaches the same question: what can we actually do about it? The answer, before March 2026, was "very little, unless you were a federal agency with specific authority." Bill C-15 changes the second half of that sentence; it does not change the first half for organizations that do not hold an authorization.

Detection is open. Passively sensing and identifying drones does not require a Transport Canada interdiction authorization. Correctional facilities, critical infrastructure operators, airports, and public venues deploy detection today.

Mitigation is authorized-only. Jamming radiocommunication is prohibited under the Radiocommunication Act; interfering with an aircraft in flight is an offence under the Aeronautics Act. Bill C-15 enables Transport Canada to authorize certain entities — anticipated to be law enforcement and similar agencies — to interdict drones that present security risks. The regulations defining who can be authorized and under what conditions are still being developed. Follow the regulation tracker.

For homeowners, private landowners, and organizations without an authorization: detect, document, and report — not jam, not shoot. The long answer is here.

The right first system is the one that matches the threat scenarios you can name in operational terms. "Detect a consumer drone approaching the north perimeter at night in time to execute a ten-minute response procedure" is a scenario a vendor can compete on. "Provide RF detection to 5 km" is a spec sheet you have already lost.

Canadian buyers should encode the legal boundary explicitly: detection-only, unless your organization holds or is actively pursuing a Bill C-15 interdiction authorization. Soliciting mitigation you cannot lawfully operate invites proposals for capability that will sit dark. The RFP checklist covers the twelve sections a serious solicitation should include, from site characterization and cold-weather requirements to demonstration-based evaluation.

The system that fits a correctional facility does not fit an outdoor stadium, and the one that fits a stadium does not fit a substation. The sector guides work through the threat model, sensor mix, and legal posture for each: corrections is the most developed; public safety, critical infrastructure, events, and defence follow.