Why Some Aircraft on ADS-B Exchange Show No Registration, Type, or ICAO Hex

ADS-B Exchange displays "n/a" for registration, type, and ICAO hex when the aircraft's transmitted identifier can't be matched to a known airframe. The site's own field notes point to four recurring causes: a non-ICAO hex ID that is dynamic and can't be connected to a type or registration, an anonymized MLAT result, an ATC contact broadcast, or a target that isn't an aircraft at all (ground vehicles and non-ICAO targets are separate map categories). In each case the data you see is real — it's the identity link that's missing.

The identifier itself may not be a real ICAO address

Every aircraft broadcasting ADS-B normally carries a 24-bit ICAO address that maps to a registration and type in public databases. ADS-B Exchange flags two situations where that mapping fails:

• Non-ICAO hex, info: Anonymized MLAT result — the position was calculated by multilateration rather than read from a GPS source, and the identifier has been deliberately obscured.
• Non-ICAO hex, info: ATC contact broadcast — the hex value came from an air-traffic-control contact rather than a standard ADS-B identity broadcast.

The site states plainly that a non-ICAO hex ID "is dynamic and can't be connected to a type or registration." A dynamic ID means the same value may not belong to the same aircraft on a later flight, so even a database lookup wouldn't give you a stable answer.

MLAT needs four receivers — and often a Mode S transponder

MLAT (multilateration) works by timing the same signal at multiple ground receivers. ADS-B Exchange notes that MLAT requires the contact to have a Mode S transponder and reception by 4 receivers. Two consequences follow:

• Aircraft that only transmit ADS-B without a Mode S transponder, or that are heard by fewer than four receivers, may appear with incomplete or absent position data.
• An anonymized MLAT result is often "the corresponding MLAT contact for the same aircraft" — meaning the same flight may show up under more than one identifier, one of which carries no registration.

UAVs and ground targets are handled differently

Two categories sit outside normal aircraft identification:

For UAVs, the absence of registration and type is expected unless the operator has registered the aircraft with the site. Ground vehicles and non-ICAO targets are filtered as separate layers, so they aren't meant to resolve to an airframe at all.

What this means when you're looking at a specific contact

If you open an aircraft page and see Reg.: n/a, Type code: n/a, and a hex flagged as non-ICAO, treat the identity as unresolved rather than wrong. You can still use the spatial and flight-activity panels — altitude, speed, track, squawk, message rate, and history — because those come from the received signal, not from a registration database. The site also notes that hovering over each data label explains what that Mode S field means, which is the fastest way to confirm whether a blank field is an identity gap or simply a value the aircraft never transmitted.

One practical caveat: a dynamic hex ID can't be used to follow the same airframe across days. If you need to track a specific aircraft, rely on a stable ICAO address where one is present, and treat anonymized MLAT contacts as position-only.