An incorrectly set altimeter results in an altitude overshoot during descent.

Attributes
ACN	567250
Time
Date	200211
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : buf.airport
State Reference	NY
Altitude	msl bound lower : 9500 msl bound upper : 10000
Environment
Flight Conditions	IMC
Light	Dawn
Aircraft 1
Controlling Facilities	tracon : buf.tracon
Operator	common carrier : air carrier
Make Model Name	B727 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	descent : intermediate altitude descent : approach
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : flight engineer pilot : multi engine pilot : cfi pilot : atp
Experience	flight time last 90 days : 180 flight time total : 7000 flight time type : 1800
ASRS Report	567250
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	altitude deviation : overshoot non adherence : clearance non adherence : far other anomaly other
Independent Detector	other controllerb
Resolutory Action	controller : issued advisory flight crew : returned to assigned altitude
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I was acting as the PNF in a 3 man crew cargo flight. Approximately 100 mi from our destination the captain began the descent from our cruise altitude. A few mins into our descent we passed through FL180 and set our altimeters to 29.89 according to the landing performance card that was filled out by our flight engineer after he listened to the destination ATIS. We leveled out at our assigned altitude of 10000 ft at which time the controller informed us that he showed us at 9500 ft. He told us the correct altimeter setting was 29.52 not 29.89. We reset our altimeters and immediately adjusted our altitude. No conflict occurred, and we continued to our destination without incident. The flight engineer later stated the ATIS was very weak and hard to understand. It seems to me that fatigue was a partial factor in our situation. We were flying night cargo and had all been up in excess of 16 hours. The center controller gave us an altimeter with our descent clearance for buf. Our destination was roc, so I remember thinking we should use the one from the ATIS in roc. Not one of us was alert enough to catch this discrepancy!

Original NASA ASRS Text

Title: AN INCORRECTLY SET ALTIMETER RESULTS IN AN ALT OVERSHOOT DURING DSCNT.

Narrative: I WAS ACTING AS THE PNF IN A 3 MAN CREW CARGO FLT. APPROX 100 MI FROM OUR DEST THE CAPT BEGAN THE DSCNT FROM OUR CRUISE ALT. A FEW MINS INTO OUR DSCNT WE PASSED THROUGH FL180 AND SET OUR ALTIMETERS TO 29.89 ACCORDING TO THE LNDG PERFORMANCE CARD THAT WAS FILLED OUT BY OUR FE AFTER HE LISTENED TO THE DEST ATIS. WE LEVELED OUT AT OUR ASSIGNED ALT OF 10000 FT AT WHICH TIME THE CTLR INFORMED US THAT HE SHOWED US AT 9500 FT. HE TOLD US THE CORRECT ALTIMETER SETTING WAS 29.52 NOT 29.89. WE RESET OUR ALTIMETERS AND IMMEDIATELY ADJUSTED OUR ALT. NO CONFLICT OCCURRED, AND WE CONTINUED TO OUR DEST WITHOUT INCIDENT. THE FE LATER STATED THE ATIS WAS VERY WEAK AND HARD TO UNDERSTAND. IT SEEMS TO ME THAT FATIGUE WAS A PARTIAL FACTOR IN OUR SIT. WE WERE FLYING NIGHT CARGO AND HAD ALL BEEN UP IN EXCESS OF 16 HRS. THE CTR CTLR GAVE US AN ALTIMETER WITH OUR DSCNT CLRNC FOR BUF. OUR DEST WAS ROC, SO I REMEMBER THINKING WE SHOULD USE THE ONE FROM THE ATIS IN ROC. NOT ONE OF US WAS ALERT ENOUGH TO CATCH THIS DISCREPANCY!

Data retrieved from NASA's ASRS site as of July 2007 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.