One example: according to the KPHX real ATIS,
EXPECT ILS OR VISUAL APCH RWY 26, ILS OR VISUAL APCH RWY 25L. DEPARTING RWY 25R.
However, Navigraph Charts shows the active runways as 7R, 25L, and 8!
Every time I fly to/from KPHX there are incorrect active runways shown.
I see a similar issue. There are currently two active ATIS sources for KPHX.
FAA IRL:
PHX ATIS INFO E 1951Z. VRB05G20KT 10SM SCT065 SCT120 37/18 A2984 (TWO NINER EIGHT FOUR). SIMUL APCHS TO PARL RWYS IN USE. USE CTN FOR ACFT ON PARL FINAL APCHS, DO NOT OVERSHOOT FINAL. EXPECT ILS OR VISUAL APCH RWY 26, ILS OR VISUAL APCH RWY 25L. DEPARTING RWY 25R. NOTICES TO AIRMEN. TWY C CLSD BTN INT, C4 AND INT C5. MULT CRANES INVOF ARPT. BIRD ACTIVITY INVOF ARPT. READBACK HOLD SHORT INSTRUCTIONS. ...ADVS YOU HAVE INFO E.
Charts determines 25R for departure and 25L for arrivals from that, seemingly forgetting runway 26 is also used for arrivals:
PilotEdge:
PHOENIX SKY HARBOR INTERNATIONAL AIRPORT, PILOTEDGE ATIS INFO INDIA.
KPHX 111951Z VRB05G20KT 10SM SCT065 SCT120 37/18 A2984 RMK AO2 SLP085 T03670178
ARRIVING RUNWAYS 7R AND 8. DEPARTING RUNWAYS 7L AND 8. VISUAL APPROACHES IN USE. ILS RUNWAY 7 RIGHT AND ILS RUNWAY 8 APPROACH IN USE. SIMULTANEOUS APPROACHES TO PARALLEL RUNWAYS IN USE. V F R DEPARTURES CONTACT CLEARANCE DELIVERY, ADVISE ON COURSE HEADING, ALTITUDE, AND IF FLIGHT FOLLOWING IS REQUESTED. READ BACK ALL RUNWAY ASSIGNMENTS AND HOLD SHORT INSTRUCTIONS.
ADVISE ON INITIAL CONTACT YOU HAVE INFORMATION INDIA.
Charts determines 07L plus 08 for departure and 07R plus 08 for arrivals (seemingly correct).
However, the final result is this:
…where both ATIS source are seemingly applied instead of honoring the priority ATIS source set in Settings (Real for me).
I imagine this is a more general bug rather than specific to PHX.
Regards,
Tim
Hi, thanks for the report!
The missing runway 26 when reading the real-world ATIS has been fixed now.
Best regards,
Nice, thanks!
Although TBH the app merging both sets of active runways instead of picking one or the other is the more annoying issue.
Regards,
Tim
We’re looking into that as well!
