Remote ID
Remote ID is a broadcast identification signal from compliant drones. Receiving it is the cheapest form of airspace awareness available, and it only shows the operators who are complying.
Key facts
- Remote ID requires most drones operating in US airspace to broadcast identification and location information that anyone nearby can receive.
- The broadcast typically includes an identifier for the aircraft, its position and altitude, and the position of its control station or take-off point.
- Receiving Remote ID needs no licence and no transmission, and receivers are inexpensive compared with radar or RF detection equipment.
- Remote ID shows compliant operators. An aircraft that is not broadcasting, whether through non-compliance, modification or age, does not appear.
- It is therefore a traffic awareness tool rather than a security control, and a site relying on it alone would see the careless operator and miss the deliberate one.
- The identifier can be linked to registration information by authorised parties, which makes Remote ID data useful in a report to law enforcement.
What Remote ID does
Remote ID requires most drones operating in US airspace to broadcast who and where they are. The broadcast is received locally by anything listening nearby, rather than being reported to a central service, and it usually carries an identifier for the aircraft, its position and altitude, and the location of the control station or the point it took off from.
The intent is to give airspace participants and authorities a way to tell one aircraft from another. Compared with the alternatives it is very cheap to receive: no transmission, no authorisation, and modest equipment cost.
What it is good for
Three things, and they are worth being specific about.
The first is a baseline. A site that receives Remote ID for a few weeks learns what normal looks like overhead, including regular commercial operators, surveying work and local hobbyist activity. That makes an unusual flight easier to recognise when it happens.
The second is the operator location. Remote ID includes the control station or take-off position, which is the part of the picture a site can act on through law enforcement.
The third is the record. A report to an agency carrying an aircraft identifier, a position track and a time is materially more useful than one describing a drone that someone saw.
What it does not cover
Remote ID reports only the aircraft that are broadcasting. An aircraft that is not broadcasting, whether through non-compliance, modification or age, will not appear.
Avoiding the broadcast is straightforward for anyone with a reason for it, and the flights most sites are concerned with come from exactly those operators. A facility relying on Remote ID alone would have good visibility of lawful activity and none of the flight it actually needed to see.
This is why Remote ID is best described as airspace awareness rather than airspace security. It belongs in the picture, and it cannot be the whole of it.
Where it fits
For most sites, Remote ID reception is a sensible first layer and a poor last one. It is inexpensive enough to justify before a full detection programme, and it produces useful baseline data during the period a site is deciding what else it needs.
Where a site has a specific concern about deliberate intrusion, the requirement moves to detecting the aircraft itself rather than its cooperation, which means radar, RF or both.
Related work
FAQ
▸If drones must broadcast Remote ID, why does a site need anything else?
Because the requirement binds operators who follow it. Someone flying contraband into a correctional facility or conducting reconnaissance of a substation has no reason to comply, and disabling or avoiding the broadcast is within reach. Remote ID gives a clear picture of lawful activity and very little about the activity most sites are concerned with.
▸What can we actually do with Remote ID data?
Several useful things. It establishes a baseline of normal activity over a site, which makes an unusual flight easier to recognise. It provides the take-off or control station location, which is where an operator can be approached. And it produces a record that supports a report to an agency.
▸Is a Remote ID receiver worth buying on its own?
For a site with no budget and no current capability it is a reasonable first step, because it is inexpensive and provides real information. It should be understood as awareness rather than protection, and a site that later needs detection of non-compliant aircraft will need radar or RF in addition.
▸Does receiving Remote ID raise privacy questions?
The broadcast is designed to be publicly receivable, so receiving it is not comparable to intercepting a private transmission. Retention and use of the resulting records still deserve a policy, particularly where the data identifies individuals operating lawfully near a site.