Remote critical infrastructure sites can be covered for drones without adding staff, if detection, alerting and recording are planned around the people you already have. That means sensors placed for the areas that matter most, coverage gaps that are known rather than discovered, alerts that reach an on-call person wherever they are, and a record that builds itself. Start with a clear view of the risk to each site, then plan coverage to match.
Why remote sites are different
Substations, reservoirs, treatment works, pumping stations and telecoms sites share a set of problems:
- Large or awkward perimeters. Many sites cover a lot of ground, often in open countryside or on hills.
- Few people on site. Some are unstaffed for much of the day. Responsibility often sits with a regional control room or an on-call engineer.
- Many sites, one team. A single security team may be responsible for dozens of locations.
- High consequences. Disruption can affect thousands of people downstream.
The National Protective Security Authority (NPSA) has published counter-drone guidance written for national infrastructure site security managers. It recommends starting with a realistic assessment of the risk to each site and building a counter-drone strategy that fits alongside the security measures you already have, rather than bolting technology on.
Start with the risk, site by site
Not every site needs the same coverage. Before choosing sensors, work through each site:
- What would a drone threaten here? Equipment, people, sensitive information, operations?
- What is the realistic concern? NPSA notes that reckless and negligent flying causes disruption around sites, as well as deliberate hostile use. A site near a popular walking route has a different profile from one in a closed valley.
- What would you need to know, and how fast? Early warning, a confirmed sighting, evidence for the police, or all three?
- Who would respond? On site, from a control room, or an engineer on call an hour away?
The answers tell you which sites need full coverage, which need partial coverage of the most sensitive areas, and which are best served by simpler measures. NPSA also points to lower-cost steps that reduce careless flying, such as engaging local businesses and the community, security-minded communications and physical measures around key assets.
Plan coverage, and be honest about the gaps
On a large site, sensor placement matters more than sensor count. Coverage should be planned around what you are protecting and the likely approaches, not spread evenly along a fence.
Every real site has gaps: behind buildings, in dips in the ground, at the edge of a sensor's range. A known gap is manageable. You can accept it, cover it with another sensor, or plan your response around it. An unknown gap is a false sense of security. Make sure your system shows where it can and can't see.
Sensor choice follows the site. Open, rural sites with clear sightlines often suit radar for tracking drones that don't broadcast anything, with Remote ID and RF detection adding identity and pilot location where available. Cameras confirm what a track is. Our guide RF, radar or Remote ID: which drone detection does your site need? covers the trade-offs in more detail.
Make the alert reach the person on call
On a lightly staffed site, the hardest part is often not detecting the drone. It is making sure the right person knows, in time, wherever they are.
That means alerts that are:
- Specific. Which site, where on it, what has been seen, and what the next step is.
- Routed. To the person responsible for that site at that time, not to everyone.
- Reachable. On screen in a control room, and by text or email for someone who is on the road.
- Rare. Duplicates, approved flights and false alarms filtered out, so a real alert is taken seriously.
An on-call engineer who receives three alerts a night for birds will stop reading them. One who receives a clear message twice a year will act on it.
Let the record build itself
When a drone is seen over a remote site, there may be nobody there to take notes. The record has to come from the system: when the drone was first and last seen, its track, which sensors saw it, any camera footage and Remote ID data, who was told and what they decided. NPSA lists evidence that supports investigation and prosecution as one of the core purposes of a counter-drone system.
Keeping that record consistent across every site also gives you something else: a picture of patterns. A drone that keeps coming back to the same sites is worth knowing about, and you only see it if every site records incidents the same way.
Keep the sensors healthy
A sensor that has quietly failed is worse than no sensor, because everyone assumes it is working. On remote sites, nobody may notice for weeks. Sensor health should be monitored continuously, with a clear alert when one drops out, so the gap is visible straight away.
Test it
NPSA recommends table-top exercises and field exercises to test the plan end to end. For remote sites, include the awkward parts: an alert at night, the on-call person in another part of the region, and a drone over the area your sensors can't see well.
How Uavity approaches it
Uavity covers large or remote perimeters without adding staff, reaches the right on-call person wherever they are, and builds a record you can hand straight to police. Our critical infrastructure page has the summary. We plan coverage with you, install and monitor our sensors around the clock, and Wardglass brings them, and the sensors you already own, into one picture across every site.
What to do next
List your sites and sort them by risk. For the top few, sketch what you are protecting, the likely approaches, and who would respond to a drone at 2am. That sketch is the start of a coverage plan.
If you'd like to see how this works for a site like yours, talk to us.