DUE TO A FLC OVERLOAD; ALT OVERSHOT WHEN A B737 FO; PF; FAILS TO RESET THE ALTIMETER ON DSCNT INTO DEN; CO.

Date: 2003-03 · Aircraft: B737-300 · Phase: approach

Anomalies: deviation-altitude-overshoot|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-published-material-policy|inflight-event-encounter-weather-turbulence|other-flc-workload

Synopsis

DUE TO A FLC OVERLOAD; ALT OVERSHOT WHEN A B737 FO; PF; FAILS TO RESET THE ALTIMETER ON DSCNT INTO DEN; CO.

Narrative

APCHING DENVER; TSTMS IN AREA. CLRED FOR SAYGE ARR; THEN LANDR; THEN BACK TO SAYGE ARR. DSNDING INTO DENVER ON THE SAYGE ARR; CLRED TO CROSS SAYGE AT 250 KTS AND 16000 FT. ACARS STUCK IN LOOP REPEATEDLY RECEIVING MESSAGE CONFIRMING OUR RELEASE; (UNABLE TO GET CURRENT ATIS VIA ACARS). PASSING 190; PNF SETS 29.38 PER APCH. PNF GOES OFF FREQ TO LISTEN TO ATIS TO CONFIRM LOW ALTIMETER SETTING. PF ANSWERS CONFUSING ATC RADIO CALL ABOUT A POSSIBLE BIRD STRIKE ON RWY 26; (WE WERE TOLD TO EXPECT RWY 35R). PASSING 170; PNF CALLS 1000 FT -- ACKNOWLEDGED BY PF. AFTER COPYING ATIS; PNF NOTICES ACFT LEVEL AT 15500. PF IMMEDIATELY RESETS HIS ALTIMETER TO 29.38 FROM 29.92; AND CORRECTS TO 16000 FT. NO TFC NOTED IN AREA; AND NO MENTION BY ATC OF DEV. TOTAL DEV LASTED LESS THAN 20 SECONDS. NUMEROUS FACTORS CONTRIBUTED TO THE DISTR OF BOTH PLTS. PF HAD LESS THAN 100 HRS IN ACFT; AND IS ABOUT TO BE FURLOUGHED. ALSO; ATC CALL ABOUT BIRD STRIKE WAS CONFUSING. PF WAS CALLED AT XA00 FOR IDENT ASSIGNMENT. HE MENTIONED SEVERAL TIMES HOW TIRED HE WAS BECAUSE OF THIS. PNF DISTR BY INABILITY TO VERIFY ALTIMETER SETTING VIA ACARS AND ATC; MODERATE AIRFRAME ICING; TURB; CLOSE PROX TO STORMS; AND CONTINUALLY CHANGING CLRNCS. APCH DSCNT CHKLIST WAS COMPLETED UP TO THE ALTIMETER SETTING VERIFICATION.

More incidents for this aircraft family →

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