Why some drones show up late, or with missing details

A DJI drone appears a kilometre away, while another drone only pops up when it's almost overhead — or arrives without a pilot location. Often the receiver isn't the problem: the drone's Remote ID is.

Free to download. Optional Silver, Gold and Platinum subscriptions. · Last updated: 2026-10-10

Not every Remote ID is equal

Every drone that broadcasts Remote ID is supposed to be readable by an ordinary phone, from a reasonable distance, with the same set of fields. The big brands mostly get this right. Outside them, the quality of Remote ID varies a lot — from cheap drones and add-on modules to self-built aircraft. BlueMark, the company behind DroneScout, looked into this in 2024 and found products on sale in the US with an FAA-accepted Declaration of Compliance that still didn't meet the rules (the full analysis). An accepted declaration means the manufacturer declared compliance; it isn't proof that the product complies.

Below are the problems we see most, and how they look in DroneScout.

Weak transmitter: the drone appears only close by

Remote ID transmitters have a minimum output power. Some modules transmit at roughly half that minimum or less, according to their own radio test documents. Every halving of power cuts the distance at which you can receive a drone by about 30 % in open air — and a lot more with trees and buildings in between.

In DroneScout: the drone appears only within tens of metres, with a low signal strength (RSSI) even when it's close, while other drones show up much further away.

Poor antenna: the drone comes and goes

A small antenna squeezed onto a module rarely sends equally well in every direction. Some designs have deep gaps in certain directions, where the signal is a small fraction of its peak. As the drone turns, it disappears and reappears.

In DroneScout: last seen keeps jumping back, and the track has gaps, although the drone is in range and in view.

Missing transports: some receivers never see the drone

The rules allow several radio transports: Bluetooth Legacy, Bluetooth Long Range, Wi-Fi Beacon and Wi-Fi NaN. A drone that broadcasts on only one of them is invisible to receivers that don't support that one — and an iPhone receives only Bluetooth Legacy. Some modules also use a Bluetooth advertising type the standard doesn't allow, which some receivers filter out.

In DroneScout: the drone shows up on one phone but not another. The Type field in its details shows the transport it arrived on. DroneScout Bridge receives all transports and passes them on as Bluetooth Legacy, which every phone receives.

Wrong or drifting position

The FAA rules require the reported positions to be accurate to about 30 m (100 ft). In one test flight, a module reported a take-off position that moved more than 300 m.

In DroneScout: the pilot or take-off icon wanders around the map, or sits far from where the drone actually took off.

Empty or invalid fields

Some fields are left empty, filled with a placeholder, or wrongly formatted:

• No operator registration number. Required in the EU, the UK and Singapore, but often never entered by the pilot — the most common gap we see.
• No pilot location. Add-on broadcast modules send the take-off point instead of the pilot's position, which is allowed for them, but some send neither.
• A serial number in the wrong format, or a session ID that changes every flight, which makes it hard to recognise the drone again.
• No altitude, or the wrong altitude reference — the US asks for altitude above sea level, the EU for height above the take-off point.
• No timestamp, so you can't tell how old the position is.

In DroneScout: a warning sign instead of the green check next to Compliant in the drone's details, and empty fields in the Full tab. A message type with a packet count that stays at zero is never being sent. More: Test your own drone's Remote ID.

Not always the drone's fault

Before blaming a drone, rule out the receiver:

• DJI drones broadcast only once they're airborne, and only in countries where Remote ID is mandatory.
• Android limits Wi-Fi scanning to about twice a minute, so drones that broadcast only Wi-Fi Beacon — like DJI — update slowly. See See more drones on Android.
• iPhones can't receive Bluetooth Long Range or Wi-Fi Remote ID at all. See Remote ID on iPhone.
• Buildings, hills and bodies block the signal; hold the phone up, in the open.

What you can do

• As a pilot or buyer: ask whether the Remote ID module was independently tested, keep its firmware up to date, and make sure you can see its status before you take off.
• As a manufacturer or builder: test your broadcast with a receiver in the field, not just on the bench — Test your own drone's Remote ID.
• As anyone: if a drone shows up late with a weak signal, it's probably the drone. With DroneScout Bridge you see every transport, up to about 2 km.