DEF-007: C-UAS Evidence Assurance

A radar cue and its own echo can look like two confirmations.

A radar detects a small aerial object and cues an EO/IR camera to slew onto it. The camera confirms a visual track. Two sensors, two readings — evidence looks doubled. But the EO/IR confirmation only exists because the radar told it where to look. If the radar's initial detection was itself marginal — a bird, a reflection, a processing artifact — the "second" confirmation is the same uncertain detection, observed again from a pointing instruction the first sensor gave it. One effective witness, counted as two.

A missing transponder isn't an answer, it's a gap.

Most cooperative aircraft broadcast Remote ID. An object without it can look like the threat category on a dashboard built to treat "no ID" as a red flag — but a missing transponder can mean a threat, a technical failure, an authorized platform outside the registry, or something else entirely. Converting that absence into a hostile classification skips the judgment an operator is actually accountable for making.

Scenario: A slow-moving contact appears near the perimeter fence at low altitude.

Radar picks up a contact and reports 87% confidence. The system automatically slews an EO/IR camera to the radar's exact bearing. The camera locks on and confirms a visual. The console now shows: Radar — CONTACT (87%). EO/IR — CONFIRMED. Two sensors, two green lights.

WITHOUT this check: The console reports "2/2 sensors confirm — HIGH CONFIDENCE TRACK." The operator escalates based on what looks like independent double-confirmation. But the EO/IR camera never searched the sky on its own — it looked exactly where the radar pointed it. If that 87% radar reading was actually a large bird catching the wind, the camera dutifully "confirmed" a bird, because a bird is the only thing it was ever pointed at.

WITH this check: The system flags that the EO/IR detection is cue-dependent on the radar detection — not a second, independent witness. The track is reported as 1 INDEPENDENT SOURCE — CUE-FOLLOWING CONFIRMATION, not 2/2 CONFIRMED, so the operator sees the real evidence picture instead of an inflated one.

A second pattern worth knowing: the drone with no ID isn't automatically the one to worry about.

A contact with no Remote ID signal could be hostile — or it could be a dead transponder battery, an older unregistered hobbyist model, or an authorized platform operating outside the registry for a mundane reason. A system that quietly treats "no signal" as "confirmed hostile" will eventually escalate a lost hobbyist drone over a training field the same way it would escalate a real threat. This keeps "unknown" honestly labeled as unknown, until protected-asset proximity, flight pattern, or timing gives an operator something real to reason about.