Narrative:

While being vectored by new york approach control for the teb VOR/DME a approach, we were instructed to depart sbj on a heading (040 degrees?). At our assigned altitude of 3000 ft, TCASII issued a traffic alert. On the TCASII display, I noticed traffic at approximately 2 O'clock position, 2 NM, 300 ft (I can't remember above or below) and closing. Shortly thereafter, TCASII issued an RA of 'climb, climb, climb.' I immediately disconnected the autoplt, added power, and initiated a climb at the target rate. I instructed my first officer to notify ATC that we were climbing for an RA. Due to frequency congestion, I'm not sure that ATC heard our transmission, though I did hear the controller instruct what I believe to be the other aircraft: 'I really need you to continue your descent to 2500 ft now,' or something to that effect. I stopped the climb at 3600 ft as TCASII informed us that we were 'clear of conflict,' and descended back to our assigned altitude of 3000 ft. I instructed the first officer to inform ATC that we had climbed to 3600 ft for an RA, though the first officer did not use the term 'RA.' instead, the first officer used the term 'traffic conflict.' the controller responded by saying, 'you gotta do what you gotta do.' the remainder of the flight proceeded uneventfully to teterboro. I am not certain of an actual miss distance, but was glad to have TCASII. Not all of our aircraft have TCASII installed. I believe that the other aircraft's delayed compliance with ATC's descent instruction coupled with very congested airspace and an extremely busy controller contributed to this event.

Related reports:

Google
 

Original NASA ASRS Text

Title: C560 FLT EXPERIENCED TCASII RA AT 3000 FT DURING VECTORS FROM N90, LNDG MMU.

Narrative: WHILE BEING VECTORED BY NEW YORK APCH CTL FOR THE TEB VOR/DME A APCH, WE WERE INSTRUCTED TO DEPART SBJ ON A HDG (040 DEGS?). AT OUR ASSIGNED ALT OF 3000 FT, TCASII ISSUED A TFC ALERT. ON THE TCASII DISPLAY, I NOTICED TFC AT APPROX 2 O'CLOCK POS, 2 NM, 300 FT (I CAN'T REMEMBER ABOVE OR BELOW) AND CLOSING. SHORTLY THEREAFTER, TCASII ISSUED AN RA OF 'CLB, CLB, CLB.' I IMMEDIATELY DISCONNECTED THE AUTOPLT, ADDED PWR, AND INITIATED A CLB AT THE TARGET RATE. I INSTRUCTED MY FO TO NOTIFY ATC THAT WE WERE CLBING FOR AN RA. DUE TO FREQ CONGESTION, I'M NOT SURE THAT ATC HEARD OUR XMISSION, THOUGH I DID HEAR THE CTLR INSTRUCT WHAT I BELIEVE TO BE THE OTHER ACFT: 'I REALLY NEED YOU TO CONTINUE YOUR DSCNT TO 2500 FT NOW,' OR SOMETHING TO THAT EFFECT. I STOPPED THE CLB AT 3600 FT AS TCASII INFORMED US THAT WE WERE 'CLR OF CONFLICT,' AND DSNDED BACK TO OUR ASSIGNED ALT OF 3000 FT. I INSTRUCTED THE FO TO INFORM ATC THAT WE HAD CLBED TO 3600 FT FOR AN RA, THOUGH THE FO DID NOT USE THE TERM 'RA.' INSTEAD, THE FO USED THE TERM 'TFC CONFLICT.' THE CTLR RESPONDED BY SAYING, 'YOU GOTTA DO WHAT YOU GOTTA DO.' THE REMAINDER OF THE FLT PROCEEDED UNEVENTFULLY TO TETERBORO. I AM NOT CERTAIN OF AN ACTUAL MISS DISTANCE, BUT WAS GLAD TO HAVE TCASII. NOT ALL OF OUR ACFT HAVE TCASII INSTALLED. I BELIEVE THAT THE OTHER ACFT'S DELAYED COMPLIANCE WITH ATC'S DSCNT INSTRUCTION COUPLED WITH VERY CONGESTED AIRSPACE AND AN EXTREMELY BUSY CTLR CONTRIBUTED TO THIS EVENT.

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.