Altitude deviation altitude overshot due to wrong altimeter setting used by flight crew.

Attributes
ACN	234424
Time
Date	199302
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : mip
State Reference	PA
Altitude	msl bound lower : 13700 msl bound upper : 14000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : eri
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	descent other other
Route In Use	enroute : direct enroute airway : zny
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 210 flight time total : 12600 flight time type : 5000
ASRS Report	234424
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : flight engineer pilot : instrument pilot : commercial
Experience	flight time last 90 days : 200 flight time total : 3400 flight time type : 1600
ASRS Report	234413
Events
Anomaly	altitude deviation : overshoot non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	flight crew : became reoriented flight crew : returned to intended course or assigned course other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Our flight was operating to lga airport. Lga was below minimums so I had the first officer talking to dispatch about our plans and how long they wanted us to hold. We were cleared to descend to 14000 ft. Passing 18000 I called the altimeter setting of 29.82. The first officer acknowledged, and both altimeters we set and checked. When leveled at 14000 ft, ZNY questioned our altitude because our mode C readout was between 13800 and 13700 ft. We stated we were at 14000 ft and then ZNY gave us the local altimeter as 29.52. We corrected our altimeters and climbed back to 14000 ft. The altimeter setting of 29.82 had come from the old ATIS information from our departure airport. The ATIS information is recorded on a card and placed in front of both pilots. When obtaining ATIS information at the destination airport, the same card is used by just turning it over and using the back side. I failed to notice I was still looking at the departure field ATIS. From now on, after departure, I am going to put a big red X on the departure side ATIS and turn the card over to the arrival side of the card, which will be blank until the arrival ATIS is obtained.

Original NASA ASRS Text

Title: ALTDEV ALT OVERSHOT DUE TO WRONG ALTIMETER SETTING USED BY FLC.

Narrative: OUR FLT WAS OPERATING TO LGA ARPT. LGA WAS BELOW MINIMUMS SO I HAD THE FO TALKING TO DISPATCH ABOUT OUR PLANS AND HOW LONG THEY WANTED US TO HOLD. WE WERE CLRED TO DSND TO 14000 FT. PASSING 18000 I CALLED THE ALTIMETER SETTING OF 29.82. THE FO ACKNOWLEDGED, AND BOTH ALTIMETERS WE SET AND CHKED. WHEN LEVELED AT 14000 FT, ZNY QUESTIONED OUR ALT BECAUSE OUR MODE C READOUT WAS BTWN 13800 AND 13700 FT. WE STATED WE WERE AT 14000 FT AND THEN ZNY GAVE US THE LCL ALTIMETER AS 29.52. WE CORRECTED OUR ALTIMETERS AND CLBED BACK TO 14000 FT. THE ALTIMETER SETTING OF 29.82 HAD COME FROM THE OLD ATIS INFO FROM OUR DEP ARPT. THE ATIS INFO IS RECORDED ON A CARD AND PLACED IN FRONT OF BOTH PLTS. WHEN OBTAINING ATIS INFO AT THE DEST ARPT, THE SAME CARD IS USED BY JUST TURNING IT OVER AND USING THE BACK SIDE. I FAILED TO NOTICE I WAS STILL LOOKING AT THE DEP FIELD ATIS. FROM NOW ON, AFTER DEP, I AM GOING TO PUT A BIG RED X ON THE DEP SIDE ATIS AND TURN THE CARD OVER TO THE ARR SIDE OF THE CARD, WHICH WILL BE BLANK UNTIL THE ARR ATIS IS OBTAINED.

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.