Narrative:

Descending from FL310 to FL240 to comply with ATC restr 10 southwest djb at FL240, controller advised us that traffic eastbound would pass under us at FL230. First officer cleared off radio to say goodbye to passenger. At that point TCASII issued a TA. The target was at approximately 10 mi, 10 O'clock, and 1200 ft below us. The target then changed from yellow to red. I immediately disconnected the autoplt (my altimeter showed us almost at FL240), glanced at the barometer set knob and switched it from 'hectapascals' to 'inches.' the altimeter readout at that point jumped from FL240 to FL238. I continued to apply back stick pressure until the vvi satisfied the TCASII climb command (about 1000 FPM). As the target passed about a mi behind us, TCASII issued a 'clear of conflict' message. I then smoothly returned the aircraft from FL242 to FL240. The flight continued to destination without further incident. The lowest readout by TCASII on the target throughout was minus 800 ft. The whole incident was set up by my failure to reselect 'inches' on my primary altimeter's barometer set knob after transferring the millibar reading to the standby altimeter. This is a procedure done in preparation for the reading of the descent checklist. I think that a simple solution to prevent a further occurrence of this incident would be to remove all standby altimeters fleetwide that have a millibar barometer window and replace them with ones that are calibrated in inches. That way the standby altimeter could be set from the ATIS card and not by fiddling with the primary altimeter knob.

Google
 

Original NASA ASRS Text

Title: ALTDEV AND TCASII ALERT WITH ERRONEOUS ALTIMETER SETTING.

Narrative: DSNDING FROM FL310 TO FL240 TO COMPLY WITH ATC RESTR 10 SW DJB AT FL240, CTLR ADVISED US THAT TFC EBOUND WOULD PASS UNDER US AT FL230. FO CLRED OFF RADIO TO SAY GOODBYE TO PAX. AT THAT POINT TCASII ISSUED A TA. THE TARGET WAS AT APPROX 10 MI, 10 O'CLOCK, AND 1200 FT BELOW US. THE TARGET THEN CHANGED FROM YELLOW TO RED. I IMMEDIATELY DISCONNECTED THE AUTOPLT (MY ALTIMETER SHOWED US ALMOST AT FL240), GLANCED AT THE BAROMETER SET KNOB AND SWITCHED IT FROM 'HECTAPASCALS' TO 'INCHES.' THE ALTIMETER READOUT AT THAT POINT JUMPED FROM FL240 TO FL238. I CONTINUED TO APPLY BACK STICK PRESSURE UNTIL THE VVI SATISFIED THE TCASII CLB COMMAND (ABOUT 1000 FPM). AS THE TARGET PASSED ABOUT A MI BEHIND US, TCASII ISSUED A 'CLR OF CONFLICT' MESSAGE. I THEN SMOOTHLY RETURNED THE ACFT FROM FL242 TO FL240. THE FLT CONTINUED TO DEST WITHOUT FURTHER INCIDENT. THE LOWEST READOUT BY TCASII ON THE TARGET THROUGHOUT WAS MINUS 800 FT. THE WHOLE INCIDENT WAS SET UP BY MY FAILURE TO RESELECT 'INCHES' ON MY PRIMARY ALTIMETER'S BAROMETER SET KNOB AFTER TRANSFERRING THE MILLIBAR READING TO THE STANDBY ALTIMETER. THIS IS A PROC DONE IN PREPARATION FOR THE READING OF THE DSCNT CHKLIST. I THINK THAT A SIMPLE SOLUTION TO PREVENT A FURTHER OCCURRENCE OF THIS INCIDENT WOULD BE TO REMOVE ALL STANDBY ALTIMETERS FLEETWIDE THAT HAVE A MILLIBAR BAROMETER WINDOW AND REPLACE THEM WITH ONES THAT ARE CALIBRATED IN INCHES. THAT WAY THE STANDBY ALTIMETER COULD BE SET FROM THE ATIS CARD AND NOT BY FIDDLING WITH THE PRIMARY ALTIMETER KNOB.

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.