All posts by lz_admin

Something shifted in the counter-drone conversation last week. It was not a Gatwick-style closure or a near-miss over Heathrow that made the difference. It was a two-day workshop in Krakow, Poland, convened by ICAO and hosted by the Polish Civil Aviation Authority. The Secretary General of the International Civil Aviation Organization, Juan Carlos Salazar, said out loud what airport operators and aviation regulators have been saying to each other in private for years: the drone threat is accelerating, fragmenting, and the only credible response is a coordinated one.

Salazar was not vague about what coordination needs to look like. He called for multi-layered detection equipment working alongside updated aviation regulations. The workshop produced two specific recommendations. First, make UTM platforms interoperable with national drone registries so that cooperative and non-cooperative drones can be told apart in real time. Second, feed civil data, local drone trends, and incident reports into national threat intelligence systems so that risk assessment runs on live data rather than quarterly reports. Within months, ICAO will release a new risk management guide that sets the framework for how every member state should approach drone threats to civil aviation.

For anyone who supplies detection hardware to airports, the Krakow workshop was not an academic exercise. It was a preview of what airport procurement specifications will look like two years from now. Passive. Networked. Interoperable with UTM. Able to tell the difference between a lost delivery drone and a threat. Those requirements describe a detection architecture built around TDOA and protocol-level identification. Not around older approaches that emit, interfere, or stop at frequency detection.

The Krakow workshop: what ICAO actually said

To understand why Krakow matters, look past the diplomatic phrasing. ICAO has historically been slow to act on drones. Member states run their own rules. Drone registration is patchy even in developed markets. Remote ID standards are years behind the actual rate of drone proliferation. For the Secretary General to personally open a counter-drone workshop and call for ‘sustained and determined international attention’ tells you the organization sees a gap between how fast the threat is evolving and how slowly the regulatory machinery has been turning.

The recommendations from Krakow are specific enough to act on. UTM systems, the unmanned traffic management platforms that handle drone airspace, need to talk to national drone registration databases. If a drone broadcasts a registration ID that checks out, it is cooperative. If it does not, or if the ID is spoofed, or if there is no ID at all, the detection system at the airport perimeter needs to flag it immediately. This is not a future wish-list item. It is an operational requirement that ICAO wants member states to implement.

The workshop also pushed for civil drone data to feed into national security intelligence pipelines. Local trend reports. Incident logs. Airspace violation records. If the local police have a record of thirty drone sightings near the approach path in the last quarter, the airport security team should not find that out from a news article. The data exists. The recommendation: connect it.

A new ICAO risk management guide is expected to arrive within months. It will frame how every member state evaluates and mitigates drone threats to civil aviation. For hardware procurement, the guide functions as a reference standard. Airports will benchmark their detection systems against ICAO’s framework. If your detection approach cannot meet the layered, interoperable, passive model that ICAO describes, you will have a procurement problem.

Why airports are the hardest detection problem in C-UAS

Every counter-drone deployment has constraints. Prisons have tall walls and a known threat axis. Border sites have open terrain and predictable approach vectors. Stadiums have defined event windows and manageable perimeters. Airports combine the worst of every other site type into one airspace, and they add requirements no other site has to handle.

The electromagnetic environment at an airport is the most hostile RF space a sensor can operate in. Air traffic control radar. Instrument landing system beacons. VHF communications. Secondary surveillance radar. Weather radar. Ground movement radar. Wi-Fi networks, cellular towers, satellite uplinks. A detection system that emits adds to that noise floor. An active radar for drone detection is not a sensor; it is another transmitter that the frequency manager has to account for, license, and coordinate. Passive detection at an airport is not a preference. It is a constraint the site itself imposes.

Then there is the cost of a false positive. If a detection system triggers a false alarm at a border post, the guards step outside and look. If it triggers one at Heathrow, the tower gets involved, flights get held, airlines file delay claims, and the operator who caused it spends the next week answering questions. An airport detection system does not get to be ‘mostly right.’ It has to know what it saw, what the target is, and where it came from, every single time.

And there is the operator problem. When Gatwick shut down in December 2018 for thirty-six hours over drone sightings, the question that paralyzed the response was not ‘is there a drone?’ It was ‘where is the person flying it.’ RF detection that tells you a drone is somewhere in a two-kilometer arc does not answer that question. To find the operator, you need positioning. Directional data from a single sensor is not positioning. Angle of arrival from a single point degrades with distance. To locate an operator to within ten meters at the far end of the perimeter, you need more than one receiver. You need a network.

TDOA, as a concept, is known in the counter-drone industry, but the implementation varies enormously between suppliers. One name that comes up in the same sentence as TDOA is Terjin, and for good reason — they invested early in the technique and built their positioning around it. But TDOA is not a single-company technology. It is a physical measurement method, the same way phased-array radar is not owned by any one manufacturer. The difference between one TDOA system and another is the signal processing pipeline, the protocol identification layer, and the networking architecture that turns individual receivers into a single detection volume.

Our team at LZ TECH approaches TDOA as one layer in a larger detection stack, not as the entire stack. The D5-B node, which this article examines in detail, pairs TDOA-based positioning with our CRPC protocol-cracking engine so that the system does two things at once: locate the signal source and decode what it is carrying. That combination — positioning plus identity — is what sets the approach apart from TDOA implementations that stop at angle of arrival.

TDOA: the physics that makes airport detection work without the airport noticing

Time Difference of Arrival solves the airport detection problem by reframing it. Instead of asking ‘what does the signal look like,’ TDOA asks ‘when did the signal arrive.’ The principle is simple to describe and hard to do well. Multiple passive receivers are placed at known locations around the protected area. Each receiver time-stamps every drone signal it picks up. Because the receivers are at different physical locations, the same signal arrives at each one at a slightly different time. The time differences, cross-referenced with the known positions of the receivers, give you a position fix on the transmitter. Both the drone in the air and the controller on the ground.

The word ‘passive’ does a lot of work here. TDOA receivers do not transmit. No radar pulse. No interrogation signal. No frequency sweep. The receivers are listening only. That means a TDOA network can be deployed anywhere at an airport without a frequency coordination meeting, without an emissions license, and without adding a single decibel to the RF environment that ATC depends on. For the airport frequency manager, TDOA is invisible.

Networked TDOA also solves the coverage geometry problem that single-sensor systems cannot. A single detection unit, however capable, has a field of view. The perimeter is larger than any one sensor can cover. The approach vector depends on wind direction, the operator’s position, and the drone’s flight mode. With three or more TDOA receivers placed around the airport, the detection volume is continuous. Overlap between receivers means a drone cannot transit from one coverage zone to another without being tracked the entire way.

Beyond pure detection, TDOA gives you a trajectory. By computing position fixes at short time intervals, under two seconds in a well-engineered system, the network reconstructs the drone’s flight path from takeoff to the current position. That trajectory has a start point. The start point is the operator. On a command screen, it appears as a red dot with a GPS coordinate. Security can dispatch to that coordinate while the drone is still in the air. That is the operational difference between TDOA and any single-channel detection method.

What D5-B brings to an airport perimeter

The D5-B is a TDOA detection and positioning node built for exactly this use case. It is a compact unit, 224 millimeters in diameter, 287.5 millimeters tall, three kilograms, that combines wideband passive RF reception with the CRPC protocol-cracking engine. The form factor matters at an airport, where every installation point needs to go through facilities approval, structural surveys, and aesthetic review. A three-kilogram unit with an IP66 rating can be mounted on an existing light pole, a terminal roof edge, or a perimeter fence post without a concrete pad and a crane.

The D5-B listens across the full 30 MHz to 6 GHz band. That span covers every commercial drone control frequency in current use, every common Wi-Fi drone band, and the custom FPV frequencies that traditional narrowband detectors miss. A single D5-B unit detects more than thirty drones simultaneously. When three or more units are networked together, they deliver directional positioning and full trajectory tracking for every target.

The positioning accuracy is under ten meters RMS. That means the system can distinguish an operator standing at the airport fence from an operator standing at a warehouse across the road. For the security team deciding whether to dispatch an intercept vehicle, a ten-meter circle is actionable. A five-hundred-meter arc from a single directional sensor is not.

The CRPC engine inside every D5-B adds a layer that TDOA alone cannot provide: identification. The receiver decodes the communication protocol between the drone and its remote controller. It extracts the drone’s model, serial number, and the home-point GPS coordinates that most consumer and commercial drones transmit as part of their standard telemetry stream. It also extracts the operator’s location from the home-point data, giving a second independent position fix that cross-checks the TDOA triangulation.

The identification runs through a drone library that covers more than 98 percent of the commercial market. DJI. Autel. Parrot. Hubsan. FIMI. Custom FPV builds with aftermarket transmitters. Wi-Fi drones that use standard 802.11 chipsets. DIY platforms assembled from off-the-shelf flight controllers. The library knows them all. The AI-RPC self-learning pipeline adds new signatures as new drone models enter the market.

Once identified, the D5-B classifies. A white-listed inspection drone operated by the airport maintenance team gets no alarm. A white-listed delivery drone on a registered commercial route gets a logged pass. An unknown drone with no registration ID, no white-list entry, on an approach vector toward the active runway threshold gets an immediate alert with position, trajectory, model, and operator location. The operator clicks ‘mark black.’ Every D5-B on the network now treats that specific drone’s electronic fingerprint as hostile.

The unit operates autonomously around the clock. No operator needs to watch a screen at 3 a.m. for the system to function. Classification, trajectory tracking, and alerting run automatically. The operator engages when the system flags a threat, not before. For an airport security operations center that already monitors dozens of camera feeds, access control systems, and fire alarms, an additional sensor system that does not demand constant attention is a requirement, not a luxury.

What ICAO’s interoperability push means for the hardware you buy today

The Krakow workshop’s clearest signal was about interoperability. ICAO wants UTM platforms to query national drone registration databases in real time. That means the detection layer, the sensors at the airport perimeter, needs to do more than flash an alarm light when a drone appears. It needs to output identification data that a UTM platform can cross-reference against a registration database.

Frequency-based detection cannot provide that data. Knowing that a signal is present on 2.4 GHz tells a UTM system nothing about which specific drone is transmitting. Protocol-level identification, the kind CRPC delivers, extracts the serial number and the telemetry data that the drone itself is broadcasting. That serial number is the bridge to the registration database. That bridge is what ICAO’s interoperability framework requires.

Without protocol-level ID in the detection layer, the UTM operator sees a dot on a screen labeled ‘unknown contact.’ They cannot tell a registered survey drone that drifted slightly off its flight plan from an unregistered drone on a collision vector. The Krakow workshop identified exactly this gap as the priority to close. Detection hardware that cannot provide identity-level data to the UTM platform is detection hardware that does not meet the emerging ICAO standard.

This is not speculation about what a future regulation might ask for. ICAO will release the risk management guide this year. Member states will write their procurement specifications against it. An airport that installs a detection system in 2026 or 2027 will live with that system for five to ten years. If it cannot output protocol-level identification to a UTM platform, the system is already on a path to obsolescence.

Beyond the airport fence: where networked TDOA makes sense

The TDOA networking model is not only for airports. Any site where the protected perimeter is large, irregular, or embedded in an urban RF environment benefits from passive networked detection. A stadium during a match. A government complex spread across multiple buildings. A correctional facility where the drone approach can come from any direction, and the threat is contraband delivery. A waterfront port facility where the approach vector is over water, with no terrain to constrain detection geometry.

In each of those sites, the same physics applies. A single sensor has a field of view. A network has a coverage volume. TDOA gives you the operator’s location alongside the drone’s position. CRPC tells you what the drone is and what it is doing. The D5-B form factor, small, light, IP66, low power, means the network can go where the threat geometry demands, not where the installation budget permits.

The ICAO framework may target civil aviation first, but the hardware model it describes, passive, networked, interoperable, protocol-aware, is the same model that protects any site where the cost of a drone incursion is measured in millions per hour instead of dollars per incident.

The Krakow signal is clear

ICAO does not regulate drone detection hardware. But it sets the framework that procurement offices use to write their specifications. The Krakow workshop made three things clear. One: the drone threat to civil aviation is not leveling off. It is rising, and ICAO’s own language now reflects the urgency airports have felt for years. Two: the response has to be coordinated across detection equipment, aviation regulation, and digital infrastructure, UTM, registries, and threat intelligence. Three: interoperability between the detection layer and the UTM layer is not a nice-to-have. It is the recommendation that will drive procurement decisions for the next decade.

For airports, the hardware implication is practical. Deploy detection that does not add to the RF noise floor. Detection that locates both the drone and the operator with actionable precision. Detection that identifies the specific drone and feeds that identity data into the UTM platform. Detection that does all of this autonomously, around the clock, with every event logged and timestamped for the incident report that ICAO recommends feeding into national intelligence pipelines.

TDOA plus CRPC delivers that package. The D5-B is one implementation of it: a three-kilogram, IP66-rated node that covers 30 MHz to 6 GHz, positions to under ten meters, identifies 98 percent of the commercial drone market by protocol fingerprint, and networks with its neighbors to cover the full perimeter. It is the kind of detection layer that slots directly into the ICAO framework, the Krakow workshop previewed. When the new risk management guide drops, airports that already have passive, networked, protocol-aware detection in place will be ahead of the specification. Airports that do not will be writing RFPs to catch up.

 

Introduction

If you have spent any time evaluating counter-drone systems, you have noticed something: every vendor has a product that does part of the job well. One vendor sells radar. Another sells RF detection. A third has the best cameras. A fourth built the jamming hardware. Nobody seems to have built the whole thing.

That is not a coincidence. Counter-drone defense is genuinely multi-technology by nature. No single sensor type covers all the threat scenarios you are likely to face. The integration problem is not a vendor failing. It is the fundamental challenge of the space.

This article is about solving that integration problem. Not by buying everything from one vendor, though that is one option. By understanding what integration actually means, what the architecture components are, and how to make the pieces work together in a way that gives you a functioning system instead of a collection of expensive components.

The limits of single-sensor counter-drone

Before we talk about integration, it is worth being clear about why you need it. Each counter-drone technology has documented blind spots.

RF detection misses autonomous drones that do not transmit, modified drones running on frequencies outside your monitoring bands, and DIY builds using custom protocols. If your detection layer is RF-only and someone flies a pre-programmed autonomous UAV over your site, you see nothing.

Radar sees moving objects but struggles to classify them. Is it a bird, a plastic bag, or a drone? Without a second sensor, you are guessing. In high-clutter environments, the track density can overwhelm operators.

EO/IR cameras need to know where to look. Point a camera at empty sky and you have a very expensive security camera. Cameras are powerful confirmation tools, but as primary detection they require either very high coverage density or external cueing from radar or RF.

No single technology gives you detection, classification, tracking, identification, and response confirmation. That is why multi-sensor architectures exist.

Multi-sensor fusion architecture

The detection-to-response chain

Every multi-sensor counter-drone system follows the same functional chain: sensor input, data fusion, threat assessment, decision, and response. The sensors see different things. The fusion layer combines what they see. The threat assessment layer decides what it means. The decision layer determines the response. The response layer executes.

The critical word is fusion. Raw data from multiple sensors is not integration. Integration means the system combines sensor data to produce a single coherent picture of the airspace. That picture should show the same object detected by multiple sensors as one track, not as three separate tracks that an operator has to correlate manually.

Data fusion is what separates a real multi-sensor system from a collection of sensors feeding separate displays. The former scales to handling multiple simultaneous incursions. The latter does not.

LZ TECH Multi-tech Fusion Detection Solution

LZ TECH’s Multi-tech Fusion Detection Solution combines radar, EO/IR, and RF in a single detection system. The stated RF detection range is up to 10 kilometers. The system handles active EO/IR searching and tracking alongside radar detection, with all sensor data processed through a unified C2 layer.

The API interface is worth noting for organizations with existing security infrastructure. An open API means the LZ TECH fusion system can feed data into a broader security operations center rather than operating as a standalone system. Whether that matters depends on how your security operations are structured.

The deployment model is flexible. LZ TECH offers both fully integrated configurations where everything comes from one vendor, and modular configurations where their detection system integrates with existing sensors or response hardware from other vendors.

Multi-tech Fusion Interception Defense System

The Interception Defense System adds the response layer to the detection architecture. Radar, EO/IR, and C2 feed into an FPV interceptor capability. The idea: when a drone is detected and classified, the system can deploy an interceptor drone to physically intercept the threat rather than relying solely on electronic countermeasures.

The multi-platform deployment options cover fixed, portable, and vehicle-mounted configurations. The environmental adaptability specifications are relevant for sites in extreme climates. We have seen systems specified for controlled indoor conditions fail in field environments within months. Temperature range and ingress protection ratings should match your actual deployment conditions, not ideal laboratory conditions.

Command and control: the brain of C-UAS

What C2 software actually does

C2 software is the layer that nobody talks about enough until it fails. It collects data from all sensors, processes and displays that data in a way that operators can use, manages alarm workflows, supports decision-making, and coordinates response devices.

In a single-sensor system, C2 is relatively simple. One sensor, one display, one response option. In a multi-sensor system with multiple response modalities, C2 becomes the critical enabling technology. If the C2 cannot handle the data volume and present it coherently, the sensor investment is largely wasted.

The specific C2 capabilities that matter in practice: real-time alarm management, data fusion across multiple sensor types, historical playback for incident review, and flexible workflow configuration for different threat scenarios.

LZ TECH CCS platform

The CCS platform is LZ TECH’s C2 offering. The core interface provides a unified command view across all connected sensors. The GIS panoramic display overlays real-time drone trajectory data on a geographic map, which is more useful than a two-dimensional radar-style display for operators who need to understand spatial relationships at a site.

Cross-region monitoring capability supports multi-site operations where a central security team oversees several locations. Smart alarm workflows let operators configure automated responses for different threat levels, which matters when multiple incursions happen simultaneously.

Cloud and local deployment options cover the range from organizations that want minimal on-premise infrastructure to those with data residency requirements or air-gapped networks. Mission replay and data logging support post-incident analysis and regulatory reporting.

Permission configuration is relevant for larger organizations where different operator roles need different access levels. A guard on patrol does not need the same system access as a site security director.

Data interoperability and open standards

One of the persistent problems in counter-drone defense is vendor lock-in. Buy a sensor system from one vendor and you often cannot easily integrate response hardware from another. The C2 software may only talk to sensors from the same vendor. Over time, you end up with a system architecture determined by what one vendor happened to sell you.

The SAPIENT standard, developed in the UK for autonomous sensor integration, is one attempt to address this. Open API interfaces like the one LZ TECH builds into CCS are another. Sensor-agnostic C2 design means you can swap individual sensors without replacing the entire system.

If you are evaluating counter-drone vendors, ask specifically about API support and sensor interoperability. The answer tells you a lot about whether the vendor is building a platform or just selling products.

Deployment models by site type

Fixed-site deployment is the most common configuration. Airports, prisons, power plants, government facilities, stadiums. These sites have defined perimeters, relatively stable threat profiles, and usually a security operations center with operators on shift. A typical configuration: RF detection at the perimeter, radar for wide-area coverage, EO/IR for confirmation, and jamming or interception for response. C2 in the operations center.

Vehicle-mounted deployment serves mobile protection scenarios. Convoy protection, VIP transport routes, border patrol, temporary event security. The vehicle-mounted system trades raw detection range for mobility. The vehicle becomes the moving protection bubble.

Portable and handheld deployment is the tactical end of the spectrum. Single officers, rapid response teams, event security patrols. A handheld jammer and detector combination is lightweight enough to carry but limited in range and duration compared to vehicle-mounted or fixed configurations.

Air-ground coordination represents the more sophisticated end of deployment models. Airborne detection assets feed data to ground-based C2, extending coverage beyond what ground sensors can achieve. LZ TECH’s D5-Air is positioned for this role.

What real deployments look like

Airport perimeter: DF Series direction finding at the fence line, D5-B TDOA positioning for precise location, VAR300 for active EO/IR scanning, VM vehicle-mounted system for patrol coverage, and H3 Pro handheld units for rapid response officers. The C2 layer coordinates all of it and feeds the airport security operations center.

Critical infrastructure: DFJ stationary jammer at the perimeter, DF direction finding for incoming threat bearing, and TR100 for integrated radar and EO/IR coverage of the inner zone. This is a layered defense model within a single site.

Large event security: portable HD5 system for rapid deployment, H3 Pro for patrol teams, HDJ 3.0 handheld jammer as the response tool. This configuration can be set up and torn down quickly, which matters for events that last days rather than years.

Border security: DF Series TDOA networking extends coverage across a linear border area, with VM vehicle-mounted units providing mobile response capability along the route.

What integration actually costs

Here is the part vendors do not put in their brochures. Integration costs money and time. Buying a fully integrated system from one vendor is the expensive option upfront but the cheaper option over three to five years when you count the engineering hours saved.

Buying best-of-breed components and integrating them yourself is cheaper at purchase but demands engineering resources you may not have. We have seen organizations buy what looked like excellent components and spend a year trying to make them work together.

The middle path is modular systems from a vendor that builds for interoperability. You buy the sensor fusion layer and response hardware from one source but retain the ability to swap individual sensors.

For most organizations evaluating counter-drone defense, the recommendation is the same: start with the threat model, work backward to the sensor requirements, and then evaluate whether the integration overhead of your chosen configuration is realistic for your organization. A simpler system that works is better than a sophisticated system that never gets fully integrated.

 

Introduction

Most counter-drone articles spend most of their time on radio frequency detection. That’s understandable. RF is versatile, passive, and cost-effective. But if you’ve deployed RF detection at any scale, you already know its limits. Autonomous drones don’t phone home. Modified UAVs use frequencies you’re not monitoring. DIY builds run on custom protocols that never get added to any library. RF sees all of these the same way: nothing.

When RF alone can’t give you the coverage picture you need, you move to active sensing. Radar and electro-optical systems fill the gaps that passive detection leaves open. They won’t replace RF in most architectures, but they change what the architecture is capable of.

This article walks through both technologies, what they do well, what they don’t, and how they fit into a real deployment. If you’re trying to figure out whether active sensing belongs in your counter-drone setup, this is the framework.

Radar for drone detection

How drone detection radar works

Radar works by sending out radio pulses and analyzing what comes back. That’s the basic principle, whether you’re tracking passenger jets or small UAVs. The difference is in the execution.

Standard air traffic radar is built for large metal aircraft. A Boeing 737 has a radar cross-section of roughly 20 to 80 square meters. A DJI Mavic 4 comes in at about 0.02 square meters, smaller than a baseball. Conventional radar filters objects of that size as noise. Counter-drone radar is a different product. It uses higher frequencies, X-band or Ku-band, and advanced signal processing to detect and track drone-sized objects.

Phased-array radar is the architecture most commonly specified for counter-drone work. Instead of a rotating dish, it uses an array of antenna elements that steer the beam electronically. That means faster scanning, more precise control, and no moving parts to fail. It’s also how modern military radar works, which should tell you something about its capability.

The key measurement that separates a useful counter-drone radar from a generic one: what’s the smallest detectable object at what range? A radar that can’t track a 0.02 square meter target at 2 kilometers isn’t solving the problem.

What radar actually gives you

Radar gives you range, bearing, and velocity of anything in its coverage volume. It works in all weather, day or night. It doesn’t care whether the drone is transmitting or flying autonomously. If something is moving through the airspace at drone-like speeds, radar will see it.

What radar doesn’t give you is identification. A radar track says there’s a small, slow airborne object at position X. It doesn’t tell you whether that’s a DJI Matrice, a homebuilt quadcopter, or a large bird. You need a second sensor for that.

The other constraint is clutter. Urban environments with lots of buildings and moving vehicles generate radar reflections. Without good filtering, your operators end up with thousands of tracks to sort through. This is where signal processing matters: modern counter-drone radar uses micro-Doppler analysis to distinguish the spinning rotor signature of a drone from the return of a truck or a bird.

The bird problem

Every counter-drone operator who has deployed radar near wildlife has a story about the pigeon incident. Birds and small drones produce similar radar signatures. Without good classification processing, a flock crossing your perimeter can generate dozens of tracks that look just like drone incursions.

The micro-Doppler signature is the key differentiator. A drone rotor produces a periodic, high-frequency return that looks like a sawtooth pattern on the Doppler spectrum. A bird’s wingbeat produces something slower and more irregular. Good counter-drone radar can classify these with reasonable accuracy, but it’s not perfect. Hovering drones produce minimal rotor return, and some large birds generate signals that look like small drones.

When you’re evaluating counter-drone radar, ask for the bird classification rate in the vendor’s test data. A 90% classification accuracy sounds solid until you run the math: at a site near a wildlife area with frequent bird crossings, 10% false positives add up fast. That’s hours of operator time spent confirming that the track is not actually a drone.

Most serious deployments handle this by layering: radar handles early detection and rough tracking, and a second sensor confirms what the radar found. We’ll get into that below.

TR100: radar and EO/IR in one package

The TR100 is LZ TECH’s answer to the sensor integration problem. Instead of buying radar from one vendor and cameras from another and figuring out how to make them talk to each other, the TR100 packages phased-array radar, visible-light cameras, thermal imaging, and wide-angle optics in a single unit. Radar detects and tracks the target. The EO/IR payload immediately slews to the bearing and provides visual confirmation.

The workflow is radar-guided. The radar detects something in the coverage volume, classifies it as a potential drone, and points the cameras at it. An operator or AI processing confirms: drone, model, threat level. This is faster than having an operator monitor a raw radar feed and manually cue cameras, which is what happens when sensors come from different vendors and don’t integrate.

Fixed-site deployments that need continuous perimeter coverage are where the TR100 makes most sense. Airports, prisons, power plants, government facilities. The all-in-one form factor simplifies installation and reduces the integration headache. The tradeoff is that you’re buying a complete sensor package whether you use all of it or not. For mobile or tactical applications, a different configuration usually works better.

Electro-optical and infrared systems

What EO/IR actually does

Electro-optical systems are cameras. Visible-light cameras capture what you can see. Infrared cameras capture heat signatures. Thermal imaging reads the infrared radiation emitted by objects, which means it works in the dark, through haze, and in conditions where visible-light cameras struggle.

The use case breaks into two modes: confirmation and primary detection. In most architectures, EO/IR is confirmation. Something else finds the drone. The cameras point at it and confirm: yes, that’s a drone, here’s the model, here’s what it’s doing. In this role, cameras are evidence and identification tools, not primary sensors.

Using optical systems for primary detection is technically possible but practically demanding. You need cameras covering 360 degrees, software that can scan for small moving objects, and enough processing power to handle the output without generating a wall of false alerts. It’s not impossible, but it’s a different engineering problem than mounting a zoom camera on a pan-tilt head and slewing it to a bearing.

Dual-spectrum imaging

Most serious counter-drone cameras combine visible-light and thermal sensors in one housing. Visible-light gives you the detail you need for identification: color, markings, payload indicators. Thermal tells you where to look at night or in fog.

A drone’s motors and electronics generate heat. At night or in low visibility, a thermal camera can pick up a drone at ranges where a visible-light camera sees nothing. The tradeoff is resolution: thermal cameras at the price points realistic for most deployments don’t give you the same identification confidence as optical. You can confirm there’s something there. You might not be able to confirm exactly what it is at maximum range.

For 24-hour coverage, dual-spectrum is the minimum configuration. Single-spectrum thermal works for detection. Single-spectrum optical works for daytime identification. Only dual-spectrum gives you both.

AI-enhanced visual detection

The manual detection problem in optical systems is real. An operator watching a camera feed for drone intrusions will miss things, especially when nothing is happening for long stretches and then multiple things happen at once. AI changes the economics of visual detection by automating the hard part.

Modern systems use computer vision models trained on drone imagery to automatically detect and classify objects in the camera’s field of view. The system flags potential drones without requiring an operator to be watching. It also handles the drone versus bird classification problem, though not perfectly.

The other piece is intelligent gimbal control. Good EO/IR systems don’t just stare at a fixed field of view. They use motion detection and predictive tracking to keep moving targets in frame. Once a drone enters the coverage area, the system tracks it across multiple camera positions if the target moves.

LZ TECH’s VAR300 is positioned around autonomous scanning. The claim is that it can operate without an external cue from radar or RF, using its own AI visual processing to detect and track drones. If that works as described, it changes the deployment model: a site could run VAR300 as a standalone detection layer without integrating other sensor types. Whether that’s the right architecture depends on the threat model and budget.

T100: PTZ tracking and pointing

The T100 is LZ TECH’s long-range PTZ tracking system. The specs that matter: 6.1 millimeter to 561 millimeter focal length. That range covers wide-area surveillance at the short end and precise identification at the long end. Daylight identification range is specified at 2 kilometers or more against a DJI Mavic 3 reference target. Thermal performance at night is specified at 1 kilometer under similar conditions.

The longer focal length is where the T100 earns its position in a deployment. When you need to confirm what a drone is doing at distance, a PTZ with serious zoom is the tool. A guard on patrol with a handheld thermal monocular can confirm there’s something in the air. The T100 can confirm the model, read any visible markings, track the flight path, and record the trajectory for evidence.

Trajectory recording is the forensic piece. A thermal clip of a drone hovering over a restricted area is useful for reporting. A video recording with time-stamped position data and zoom level is useful for prosecution. Different sites have different needs here. Government facilities and airports usually need the evidence chain. Private facilities often don’t.

Why you need both radar and EO/IR

Here’s how a properly integrated radar-EO/IR system works in practice. Something enters the radar coverage volume. The radar detects it, classifies it as a potential drone based on size and movement profile, and calculates the bearing and range. That bearing is passed to the EO/IR system within milliseconds. The cameras slew to the correct heading and zoom level automatically. An operator or AI confirms: drone, model, intent assessment. If response is warranted, the system is already tracking the target with cameras.

Without that integration, you have two separate workflows. The radar operator sees a track and has to manually cue the cameras to that bearing. That takes seconds, during which the target might move. If multiple tracks appear simultaneously, the operator is juggling. Under stress, with adrenaline, during a real incident, that lag matters.

The other reason integration matters: confirmation is not optional for most response decisions. If your response to a drone is jamming its link, you want to be reasonably confident that what you’re jamming is actually a drone and not a bird, a plastic bag, or a weather balloon. Radar alone doesn’t give you that confidence. Cameras do.

LZ TECH’s Multi-tech Fusion Detection Solution is designed around this integration model. Radar and EO/IR are part of the same system, sharing data through the C2 layer. The vendor argument is that buying the pieces separately and integrating them yourself is the expensive and time-consuming path. It’s a reasonable argument for sites that don’t have an engineering team that wants to own the integration.

Choosing the right active sensing configuration

Fixed-site deployments with continuous monitoring needs are the clearest case for integrated radar-EO/IR. Airports, critical infrastructure, government facilities. These sites need 24/7 coverage, fast response times, and a clear evidence chain. The TR100 handles all of that in a single installation.

Sites that already have RF detection and want to add active sensing without a full integrated system can add T100 cameras to an existing setup. The cameras don’t require radar as a cue, though they’ll perform better with it. This is a reasonable upgrade path for sites that deployed RF first and are now expanding coverage.

VAR300 is the autonomous option. If the deployment scenario requires a sensor that can detect and track drones without relying on other systems, VAR300’s standalone AI visual processing is worth evaluating. The tradeoff versus integrated radar-EO/IR is that visual-only detection has a harder time in poor weather and at longer ranges than radar-assisted systems.

The question we keep coming back to is the same one that drives the rest of the counter-drone architecture: what are you actually defending against? Amateur operators near your perimeter don’t need the same sensor configuration as sophisticated actors running modified UAVs with intentional evasion tactics. Match the active sensing investment to the actual threat profile, not to the specifications of the most capable system available.

The bottom line

Radar and EO/IR fill the gaps that passive RF detection leaves open. They handle autonomous drones, provide visual confirmation for response decisions, and give you an evidence chain for anything you decide to act on.

Radar alone is early warning without identification. EO/IR alone is confirmation without the range to find targets on its own. Together, they complete the detection loop that RF starts.

Integrated systems like the TR100 simplify deployment by removing the integration problem. Modular systems like T100 plus existing sensors give you more flexibility if you have the engineering capability to own the integration yourself.

For sites where autonomous drones are a documented threat, where evidence collection matters, or where RF-only coverage has proven insufficient, active sensing belongs in the architecture. The specific configuration depends on the site, the threat model, and the budget.

Introduction

A security director at a Middle Eastern airport called us last year with a problem. He’d bought a counter-drone system, radar plus RF detection, plus cameras, and it was generating 200+ alerts per day. His team was exhausted. The system was technically working, but they couldn’t keep up with the noise. By month three, they were ignoring most alerts entirely.

That’s the thing about detection technology. The hard part isn’t buying sensors. It’s matching the sensors to the environment in a way that produces actionable information without drowning your operators.

This article compares the three primary detection technologies, radio frequency (RF), radar, and optical sensors, in terms of how they actually perform in the field. Not spec sheets. Not marketing claims. What happens when you deploy them?

If you’re in procurement and trying to figure out where to invest a limited budget, this is the framework we wish someone had given us.

Radio frequency detection

How it works

RF detection listens for the signals drones use to communicate with their controllers. Every commercial drone, DJI, Autel, Parrot, and the various Chinese OEMs, transmits on known bands: primarily 2.4 GHz and 5.8 GHz, sometimes 900 MHz or 1.2 GHz for longer-range links.

An RF system consists of one or more antennas plus processing hardware that monitors these bands. When it detects a signal matching known drone signatures, it can identify the model and sometimes extract a unique identifier, similar to a MAC address.

The detection range depends on antenna gain, processing sensitivity, and environmental conditions. In practice, most RF systems detect commercial drones at 2-5 km under favorable conditions. Urban environments with high RF noise reduce that range.

What RF actually detects

Here’s the constraint that matters most: RF only detects drones that are transmitting. If a drone is flying autonomously, following pre-programmed waypoints with no active link to a controller, RF sees nothing. If a drone is using a frequency you’re not monitoring, RF sees nothing. If a drone has been modified to use encrypted or proprietary links, RF probably sees nothing.

This isn’t a minor gap. The UK Ministry of Defence estimated in a 2023 briefing that roughly 15-20% of drone incursions at sensitive sites involved autonomous flight. That number is climbing as cheap flight controllers with GPS waypoint capabilities become widely available.

RF detection is strongest against amateur operators, people flying DJI consumer drones near your perimeter, because they don’t know better. It’s weakest against anyone who knows you’re listening.

The library problem

RF systems work by matching detected signals against a library of known signatures. That library needs constant updating. Every time a manufacturer changes a protocol, DJI updates the OcuSync firmware, Autel releases a new transmission standard, the vendor has to reverse-engineer it and push an update to customers.

Between updates, modified drones pass through undetected. The lag isn’t theoretical. After DJI released the Mini 3 Pro with an updated transmission protocol in 2022, several counter-drone vendors took 4-6 months to fully integrate the new signatures. During that window, those drones flew through coverage.

LZ TECH’s approach, CRPC or Cognitive Radio Protocol Cracking, attempts to address this by reconstructing protocols rather than matching against libraries. The claim is that this works against DIY and modified drones. We haven’t independently verified the full scope, but the technical direction addresses a real gap in conventional RF detection.

Deployment considerations

RF detection is typically the most accessible entry point for counter-drone capability. Handheld detectors can be carried on patrol. Fixed-site RF systems with multi-antenna arrays and controller triangulation scale to cover larger perimeters depending on coverage area and processing capability.

Installation is relatively simple. You mount antennas with clear line-of-sight to your perimeter, run cables to processing hardware, and connect to your monitoring network. No transmission license required. RF detection is passive.

For sites where a single sensor is all the budget allows, RF is the usual starting point. Just understand what you’re getting: a system that detects most commercial drones flown by people who aren’t trying hard to evade you.

Radar

How it works

Radar sends out radio pulses and measures the return. By analyzing the reflected signal, it can determine direction, distance, and velocity of objects in its coverage area.

Standard air traffic radar is built for large, metal aircraft. A typical passenger jet has a radar cross-section of 10-100 square meters. A DJI Mavic 4 has a cross-section of roughly 0.02 square meters, smaller than a baseball. Conventional radar filters objects this small as noise.

Counter-drone radar is different. It’s optimized for small, slow targets, often using higher frequencies (X-band or Ku-band) and advanced processing to detect drone-sized objects. Micro-Doppler processing analyzes the frequency shift from spinning rotors, helping distinguish drones from birds.

Detection range and coverage

A well-specified counter-drone radar detects small UAVs at 3-10 km, depending on the radar design and environmental factors. Unlike RF, radar doesn’t depend on the drone transmitting. It sees anything with mass and velocity in its coverage volume.

The coverage geometry matters. A 2D radar provides azimuth and range but not elevation. You know something is at bearing 270 degrees and 2 km out, but not how high. A 3D radar adds elevation, giving you full position. For sites where altitude matters, airports, for example, 3D is worth the premium.

The thing radar doesn’t give you: identification. A radar track says ‘small, slow airborne object at position X, Y, Z.’ It doesn’t tell you whether that’s a DJI Matrice, a homemade quadcopter, or a large bird. You need a second sensor, usually optical, to confirm what the radar found.

The bird problem

Birds and small drones have similar radar signatures. A flock of pigeons can generate dozens of tracks. Without good classification processing, your operators get alerts every time birds cross your perimeter.

Modern counter-drone radar uses micro-Doppler analysis to differentiate. The rotor signature of a drone creates a different frequency pattern than bird wingbeats. It’s not perfect. A hovering drone has a minimal micro-Doppler signature, and large birds can be misclassified. But it reduces false positives significantly compared to unprocessed radar.

If you’re evaluating radar, ask for the bird classification rate in the vendor’s test data. A 90% classification accuracy sounds good until you realize that 10% of bird tracks still generate alerts. At a site near a wildlife area, that adds up.

Deployment considerations

Radar represents a larger investment than RF. Installation requires a clear line of sight, a stable mounting platform, and power. Most radar also requires a transmission license, which adds regulatory overhead in some jurisdictions.

For fixed sites with a real budget, airports, power plants, and military installations, radar is worth it. The ability to detect autonomous drones, see beyond line of sight, and track multiple targets simultaneously justifies the investment if the threat model includes coordinated or evasive incursions.

For smaller budgets or mobile applications, radar may be more capabilities than the site requires. A sports stadium that hosts 20 events per year probably doesn’t need a full radar installation. An air base that operates 24/7/365 absolutely does.

Optical sensors (EO/IR)

How they work

Optical sensors use cameras, visible light, infrared, and thermal to detect and identify drones. Electro-optical (EO) cameras capture visible light. Infrared (IR) cameras capture heat signatures. Together, they provide positive identification: you can see the drone, confirm the model, and potentially identify any payload.

The limitation is the detection range and the field of view. A high-resolution zoom camera can identify a drone at 2-3 km, but only if it’s pointed in the correct direction. The narrower the field of view, the longer the range, and the smaller the area you’re actually monitoring.

Detection vs confirmation

Here’s where optical sensors fit in most architectures: they’re confirmation, not primary detection. A radar or RF system alerts on a potential drone at a specific location. The optical system slews to that bearing and zooms in. A human operator or AI processing confirms: yes, that’s a drone, and here’s the model.

Using optical sensors for primary detection is technically possible but practically difficult. You’d need multiple cameras covering 360 degrees, and you’d need software capable of scanning for small, fast-moving targets. The processing load is significant, and the false-alarm rate is higher than that of radar.

LZ TECH’s VAR300 is positioned as active optical detection, a system that scans for drones without needing an external cue. The technology exists. Whether it’s the right fit compared to radar-plus-optical depends on your threat model and budget.

Night and weather performance

Visible-light cameras work poorly at night. Thermal cameras work better; a drone’s motors and battery generate heat, but resolution is lower, and range drops. Fog, haze, and precipitation degrade both.

For 24-hour coverage, you need thermal as well as optical. That increases system complexity. A thermal camera with the resolution to identify drone models at a distance requires a significant investment. Add visible-light capability and a gimbal mount, and the per-position setup becomes one of the more expensive elements in a layered architecture.

The forensic value

Optical sensors provide something radar and RF can’t: evidence. A video recording of a drone crossing your perimeter is usable in prosecution in a way that a radar track isn’t. If you’re in a jurisdiction where legal action against drone operators is realistic, optical coverage matters for more than detection.

The LZ TECH T100 is the PTZ tracker designed for exactly this. 6.1 mm to 561 mm focal length range. Auto-tracking once a target is identified. Recording as evidence for after-action review.

Side-by-side comparison

Factor	RF Detection	Radar	Optical
Detection Range	2-5 km	3-10 km	0.5-3 km
Autonomous Drones	No	Yes	Yes (with cueing)
Identification	Model + Serial	None (track only)	Visual confirmation
Weather Independence	High	High	Low
Regulatory Burden	None (passive)	Transmission license	None

How to choose for your site

Start with your threat model

Every procurement decision starts with the same question: what are you actually defending against? The answer drives everything else.

If your primary threat is amateur operators, tourists flying DJI near your perimeter, hobbyists who don’t know better, RF detection is probably sufficient. These operators use stock equipment, transmit continuously, and aren’t trying to evade you. A well-specified RF system plus training gives you solid coverage.

If your threat model includes sophisticated operators, people who know you have counter-drone capability and are trying to get past it, you need more. Autonomous flight, modified protocols, and deliberate evasion all degrade RF effectiveness. Radar becomes necessary.

If your site has legal exposure, meaning prosecuting drone operators is realistic and useful, optical coverage matters for evidence collection. If prosecution isn’t on the table, optical is lower priority.

Layer for what matters

Most sites end up with layered coverage. RF as the primary detection layer. Radar to catch autonomous drones. Optical for confirmation and evidence. The question isn’t which single sensor to buy. It’s how much coverage you can afford and where to prioritize.

For fixed sites with real budgets: start with RF, add radar, confirm with optical. That’s the standard architecture, and it works for most threat models.

For limited budgets: RF first. Add radar if autonomous drones are a documented concern. Add optical if legal action against operators is realistic.

For mobile or temporary coverage: handheld RF detectors plus a portable camera system. The LZ TECH H3 Pro plus T100 gives you detection and confirmation in a package that fits in a vehicle.

The integration challenge

Buying sensors is easy. Making them work together isn’t. Each sensor generates alerts. Each alert needs to be correlated with alerts from other sensors. A drone that appears on radar at bearing 270 degrees and 2 km needs to match with the RF detection of a DJI Mavic at the same position, and the optical track that confirms the model.

That correlation happens in C2 software. If your C2 system can’t fuse the data, your operators are manually matching tracks. They’ll miss things under stress.

Before you buy sensors, evaluate the C2 layer. Can it ingest data from multiple vendor types? Does it support standard protocols like SAPIENT? Does it correlate tracks automatically, or does it just display three different alert streams?

The best sensor architecture in the world is useless if your C2 layer can’t make sense of the output.

A real example: airport perimeter protection

Let’s walk through how this works in practice. Say you’re protecting a regional airport, maybe 20 commercial flights per day plus general aviation. The budget is limited. You can’t afford a military-grade installation.

Your threat model: mostly amateur operators flying consumer drones near the approach path, with occasional sophisticated incursions that need detection and response.

Here’s how we’d spec it, starting from scratch.

Layer 1, RF detection. Fixed-site RF system covering the approach paths. 2-3 antenna positions with a clear line of sight. This catches 80-90% of your likely incursions, the hobbyists and tourists.

Layer 2, Radar. Single 3D radar positioned to cover the primary approach corridor. This catches autonomous flights and anything using modified protocols.

Layer 3, Optical. Two PTZ camera positions, one at each runway end. These confirm tracks and provide evidence for prosecution.

Start with RF and add layers as incidents prove the need. The architecture supports expansion.

What you don’t do: buy a single radar and expect it to solve everything. Or buy RF and get surprised when autonomous drones fly through. The threat model dictates the architecture, not the other way around.

The bottom line

RF detection is the entry point. It’s cost-effective, easy to deploy, and catches most amateur incursions. It doesn’t catch autonomous drones or sophisticated operators who know you’re listening.

Radar is for sites with real threat exposure. It sees everything in its coverage volume: autonomous, modified, or deliberately evasive. It requires a larger investment and regulatory approval, but it closes the biggest gap in RF-only coverage.

Optical is confirmation and evidence. It tells you what you’re looking at and records it for later use. It’s not primary detection, range and field of view are too limited, but it’s essential for prosecution and forensics.

The right answer is almost always layered. Start with RF, add radar when your threat model demands it, and overlay optical for confirmation. Match the technology to the actual threat, not to marketing claims about capabilities you’ll never use.

And evaluate the C2 layer as carefully as you evaluate sensors. A good integration layer with modest sensors outperforms great sensors with a C2 system that can’t correlate the data.

For airports around the world, drone incursions are no longer isolated incidents.Over the past few years, unauthorized drones have repeatedly disrupted runway operations, delayed flights, and raised serious concerns about aviation safety. What used to be considered a niche security issue has become a growing operational challenge for airport authorities and aviation regulators alike.Drone Incidents Are Changing the Security LandscapeIn December 2024, Stewart International Airport in New York temporarily shut down its runway after the Federal Aviation Administration reported a drone operating in the vicinity of the airport at approximately 9:30 p.m. on December 13. Flight operations were suspended for about one hour as a precaution. Although the disruption was relatively brief, the incident attracted national attention because it occurred amid a broader wave of drone sightings across the northeastern United States. Kathy Hochul publicly called for stronger federal counter-UAS support, emphasizing that even a single unidentified drone can force airport operators to halt runway activity and implement emergency procedures.In October 2025, Munich Airport suspended flight operations after several drones were reported near the airfield. According to airport and police statements, the first reports were received around 8:30 p.m. on October 2, with additional sightings continuing over the following hours. At 10:18 p.m., airport authorities began suspending operations, and both runways were fully closed shortly thereafter. Despite an extensive search involving local and federal police, the drone operators were not identified. The case highlighted how coordinated drone activity can disrupt one of Europe’s busiest airports and how difficult it remains to locate operators in real time. In November 2025, Brussels Airport temporarily halted operations following drone sightings near the airport. The disruption was part of a broader series of incidents that also affected Liège Airport and nearby military facilities. The Belgian government convened emergency meetings with national security officials, and European authorities described the events as evidence that drone incursions are becoming a serious threat to critical infrastructure. The incident underscored a growing concern across Europe: airports need continuous low-altitude surveillance and faster identification capabilities to distinguish between harmless sightings and genuine security risks.These recent incidents reveal a consistent pattern. In each case, airport authorities were forced to make operational decisions with limited information. They knew a drone might be present, but they often could not immediately determine the drone model, operator location, or threat level. That uncertainty—not just the drone itself—is what causes runway closures, flight delays, and significant economic losses. For airports, even a brief drone sighting can trigger:

Temporary runway closures

Flight delays and cancellations

Emergency response procedures

Significant financial losses

Reputational damage

As drone technology becomes more accessible and capable, airports are facing a difficult question: how can they monitor low-altitude airspace continuously without interfering with critical communication systems? Increasingly, the answer lies in passive counter-UAS technology.

Why Passive Detection Is Gaining Attention

The challenge is not simply detecting that a drone is present. Security teams need to know what type of drone it is, where it is located, and whether it represents a genuine threat. Traditional surveillance technologies such as radar and cameras remain important, but they are not always sufficient on their own. Passive RF detection offers a different approach. Instead of transmitting signals, passive systems listen for communication between drones and their controllers. This allows airports to detect and identify UAV activity without emitting electromagnetic energy or interfering with navigation and communication systems. For aviation environments, that is a major advantage. Passive systems can operate discreetly, continuously, and safely within highly sensitive electromagnetic environments.

From Signal Detection to Drone Identification

Detecting a signal is only the first step. The real value lies in understanding what that signal represents. Advanced technologies such as CRPC® (Cognitive Radio Protocol Cracking), developed by LZ TECH, make it possible to analyze drone communication protocols and extract detailed operational information. This enables security teams to identify drone models, distinguish authorized aircraft from suspicious ones, and determine both drone and pilot locations in real time. As new drone manufacturers and protocols continue to emerge, this level of protocol analysis is becoming increasingly important for effective counter-UAS operations.

A More Practical Approach to Airport Protection

Airports rarely rely on a single sensor. The most effective counter-UAS deployments combine multiple technologies, including:

Passive RF detection

Remote ID monitoring

Electro-optical tracking

Precision mitigation technologies

Centralized command and control

Together, these systems provide a clearer operational picture and help security personnel respond more confidently to drone-related incidents.

What Airport Operators Are Looking For in 2026

When evaluating counter-UAS systems, airport operators are placing greater emphasis on practical deployment considerations. Key requirements typically include:

Non-interference with existing communication systems

Accurate identification of drone models

Low false alarm rates

Scalable architecture

Centralized situational awareness

Passive detection platforms are increasingly aligned with these priorities, particularly when integrated into a broader layered defense strategy. As drone activity continues to grow, airport security is shifting from reactive incident response to persistent airspace awareness. The goal is no longer just to spot a drone. It is to understand who is flying it, what it is doing, and whether immediate action is required.

For airports, system integrators and aviation security agencies, passive counter-UAS technologies are becoming an essential part of that strategy. To learn more about airport-focused drone detection and mitigation solutions, visit LZ TECH’s Aviation Security Solutions.