Request a briefing

Briefing

Counter-drone protection for fixed sites

A practical counter-UAS briefing for site owners: the drone threat to infrastructure, detection technologies, identification, legal response options and how to build a C-UAS program.

The problem has changed

Small drones have gone from hobby to everyday tool to genuine security concern in under a decade. They are cheap, easy to fly, and able to carry cameras or small payloads over fences that were designed to stop people on foot. Prisons, airports, stadiums, energy facilities, data centers and military bases all report regular incursions.

Most incursions are careless rather than hostile — a hobbyist, a photographer, a real-estate shoot. But a meaningful share are reconnaissance: someone mapping a site's layout, guard routines and blind spots. A smaller share involve contraband delivery or worse. A counter-drone program has to handle all three without overreacting to the first.

The kill chain, in plain language

Counter-UAS practitioners describe the problem as a chain of steps. If any link is missing, the program fails.

  1. Detect that something is in the airspace.
  2. Track it continuously so you know where it is going.
  3. Identify what it is — a drone, a bird, a balloon — and ideally whose it is.
  4. Decide whether it is a threat and what response is lawful and proportionate.
  5. Respond using the options available to you.
  6. Record everything for investigation, prosecution and improvement.

Most site owners can do the first three and the last one themselves. Decision and response are where legal authority becomes critical.

Detection technologies compared

TechnologyStrengthsLimitations
Radio-frequency sensingDetects controller and video links; may identify make and model; can locate the pilotMisses autonomous drones flying without a link; crowded spectrum
RadarDetects any physical object, day or night, at rangeSmall drones have small signatures; must separate them from birds
Electro-optical / infraredVisual confirmation and classification; evidenceNarrow field of view; needs cueing from another sensor
AcousticPassive, low cost, useful in cluttered areasShort range; noisy environments
Remote ID receiversReads broadcast identification from compliant dronesOnly cooperative drones broadcast; hostile ones won't

No single technology is sufficient. Effective programs fuse at least two — typically radar and RF — with cameras for confirmation. Elevation helps every one of them, which is why perched sentries are valuable: a Kestrel on a rooftop sees over the clutter that limits ground-level sensors.

Response options and the law

This is the part most vendors gloss over. In many countries, the authority to interfere with an aircraft in flight — including jamming, spoofing, capturing or disabling a drone — is restricted to specific government agencies. Private operators of critical infrastructure often cannot lawfully take active measures themselves, even on their own property.

What site owners can usually do:

  • Detect, track, identify and record.
  • Locate the pilot where technology allows, and report to law enforcement.
  • Take passive protective measures: move people and sensitive operations indoors, obscure sensitive areas, adjust operations.
  • Coordinate with authorized agencies who can respond.

Government and defense customers may have authority for active responses, and their systems are configured accordingly. Tencer's position is simple: our systems cue and support authorized responders, and any defeat action requires an explicit human decision in Meridian. Read our responsible-autonomy doctrine.

Before buying any counter-drone capability, get legal advice on what your organization is permitted to do in your jurisdiction.

Building a counter-UAS program

1. Assess

Start with a threat and airspace assessment: what is around you, who might fly over, and what they could learn or do. Many sites discover they already experience regular overflights.

2. Baseline

Run detection for 30–90 days before designing a response. The data on frequency, timing, direction and drone type is invaluable.

3. Design

Choose layered sensors for your geography, decide who monitors, and write response procedures with law enforcement involved from the start.

4. Integrate

Counter-drone should not be a separate island. Tracks should appear on the same operating picture as ground intrusions, so operators see the whole situation. Meridian fuses aerial and ground tracks on one map.

5. Exercise

Test regularly with authorized flights. Procedures that are never exercised do not work on the night.

Metrics that matter

Counter-drone vendors quote maximum detection ranges measured in ideal conditions against large drones. Those numbers rarely survive contact with a real site. When you evaluate systems, ask for performance against the drones you actually expect, in the environment you actually have.

  • Probability of detection for small consumer drones at the ranges that matter to you — usually the distance at which a drone could photograph or reach a sensitive asset, not the maximum range on the data sheet.
  • False alarm rate per day, including birds, which are the classic weakness of radar-based detection. A system that alerts on every gull will be switched off within a month.
  • Time to classify: how long from first detection until an operator knows it is a drone and not a bird or a balloon.
  • Track continuity: how often the system loses a track behind buildings or terrain and has to re-acquire it.
  • Pilot location rate: for RF-equipped systems, the fraction of incidents in which the operator's position was identified.

Insist on a site trial. Thirty days of baseline detection on your own site, with authorized test flights, will tell you more than any brochure. Include night flights, flights in rain and wind, and flights that use terrain and buildings for cover — the conditions a deliberate adversary would choose.

Common mistakes

Buying effectors before detection. Organizations sometimes start with a jammer or interceptor because it is tangible. Without reliable detection and tracking, an effector is useless — and in many jurisdictions, unlawful for private operators anyway.

Treating counter-drone as a separate system. A drone over a fence line is often reconnaissance for something that happens on the ground later. If aerial and ground tracks live on different screens, operators miss the connection.

Ignoring the pilot. The drone is the symptom; the person flying it is the problem. Programs that focus on locating pilots and working with police get better long-term outcomes than programs that only chase aircraft.

Not planning for autonomy. Increasingly, drones fly pre-programmed routes without a radio link. RF-only detection will not see them. Build radar and optical detection into the design from day one.

Where redeployable sentries fit

Fixed counter-drone sensors share the weakness of all fixed sensors: once mapped, they can be avoided. Redeployable sentries add three things. They raise sensors above local clutter, they change the coverage geometry unpredictably, and after a detection they can relocate to keep a drone or its launch point in view. Combined with Bulwark radar masts, they form a layered detection network that adapts as the threat does.

For military users, the same architecture supports base defense against small drones as part of a wider integrated air-defense picture. See our defense brief.

Frequently asked questions

Can a private company shoot down or jam a drone?

In many jurisdictions, no. Active interference with aircraft is typically reserved for authorized government agencies. Private operators can usually detect, track, identify, record and report. Seek legal advice for your location.

What is the best drone detection technology?

There is no single best technology. Effective systems fuse radar and RF detection, with cameras for confirmation, and benefit significantly from elevated sensor positions.

Does Tencer sell drone defeat systems?

Tencer systems detect, track and cue. Government and defense customers can integrate authorized effectors, and every defeat action requires explicit human authorization.

Next step

Put a Kestrel over your site in thirty days.

Request a classified-capable briefing, a live demonstration or a site assessment. A program lead replies within one business day.