Drone ID on the Wire RF Detection, Spoofing, and the Limits of Awareness

The talk opens with a practical problem: drones are active over wildfires, large events and protected sites, and defenders need to know what they look like on the radio spectrum. The speaker explains that Remote ID, the FAA-mandated beacon, is a one-way, unencrypted and unauthenticated broadcast carrying a serial number, position, altitude, speed and often the operator's location. The standard fixes the payload but not the waveform, so vendors transmit over Bluetooth or Wi-Fi in different ways, and a detector needs several radios to cover them.

The middle section covers what a cheap monitor-mode Wi-Fi board and Wireshark can capture. A single sensor on Treasure Island logged 55 flights in one weekend. The talk then walks through DJI's OcuSync link, which hops between 2.4 and 5.8 GHz and could be decoded until a protocol change cut off older Aeroscope units. Analog FPV video, MAVLink telemetry and direction finding on 900 MHz links are easier to pick up. Because no message is authenticated, recorded frames can be replayed and identities spoofed, and a single drone can even be used to flood a sensor with fake tracks.

The closing takeaway is that every drone should be treated as a threat until identified, and that RF detection works best when fused with radar and optical sensors. Autonomous waypoint flights, fiber-tethered drones and LTE-controlled drones remain invisible to RF sensing, and jamming tends to be wideband. The speaker argues that authenticated Remote ID is needed before drones can safely share airspace.