. |
/O\
\_______[|(.)|]_______/
o ++ O ++ o
With these airframes, the words "correct id" take on a completely new meaning...Gerard wrote:Freedar.uk showed the correct id 02-5001 (ADS-B: 99-4163)
Inb Mildenhall. Was just up trying to contact Mildenhall CP on both 313.550 and 300.800 (and atc wise 125.005 -> 132.205 -> 1281.60 -> 135.425, Idesi-Lapra and in the descent)Melchior Timmers wrote:AE0433 /02-5001 showing ETAR to CONUS again (now above Belgium)
09001 given serial at FC. Readed of on landing at Mildenhall.Melchior Timmers wrote:AE0433 /02-5001 showing ETAR to CONUS again (now above Belgium)
Ah, thanks. Then they were wrong in my database as well.n5205e00421 wrote:At ADSBexchange the hexcode-tieups changed from correct to wrong some time ago. AE0433 has always been 02-5001 and AE0446 has always been 99-6143 in real life. I have posted it on their forum but it has not been changed so far.
L.
But not with te correct serial on adsb. Adsb showed 99-6143AK01 wrote:There's something going wrong here. AE0443/ 09001 flew Ramstein Mildenhall this morning, not AE0433. AE0433/ 25001 flew Ramstein Conus yesterday.
An aircraft does not transmit its serial/registration on Mode-S/ADS-B, only its hexcode. It is up to a receiver or website to show the correct serial for that hexcode. ADSB-exchange had it wrong in its database here. E.g. Planefinder just showed 99-6143 correctly for hexcode AE0446..Rabbit wrote:But not with te correct serial on adsb. Adsb showed 99-6143
As a member you get access to all our
premium content and benefits learn more