Narrative:

I was PIC from pbi to mia. 2-3 mins into our departure from runway 13 at pbi, as we contacted pbi departure control, our instructions were to climb and maintain 2000 ft. Just before leveloff we had a TCASII traffic resolution showing this at our 12 O'clock and less than 1/2 mi head-on and our altitude, TCASII computer resolved to climb. Since we were on VMC conditions and this traffic was not in sight, I instructed the first officer to continue his climb to 2500 ft, thus complying with our TCASII RA. ATC warned us about our altitude to which I only had the time to reply, 'we had a TCASII RA, we took the climb.' we noted a second traffic who was at our 11 O'clock position and approximately 3 1/2 mi away at 3000 ft. Thus we decided to stay 500 ft below him and 500 ft on top of the conflicting one as to avoid changing our heading. For a second time, I told ATC about our TCASII RA and for a second time, no acknowledgement was made by ATC. The fact is that this type of event is not isolated and it happens on a regular basis. We are always vectored at 3000 ft from pbi to mia, over the everglades, on IFR flight plans (VMC or IMC) right in the middle of training areas used by student pilots as well as more advanced pilots, using experimental aircraft doing acrobatics. On one of the many instances this had happened to me, our conflicting traffic was a biplane, on a spin diving towards us. I feel regionals should be also kept in STAR's profile. It's too dangerous to cruise around training areas.

Google
 

Original NASA ASRS Text

Title: WHILE ATTEMPTING TO COMPLY WITH TCASII RA THE RPTR AVOIDED ONE ACFT BY 500 FT BUT CAME 500 FT TOO CLOSE TO ANOTHER ACFT IN THE PROCESS. THE RPTR SUGGESTS TRACON NOT TAKE REGIONAL ACRS OFF DEP RTES AND INTO TRAINING AREAS.

Narrative: I WAS PIC FROM PBI TO MIA. 2-3 MINS INTO OUR DEP FROM RWY 13 AT PBI, AS WE CONTACTED PBI DEP CTL, OUR INSTRUCTIONS WERE TO CLB AND MAINTAIN 2000 FT. JUST BEFORE LEVELOFF WE HAD A TCASII TFC RESOLUTION SHOWING THIS AT OUR 12 O'CLOCK AND LESS THAN 1/2 MI HEAD-ON AND OUR ALT, TCASII COMPUTER RESOLVED TO CLB. SINCE WE WERE ON VMC CONDITIONS AND THIS TFC WAS NOT IN SIGHT, I INSTRUCTED THE FO TO CONTINUE HIS CLB TO 2500 FT, THUS COMPLYING WITH OUR TCASII RA. ATC WARNED US ABOUT OUR ALT TO WHICH I ONLY HAD THE TIME TO REPLY, 'WE HAD A TCASII RA, WE TOOK THE CLB.' WE NOTED A SECOND TFC WHO WAS AT OUR 11 O'CLOCK POS AND APPROX 3 1/2 MI AWAY AT 3000 FT. THUS WE DECIDED TO STAY 500 FT BELOW HIM AND 500 FT ON TOP OF THE CONFLICTING ONE AS TO AVOID CHANGING OUR HDG. FOR A SECOND TIME, I TOLD ATC ABOUT OUR TCASII RA AND FOR A SECOND TIME, NO ACKNOWLEDGEMENT WAS MADE BY ATC. THE FACT IS THAT THIS TYPE OF EVENT IS NOT ISOLATED AND IT HAPPENS ON A REGULAR BASIS. WE ARE ALWAYS VECTORED AT 3000 FT FROM PBI TO MIA, OVER THE EVERGLADES, ON IFR FLT PLANS (VMC OR IMC) RIGHT IN THE MIDDLE OF TRAINING AREAS USED BY STUDENT PLTS AS WELL AS MORE ADVANCED PLTS, USING EXPERIMENTAL ACFT DOING ACROBATICS. ON ONE OF THE MANY INSTANCES THIS HAD HAPPENED TO ME, OUR CONFLICTING TFC WAS A BIPLANE, ON A SPIN DIVING TOWARDS US. I FEEL REGIONALS SHOULD BE ALSO KEPT IN STAR'S PROFILE. IT'S TOO DANGEROUS TO CRUISE AROUND TRAINING AREAS.

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.