Unknown or Invalid Airport Code
Hint #1: Airport code must be a 3 or 4 digit ICAO (e.g., AUS/KAUS) or FAA (e.g., 3R9 or CA35) code.
Hint #2: IATA codes are not currently supported (i.e., Tokyo/Narita’s ICAO code is RJAA, not NRT or KNRT).
message when I try to go to any part of tracking or airport info page. I have seen some new things showing the code may be switching to RTS, but that has the same problem.
The new NASR database was published the for release this morning, so the switch was flipped late last night. The IATA code for the airport is “RTS” now in the NASR database.
The breakage was just a byproduct of the awkward stage where an airport code is changed in some of the databases but not in all of the database. I’ve “fixed the glitch” but don’t be shocked if it breaks again in new, interesting ways when the next NASR database is rolled out (56 days from now) if the rest of the world hasn’t caught on to the new code yet.
The bottom line is that changing airport codes creates ripples of confusion throughout the flight tracking universe.