flightaware.com/live/airport/PAUN
It is a valid airport, as shown by
flightaware.com/resources/airport/PAUN with information/procedures/etc
But the daily arrival graph says no such airport.
This appears to be the case for any alaska airport where the 3 letters of the IATA code don’t match up
flightaware.com/live/airport/PADL - also broken
flightaware.com/live/airport/PANC - works fine
Any theories?
I’m still trying to sort out why nobody out of PANC going to other alaskan destinations files flight plans correctly, it looks like they are all filed with K + the 3 digit ATA code instead of the proper P*** code. I wonder where exactly the process is breaking down?
Now this is interesting:
flightaware.com/live/flight/NAC6 … /PANC/KKSM
But on this map KKSM is plotted at the place where PASM is… which is what this airport is: flightaware.com/live/airport/PASM
Problem also exists at:
flightaware.com/live/flight/CPT7 … /PJHM/PHNL
I tried searching, but couldn’t find something apropos. My apologies if I missed a previous discussion.
emoticon.