When a drone shows up over a crowd, a crime scene, a jail perimeter, or critical infrastructure, the first operational question is usually not "can we knock it down?" It is who is flying, and where are they standing?
For most state and local agencies, the lawful, fast answer starts with Remote ID—the broadcast many drones already send—plus a receiver that can hear it. Defeat options (jamming, takeover, kinetic) sit behind separate legal authorities such as SAFER SKIES certification. This guide stays on the locate the operator problem.
Not legal advice. Follow your agency policy, state law, and federal coordination rules.
What Remote ID actually gives you
Under FAA Part 89, most drones operating in the National Airspace System must identify themselves in real time. In the common broadcast mode, the aircraft emits messages over radio (commonly Wi-Fi and/or Bluetooth in consumer and many enterprise designs) that can include:
- A unique identifier for the aircraft / session
- Position and altitude of the aircraft
- Operator / takeoff location when the system provides it
- Timestamp and related status fields
If you can receive that broadcast, you often get a mapable aircraft track and a cue toward the pilot—without touching the control link and without jamming.
Remote ID is not magic. Non-compliant or darkened aircraft may not broadcast. Terrain, RF noise, and antenna placement matter. Treat it as the first sensor layer, not the only one. See how drone detection works and what affects Remote ID detection range for the mechanics.
Receivers vs lookup tools (DiSCVR and friends)
Do not confuse two different jobs:
- Receive — A Remote ID receiver (handheld, vehicle, rooftop, or fixed site) hears the broadcast in the field and shows aircraft and, when present, operator location in real time. This is what Z-SCAN and Z-SCAN MINI do.
- Lookup — Federal / portal tools such as FAA DiSCVR (and related law-enforcement channels) help authorized users resolve identity and registration after or alongside detection. Lookup does not replace a receiver. FAA materials themselves emphasize that DiSCVR is not a field detection sensor.
A clean mental model: MINI/Z-SCAN hear the sky; DiSCVR helps you name what you heard when your access and the data support it.
That split also explains why a portal login is not a substitute for putting a receiver on the person or rooftop that owns the problem. Lookup happens after something was heard, photographed, or reported. Receive happens while the aircraft is still in the air.
A practical police workflow
1. Detect early. Put a receiver on the person, vehicle, or rooftop that owns the problem (event perimeter, DOC fence line, command post). Alerts beat eye-witness panic.
2. Correlate aircraft and operator location. When the broadcast includes operator / takeoff position, push that pin to the unit that can move. When it does not, use aircraft track, line-of-sight, cameras, and witnesses—still without jamming.
3. Document. Preserve tracks, screenshots, and exportable logs. Prosecutors and after-action reviews need time-synced evidence, not verbal "we saw a drone."
4. Decide the response lane.
- Observe / contact / cite under existing authorities
- Hold for federal partners if the threat escalates
- Only if your agency is certified and equipped under frameworks like SAFER SKIES, consider Detection and Warning or Mitigation tools on the federal authorized lists
Most shifts will end in lane one or two. That is fine. The receiver still earned its keep.
What not to do
- Do not assume you can jam because a drone is annoying. Unauthorized interference with radio communications and aircraft is a federal problem.
- Do not buy "drone killer" marketing for a locate-the-pilot job.
- Do not skip training on how your receiver displays operator location vs aircraft location—mixed pins create bad pursuits.
Where Zing fits
- Z-SCAN MINI — portable Remote ID detection for patrol, event teams, and mutual-aid kits. Cloud-connected awareness, alerts, and a 30-day trial so the agency can prove the workflow before budget season.
- Z-SCAN — site-scale coverage when the problem is a fixed facility (jail, plant, stadium infrastructure) rather than a single squad.
- Airspace Platform — shared picture across shifts and agencies without turning every sergeant into a systems admin.
Zing products receive and display. They do not jam, disable, or take over aircraft. Operator contact and enforcement stay with sworn personnel and policy.
Corrections and public safety
Jails and prisons see drones used for contraband and surveillance. The locate problem is the same; the perimeter is just fixed. Pair this guide with correctional facility deployments and, where relevant, the SAFER SKIES path for certified C-UAS later. Passive receive-and-log still comes first.
The same pattern shows up in public safety work: a crime scene, a crowd, or a sensitive operation needs to know what is overhead without pulling the whole detail off the ground problem. A receiver on the command post or a MINI on a supervisor's belt answers the first question. Response stays with the agency.
What this looks like in the field
Zing's public deployments are Remote ID awareness jobs, not defeat jobs. Z-SCAN is in use at multiple Oregon Department of Corrections facilities, at Salinas Airport in California, and Zing placed first (with a $100k prize) at the Proven in Pendleton Counter-UAS Challenge. Those sites still need a locate-and-document workflow: hear the broadcast, map the aircraft, and—when the message includes it—cue a unit toward the operator.
That is also why a 30-day Z-SCAN MINI trial exists. An agency can run the workflow on its own airspace—patrol, event, or fence line—before it writes a capital request or starts a certification packet.
If the site is a fixed facility preparing a Section 2209 / UAFR conversation, the same receive-and-log habit is the baseline. Police and corrections partners often share that picture even when the paperwork sits with the facility.