Narrative:

Our trip began at XA30 with a departure from sfo with the destination of teb. The occurrence began on our descent to cross lvz at FL180. The descent rate to make this restr is typically excessive, requiring a 2000-3000 FPM descent. As we made the crossing restr and passed lvz, we were given a descent to 17000 ft. I heard the first officer repeat to the ATC controller the altimeter of .32 inches. I repeated 30.32 and placed 30.32 inches in my primary altimeter and also my standby altimeter on the left side of the cockpit. As I continued my descent to 17000 ft, I received a TA on the TCASII. The TCASII initially showed traffic 800 ft below and about 10 mi off our left wing. I immediately realized that the amount of altitude that I still needed to lose conflicted with the altitude of the dash 8 traffic. I then proceeded to disconnect the autoplt and shallow my descent from approximately 800 FPM to less than 500 FPM, and then to level off. The TCASII was advising to monitor vertical speed, and I viewed the TCASII as indicating the dash 8 traffic off our left wing and 500 ft below us. From the initial TCASII alert, both the first officer and myself had the dash 8 in visual contact. I believe the first officer reported the traffic in sight to ATC. I do recall the dash 8 traffic reporting our aircraft in sight. As the first officer was looking across and out the left side windshield, he was able to notice that his altimeter varied from the one on my side (left side). He immediately realized at that time, that the altimeter setting was incorrectly entered into my altimeters. He corrected the altimeters, and I immediately returned to 17000 ft from 16500 ft. As corrective action, we have implemented full readback of all instructions and clrncs to ATC and within our cockpits. It was the misinterp of .32 inches that led to the occurrence. We have also initiated an annual recurrent CRM training headed by a former airline training captain. Supplemental information from acn 570387: I read back 32 inches instead of 29.32 inches. The captain put 30.32 inches in his altimeter, and I placed 29.32 inches. I then checked teb ATIS and teb altimeter setting was 29.30 inches. I then told the captain that the altimeter was 29.32, but at that time, ATC was giving numerous reports of dash 8 traffic at about 10 O'clock position. I told ny ATC that we had the traffic in sight, and that we were descending to 17000 ft. I noticed that the captain's altimeter still read above 17000 ft, but controller still was questioning us about our altitude. This is when I noticed the captain's altimeter at 30.32 inches and corrected to 29.32 inches. At that time, we were at 16500 ft at all times, we had the dash 8 in sight.

Google
 

Original NASA ASRS Text

Title: HAWKER 800 CREW MISSET THE ALTIMETER BY 1 INCH AT THE TRANSITION ALT AND HAD TCASII TA WITH ANOTHER ACFT.

Narrative: OUR TRIP BEGAN AT XA30 WITH A DEP FROM SFO WITH THE DEST OF TEB. THE OCCURRENCE BEGAN ON OUR DSCNT TO CROSS LVZ AT FL180. THE DSCNT RATE TO MAKE THIS RESTR IS TYPICALLY EXCESSIVE, REQUIRING A 2000-3000 FPM DSCNT. AS WE MADE THE XING RESTR AND PASSED LVZ, WE WERE GIVEN A DSCNT TO 17000 FT. I HEARD THE FO REPEAT TO THE ATC CTLR THE ALTIMETER OF .32 INCHES. I REPEATED 30.32 AND PLACED 30.32 INCHES IN MY PRIMARY ALTIMETER AND ALSO MY STANDBY ALTIMETER ON THE L SIDE OF THE COCKPIT. AS I CONTINUED MY DSCNT TO 17000 FT, I RECEIVED A TA ON THE TCASII. THE TCASII INITIALLY SHOWED TFC 800 FT BELOW AND ABOUT 10 MI OFF OUR L WING. I IMMEDIATELY REALIZED THAT THE AMOUNT OF ALT THAT I STILL NEEDED TO LOSE CONFLICTED WITH THE ALT OF THE DASH 8 TFC. I THEN PROCEEDED TO DISCONNECT THE AUTOPLT AND SHALLOW MY DSCNT FROM APPROX 800 FPM TO LESS THAN 500 FPM, AND THEN TO LEVEL OFF. THE TCASII WAS ADVISING TO MONITOR VERT SPD, AND I VIEWED THE TCASII AS INDICATING THE DASH 8 TFC OFF OUR L WING AND 500 FT BELOW US. FROM THE INITIAL TCASII ALERT, BOTH THE FO AND MYSELF HAD THE DASH 8 IN VISUAL CONTACT. I BELIEVE THE FO RPTED THE TFC IN SIGHT TO ATC. I DO RECALL THE DASH 8 TFC RPTING OUR ACFT IN SIGHT. AS THE FO WAS LOOKING ACROSS AND OUT THE L SIDE WINDSHIELD, HE WAS ABLE TO NOTICE THAT HIS ALTIMETER VARIED FROM THE ONE ON MY SIDE (L SIDE). HE IMMEDIATELY REALIZED AT THAT TIME, THAT THE ALTIMETER SETTING WAS INCORRECTLY ENTERED INTO MY ALTIMETERS. HE CORRECTED THE ALTIMETERS, AND I IMMEDIATELY RETURNED TO 17000 FT FROM 16500 FT. AS CORRECTIVE ACTION, WE HAVE IMPLEMENTED FULL READBACK OF ALL INSTRUCTIONS AND CLRNCS TO ATC AND WITHIN OUR COCKPITS. IT WAS THE MISINTERP OF .32 INCHES THAT LED TO THE OCCURRENCE. WE HAVE ALSO INITIATED AN ANNUAL RECURRENT CRM TRAINING HEADED BY A FORMER AIRLINE TRAINING CAPT. SUPPLEMENTAL INFO FROM ACN 570387: I READ BACK 32 INCHES INSTEAD OF 29.32 INCHES. THE CAPT PUT 30.32 INCHES IN HIS ALTIMETER, AND I PLACED 29.32 INCHES. I THEN CHECKED TEB ATIS AND TEB ALTIMETER SETTING WAS 29.30 INCHES. I THEN TOLD THE CAPT THAT THE ALTIMETER WAS 29.32, BUT AT THAT TIME, ATC WAS GIVING NUMEROUS RPTS OF DASH 8 TFC AT ABOUT 10 O'CLOCK POS. I TOLD NY ATC THAT WE HAD THE TFC IN SIGHT, AND THAT WE WERE DSNDING TO 17000 FT. I NOTICED THAT THE CAPT'S ALTIMETER STILL READ ABOVE 17000 FT, BUT CTLR STILL WAS QUESTIONING US ABOUT OUR ALT. THIS IS WHEN I NOTICED THE CAPT'S ALTIMETER AT 30.32 INCHES AND CORRECTED TO 29.32 INCHES. AT THAT TIME, WE WERE AT 16500 FT AT ALL TIMES, WE HAD THE DASH 8 IN SIGHT.

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.