What is drone Remote ID — and how do you receive it?
Remote ID is a short radio message that compliant drones broadcast continuously while flying — a “digital licence plate” readable by anyone with the right receiver. This page explains what it contains, how it is transmitted, and what you need to pick it up.
What is drone Remote ID?
Remote ID is a regulatory requirement for drones to continuously broadcast their identity and position over radio while in flight, so that anyone nearby can identify the aircraft and see where it and its operator are. It is often described as a digital licence plate for drones.
Two technical standards define the message format in practice: ASTM F3411 (used for the FAA's rules in the United States) and ASD-STAN prEN 4709-002 (used for Direct Remote ID in the European Union). The two are closely aligned, which is why a single receiver can generally handle both.
Remote ID comes in two forms. Broadcast Remote ID is transmitted directly over the air to anyone in range, with no internet connection involved, and is unencrypted by design — public readability is the entire point of the rule. This is the form a local receiver such as D.A.R.S. picks up. Network Remote ID instead reports the aircraft's identity and position over an internet connection to a service provider; it is already in operational use and expanding, but it cannot be received off-air locally.
What information does Remote ID broadcast?
A Remote ID broadcast carries the drone's serial or registration ID, its live GPS position, altitude and speed, the take-off or operator location, and an optional free-text description — split across several defined message types.
| Message type | What it carries |
|---|---|
| Basic ID | Drone serial number or registration ID, and UA type |
| Location / Vector | Live latitude, longitude, altitude, speed, heading |
| Authentication | Optional signature data for verifying the message |
| Self ID | Optional free-text description of the flight |
| System | Operator / take-off location and related data |
| Operator ID | Operator's registration identifier |
Not every drone sends every message type, and some fields are optional or may be left empty. In practice a receiver builds a picture of each aircraft by collecting whichever messages that drone actually transmits and merging them per aircraft.
How is Remote ID transmitted?
Remote ID is broadcast over ordinary consumer radio: Bluetooth Low Energy advertisements, or WiFi (Beacon frames and WiFi NAN). Which one a given drone uses depends on its manufacturer and model — there is no single universal method.
- Bluetooth Legacy (BLE 4.x) — advertising packets on 2.4 GHz. Very widely used.
- Bluetooth Long Range (BLE 5.x Coded PHY) — same band, greater range.
- WiFi Beacon — Remote ID embedded in a vendor-specific information element inside a beacon frame.
- WiFi NAN (Neighbor Awareness Networking) — a WiFi-based neighbourhood discovery mechanism.
This fragmentation is the single biggest practical problem when receiving Remote ID: a receiver that only listens on Bluetooth will silently miss every WiFi-broadcasting drone in the area, and vice versa. Coverage of both transports is what determines how much of the local traffic you actually see.
Note on bands. Bluetooth Remote ID is always 2.4 GHz. WiFi Remote ID may be broadcast on 2.4 GHz or 5 GHz depending on the aircraft, so a 2.4 GHz-only receiver — which covers the large majority of traffic today — will not see drones that broadcast exclusively on 5 GHz.
How do you receive Remote ID signals?
You need a radio that can listen passively on 2.4 GHz for both BLE advertisements and WiFi frames, decode the Remote ID payload inside them, and present the result. Receiving is entirely passive — nothing is transmitted at the drone.
The receiving chain has three stages:
- Capture — put a WiFi radio into monitor/promiscuous mode to see beacon frames not addressed to you, and run a BLE scan for advertisements.
- Decode — find the Remote ID vendor-specific element or BLE service data, then parse the fixed-size message structures out of it.
- Present — merge messages per aircraft and display them on a map or list, typically on a phone.
D.A.R.S. performs all three: it turns an M5Stack Unit C6L into a passive receiver that scans WiFi and Bluetooth simultaneously and relays every detection to an Android app over an encrypted Bluetooth LE link.
Is a phone app enough, or do you need dedicated hardware?
A phone alone can pick up some Remote ID, but it is limited by its own radios. Most phones cannot put their WiFi chip into the monitor mode needed to capture WiFi Beacon Remote ID, so a phone-only setup typically sees the Bluetooth half of the traffic and misses the WiFi half.
A dedicated receiver exists to remove that limitation: it does the promiscuous WiFi capture the phone cannot, scans Bluetooth at the same time, and hands the combined feed to the phone — which is then just a screen, not the radio. That is the entire reason external Remote ID receivers exist.
What range can you expect from a Remote ID receiver?
Realistically a few hundred metres in built-up areas, extending toward roughly a kilometre with clear line of sight. Remote ID uses low-power consumer radio, so range depends far more on obstructions and antenna placement than on the receiver.
Because the drone is usually airborne with an unobstructed path to the ground, real reception is often better than the same link would be at ground level. Anything claiming multi-kilometre guaranteed Remote ID reception should be treated sceptically — the limiting factor is the drone's transmitter, not your receiver.
Does Remote ID detection work with DJI drones?
Yes, for DJI aircraft that broadcast standards-compliant Remote ID — which covers models built to meet the FAA and EU requirements. It does not cover DJI's older proprietary “DroneID” telemetry, which is a different, separate protocol.
This distinction matters and is often blurred in marketing. Standards-based Remote ID (ASTM F3411 / ASD-STAN) is what compliant drones broadcast over WiFi and Bluetooth, and is what a Remote ID receiver decodes. DJI's legacy proprietary telemetry rode on its OcuSync control link and is not the same signal. If a drone is old enough, region-specific enough, or has been modified so that it does not broadcast standard Remote ID, no Remote ID receiver will see it.
Is it legal to receive Remote ID broadcasts?
Receiving Remote ID is generally lawful, because the broadcasts are unencrypted and intended to be publicly readable — that is the stated purpose of the regulation. A passive receiver transmits nothing and does not interfere with the aircraft.
Two caveats worth stating plainly. First, radio, privacy and data-protection law varies by country, and what you subsequently do with collected data (storing it, publishing it, combining it with other records) can be regulated even where reception is not. Second, this is general information and not legal advice — if you intend to operate at scale or commercially, check your local rules.
Reception is not interception. Remote ID is a public safety broadcast, deliberately sent in the clear. Decoding it is categorically different from attempting to access a drone's encrypted control link, which is unlawful in most jurisdictions and which D.A.R.S. does not do.
How is Remote ID detection different from radar or RF drone detection?
Remote ID detection reads a cooperative broadcast the drone chooses to send, so it gives you identity and exact GPS position cheaply. Radar and RF-signature systems detect uncooperative aircraft that are not broadcasting, but cost far more and rarely give you an identity.
| Approach | Sees non-broadcasting drones | Gives identity | Typical cost |
|---|---|---|---|
| Remote ID receiver | No | Yes — ID, operator location | Low |
| RF signature detection | Yes | Rarely — model class at best | High |
| Radar | Yes | No | Very high |
| Acoustic | Yes | No | Medium, short range |
For the everyday question a drone pilot actually has — “who else is flying here right now, and where is their operator?” — Remote ID is the direct answer, and by a wide margin the cheapest one. It is not a counter-drone system and does not claim to be: a drone that is not broadcasting Remote ID is invisible to it.
Frequently asked questions
Do all drones broadcast Remote ID?
No. Only drones that are required to comply and are actually configured to do so. Requirements depend on jurisdiction, aircraft weight and class, and when the aircraft was built. Home-built, exempt, very light, or deliberately non-compliant aircraft will not appear.
Does receiving Remote ID require an internet connection?
No. Broadcast Remote ID is a direct radio transmission from the aircraft. Reception works fully offline, which is one of its practical advantages in the field.
Can the drone operator tell that I am receiving their Remote ID?
No. Reception is entirely passive — the receiver only listens and never transmits anything to the aircraft, so there is nothing for the operator to detect.
Can I see where the pilot is standing?
Often yes. The System message carries the operator or take-off location, so when a drone transmits it you can see roughly where the aircraft is being flown from. Not every drone populates this field.
What is the difference between Broadcast and Network Remote ID?
Broadcast Remote ID is sent over local radio directly from the aircraft, so anyone nearby with a receiver can read it offline. Network Remote ID reports identity and position over an internet connection to a service provider, where it is accessed through that service rather than off-air.
Both are real and in use. The United States dropped the network requirement from the FAA's final rule, leaving broadcast as the US mandate — which is why broadcast is often described as “the” Remote ID. In Europe the picture is different: Switzerland already operates network identification, and network identification is a defined service under the EU's U-space regulatory framework, so its role grows as U-space airspace is designated.
What this means for a receiver. A local Remote ID receiver can only see the broadcast transmission — network Remote ID travels over the internet to a service provider and never touches your antenna. The two are complementary, not alternatives.
Go deeper on Remote ID
Focused guides on how Remote ID works, how to receive it, and the rules around it.
How it works
Receiving it
Trust, rules & use
Receive Remote ID yourself
D.A.R.S. turns an M5Stack Unit C6L into a passive WiFi + Bluetooth Remote ID receiver, with a live feed to your Android phone. One-time €34, per device.
See D.A.R.S. →