Narrative:

Air carrier X was on approach to runway 9R at fll at approximately 1700 ft, 2-3 mi west of the airport. Suddenly, I observed air carrier X climbing to 3000 ft. The tower said air carrier X had a TCASII alert and initiated a go around. The reason there was an aircraft in his immediate vicinity at approximately the same altitude VFR and wbound. The VFR aircraft was not in radar control or talking to any air traffic controllers at the time! Supplemental information from acn 243378: working the 'G' scope, small aircraft Y called reporting he departed fxe airport en route to mth requesting flight following at 2000 ft. His radio was poor so I asked twice for his call sign and issued a beacon code. Moments later the aircraft tagged on the runway 9L final at fll, 12 mi southwest of fxe, with the air carrier X on top at almost the same altitude. I issued traffic, stated aircraft position. The pilot said very casually he had air carrier X in sight. I informed small aircraft Y that his position was not a good place to be at this time of day. Hearing the 'left' controller report the air carrier X was going around, I called fll tower and asked if the go around was because of the small aircraft Y. The tower said yes, and air carrier X would file an near midair collision also. Pilot awareness with arsa and TCA procedures is very lacking in this area. TCA violations occur almost daily. Small aircraft Y violated the fll arsa to cause the confliction with air carrier X.

Google
 

Original NASA ASRS Text

Title: MULTIPLE RWY OP PARALLEL RWYS ACR X TCASII RA WITH SMA Y UNAUTH PENETRATION OF AIRSPACE ARSA. EVASIVE ACTION TAKEN.

Narrative: ACR X WAS ON APCH TO RWY 9R AT FLL AT APPROX 1700 FT, 2-3 MI W OF THE ARPT. SUDDENLY, I OBSERVED ACR X CLBING TO 3000 FT. THE TWR SAID ACR X HAD A TCASII ALERT AND INITIATED A GAR. THE REASON THERE WAS AN ACFT IN HIS IMMEDIATE VICINITY AT APPROX THE SAME ALT VFR AND WBOUND. THE VFR ACFT WAS NOT IN RADAR CTL OR TALKING TO ANY AIR TFC CTLRS AT THE TIME! SUPPLEMENTAL INFO FROM ACN 243378: WORKING THE 'G' SCOPE, SMA Y CALLED RPTING HE DEPARTED FXE ARPT ENRTE TO MTH REQUESTING FLT FOLLOWING AT 2000 FT. HIS RADIO WAS POOR SO I ASKED TWICE FOR HIS CALL SIGN AND ISSUED A BEACON CODE. MOMENTS LATER THE ACFT TAGGED ON THE RWY 9L FINAL AT FLL, 12 MI SW OF FXE, WITH THE ACR X ON TOP AT ALMOST THE SAME ALT. I ISSUED TFC, STATED ACFT POS. THE PLT SAID VERY CASUALLY HE HAD ACR X IN SIGHT. I INFORMED SMA Y THAT HIS POS WAS NOT A GOOD PLACE TO BE AT THIS TIME OF DAY. HEARING THE 'L' CTLR RPT THE ACR X WAS GOING AROUND, I CALLED FLL TWR AND ASKED IF THE GAR WAS BECAUSE OF THE SMA Y. THE TWR SAID YES, AND ACR X WOULD FILE AN NMAC ALSO. PLT AWARENESS WITH ARSA AND TCA PROCS IS VERY LACKING IN THIS AREA. TCA VIOLATIONS OCCUR ALMOST DAILY. SMA Y VIOLATED THE FLL ARSA TO CAUSE THE CONFLICTION WITH ACR X.

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.