Wrong altimeter setting creates an altitude deviation altitude overshot in descent in cpr aircraft.

Attributes
ACN	234404
Time
Date	199302
Day	Sun
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : djb
State Reference	OH
Altitude	msl bound lower : 9000 msl bound upper : 10000
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Operator	general aviation : corporate
Make Model Name	Light Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other Other
Flight Phase	descent other
Route In Use	enroute airway : zob
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
Experience	flight time last 90 days : 109 flight time total : 1925
ASRS Report	234404
Person 2
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 125 flight time total : 3400
ASRS Report	234398
Events
Anomaly	altitude deviation : overshoot non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance 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:

During a descent into the cleveland area, we were given a clearance from a flight level to cross an intersection at 10000. The cleveland controller gave me an altimeter setting, believed to be 30.37. On the readback I read the crossing restriction and altitude, altimeter setting of 30.37. I immediately put 30.37 in my altimeter. Out of FL180 I made a callout, 'out of 180, altimeter 037!' after leveling at 10000 we were told by ATC to maintain 10000. I responded that we were level at 10000. I wondered why ATC asked us to maintain 10000, so I radioed back for an altimeter setting. ATC replied 29.37. I read back 937 and we climbed to 10000. Supplemental information from acn 234398: we radioed back that we were level at 10, and then requested the altimeter again. The controller gave us 29.37, I immediately climbed and reset the altimeter. The difference was 1000 ft of altitude. The 29.37 altimeter was verified by my copilot on the cle ATIS. I don't know if the controller gave us the wrong altimeter, or if we misunderstood him, or if we just set it in error.

Original NASA ASRS Text

Title: WRONG ALTIMETER SETTING CREATES AN ALTDEV ALT OVERSHOT IN DSCNT IN CPR ACFT.

Narrative: DURING A DSCNT INTO THE CLEVELAND AREA, WE WERE GIVEN A CLRNC FROM A FLT LEVEL TO CROSS AN INTXN AT 10000. THE CLEVELAND CTLR GAVE ME AN ALTIMETER SETTING, BELIEVED TO BE 30.37. ON THE READBACK I READ THE XING RESTRICTION AND ALT, ALTIMETER SETTING OF 30.37. I IMMEDIATELY PUT 30.37 IN MY ALTIMETER. OUT OF FL180 I MADE A CALLOUT, 'OUT OF 180, ALTIMETER 037!' AFTER LEVELING AT 10000 WE WERE TOLD BY ATC TO MAINTAIN 10000. I RESPONDED THAT WE WERE LEVEL AT 10000. I WONDERED WHY ATC ASKED US TO MAINTAIN 10000, SO I RADIOED BACK FOR AN ALTIMETER SETTING. ATC REPLIED 29.37. I READ BACK 937 AND WE CLBED TO 10000. SUPPLEMENTAL INFO FROM ACN 234398: WE RADIOED BACK THAT WE WERE LEVEL AT 10, AND THEN REQUESTED THE ALTIMETER AGAIN. THE CTLR GAVE US 29.37, I IMMEDIATELY CLBED AND RESET THE ALTIMETER. THE DIFFERENCE WAS 1000 FT OF ALT. THE 29.37 ALTIMETER WAS VERIFIED BY MY COPLT ON THE CLE ATIS. I DON'T KNOW IF THE CTLR GAVE US THE WRONG ALTIMETER, OR IF WE MISUNDERSTOOD HIM, OR IF WE JUST SET IT IN ERROR.

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.