Pbi controller described a conflict event when IFR departure traffic had to be vectored off the SID ...

Narrative:

Aircraft X departed pbi and climbed to 12;000 ft. Aircraft Y; 15 miles east of pbi on a 090 heading talking to mia center. I noticed a VFR tag at 7;500 ft that had dropped off passing over the radar antenna and stopped aircraft X at 7;000 ft to avoid traffic. Aircraft X was on the IVNKA1 RNAV departure off pbi going to ZZZ. I called the traffic. He had the VFR on TCAS. The VFR then turned and started descending rapidly into aircraft X. I immediately took action by turning aircraft X off the RNAV SID to a 090 heading to avoid the VFR aircraft descending into him to his left. In turning him; I was basically splitting the difference between the VFR and the IFR aircraft Y east bound to myaf already on ZMA climbing out of 6;000 ft for 7;000 ft on a 090 heading. Because aircraft X was also climbing out of 6;000 ft for 7;000 ft; I believe I may have had less than 3 miles separation between him and aircraft Y. I knew they were separated as did the pilot of aircraft X. I chose the safer of 2 situations knowing I would have a loss of separation. My only recommendation would be to give pbi a class bravo airspace based on the amount of IFR and VFR traffic they work. Having VFR pilots not talking to anyone and able to climb and descend as they wish in an airspace this busy is unsafe and a disservice to the flying public.

Original NASA ASRS Text

Title: PBI Controller described a conflict event when IFR departure traffic had to be vectored off the SID to avoid descending VFR traffic; the reporter suggesting PBI be given a Class B to preclude future similar type events.

Narrative: Aircraft X departed PBI and climbed to 12;000 FT. Aircraft Y; 15 miles east of PBI on a 090 heading talking to MIA center. I noticed a VFR tag at 7;500 FT that had dropped off passing over the RADAR antenna and stopped Aircraft X at 7;000 FT to avoid traffic. Aircraft X was on the IVNKA1 RNAV departure off PBI going to ZZZ. I called the traffic. He had the VFR on TCAS. The VFR then turned and started descending rapidly into Aircraft X. I immediately took action by turning Aircraft X off the RNAV SID to a 090 heading to avoid the VFR aircraft descending into him to his left. In turning him; I was basically splitting the difference between the VFR and the IFR Aircraft Y East bound to MYAF already on ZMA climbing out of 6;000 FT for 7;000 FT on a 090 heading. Because Aircraft X was also climbing out of 6;000 FT for 7;000 FT; I believe I may have had less than 3 miles separation between him and Aircraft Y. I knew they were separated as did the pilot of Aircraft X. I chose the safer of 2 situations knowing I would have a loss of separation. My only recommendation would be to give PBI a Class Bravo airspace based on the amount of IFR and VFR traffic they work. Having VFR pilots not talking to anyone and able to climb and descend as they wish in an airspace this busy is unsafe and a disservice to the flying public.

Data retrieved from NASA's ASRS site as of July 2013 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.

Attributes
ACN	991841
Time
Date	201202
Local Time Of Day	1801-2400
Place
Locale Reference	PBI.TRACON
State Reference	FL
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Gulfstream IV / G350 / G450
Operating Under FAR Part	Part 91
Flight Phase	Climb
Flight Plan	IFR
Aircraft 2
Make Model Name	Cessna Stationair/Turbo Stationair 7/8
Flight Phase	Climb
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Departure Approach
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

Pbi controller described a conflict event when IFR departure traffic had to be vectored off the SID to avoid descending VFR traffic; the reporter suggesting pbi be given a class B to preclude future similar type events.