Nct controller describes situation where he is concerned about separating 3 aircraft minimally by al...

Narrative:

I was working the sutro sector. Aircraft X was being vectored on a left downwind leg for the GPS RY12 approach into haf at 4;000 ft. Sfo was on the 28L/right shoreline configuration due to the runway construction. Aircraft Y departed runway 28 on the eugene departure and was stopped initially at 3;000 ft; for aircraft X. After aircraft X passed; I climbed aircraft Y to 4;000 ft because I had VFR traffic transitioning at 4;500 ft. I turned aircraft X to heading 290; for base leg. I had intended to turn aircraft Y to the southwest but I had [another aircraft] climbing out slowly ahead so I had to delay the turn. About this time; traffic became busy and complex when sfo sent two aircraft around simultaneously. Aircraft Z was sent around on 265 heading climbing to 3;100 ft. Aircraft a was sent around off the right on a 350 heading climbing to 3;000 ft. I was focused on dealing with the two go-arounds and was not aware that I didn't have enough lateral separation with aircraft X and aircraft Y. Proximity was 1.81 miles; on parallel headings. The 350 heading for go-around is not standard operating procedure. The turn put aircraft a turning towards a departure off oakland; so my focus was to turn him out of the way.I should have turned aircraft X to 310 heading and I would have had divergence. I don't have any recommendations for preventing [another] occurrence of this event. Just be vigilant.

Original NASA ASRS Text

Title: NCT Controller describes situation where he is concerned about separating 3 aircraft minimally by altitude and what he thinks is course divergence. He then has two go-arounds which takes his concentration off the other three aircraft resulting in a loss of separation.

Narrative: I was working the Sutro Sector. Aircraft X was being vectored on a left downwind leg for the GPS RY12 Approach into HAF at 4;000 FT. SFO was on the 28L/R Shoreline configuration due to the runway construction. Aircraft Y departed RWY 28 on the Eugene Departure and was stopped initially at 3;000 FT; for Aircraft X. After Aircraft X passed; I climbed Aircraft Y to 4;000 FT because I had VFR traffic transitioning at 4;500 FT. I turned Aircraft X to heading 290; for base leg. I had intended to turn Aircraft Y to the southwest but I had [another aircraft] climbing out slowly ahead so I had to delay the turn. About this time; traffic became busy and complex when SFO sent two aircraft around simultaneously. Aircraft Z was sent around on 265 heading climbing to 3;100 FT. Aircraft A was sent around off the right on a 350 heading climbing to 3;000 FT. I was focused on dealing with the two go-arounds and was not aware that I didn't have enough lateral separation with Aircraft X and Aircraft Y. Proximity was 1.81 miles; on parallel headings. The 350 heading for go-around is not standard operating procedure. The turn put Aircraft A turning towards a departure off Oakland; so my focus was to turn him out of the way.I should have turned Aircraft X to 310 heading and I would have had divergence. I don't have any recommendations for preventing [another] occurrence of this event. Just be vigilant.

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	1181035
Time
Date	201406
Local Time Of Day	1801-2400
Place
Locale Reference	SFO.Airport
State Reference	CA
Environment
Light	Dusk
Aircraft 1
Make Model Name	Small Aircraft High Wing 1 Eng Fixed Gear
Flight Phase	Cruise
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Transport Low Wing 2 Turboprop Eng
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 11
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

Nct controller describes situation where he is concerned about separating 3 aircraft minimally by altitude and what he thinks is course divergence. He then has two go-arounds which takes his concentration off the other three aircraft resulting in a loss of separation.