Narrative:

First officer was PF; I was captain; pilot monitoring. We were at FL280 just beginning to review the arrival and approach for iah when ZHU called traffic to us at 2 O'clock position; 6 mi from FL270. We searched for the traffic and I scanned my TCAS display. My TCAS showed traffic in that direction 700 ft below us. TCAS then gave us a 'traffic traffic' alert and the threat target turned amber. A very short time later; we got an RA to 'climb climb.' first officer was flying and turned off the autoplt and initiated a climb. We climbed to approximately FL285 as traffic flew below us. I called center and advised them we had a TCAS RA and were climbing. Traffic cleared below us and we descended back to FL280. I then noticed that the first officer's altimeter was set at 30.19 inches which was the iah field barometric setting. I pointed that out to the first officer. He then realized that he had been presetting the iah field barometric setting just at the instant ZHU called the traffic to us. The traffic call had distraction him and he did not reset the standard altimeter setting (29.92). We then figured that his misset altimeter had caused the TCAS altitude and further caused the TCAS RA. ZHU had the other aircraft verify their altitude. The aircraft stated they were level at FL270. Center also said their mode C readout concurred with that altitude and we were cleared to descend back to FL280. I do not believe we caused any traffic conflict with any other aircraft by our 500 ft climb. Center never mentioned any other traffic to us. On this type aircraft; you can preset a local altimeter setting and then pull the knob to set 'standard' or standard 29.92 inches. In all of my 15+ yrs of flying airbus aircraft; I have never seen an incident of this nature. But I now will never preset the local altimeter setting when flying at FL180 or above.

Google
 

Original NASA ASRS Text

Title: A319 FLT CREW DEVIATED FROM THEIR ASSIGNED ALT OF 28000 FT IN RESPONSE TO A TCAS RA.

Narrative: FO WAS PF; I WAS CAPT; PLT MONITORING. WE WERE AT FL280 JUST BEGINNING TO REVIEW THE ARR AND APCH FOR IAH WHEN ZHU CALLED TFC TO US AT 2 O'CLOCK POS; 6 MI FROM FL270. WE SEARCHED FOR THE TFC AND I SCANNED MY TCAS DISPLAY. MY TCAS SHOWED TFC IN THAT DIRECTION 700 FT BELOW US. TCAS THEN GAVE US A 'TFC TFC' ALERT AND THE THREAT TARGET TURNED AMBER. A VERY SHORT TIME LATER; WE GOT AN RA TO 'CLB CLB.' FO WAS FLYING AND TURNED OFF THE AUTOPLT AND INITIATED A CLB. WE CLBED TO APPROX FL285 AS TFC FLEW BELOW US. I CALLED CTR AND ADVISED THEM WE HAD A TCAS RA AND WERE CLBING. TFC CLRED BELOW US AND WE DSNDED BACK TO FL280. I THEN NOTICED THAT THE FO'S ALTIMETER WAS SET AT 30.19 INCHES WHICH WAS THE IAH FIELD BAROMETRIC SETTING. I POINTED THAT OUT TO THE FO. HE THEN REALIZED THAT HE HAD BEEN PRESETTING THE IAH FIELD BAROMETRIC SETTING JUST AT THE INSTANT ZHU CALLED THE TFC TO US. THE TFC CALL HAD DISTR HIM AND HE DID NOT RESET THE STANDARD ALTIMETER SETTING (29.92). WE THEN FIGURED THAT HIS MISSET ALTIMETER HAD CAUSED THE TCAS ALT AND FURTHER CAUSED THE TCAS RA. ZHU HAD THE OTHER ACFT VERIFY THEIR ALT. THE ACFT STATED THEY WERE LEVEL AT FL270. CTR ALSO SAID THEIR MODE C READOUT CONCURRED WITH THAT ALT AND WE WERE CLRED TO DSND BACK TO FL280. I DO NOT BELIEVE WE CAUSED ANY TFC CONFLICT WITH ANY OTHER ACFT BY OUR 500 FT CLB. CTR NEVER MENTIONED ANY OTHER TFC TO US. ON THIS TYPE ACFT; YOU CAN PRESET A LCL ALTIMETER SETTING AND THEN PULL THE KNOB TO SET 'STD' OR STANDARD 29.92 INCHES. IN ALL OF MY 15+ YRS OF FLYING AIRBUS ACFT; I HAVE NEVER SEEN AN INCIDENT OF THIS NATURE. BUT I NOW WILL NEVER PRESET THE LCL ALTIMETER SETTING WHEN FLYING AT FL180 OR ABOVE.

Data retrieved from NASA's ASRS site as of January 2009 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.