ADS-B and Remote ID drones around your airport, and the pilots flying them, on the same map as your aircraft
RunwayStats has always tracked ADS-B-equipped drones with the same receivers that track your aircraft. Now a dedicated Remote ID receiver adds the drones that don't carry ADS-B, which is most of them, and turns every broadcast into live, recorded, alertable data inside the dashboard you already use. See the drone, see the pilot, and know the moment a drone is somewhere the FAA has restricted.
Drone detection isn't reserved for hubs and towered fields. Any RunwayStats airport can add it, from a small GA field to a commercial service airport.
Every Remote ID drone position is checked against FAA UAS Facility Maps and National Security UAS Flight Restrictions, so alerts flag real airspace problems, not just any drone nearby.
Drones and manned aircraft live in the same record, with the same filters, reports, and playback. No separate system, no extra login.
See Them, Track Them, And Get Alerted, Inside The Dashboard You Already Use
Some drones carry ADS-B, and RunwayStats has always tracked them right alongside your manned traffic. Most don't, but Remote ID requires them to broadcast who they are, where they are, and where their pilot is standing, and most airports still have no way to hear it. RunwayStats listens for both and turns them into the same live, recorded, alertable data you already rely on for manned traffic: no separate security console, no extra login, and no guessing about where drones are allowed.
ADS-B and Remote ID drones appear on your live map alongside every aircraft and ground vehicle, with the pilot's location plotted next to each Remote ID drone. Drone markers show height above ground and MSL, and the active target count breaks out aircraft, vehicles, and drones at a glance.
Every Remote ID drone position is checked against FAA data around your airport. When an airborne drone enters a National Security UAS Flight Restriction, an active part-time restriction, or climbs above the ceiling the FAA's UAS Facility Map sets for its grid cell, your contacts get a text and email with a link to the drone's track, the pilot's location, and the restricted area on one map.
Toggle the FAA's own drone airspace data right on the live view and playback maps, so anyone on staff can see at a glance where drones can and can't fly, and how high.
Each drone flight is logged as its own operation with the full drone track, the pilot's track, and an altitude profile. Replay any incident in Playback alongside the manned traffic flying at the same moment, then share the facts with law enforcement or your board.
Filter heat maps to drones and the patterns appear: where drones fly most, the corridors they repeat, and how close they get to your approach paths. Analytics and the operations list include a Drone/UAS category, so you can trend drone activity over time and target outreach where it matters.
Draw your own areas, like runway approaches, the ramp, the fuel farm, or the stadium next door, and set custom notifications for drones that enter them. Area tracking logs every drone that passes through, so you have a record for every zone that matters.
Standalone counter-drone systems give a security desk one more screen to watch. RunwayStats puts drones in the same record as every takeoff and landing, so when a drone shows up near final, you see the drone, the pilot, and the aircraft on approach together, then replay it, report it, and alert on it with the tools your team already knows.
A Receiver, A Broadcast, And Your Dashboard
Your RunwayStats ADS-B receiver already tracks ADS-B-equipped drones. A dedicated Remote ID receiver is added alongside it, listening for the broadcasts the FAA requires most drones to send.
ADS-B drones broadcast their position, altitude, and speed like any aircraft. Remote ID broadcasts add the drone's ID and the pilot's control station or takeoff location.
Drones appear in the live view, playback, operations, analytics, heat maps, and notifications you already use, checked against FAA airspace data around the clock.
Drone data works with the rest of the platform: airport operations tracking for every manned flight on the same map, custom area tracking and notifications for the zones you care about, and statewide programs for state aviation offices overseeing many airports.
Remote ID, Pilots, Alerts, And Hardware
Remote ID is the FAA rule (14 CFR Part 89) that requires most drones flying in U.S. airspace to broadcast their identity, position, altitude, speed, and the location of the pilot's control station or takeoff point. It works like a digital license plate. RunwayStats receives those broadcasts at your airport and puts every drone on your map.
Yes, and it always has. Drones equipped with ADS-B are picked up by the same RunwayStats receivers that track your manned aircraft, with no extra hardware, and they show on the live map as drones. The Remote ID receiver adds the much larger group of drones that don't carry ADS-B.
Any drone broadcasting ADS-B or Remote ID. Remote ID can be built in (Standard Remote ID) or added with a broadcast module, and it is required for every drone that must be registered with the FAA, which includes all commercially flown drones and recreational drones over 250 grams. Drones that broadcast neither, such as those flown inside FAA-Recognized Identification Areas (FRIAs) or flown illegally without Remote ID, cannot be detected. RunwayStats shows FRIAs on the map so you know where those flights are allowed.
Yes. Drones with Standard Remote ID broadcast the location of the pilot's control station, and RunwayStats plots it alongside the drone, with its own track on the flight's detail page. Drones using an add-on broadcast module report their takeoff location instead. ADS-B does not carry pilot location, so ADS-B-only drones show the drone without a pilot marker.
RunwayStats checks every Remote ID drone position against FAA data, including National Security UAS Flight Restrictions (part-time restrictions while they are active) and UAS Facility Map ceilings. When an airborne drone is inside a restriction, or above the highest altitude the FAA will automatically authorize in that facility map grid cell, your contacts get an email and text message with a link to a map of the drone's track, the pilot's location, and the restricted area. You can also draw your own areas, such as runway approaches or the ramp, and get alerted when a drone enters them.
Not for ADS-B drones: your existing RunwayStats receivers already track them. For Remote ID, a dedicated Remote ID receiver is added to the RunwayStats system at your airport. From there it is seamless: drones appear in the same live view, playback, operations, analytics, heat maps, and notifications you already use, with no separate login or extra screen.
Every drone flight is logged as its own record, and Remote ID drones carry a Drone/UAS aircraft type. Drone/UAS filters on the operations, analytics, heat map, live view, and playback pages let you isolate drone activity or leave it out.
No. RunwayStats detects, tracks, records, and alerts. Disabling or taking control of a drone is tightly restricted by federal law to authorized agencies. RunwayStats gives your staff and law enforcement the drone's track and the pilot's location so they can respond quickly and appropriately.
No. Drone Detection is available as a Tier Add On at any RunwayStats airport, from small general aviation fields to commercial service airports. Small and non-towered airports often have no one else watching the sky around them.
We'll show you real Remote ID drones on a live RunwayStats airport: the drone, the pilot, the FAA airspace around them, and the alert your team would have received.
