Narrative:

On approach into denver aircraft was on autoplt. I was the PF and got the ATIS. I wrote down altimeter 30.44. I heard the wrong altimeter, the setting was really 30.04. When the copilot saw the high altimeter setting he said 'boy, that's really high.' in clear lingo we call that 'inquiry.' I said, 'yes the pressure is rising rapidly.' but not that rapidly. I should have double checked the altimeter setting then and there but I didn't. Complacency set in and on our descent to 11000 ft we got an RA for traffic at 10000 ft. It said 'climb,' we complied and 'clear of conflict.' after that, 5 mins later, approach control said he saw us level at 9600 ft and the altimeter was 30.04. That is when we reset our altimeter, saw we were 400 ft low, and climbed to 10000 ft. My mistake in not 'reading' the 'inquiry' from my copilot as to what the altimeter setting was, was the last link in the chain that led to the altitude deviation. Callback conversation with reporter revealed the following information: reporter stated that he was operating a B737-300 at the time of this incident. He clarified that he had been reclred to 10000 ft after the response to TCASII descending to 11000 ft. He further stated that he never did see the other aircraft to which a TCASII RA was given and responded to. He stated that he was used to flying in alaska where there are many large variations in the altimeter setting which caused him to not really be alerted to the error he made in setting the new altimeter reading.

Related reports:

Google
 

Original NASA ASRS Text

Title: FLC OF AN MLG SET THE WRONG ALTIMETER SETTING RESULTING IN OVERSHOOTING DSCNT ALT.

Narrative: ON APCH INTO DENVER ACFT WAS ON AUTOPLT. I WAS THE PF AND GOT THE ATIS. I WROTE DOWN ALTIMETER 30.44. I HEARD THE WRONG ALTIMETER, THE SETTING WAS REALLY 30.04. WHEN THE COPLT SAW THE HIGH ALTIMETER SETTING HE SAID 'BOY, THAT'S REALLY HIGH.' IN CLR LINGO WE CALL THAT 'INQUIRY.' I SAID, 'YES THE PRESSURE IS RISING RAPIDLY.' BUT NOT THAT RAPIDLY. I SHOULD HAVE DOUBLE CHKED THE ALTIMETER SETTING THEN AND THERE BUT I DIDN'T. COMPLACENCY SET IN AND ON OUR DSCNT TO 11000 FT WE GOT AN RA FOR TFC AT 10000 FT. IT SAID 'CLB,' WE COMPLIED AND 'CLR OF CONFLICT.' AFTER THAT, 5 MINS LATER, APCH CTL SAID HE SAW US LEVEL AT 9600 FT AND THE ALTIMETER WAS 30.04. THAT IS WHEN WE RESET OUR ALTIMETER, SAW WE WERE 400 FT LOW, AND CLBED TO 10000 FT. MY MISTAKE IN NOT 'READING' THE 'INQUIRY' FROM MY COPLT AS TO WHAT THE ALTIMETER SETTING WAS, WAS THE LAST LINK IN THE CHAIN THAT LED TO THE ALTDEV. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THAT HE WAS OPERATING A B737-300 AT THE TIME OF THIS INCIDENT. HE CLARIFIED THAT HE HAD BEEN RECLRED TO 10000 FT AFTER THE RESPONSE TO TCASII DSNDING TO 11000 FT. HE FURTHER STATED THAT HE NEVER DID SEE THE OTHER ACFT TO WHICH A TCASII RA WAS GIVEN AND RESPONDED TO. HE STATED THAT HE WAS USED TO FLYING IN ALASKA WHERE THERE ARE MANY LARGE VARIATIONS IN THE ALTIMETER SETTING WHICH CAUSED HIM TO NOT REALLY BE ALERTED TO THE ERROR HE MADE IN SETTING THE NEW ALTIMETER READING.

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.