Narrative:

Departed pdk on vectors. Cleared to climb to 9000 ft. Passing 8300 ft got a 'TA' and saw target at 8700 ft on my left. I stopped climb at 8500 ft and DC9 type passed overhead. Controller also told me to stop climb, but I already had. I did not see target until it was close. This is a frequent problem that is caused by 'selectivity' programmed into set. I wasn't told of this during training, but learned it through complaining to technical people at cessna. Equipment is bendix/king/allied signal tcasi. Callback conversation with reporter revealed the following information: reporter captain says that 'selectivity' refers to the FAA concerns of over saturation of the TCAS system and has potential for disrupting their capability. Consequently, the software for tcasi was developed to alert only in close encounters and not as broad coverage as TCASII. Reporter says that generally tcasi won't alert on traffic more than 2 mi, but if there is very light traffic and not much interrogations, it is possible to see traffic farther away. If the traffic is paralleling the tcasi aircraft, it may drop it as a threat, but if that traffic turns and closes the distance, then tcasi will bring it back. In this case the controller turned the intruder into the reporter aircraft and, had the reporter not taken evasive action by leveling until clear of traffic, it could have been a very near midair.

Related reports:

Google
 

Original NASA ASRS Text

Title: TCASI RA DURING CLB. RPTR STOPPED CLB WHEN OBSERVING TCAS TFC. IT WAS A DC9 BEING VECTORED BY DEP CTL. OPERROR PUT ACFT TOO CLOSE AND TCASI PREVENTED THEM BEING CLOSER. RPTR CAPT WOULD LIKE TCASI TO PROVIDE MORE TFC READOUTS AND AT GREATER DISTANCES. RPTR SAYS TCASI USUALLY WILL ALERT ONLY ON IMMEDIATE THREATS WITHIN 2 MI.

Narrative: DEPARTED PDK ON VECTORS. CLRED TO CLB TO 9000 FT. PASSING 8300 FT GOT A 'TA' AND SAW TARGET AT 8700 FT ON MY L. I STOPPED CLB AT 8500 FT AND DC9 TYPE PASSED OVERHEAD. CTLR ALSO TOLD ME TO STOP CLB, BUT I ALREADY HAD. I DID NOT SEE TARGET UNTIL IT WAS CLOSE. THIS IS A FREQUENT PROB THAT IS CAUSED BY 'SELECTIVITY' PROGRAMMED INTO SET. I WASN'T TOLD OF THIS DURING TRAINING, BUT LEARNED IT THROUGH COMPLAINING TO TECHNICAL PEOPLE AT CESSNA. EQUIP IS BENDIX/KING/ALLIED SIGNAL TCASI. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR CAPT SAYS THAT 'SELECTIVITY' REFERS TO THE FAA CONCERNS OF OVER SATURATION OF THE TCAS SYS AND HAS POTENTIAL FOR DISRUPTING THEIR CAPABILITY. CONSEQUENTLY, THE SOFTWARE FOR TCASI WAS DEVELOPED TO ALERT ONLY IN CLOSE ENCOUNTERS AND NOT AS BROAD COVERAGE AS TCASII. RPTR SAYS THAT GENERALLY TCASI WON'T ALERT ON TFC MORE THAN 2 MI, BUT IF THERE IS VERY LIGHT TFC AND NOT MUCH INTERROGATIONS, IT IS POSSIBLE TO SEE TFC FARTHER AWAY. IF THE TFC IS PARALLELING THE TCASI ACFT, IT MAY DROP IT AS A THREAT, BUT IF THAT TFC TURNS AND CLOSES THE DISTANCE, THEN TCASI WILL BRING IT BACK. IN THIS CASE THE CTLR TURNED THE INTRUDER INTO THE RPTR ACFT AND, HAD THE RPTR NOT TAKEN EVASIVE ACTION BY LEVELING UNTIL CLR OF TFC, IT COULD HAVE BEEN A VERY NEAR MIDAIR.

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.