Border & Territorial Security
Every border security problem is different. We assess your terrain, threat profile and existing capability, then configure the solution that fits.
Glossary
Counter-UAS.
Counter-UAS is the detection, tracking, identification and defeat of small uncrewed aircraft. It is a distinct discipline from operating uncrewed systems, with different sensors, different legal authorities and different operators. The hard part is not detection or defeat — it is identifying, quickly and reliably, which of the many aircraft in the sky is actually a threat.
The asymmetry
A small uncrewed aircraft costs a few hundred dollars, needs no airfield and can be flown by someone with a weekend’s practice. The systems that reliably detect, identify and stop one cost orders of magnitude more and need trained people watching them around the clock.
That asymmetry is structural and it is not going to reverse. Any counter-UAS program that begins by promising to make the threat go away is mis-scoped. The realistic objective is to protect the specific things whose loss is unacceptable, at a cost proportionate to that loss, and to accept that the rest of the airspace will contain drones you did not authorize.
The chain
Five steps, and a system is only as good as its weakest one.
Detect. Something notices an aircraft is present.
Track. The detection becomes a track with position, heading and speed, held over time.
Identify. The track is classified as hostile, unknown or friendly.
Decide. Someone with the authority to act determines whether to.
Defeat. An effect is applied.
Procurement attention concentrates on detection and defeat, because those are what a vendor can demonstrate. Operational failure concentrates in the middle three.
What each sensor can and cannot do
Radar provides range and track quality nothing else matches, and works whether or not the aircraft is transmitting. It struggles with very small, slow, low-flying targets against ground clutter, and it will generate tracks on birds.
Radio-frequency sensing detects the control and video links, costs comparatively little, and can often identify the airframe type from its signature. Its limitation is absolute: an aircraft flying a pre-programmed route with its link switched off emits nothing at all.
Electro-optical and infrared confirms visually and produces the evidence an investigation needs. It has to be cued onto a track — a turret will not find a small drone by searching — and it is limited by weather and darkness like any optical sensor.
Acoustic is cheap and short-ranged, and suits a compact site with a low ambient noise floor.
Every single-sensor architecture therefore has a known blind spot. A supplier who does not volunteer theirs is not describing the product accurately.
Why identification is the bottleneck
In any real environment, the overwhelming majority of detections are benign. Hobbyists. News crews. Survey and agricultural flights. Utility inspections. And, routinely, the customer’s own uncrewed systems.
A program that cannot separate those from a threat quickly produces alert fatigue, and alert fatigue is the mechanism by which a real incident gets missed. The two things that most improve this are a dependable way to identify friendly aircraft, and a written classification procedure the watch actually follows — not a confidence score on a display that operators learn to ignore.
It is also the strongest argument for integration over a standalone system. A counter-UAS capability connected to the same operations picture as everything else will classify your own aircraft correctly. A box in a corner will not.
Why demonstrations outperform deployments
A demonstration knows what the target is, when it is coming and from where. The airspace is otherwise empty, the weather is chosen, and the operators are the vendor’s own.
A deployment has none of that. It runs continuously, against unknown traffic, in whatever weather occurs, watched by people who have to stay alert through weeks in which nothing happens. The gap between the two is not vendor dishonesty so much as a difference in conditions that buyers should price in when reading any performance claim.
The useful question to ask a supplier is not what the system detected at the range day. It is what its false-positive rate looks like over a month at a site like yours, and what the watch does with those.
Defeat is a legal question before it is a technical one
Interfering with an aircraft in flight, or with a radio transmission, is regulated in almost every country and criminal in many — irrespective of the intent of the aircraft being interfered with.
Which agency may engage, in what circumstances, over what ground, and with which effects, is a question of national law that differs sharply between a military installation, a civil airport, a border zone and a city center. Radio-frequency defeat in particular can affect navigation and communications well beyond the intended target, which is why siting and power are controlled.
Detection and tracking are almost always permissible. What may lawfully be done next is the question worth settling before any architecture is chosen, because a system bought with effectors the customer may not use is an expensive detection system with an unusable attachment.
What a realistic program looks like
A site survey before procurement, because radar and RF performance depend heavily on siting, clutter and line of sight. A layered sensor set rather than a single one. An identification procedure written down and rehearsed. A manned watch with the authority to act, or a defined route to someone who has it. And scheduled verification against a known target, because a counter-UAS system degrades invisibly — a sensor slightly out of calibration still produces tracks, they are just worse, and nobody notices until an incident.
Common Questions
What does counter-UAS mean?
The detection, tracking, identification and defeat of small uncrewed aircraft. It is a distinct discipline from operating uncrewed systems, with different sensors, different legal authorities and different operators, even though the two are frequently procured together.
What is the counter-UAS kill chain?
Detect, track, identify, decide, defeat. A system is only as capable as its weakest link, and identification is usually the weakest because most detections in any real environment are benign.
What is RF defeat?
Disrupting the radio link between an aircraft and its operator, or the satellite navigation it relies on, so that it lands, returns or loses its way. It is the most common non-kinetic effect, and it is regulated everywhere because the same emission can affect communications and navigation well beyond the intended target.
Why do counter-UAS demonstrations look better than deployments?
A demonstration knows what the target is, when it is coming and where from, and there is no benign traffic. A deployment has none of those advantages and has to distinguish a threat from hobbyists, media and the customer's own systems, continuously, with a watch that has to stay alert between incidents.
Does counter-UAS work against pre-programmed drones?
Only partly, and this is the gap worth understanding. An aircraft flying a pre-loaded route with its control link off emits nothing for a radio-frequency sensor to find, and radio-frequency defeat has nothing to disrupt. Radar and optical detection still work; the link-based half of a typical architecture does not.