Sfo departure controller experienced a loss of separation event involving sfo and oak departure traf...

Narrative:

I was working the sutro departure sector. A C172 was at 6;000 ft on a northbound vector approximately 10 miles west of sfo. Two departures came off sfo and one off oak simultaneously. There was a VFR transitioning at 3;500 ft northbound who was 3 miles west of sfo. I turned the VFR westbound; so I wouldn't have to restrict a B737 below him; I climbed the B737 to 10;000; then turned him westbound. Another airliner came off oakland climbing out westbound; so I had to keep the B737 turning to the west and then south; once the B737 was above 4;000; above the VFR. I also had a falcon depart sfo runway 28 straight out; I had to keep him below the B737; and also below the C172; so I only climbed him to 5;000. I turned the B737to south bound heading then heading 150. The B737 made a really wide turn; which resulted in loss of separation. Sfo tower was not taking any transitions through their airspace. This always adds to the complexity of this sector; as the radar controller is forced to climb vfrs to 3;500 ft and work them through departure traffic. I was distracted with the VFR; keeping him turning out of the way. I thought I had divergence with the B737 and the C172; but the supervisor on duty brought to my attention that he didn't think I had the required separation. The B737 was climbing out 6;600; and approximately 2 miles when they passed. About a year ago; sfo tower had a near miss with a B777 and a VFR transitioning through their airspace at 2;000 ft. The local controller forgot about the VFR and launched the B777 into him. Ever since; sfo tower has changed their procedures for VFR transitions. They just flatly refuse to work them sometimes when they have traffic and even when they don't. It has become a static restriction with them to refuse VFR transitions at certain times of the day; no matter what the traffic situation. This creates a more complex workload for the radar controller; as they often have to climb the vfrs above sfo's airspace and work them through departure traffic as they come off the airport. For years; sfo has not had any problems working vfrs through their airspace. Now it has become a huge problem. Not sure what's changed to cause the problem. Not sure of a resolution.

Original NASA ASRS Text

Title: SFO Departure Controller experienced a loss of separation event involving SFO and OAK departure traffic complicated because of SFO's refusal to allow a VFR overflight to transverse their airspace.

Narrative: I was working the Sutro Departure Sector. A C172 was at 6;000 FT on a northbound vector approximately 10 miles west of SFO. Two departures came off SFO and one off OAK simultaneously. There was a VFR transitioning at 3;500 FT northbound who was 3 miles west of SFO. I turned the VFR westbound; so I wouldn't have to restrict a B737 below him; I climbed the B737 to 10;000; then turned him westbound. Another airliner came off Oakland climbing out westbound; so I had to keep the B737 turning to the west and then south; once the B737 was above 4;000; above the VFR. I also had a Falcon depart SFO Runway 28 straight out; I had to keep him below the B737; and also below the C172; so I only climbed him to 5;000. I turned the B737to south bound heading then heading 150. The B737 made a really wide turn; which resulted in loss of separation. SFO Tower was not taking any transitions through their airspace. This always adds to the complexity of this sector; as the RADAR Controller is forced to climb VFRs to 3;500 FT and work them through departure traffic. I was distracted with the VFR; keeping him turning out of the way. I thought I had divergence with the B737 and the C172; but the supervisor on duty brought to my attention that he didn't think I had the required separation. The B737 was climbing out 6;600; and approximately 2 miles when they passed. About a year ago; SFO Tower had a near miss with a B777 and a VFR transitioning through their airspace at 2;000 FT. The Local Controller forgot about the VFR and launched the B777 into him. Ever since; SFO Tower has changed their procedures for VFR transitions. They just flatly refuse to work them sometimes when they have traffic and even when they don't. It has become a static restriction with them to refuse VFR transitions at certain times of the day; no matter what the traffic situation. This creates a more complex workload for the RADAR Controller; as they often have to climb the VFRs above SFO's airspace and work them through departure traffic as they come off the airport. For years; SFO has not had any problems working VFRs through their airspace. Now it has become a huge problem. Not sure what's changed to cause the problem. Not sure of a resolution.

Data retrieved from NASA's ASRS site as of April 2012 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	949210
Time
Date	201105
Local Time Of Day	1801-2400
Place
Locale Reference	NCT.TRACON
State Reference	CA
Aircraft 1
Make Model Name	B737-800
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Skyhawk 172/Cutlass 172
Flight Phase	Cruise
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Departure
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict

Sfo departure controller experienced a loss of separation event involving sfo and oak departure traffic complicated because of sfo's refusal to allow a VFR overflight to transverse their airspace.