Here's another oddity.
Approx 1140utc dec1, there was a flight near new orleans by n511uw. Which appears to be Airmed services llc. (A..m..d?). But the callsign transmitted appears to be it's reg.
Enter zk-hgu. (Who have a local callsign use of AMDx) Who, looking at its flight playback list, completed a flight between the US and NZ at warp9, completing some auto route data. And later a static position playback flight matching n511uw location at the above time - but with clear callsign AMD6
(With a vrate of -30,000 fpm...)
Can't put a finger on the how here. It's not like n511uw is using a miscoded transponder. Or appears to be transmitting an AMD callsign. Or being spoofed. Unless the 2nd box is and being matched wrong?
Or is this the route table being funny since there are multiple instances of AMD (also south africa red cross mercy flight) used around the globe. And it was later set aside for use in new Zealand.
Approx 1140utc dec1, there was a flight near new orleans by n511uw. Which appears to be Airmed services llc. (A..m..d?). But the callsign transmitted appears to be it's reg.
Enter zk-hgu. (Who have a local callsign use of AMDx) Who, looking at its flight playback list, completed a flight between the US and NZ at warp9, completing some auto route data. And later a static position playback flight matching n511uw location at the above time - but with clear callsign AMD6
(With a vrate of -30,000 fpm...)
Can't put a finger on the how here. It's not like n511uw is using a miscoded transponder. Or appears to be transmitting an AMD callsign. Or being spoofed. Unless the 2nd box is and being matched wrong?
Or is this the route table being funny since there are multiple instances of AMD (also south africa red cross mercy flight) used around the globe. And it was later set aside for use in new Zealand.
Comment