A DSNDING B727 FREIGHTER OVERSHOOTS ITS ASSIGNED ALT WHEN THE CREW MISSETS THE ALTIMETER AT TOO LOW A SETTING SE OF DEN; CO.

Date: 2000-01 · Aircraft: B727-200 · Phase: descent

Anomalies: deviation-altitude-overshoot|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-published-material-policy|other-fatigue

Synopsis

A DSNDING B727 FREIGHTER OVERSHOOTS ITS ASSIGNED ALT WHEN THE CREW MISSETS THE ALTIMETER AT TOO LOW A SETTING SE OF DEN; CO.

Narrative

WE WERE ASSIGNED ALT 13000 FT. ON DSCNT THROUGH FL180; I SET MY ALTIMETER TO 30.58; HAVING MISREAD THE LNDG DATA CARD. THE ALTIMETER SHOULD HAVE BEEN 29.58. THIS CAUSED A 1000 FT ERROR AND AS WE WERE DSNDING THROUGH 13500 FT; THE CTLR ADVISED OUR ALT WAS SHOWING 12500 FT AND REISSUED THE CORRECT ALTIMETER OF 29.58. I WAS IN SUCH A HURRY TO CORRECT THE ALT AND THE ALTIMETER THAT I CLBED THROUGH 13000 FT AND HAD TO CORRECT AGAIN. ON LNDG; I CONTACTED THE APCH CTL SUPVR AND HE INDICATED THAT NO OTHER TFC WAS INVOLVED. THIS WAS THE LAST LEG OF AN 11 HR DAY AND THE LAST FLT OF A LONG 3 WK ROTATION AND FATIGUE COULD BE A CASUAL FACTOR. THE FE SET 29.58 IN HIS ALTIMETER AND WROTE 29.58 ON THE CARD. DURING THE CHKLIST; I READ 30.58 AND SET THAT IN MY ALTIMETER; AS DID THE FO. THE FE DID NOT CATCH THE BAD CALL. ON LATER DISCUSSION WITH THE CREW; THE FE REALIZED THAT WHEN THE CHKLIST WAS BEING READ; ALL HE HEARD WAS '58' AND DIDN'T CATCH THE REST OF THE CALL. JUST GOES TO SHOW THAT FATIGUE CAN CATCH YOU EVEN WHEN YOU ARE FOLLOWING ALL THE PROCS. I'M JUST GLAD THAT THE REST OF THE SYS WORKED. THE CTLR NOTICED THE ALT AND MADE THE CORRECTION. WE WERE ALSO VERY LUCKY THERE WAS NO OTHER TFC.

More incidents for this aircraft family →

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