Narrative:

While working ar-I I handed off air carrier X to ar-F and affected a frequency change. While scanning my airspace and adjoining sectors I noticed an small aircraft squawking VFR northbound mode C indicating 9500 ft. I noticed that the traffic was a factor for air carrier X and attempted to alert the controller working air carrier X. The ar-F controller was busy and I could not get his attention. I observed the 2 aircraft pass then heard the ar-F controller inform the watch supervisor that air carrier X was conducting an RA for the traffic. Air carrier X climbed and put himself in conflict with air carrier Y at 11000 ft 2 mi in front of air carrier X. A system error occurred between these 2 IFR aircraft. Air carrier Y was being worked by ZMA. I believe this system error occurred because of TCASII's inability to provide adequate information and safe RA's. Air carrier X executed the RA after the VFR small aircraft had passed and traffic was no longer a factor. Due to sector saturation traffic was not issued to air carrier X on the VFR small aircraft. Supplemental information from acn 241246: I was working air carrier Y at 11000 ft. Palm beach approach was working air carrier X at 10000 ft who did a TCASII maneuver for an small aircraft VFR at 9500 ft air carrier X climbed into air carrier Y without me having any idea the aircraft was involved in a TCASII maneuver or going to stop at 10500 ft. Since air carrier X was being worked by another facility I was not informed of the maneuver at all. Furthermore, the air carrier X flight plan did not indicate he had TCASII. The flight plan on the air carrier Y indicated he had TCASII. After the aircraft passed I asked the air carrier Y pilot if he got a TCASII alert. He then informed me his TCASII was broken.

Google
 

Original NASA ASRS Text

Title: TCASII INDUCED LTSS. ACR X TCASII RA FROM VFR SMA HAD LTSS FROM ACR Y. PLTDEV.

Narrative: WHILE WORKING AR-I I HANDED OFF ACR X TO AR-F AND AFFECTED A FREQ CHANGE. WHILE SCANNING MY AIRSPACE AND ADJOINING SECTORS I NOTICED AN SMA SQUAWKING VFR NBOUND MODE C INDICATING 9500 FT. I NOTICED THAT THE TFC WAS A FACTOR FOR ACR X AND ATTEMPTED TO ALERT THE CTLR WORKING ACR X. THE AR-F CTLR WAS BUSY AND I COULD NOT GET HIS ATTN. I OBSERVED THE 2 ACFT PASS THEN HEARD THE AR-F CTLR INFORM THE WATCH SUPVR THAT ACR X WAS CONDUCTING AN RA FOR THE TFC. ACR X CLBED AND PUT HIMSELF IN CONFLICT WITH ACR Y AT 11000 FT 2 MI IN FRONT OF ACR X. A SYS ERROR OCCURRED BTWN THESE 2 IFR ACFT. ACR Y WAS BEING WORKED BY ZMA. I BELIEVE THIS SYS ERROR OCCURRED BECAUSE OF TCASII'S INABILITY TO PROVIDE ADEQUATE INFO AND SAFE RA'S. ACR X EXECUTED THE RA AFTER THE VFR SMA HAD PASSED AND TFC WAS NO LONGER A FACTOR. DUE TO SECTOR SATURATION TFC WAS NOT ISSUED TO ACR X ON THE VFR SMA. SUPPLEMENTAL INFO FROM ACN 241246: I WAS WORKING ACR Y AT 11000 FT. PALM BEACH APCH WAS WORKING ACR X AT 10000 FT WHO DID A TCASII MANEUVER FOR AN SMA VFR AT 9500 FT ACR X CLBED INTO ACR Y WITHOUT ME HAVING ANY IDEA THE ACFT WAS INVOLVED IN A TCASII MANEUVER OR GOING TO STOP AT 10500 FT. SINCE ACR X WAS BEING WORKED BY ANOTHER FACILITY I WAS NOT INFORMED OF THE MANEUVER AT ALL. FURTHERMORE, THE ACR X FLT PLAN DID NOT INDICATE HE HAD TCASII. THE FLT PLAN ON THE ACR Y INDICATED HE HAD TCASII. AFTER THE ACFT PASSED I ASKED THE ACR Y PLT IF HE GOT A TCASII ALERT. HE THEN INFORMED ME HIS TCASII WAS BROKEN.

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.