EA32 ALT BUST. CREW WAS DISTRACTED WHEN THE CAPT WAS DISCUSSING A MAINT PROB WITH THE CABIN ATTENDANT. THE FO SET A WRONG ALT IN THE ALT WINDOW; AND THE AUTOPLT DSNDED TO THAT ALT.

1998-06 · NASA ASRS report 405212

Date: 1998-06 · Aircraft: A320

Anomalies: deviation-altitude-overshoot|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-far

Synopsis

EA32 ALT BUST. CREW WAS DISTRACTED WHEN THE CAPT WAS DISCUSSING A MAINT PROB WITH THE CABIN ATTENDANT. THE FO SET A WRONG ALT IN THE ALT WINDOW; AND THE AUTOPLT DSNDED TO THAT ALT.

Narrative

I WAS THE COPLT ON THIS FLT. MY CAPT WAS DISCUSSING AN ISSUE WITH THE LEAD FLT ATTENDANT; SO I WAS RESPONSIBLE FOR FLYING THE ACFT AND COMMUNICATING WITH ATC. ATC CLRED US TO DSND TO FL270. I HEARD 'FL270;' READ BACK 'FL270;' BUT SET 26000 FT IN THE ALT WINDOW; THINKING I HAD SET 27000 FT. I INITIATED THE DSCNT VIA AUTOPLT. DURING THE DSCNT MY CAPT CONCLUDED HER DISCUSSION WITH THE FLT ATTENDANT; AND I TOLD HER WE HAD BEEN CLRED TO FL260. UPON LEVELING AT FL260; I NOTICED ATC HAD JUST CLRED ANOTHER ACFT TO DSND TO FL270. I QUERIED ATC ABOUT OUR ALT. THE CTLR RESPONDED THAT 'FL270 WAS ASSIGNED; DSND NOW TO FL240 AND EXPEDITE THROUGH FL250.' I DISCONNECTED THE AUTOPLT AND EXTENDED THE SPD BRAKES TO EXPEDITE THE DSCNT. THE CTLR REITERATED 'BE OUT OF FL250 AS RAPIDLY AS POSSIBLE' OR SOMETHING TO THAT EFFECT. I RPTED BEING BELOW FL250. AFTER LEVELING AT FL240; WE WERE THEN HANDED OFF TO THE NEXT SECTOR; WITH NO APPARENT CONFLICT GENERATED BY OUR ALTDEV. I BELIEVE THIS WAS A CASE OF ME SEEING WHAT I WANTED TO SEE IN THE ALT WINDOW; AND THEN; CONVINCED I HAD PROPERLY SET THE ALT; THINKING FL260 WAS THE ASSIGNED ALT. FATIGUE MAY HAVE PLAYED A SMALL ROLE AS IT HAD BEEN A BUSY FLT WITH AN EQUIP MALFUNCTION; TSTM AVOIDANCE; AND A HIGH WORKLOAD INTL DEP. I WILL BE MORE DILIGENT IN THE FUTURE WHEN AS BOTH PF AND COMMUNICATING WITH ATC; I AM THE ONLY SAFEGUARD IN COMPLYING WITH ATC CLRNCS. SUPPLEMENTAL INFO FROM ACN 404400: CONTRIBUTING FACTORS: SINCE THE DEP OUT OF MEXICO CITY; THE WORKLOAD HAD BEEN HIGH DUE TO RADAR FAILURE; AN INCREASING TEMP ON A PACK THAT HAD BEEN A PROB ON THE PREVIOUS FLT AND CLRED BY MEX MAINT; INABILITY TO TALK TO COMPANY DUE TO INTERMITTENT ACARS AND NO WORKING COMMERCIAL RADIO FREQ UNTIL CLOSER TO HOUSTON. IN AN ATTEMPT TO REMEDY THESE PROBS I HAD ASKED THE FO TO USE THE AUTOPLT AND WORK THE RADIOS ON 2 OR 3 OCCASIONS. THIS COORD SEEMED TO WORK WELL AND THINGS WENT SMOOTH. I BELIEVE THE FO SAW ME TALKING TO THE FLT ATTENDANT AND WHEN I MISSED THE CALL; ASSUMED IT WAS OK TO ANSWER ATC AND DSND. HOWEVER; WITHOUT MY VERIFICATION OF ALT; OUR SIT CAUSED A QUESTIONABLE ALTDEV.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.