F11 radar controller reported of a conflict between two aircraft. The reporter was vectoring one air...

Narrative:

Working stn (radar position); weather moving in and got really busy. This sector is one of the most complicated and busiest in F11 airspace. The sector got saturated with VFR and IFR approaches to sfb; a paola sector was opened to work the final traffic for sfb; I was working all the other airspace; all traffic off sfb and orl plus lee while paola worked just the final traffic.I had an IFR aircraft X off lee for ILS 9L at sfb. I was vectoring him towards the paola final; I saw aircraft Y on paola on the base leg; so I kept aircraft X driving towards the paola airspace. I was busy with departure traffic off the other airports and vectoring all the arrival traffic to the paola airspace. Aircraft X was in handoff status when the paola sector yelled; 'who's got aircraft X turn him north.' so I did and switched him to paola. What I didn't see was the aircraft Y was turned back out for the downwind from the base for re sequencing.both paola and stn (my sector) were out of control and very; very busy. I would be surprised if more errors are found upon review. Long time on position and over loaded sector. To complicate matters; these airports are where many flight schools operate out of. Meaning language barrier and pilot experience and understanding are very limited.recommendations:1. Staffing at F11. We routinely do not have the staffing to properly staff handoff positions and open other sectors. Help comes too little too late many times. 2. Sectorize the stn position; we need a departure side and arrival side for stn; and it needs to be charts with frequencies on VFR sectionals. 3. Display paola airspace on maps.4. I should have terminate VFR practice approaches.5. Back to staffing; the ncept (safety team) must revisit the staffing at F11 and increase this staffing; we currently work twice the aircraft annual per controller of any comparable facility and my guess many ATC 12s; we have about the highest time of position for the country; all this leads to mental fatigue. We just get worn out with busy traffic; short breaks; no spot leave; no chance of getting away from the fray for a bit.

Original NASA ASRS Text

Title: F11 Radar Controller reported of a conflict between two aircraft. The reporter was vectoring one aircraft to final; while the second aircraft was also being vectored. A loss of separation ensued. Reporter attributed loss of separation due to workload and staffing.

Narrative: Working STN (RADAR Position); weather moving in and got really busy. This sector is one of the most complicated and busiest in F11 airspace. The sector got saturated with VFR and IFR approaches to SFB; a Paola sector was opened to work the final traffic for SFB; I was working all the other airspace; all traffic off SFB and ORL plus LEE while Paola worked just the final traffic.I had an IFR Aircraft X off LEE for ILS 9L at SFB. I was vectoring him towards the Paola final; I saw Aircraft Y on Paola on the base leg; so I kept Aircraft X driving towards the Paola airspace. I was busy with departure traffic off the other airports and vectoring all the arrival traffic to the Paola airspace. Aircraft X was in handoff status when the Paola sector yelled; 'Who's got Aircraft X turn him north.' So I did and switched him to Paola. What I didn't see was the Aircraft Y was turned back out for the downwind from the base for re sequencing.Both Paola and STN (my sector) were out of control and very; very busy. I would be surprised if more errors are found upon review. Long time on position and over loaded sector. To complicate matters; these airports are where many flight schools operate out of. Meaning language barrier and pilot experience and understanding are very limited.Recommendations:1. Staffing at F11. We routinely do not have the staffing to properly staff handoff positions and open other sectors. Help comes too little too late many times. 2. Sectorize the STN position; we need a departure side and arrival side for STN; and it needs to be charts with frequencies on VFR sectionals. 3. Display Paola airspace on maps.4. I should have terminate VFR practice approaches.5. Back to staffing; the NCEPT (Safety Team) must revisit the staffing at F11 and increase this staffing; we currently work twice the aircraft annual per controller of any comparable facility and my guess many ATC 12s; we have about the highest time of position for the country; all this leads to mental fatigue. We just get worn out with busy traffic; short breaks; no spot leave; no chance of getting away from the fray for a bit.

Data retrieved from NASA's ASRS site 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	1373055
Time
Date	201607
Local Time Of Day	0601-1200
Place
Locale Reference	F11.TRACON
State Reference	FL
Environment
Light	Daylight
Aircraft 1
Make Model Name	Small Aircraft Low Wing 1 Eng Fixed Gear
Operating Under FAR Part	Part 91
Flight Phase	Initial Approach
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Aircraft Low Wing 1 Eng Fixed Gear
Operating Under FAR Part	Part 91
Flight Phase	Initial Approach
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Approach Departure
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 15
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types Inflight Event / Encounter Weather / Turbulence

F11 radar controller reported of a conflict between two aircraft. The reporter was vectoring one aircraft to final; while the second aircraft was also being vectored. A loss of separation ensued. Reporter attributed loss of separation due to workload and staffing.