Narrative:

The traffic that caused the RA was VFR. We were descending on v- 226 south of cip VOR and the clearance was to cross grace at 10000 ft and 250 KTS. The center controller was working the VFR traffic as well as us. The controller told the VFR that he was climbing into an arrival corridor and was in conflict with several jets descending into pit. The controller recommended a turn of 10 degrees to avoid the arrival traffic. The VFR went by the airplane in front of us evidently without a problem. At this time, we noticed the traffic on TCASII. The traffic was at 12 O'clock about 1000 ft below us and climbing. The controller never issued the traffic to us. As we watched the traffic approach, I expected the controller to give one of us a vector, but he did not. Next, we got a TA, which was not a surprise at this point. I told the copilot to be prepared for an RA. TCASII issued an RA to climb within seconds. So we began the climb maneuver at approximately 11000 ft, we got a clear of conflict advisory at 12000 ft. We advised the center controller that we were climbing in response to an RA. His response was that the traffic was clear to the right of us. I told him that we were still required to respond to the RA. He said okay and that he understood. Shortly after the conflict, he handed us off to pit approach. I told the approach controller that we would be unable to cross grace at 10000 ft and 250 KTS due to responding to the previously issued RA. I called pit approach control on the telephone after we landed to make sure that they were fully aware of what happened, and to explain why we did not cross grace at our assigned speed and altitude. The supervisor said that there was no problem in relation to the event. He said that they saw the conflict but, of course, were not working either of us at the time.

Related reports:

Google
 

Original NASA ASRS Text

Title: TCASII RA CAUSES MLG FLC TO DEVIATE FROM CLRNC. ALTDEV ALT UNDERSHOT. POTENTIAL CONFLICT.

Narrative: THE TFC THAT CAUSED THE RA WAS VFR. WE WERE DSNDING ON V- 226 S OF CIP VOR AND THE CLRNC WAS TO CROSS GRACE AT 10000 FT AND 250 KTS. THE CTR CTLR WAS WORKING THE VFR TFC AS WELL AS US. THE CTLR TOLD THE VFR THAT HE WAS CLBING INTO AN ARR CORRIDOR AND WAS IN CONFLICT WITH SEVERAL JETS DSNDING INTO PIT. THE CTLR RECOMMENDED A TURN OF 10 DEGS TO AVOID THE ARR TFC. THE VFR WENT BY THE AIRPLANE IN FRONT OF US EVIDENTLY WITHOUT A PROB. AT THIS TIME, WE NOTICED THE TFC ON TCASII. THE TFC WAS AT 12 O'CLOCK ABOUT 1000 FT BELOW US AND CLBING. THE CTLR NEVER ISSUED THE TFC TO US. AS WE WATCHED THE TFC APCH, I EXPECTED THE CTLR TO GIVE ONE OF US A VECTOR, BUT HE DID NOT. NEXT, WE GOT A TA, WHICH WAS NOT A SURPRISE AT THIS POINT. I TOLD THE COPLT TO BE PREPARED FOR AN RA. TCASII ISSUED AN RA TO CLB WITHIN SECONDS. SO WE BEGAN THE CLB MANEUVER AT APPROX 11000 FT, WE GOT A CLR OF CONFLICT ADVISORY AT 12000 FT. WE ADVISED THE CTR CTLR THAT WE WERE CLBING IN RESPONSE TO AN RA. HIS RESPONSE WAS THAT THE TFC WAS CLR TO THE R OF US. I TOLD HIM THAT WE WERE STILL REQUIRED TO RESPOND TO THE RA. HE SAID OKAY AND THAT HE UNDERSTOOD. SHORTLY AFTER THE CONFLICT, HE HANDED US OFF TO PIT APCH. I TOLD THE APCH CTLR THAT WE WOULD BE UNABLE TO CROSS GRACE AT 10000 FT AND 250 KTS DUE TO RESPONDING TO THE PREVIOUSLY ISSUED RA. I CALLED PIT APCH CTL ON THE TELEPHONE AFTER WE LANDED TO MAKE SURE THAT THEY WERE FULLY AWARE OF WHAT HAPPENED, AND TO EXPLAIN WHY WE DID NOT CROSS GRACE AT OUR ASSIGNED SPD AND ALT. THE SUPVR SAID THAT THERE WAS NO PROB IN RELATION TO THE EVENT. HE SAID THAT THEY SAW THE CONFLICT BUT, OF COURSE, WERE NOT WORKING EITHER OF US AT THE TIME.

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.