2000-06 · NASA ASRS report 474646
B737 CREW HAD ALTDEV IN ZAB CLASS A.
WE WERE CRUISING AT FL240 ON THE FOSSL 5 ARR TO PHX. WE WERE RUNNING LATE SO I HAD ENGAGED RTA MODE TO MAKE UP TIME AND WE WERE DOING OK AS WE WERE PROJECTING AN ARR WITHIN 15 MINS OF SCHEDULE. SHORTLY AFTER PASSING SACHO INTXN THE FO WENT OFF FREQ TO GET ATIS AND CALL COMPANY. SHORTLY AFTER THAT ATC GAVE US DIRECT TONTO. I ENTERED THIS INTO THE COMPUTER AND THE ACFT TURNED TOWARDS TONTO. SUDDENLY; TO MY SURPRISE; I OBSERVED THE AUTOTHROTTLES DECREASING PWR AND THE SPD BUG COME BACK APPROX 20+ KTS. I CHKED THE RTA PAGE AND NOTICED THAT AN EXTRA 2 MINS HAD OPENED UP IN THE RTA WINDOW AND SINCE OUR PREVIOUS ETA WAS STILL ENTERED; THE COMPUTER WAS SLOWING DOWN TO COMPENSATE FOR THE NEW ROUTING. WANTING TO TAKE FULL ADVANTAGE OF THE SHORTCUT I DESELECTED VNAV AND INCREASED SPD VIA THE MODE CTL PANEL. I OBSERVED THE AUTOTHROTTLES INCREASE PWR AND TURNED MY ATTN TO REPROGRAMMING THE COMPUTER. IN THE MIDDLE OF MY PROGRAMMING EFFORTS ATC CLRED US TO CROSS TONTO AT 12000 FT AND 250 KTS. I RESET THE ALT ON THE MPC AND WENT BACK TO PROGRAMMING THE COMPUTER WHICH DIDN'T LIKE THE PARAMETER THAT I WAS ENTERING SO I HAD TO CHOOSE ANOTHER. THAT DONE I NOTICED THAT I HAD A FLASHING YELLOW AUTOPLT WARNING LIGHT AND THAT FOR SOME REASON WE WERE IN CTL WHEEL STEERING PITCH. BY THIS TIME I WAS A BIT FED UP WITH THE COMPUTER SO I ELECTED TO START MY DSCNT IN VERT SPD MODE EVEN THOUGH WE WERE WELL OUTSIDE OUR TOP OF DSCNT POINT. I ENGAGED VERT SPD AND DIALED IN A 1000 FPM DSCNT; WHEREUPON THE AUTOPLT DEFAULTED TO LEVEL CHANGE. THINKING THIS WAS THE NORMAL 'GLITCH' THAT SOME OF OUR ACFT HAVE; IN THAT VERT SPD WILL DEFAULT TO LEVEL CHANGE IF YOU SPIN THE VERT SPD WHEEL TOO FAST; I REENGAGED VERT SPD AND OBSERVED 1000 FT IN THE WINDOW. HOWEVER; THE AUTOTHROTTLES DID NOT COME BACK VERY FAR AND THE ACFT DID NOT SEEM TO BE RESPONDING TO THE COMMANDED DSCNT. I CHKED THE ALTIMETER AND NOTICED THAT WE WERE 300 FT HIGH AND CLBING. BY THIS TIME I AM GETTING CONFUSED. DURING THE RESULTING RECHK OF MY INSTS I NOTICE TO MY HORROR THAT THE ALTIMETER IS READING 25300 FT NOT 24300 FT AS I HAD ORIGINALLY PERCEIVED. WE HAD GAINED OVER 1000 FT IN LESS THAN 1 MIN. IN RETROSPECT THE 1000 FT THAT I SAW IN THE VERT SPD WINDOW AFTER THE SECOND ENGAGEMENT MUST HAVE BEEN +1000 FT NOT -1000 FT. I IMMEDIATELY RETARDED THE THRUST LEVERS MANUALLY AND PITCHED OVER MANUALLY JUST AS THE FO CAME BACK AFTER GETTING ATIS; ETC. DURING THIS ENTIRE INCIDENT ATC DIDN'T SAY A WORD TO US; THERE WERE NO TA'S OR RA'S FROM THE TCASII AND WE CONTINUED THE REMAINDER OF THE ARR NORMALLY. I CAN ONLY SURMISE THAT WHEN I DESELECTED VNAV THAT THE AUTOPLT FOR SOME REASON DEFAULTED TO CTL WHEEL STEERING PITCH AND NOT ALT HOLD AS IT SHOULD AND WITH THE ADDITION OF PWR TO INCREASE SPD THE ACFT STARTED TO CLB. WITH ATC GIVING US THE XING RESTR IMMEDIATELY THEREAFTER AND MY RESETTING THE ALT ALERTER; THIS REMOVED ALT PROTECTION AS THE ALERTER WOULD THEN ONLY WARN OF DEVS FROM 12000 FT. THIS WAS AN INTERESTING COMBINATION OF EVENTS. ONE WOULD THINK THAT AFTER 34 YRS OF FLYING; OF WHICH ALMOST 14 YRS ARE FLYING JET AIRLINERS; THAT I WOULDN'T BE SURPRISED AT HOW FAST A SIT CAN GO TO HELL IN A HAND BASKET. MY ONLY CONCLUSION IS THAT THE TIME INTERVAL FOR DISASTER IS GETTING SHORTER. THINKING BACK I NOW REMEMBER A SIMILAR 'HAPPENING' ABOUT A MONTH AGO WHEN AN AUTOPLT; FOR NO APPARENT REASON; DEFAULTED TO CTL WHEEL STEERING PITCH. AT THE TIME I WAS NOT DISTRACTED BY ANY DUTIES AND CAUGHT THE 'GLITCH' IMMEDIATELY. AS USUAL IT HAPPENED IN THE APCH PHASE AND WE HAD NO TIME TO TROUBLESHOOT THE PROB TO DISCERN WHETHER IT WAS HUMAN OR SOFTWARE ERROR. WHENEVER THINGS LIKE THIS HAPPEN; MY INITIAL REACTION IS TO ASSUME THAT I DID SOMETHING WRONG IN PROGRAMMING OR MODE SELECTION. I NOW BELIEVE THAT ANY ERROR ON MY PART HAS BEEN OVER USE OF THE COMPUTER TO BEGIN WITH. IN THE FUTURE I WILL ONLY USE IT FOR RUDIMENTARY LNAV; VNAV AND AS A BACKUP IF FEASIBLE. I WILL NO LONGER ENGAGE IN 'ADVANCED FMC' AS MY CURRENT FO REFERS TOIT. THE COMPUTER REQUIRES ENTIRELY TOO MUCH ATTN TO BE PAID TO IT CONSIDERING THE SUPERSATURATED ATC ENVIRONMENT THAT WE OPERATE IN. PLEASE NOTE THAT THIS INCIDENT OCCURRED 120 MI FROM DEST; IN CRUISE AND ONLY 1 AMENDED CLRNC. NOT TO BLAME ATC BUT I WAS SURPRISED THAT SOME ALARM DID NOT ALERT THE CTLR TO THIS. MY GUESS IS THAT HE TOO WAS DISTRACTED BY SOME OTHER DUTY THAT REQUIRED HIS ATTN TO BE DIVERTED MOMENTARILY FROM HIS SCREEN.
More incidents for this aircraft family
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
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.
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.
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.
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.