|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||1801 To 2400|
|Locale Reference||airport : phx.airport|
|Altitude||msl single value : 8000|
|Controlling Facilities||tracon : p50.tracon|
|Operator||common carrier : air carrier|
|Make Model Name||A320|
|Operating Under FAR Part||Part 121|
|Navigation In Use||other|
|Route In Use||arrival star : eagul|
|Affiliation||company : air carrier|
|Function||flight crew : captain|
oversight : pic
|Qualification||pilot : atp|
|Anomaly||aircraft equipment problem : less severe|
non adherence : published procedure
|Independent Detector||other flight crewa|
|Resolutory Action||flight crew : overrode automation|
EAGUL2 arrival into phx -- the FMS properly loads all of the crossing restrictions; however; just prior to queny at 210 KTS and 8000 ft it inserts a deceleration point. It appears as though the profile will cross queny as charted but instead the approach is automatically activated at the decel point and the airplane wants to slow to vref/vls. At this point you have to manually select 210 KTS. Every pilot I have flown with has missed this -- in fact; when I tell them in advance that it will happen -- they don't believe me. The decel point cannot be cleared so the only alternative is to manually override it. This happens at a busy time (frequency change; looking for traffic; runway; etc) and can lead to a mode reversion and crossing restriction error not to mention an unnecessary distraction. This error is built into the database and needs to be corrected. The exact same thing happens on the GEELA2 and KOOLY1 arrivals.callback conversation with reporter revealed the following information: the reporter believes the database may be to blame; although anything is possible. Reporter has also had the anomaly occur on two other phx arrs with the same altitude and airspeed restrictions at loosy on the GEELA2 and basha on the KOOLY1 arrs. The anomaly occurs every time on any ship that he may be flying.
Original NASA ASRS Text
Title: A320 CAPT REPORTS FMGC AUTOMATICALLY ACTIVATED APCH PHASE MODE APPROACHING QUENY ON THE EAGUL2 ARR TO PHX; CAUSING THE ACFT TO SLOW UNEXPECTEDLY.
Narrative: EAGUL2 ARRIVAL INTO PHX -- THE FMS PROPERLY LOADS ALL OF THE CROSSING RESTRICTIONS; HOWEVER; JUST PRIOR TO QUENY AT 210 KTS AND 8000 FT IT INSERTS A DECELERATION POINT. IT APPEARS AS THOUGH THE PROFILE WILL CROSS QUENY AS CHARTED BUT INSTEAD THE APPROACH IS AUTOMATICALLY ACTIVATED AT THE DECEL POINT AND THE AIRPLANE WANTS TO SLOW TO VREF/VLS. AT THIS POINT YOU HAVE TO MANUALLY SELECT 210 KTS. EVERY PILOT I HAVE FLOWN WITH HAS MISSED THIS -- IN FACT; WHEN I TELL THEM IN ADVANCE THAT IT WILL HAPPEN -- THEY DON'T BELIEVE ME. THE DECEL POINT CANNOT BE CLEARED SO THE ONLY ALTERNATIVE IS TO MANUALLY OVERRIDE IT. THIS HAPPENS AT A BUSY TIME (FREQUENCY CHANGE; LOOKING FOR TRAFFIC; RUNWAY; ETC) AND CAN LEAD TO A MODE REVERSION AND CROSSING RESTRICTION ERROR NOT TO MENTION AN UNNECESSARY DISTRACTION. THIS ERROR IS BUILT INTO THE DATABASE AND NEEDS TO BE CORRECTED. THE EXACT SAME THING HAPPENS ON THE GEELA2 AND KOOLY1 ARRIVALS.CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR BELIEVES THE DATABASE MAY BE TO BLAME; ALTHOUGH ANYTHING IS POSSIBLE. RPTR HAS ALSO HAD THE ANOMALY OCCUR ON TWO OTHER PHX ARRS WITH THE SAME ALT AND AIRSPD RESTRICTIONS AT LOOSY ON THE GEELA2 AND BASHA ON THE KOOLY1 ARRS. THE ANOMALY OCCURS EVERY TIME ON ANY SHIP THAT HE MAY BE FLYING.
Data retrieved from NASA's ASRS site as of May 2009 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.