Narrative:

On may/thu/97, inbound to houston's intercontinental airport in a B737-200 equipped with TCASII, we were on and off the cougar 6 arrival several times and at this particular time we were being vectored for spacing. On a heading of 270 degrees and level at 10000 ft MSL and in WX, we received a TCASII alert 'traffic. Traffic.' I looked down to the screen to identify and saw the red indication in front of our aircraft amongst the WX we were painting. Immediately thereafter I heard, 'climb, climb' and I initiated an immediate climb to approximately 11500 ft, at which time I heard TCASII announce 'clear of traffic, clear of traffic.' we notified ATC of what we did and why we took this action, and they stated that we had been assigned 10000 ft. We again stated that we had climbed in response to a TCASII alert and that we were descending back to 10000 ft. We were then instructed to call ATC when we got on the ground, reason 'pilot deviation.' on the telephone with center we discussed what we did and why we did it and I was told we had conflict with another aircraft at 11000 ft and had come as close as 100 ft and 1.6 mi. I am not aware of any other traffic that was in our immediate area although I'm sure there was some. Traffic and congestion on frequency was a definite factor. Having an ear piece in one ear and listening to a TCASII alert with the other ear on an overhead speaker and not having TCASII cancel VHF could have been a factor. This was a clear cut response to a TCASII alert that put our aircraft in jeopardy. Callback conversation with reporter revealed the following information: the reporter said that he was in clouds at 10000 ft near dwh when he got an 'RA' to climb. Afterwards, the controller was very upset and requested that the flight crew call the ARTCC facility. The facility supervisor, apparently, told the reporter that his flight had missed an air carrier flying at 11000 ft by only 100 ft and 1.6 mi. This was a good conversation, according to the reporter and he has heard nothing more from the FAA. His company was maintaining contact with the FAA and his chief pilot said that he would advise the captain if any further action was necessary. The reporter is an instructor and one of his fellow instructor's sons flies simulated dog-fight missions out of dwh and, according to the reporter, has had a number of incidents where the clients (the dog- fighters) spillout of their block of airspace. The reporter said that he forgot to ask the controller what type of aircraft caused the 'RA.'

Related reports:

Google
 

Original NASA ASRS Text

Title: AN ACR FLC IN A B737-200 REACTS TO AN 'RA,' AND DURING THEIR EVASIVE CLB THEY COME CLOSE TO ANOTHER ACR AT 11000 FT. THE ARTCC RADAR CTLR WAS UPSET.

Narrative: ON MAY/THU/97, INBOUND TO HOUSTON'S INTERCONTINENTAL ARPT IN A B737-200 EQUIPPED WITH TCASII, WE WERE ON AND OFF THE COUGAR 6 ARR SEVERAL TIMES AND AT THIS PARTICULAR TIME WE WERE BEING VECTORED FOR SPACING. ON A HDG OF 270 DEGS AND LEVEL AT 10000 FT MSL AND IN WX, WE RECEIVED A TCASII ALERT 'TFC. TFC.' I LOOKED DOWN TO THE SCREEN TO IDENT AND SAW THE RED INDICATION IN FRONT OF OUR ACFT AMONGST THE WX WE WERE PAINTING. IMMEDIATELY THEREAFTER I HEARD, 'CLB, CLB' AND I INITIATED AN IMMEDIATE CLB TO APPROX 11500 FT, AT WHICH TIME I HEARD TCASII ANNOUNCE 'CLR OF TFC, CLR OF TFC.' WE NOTIFIED ATC OF WHAT WE DID AND WHY WE TOOK THIS ACTION, AND THEY STATED THAT WE HAD BEEN ASSIGNED 10000 FT. WE AGAIN STATED THAT WE HAD CLBED IN RESPONSE TO A TCASII ALERT AND THAT WE WERE DSNDING BACK TO 10000 FT. WE WERE THEN INSTRUCTED TO CALL ATC WHEN WE GOT ON THE GND, REASON 'PLTDEV.' ON THE TELEPHONE WITH CTR WE DISCUSSED WHAT WE DID AND WHY WE DID IT AND I WAS TOLD WE HAD CONFLICT WITH ANOTHER ACFT AT 11000 FT AND HAD COME AS CLOSE AS 100 FT AND 1.6 MI. I AM NOT AWARE OF ANY OTHER TFC THAT WAS IN OUR IMMEDIATE AREA ALTHOUGH I'M SURE THERE WAS SOME. TFC AND CONGESTION ON FREQ WAS A DEFINITE FACTOR. HAVING AN EAR PIECE IN ONE EAR AND LISTENING TO A TCASII ALERT WITH THE OTHER EAR ON AN OVERHEAD SPEAKER AND NOT HAVING TCASII CANCEL VHF COULD HAVE BEEN A FACTOR. THIS WAS A CLR CUT RESPONSE TO A TCASII ALERT THAT PUT OUR ACFT IN JEOPARDY. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR SAID THAT HE WAS IN CLOUDS AT 10000 FT NEAR DWH WHEN HE GOT AN 'RA' TO CLB. AFTERWARDS, THE CTLR WAS VERY UPSET AND REQUESTED THAT THE FLC CALL THE ARTCC FACILITY. THE FACILITY SUPVR, APPARENTLY, TOLD THE RPTR THAT HIS FLT HAD MISSED AN ACR FLYING AT 11000 FT BY ONLY 100 FT AND 1.6 MI. THIS WAS A GOOD CONVERSATION, ACCORDING TO THE RPTR AND HE HAS HEARD NOTHING MORE FROM THE FAA. HIS COMPANY WAS MAINTAINING CONTACT WITH THE FAA AND HIS CHIEF PLT SAID THAT HE WOULD ADVISE THE CAPT IF ANY FURTHER ACTION WAS NECESSARY. THE RPTR IS AN INSTRUCTOR AND ONE OF HIS FELLOW INSTRUCTOR'S SONS FLIES SIMULATED DOG-FIGHT MISSIONS OUT OF DWH AND, ACCORDING TO THE RPTR, HAS HAD A NUMBER OF INCIDENTS WHERE THE CLIENTS (THE DOG- FIGHTERS) SPILLOUT OF THEIR BLOCK OF AIRSPACE. THE RPTR SAID THAT HE FORGOT TO ASK THE CTLR WHAT TYPE OF ACFT CAUSED THE 'RA.'

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.