A B737-300 crew had a 1000 ft altitude overshoot descending into den.

Attributes
ACN	537828
Time
Date	200202
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : d01.tracon
State Reference	CO
Altitude	msl bound lower : 13000 msl bound upper : 14000
Environment
Flight Conditions	VMC
Aircraft 1
Controlling Facilities	tracon : d01.tracon
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	descent : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : multi engine pilot : commercial
ASRS Report	537828
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	altitude deviation : overshoot non adherence : company policies non adherence : published procedure non adherence : far other anomaly other
Independent Detector	other flight crewa other flight crewb
Resolutory Action	controller : issued new clearance none taken : detected after the fact
Consequence	other
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

On our arrival into denver, we were cleared to FL190, then after leveling we were cleared to 14000 ft. The captain was PF. He called for approach descent checklist. Passing through FL180, I stated 'altimeters 29.64 set.' the captain responded, '64 set.' we continued our descent, discussing the need to advise flight attendants of WX and turbulence conditions and to situation down now, and to stay down with a prepare for landing remain seated etc. I went through that over the interphone. When I hung up with flight attendants, I turned and saw my altimeter with us leveled at 13000 ft, the altitude alerter at '000' and the captain's at 14000 ft. The captain had set in 30.64, thus with the 'a' autoplt engaged we were 1000 ft low. I told the captain immediately of the error and he clicked off the autoplt and started a climb. I advised ATC we were 'climbing back to 14000 ft due to an altimeter error.' (by now we were at 13400 ft and climbing.) ATC responded 'descend now to 11000 ft' and did not comment on our altitude deviation. (On a side note, our TCASII became inoperative earlier in the leg, which added to my concern for traffic separation.)

Original NASA ASRS Text

Title: A B737-300 CREW HAD A 1000 FT ALT OVERSHOOT DSNDING INTO DEN.

Narrative: ON OUR ARR INTO DENVER, WE WERE CLRED TO FL190, THEN AFTER LEVELING WE WERE CLRED TO 14000 FT. THE CAPT WAS PF. HE CALLED FOR APCH DSCNT CHKLIST. PASSING THROUGH FL180, I STATED 'ALTIMETERS 29.64 SET.' THE CAPT RESPONDED, '64 SET.' WE CONTINUED OUR DSCNT, DISCUSSING THE NEED TO ADVISE FLT ATTENDANTS OF WX AND TURB CONDITIONS AND TO SIT DOWN NOW, AND TO STAY DOWN WITH A PREPARE FOR LNDG REMAIN SEATED ETC. I WENT THROUGH THAT OVER THE INTERPHONE. WHEN I HUNG UP WITH FLT ATTENDANTS, I TURNED AND SAW MY ALTIMETER WITH US LEVELED AT 13000 FT, THE ALT ALERTER AT '000' AND THE CAPT'S AT 14000 FT. THE CAPT HAD SET IN 30.64, THUS WITH THE 'A' AUTOPLT ENGAGED WE WERE 1000 FT LOW. I TOLD THE CAPT IMMEDIATELY OF THE ERROR AND HE CLICKED OFF THE AUTOPLT AND STARTED A CLB. I ADVISED ATC WE WERE 'CLBING BACK TO 14000 FT DUE TO AN ALTIMETER ERROR.' (BY NOW WE WERE AT 13400 FT AND CLBING.) ATC RESPONDED 'DSND NOW TO 11000 FT' AND DID NOT COMMENT ON OUR ALTDEV. (ON A SIDE NOTE, OUR TCASII BECAME INOP EARLIER IN THE LEG, WHICH ADDED TO MY CONCERN FOR TFC SEPARATION.)

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.