1.  PURPOSE.

This Standard Operating Procedure (SOP) outlines the procedures to be used by controllers working a Norcal Approach "Sutro" Sector, the primary airports KSFO and KOAK, and satellite airports, to ensure that traffic flows are handled in as efficient and timely a manner as possible. By specifying standard handoff points, departure and arrival routes, coordination between adjacent facilities may be greatly reduced.

2. ROLES AND RESPONSIBILITIES.

The Office of Primary Responsibility (OPR) for this SOP is the ZOA Facility Advisory Board. This SOP shall be maintained, revised, updated or cancelled by the ZOA Facility Advisory Board. Any suggestions for modification / amendment to this SOP should be sent to the FAB for review.

3.  DISTRIBUTION.

This SOP is intended for use by controllers staffing positions within Norcal TRACON "Sutro" sector airspace, as well as controllers working at positions interfacing with Norcal TRACON "Sutro" sector facilities. 

4. BACKGROUND.

Over time, controllers have found that having aircraft arrive via pre-approved arrival routes, either by STAR’s (Standard Terminal Arrival Routes) or via vectors through pre-determined arrival fixes, provides for a more orderly traffic flow, and reduces the need for communication between Norcal Approach and other Norcal TRACON and ZOA Center positions. It is also vitally important that all facilities understand what an airplane is going to do (i.e., what altitude he has been cleared to) when he approaches an adjacent controller's airspace. These procedures outline what instructions pilots will be issued as they go from controller to controller.

5. PRIMARY RESPONSIBILITIES.

1. Separate SFO and OAK departures during normal (west) operations.

2. Sequence SFO and OAK arrivals into SFO_APP airspace during east operations.

3. Work SFO 10L/R arrivals when those runways are in use.

4. Sequence and separate STS arrivals and departures.

6. PROCEDURES.

a. Frequencies and  Callsigns

1. Norcal approach "Sutro" sector shall use 135.1 as its frequency and STS_APP as text call

2. When handling arrivals and transitions, Norcal Approach shall use "Norcal Approach" as voice call sign. When handling departures, Norcal Approach shall use "Norcal Departure" as voice call sign.

3. Frequencies for secondary airports should be determined from appropriate publications.

b. Airspace and Sectorization Plan:

1. STS_APP shall own the airspace within the lateral limits depicted on this graphic in west ops and this graphic in east ops from surface to FL230, excepting all actively manned Class D airspace within the lateral limits.

2. The Sector file authorized for use in operating this sector is the certified Oakland Center sector file available on the "downloads" page of the ZOA ARTCC web site.

c. Release Procedures and Runway Use Plans - West Flow Operations:

1. STS_APP and CCR_APP share the airspace between OAK and SFO. Initial separation of departures/missed approaches will be provided by the respective tower. Careful attention must be paid to the procedures in this section and SOP_050 to ensure separation of departures from OAK and SFO.

2. At SFO, departures will be handled as set forth in SOP_050. SOP_050 restricts west/south departures to specific DPs/routing. Releases are required for other DPs due to the need for coordination between STS and CCR_APP to avoid conflicts with other SFO/OAK departures. Releases may be required at other times at STS_APP's discretion.

3. At OAK, departures will be handled as set forth in SOP_050. SOP_050 restricts west/south departures to specific DPs/routing. Releases are required for other DPs due to the need for coordination between STS and CCR_APP to avoid conflicts with other SFO/OAK departures. Releases may be required at other times at CCR_APP's discretion.

d. Release Procedures and Runway Use Plans – All Operations:

1.The active runway plan for SFO will be determined by SFO_TWR per SOP_050. Normal prevailing winds are from the west, using runways 28 and runways 1.

2. The active runway plan for OAK will be determined by OAK_TWR per SOP_050. Normal prevailing winds are from the west, using runway 29 and runways 27.

3. Departure release procedures with STS_TWR will only be in use upon request by STS_APP.

e. Special Instructions:

1. Aircraft arriving on flight plans indicating “NO STAR” (or those that have not filed for an approved STAR) shall have their clearances amended to approved STAR’s listed in this SOP, so that all traffic is placed on consistent arrivals streams.

2. Aircraft filing “NO SID” (or those that have not filed for an approved SID) shall be have their clearances amended to approved SID’s listed in this SOP, so that all traffic is placed on consistent departure streams.

3. During normal/west ops SFO_APP and OAK_APP shall assume control of the respective towers.

4. During east ops, SFO_APP shall assume control of both SFO_TWR and OAK_TWR.

5. During all ops, if STS_TWR is not online, STS_APP shall assume control of the STS_TWR position.

f. Normal (West Flow) Operations - Bay Arrivals:

1. GOLDN5 arrivals for SFO are received from OAK_C_CTR with instructions to “descend at pilot’s discretion, maintain FL240”. This is the preferred arrival for SFO from the north. STS_APP shall instruct aircraft to “cross LOZIT 11000”. By default, aircraft shall be instructed to "Depart SFO VOR heading 140", to expect runway 28L, scratched "v8L" or "i8L" based on weather, and handed off to SFO_APP at 11000. If SFO_APP wishes to accept arrivals on the "Slam-Dunk" / "Down the Bay," arrival to 28R, they will request a pointout from STS_APP. When this happens, aircraft must be instructed to "Turn left heading 100" at the western shoreline of the pacific ocean (near DUXBY intersection), scratched "v8R" or "i8R" based on weather, and handed off to SFO_APP AS SOON AS POSSIBLE so that SFO_APP may start their descent from 11000. By granting the pointout, STS_APP accepts responsibility to protect the GOLDN5 aircraft from their PORTE3/OFFSH5 and SKYL3/COAST5 departures while it's in their airspace.

Consult the Norcal Approach "Woodside" sector (SFO_APP) SOP for more in depth information on this arrival and how Sutro and Woodside can effectively work it as a team.

2. PYE1 arrivals for SFO are received from OAK_C_CTR with instructions to “descend at pilot’s discretion, maintain FL240”. STS_APP shall instruct aircraft to “cross STINS 11000 and HADLY 7000" and handoff to SFO_APP. 

3. Oceanic arrivals for OAK are received from OAK_A_CTR with instructions to cross PYE 7000 to pass beneath the PYE1 and GOLDN5 streams. Hand these arrivals to CCR_APP.

4. Oceanic arrivals for SFO are received from OAK_A_CTR routed BRINY.OSI with instructions to cross BRINY at 8000 or 25 DME SW of OSI at 8000. These aircraft shall be merged with PYE1 arrivals and handed to SFO_APP.

5. Oceanic arrivals for SJC are received from OAK_A_CTR routed SFO.SJC with instructions to cross SFO at 12000. These aircraft shall be merged with GOLDN5 arrivals, instructed to depart SFO heading 110, and passed to SJC_APP (SJC_APP has shelf above SFO_APP from 12000-15000).

6. GOLDN5 arrivals for SJC are received from OAK_C_CTR with instructions to “descend at pilot’s discretion, maintain FL240”. STS_APP shall instruct aircraft to ”cross Duxby at 12000”. These aircraft shall be merged with Oceanic arrivals and instructed to depart SFO heading 110. Hand off these arrivals to SJC_APP.

7. Missed approaches off SFO are passed to STS_APP by SFO_TWR with instructions to “fly runway heading, c/m 5000.” These aircraft shall be vectored onto a downwind reference the MVAs, sequenced with other SFO arrivals, and handed off to SFO_APP.

g. Normal (West Flow) Operations - Bay Departures:

1. SFO PORTE3, OFFSH5, EUGEN5, and MOLEN3 departures may proceed via pilot navigation. 1L/R departures should be monitored closely to ensure they begin the turn promptly at 4 DME to avoid conflict with OAK departures.

2. GAPP3 westbound departures shall be vectored on course as MVA permits. Departures off 1L/R shall be vectored as soon as practical to avoid conflict with OAK departures.

3. CCR_APP works all north/east SFO8 departures; these departures will normally use 1L/R, if 28L/R is used CCR_APP must point these departures out to STS_APP prior to release to avoid conflict with other traffic.

4. CUIT2 and REBAS3 DPs are handled by CCR_APP. These DPs always require a release from CCR_APP and prior to releasing these departures, CCR_APP must point them out to STS_APP prior to release to avoid conflict with other SFO and OAK departures.

5. North/Eastbound departures off runways 28L/R shall be assigned the SHOR1 DP when weather permits. CCR_APP will handle these departures and they shouldn't be a factor for STS_APP's traffic.

6. If any other DP is used for North/eastbound departures off SFO, CCR_APP is required to point them out to STS_APP prior to issuing the required release.

7. OAK NUEVO5 departures shall proceed under pilot navigation to until reaching 3000' and then be vectored to join the SAU 168 radial and instructed to resume own navigation. These should be handed off to MRY_APP (127.15) at/below 15,000', or OAK_A_CTR (128.70) above 15,000'.

8. OAK SKYL3 and COAST5 departures shall proceed under pilot navigation to until reaching 2000' and then be vectored to join the DP and instructed to resume own navigation, and handed off to OAK_A_CTR (128.70).

9. OAK OAK5 departures shall be vectored on course as MVAs permit.

10. Use of any other DP off OAK for west/southbound aircraft shall require OAK_TWR to obtain a release from STS_APP and prior to releasing these departures, STS_APP must point them out to CCR_APP to avoid conflict with other SFO and OAK departures.

h. East Flow Operations – Bay Arrivals:

1. SFO_APP has a relatively small airspace area. STS_APP and CCR_APP are set up to feed a predictable stream of arrival aircraft so that SFO_APP can handle the arrivals in its airspace. SFO_APP may place restrictions on arrivals at any time by contacting STS_APP and/or CCR_APP. SFO_APP may require a certain number of miles-in-trail (MIT) between arrivals. During busy periods, when the controller feels that parallel visual approaches are not practical to 19L/R at SFO, it is recommended that SFO_APP require 10 MIT between arrival aircraft coming from the feeder sectors.

2. HADLY2 arrivals for SFO and OAK are received from MRY_APP with instructions to descend to 6000; handle these arrivals as follows:

a. SFO arrivals landing 19L/R – Merge these aircraft with any STINS or Oceanic arrivals and about 10 miles south of SAU assign a heading of 010; hand to SFO_APP with an assigned speed of 210 knots.

b. SFO arrivals landing 10L/R – This configuration is very rare, the preferred east ops configuration is landing 19L/R. If winds require the use of 10L/R, vector these arrivals to final reference other arrivals.

c. OAK arrivals – Leave these aircraft routed over SAU. Sequence with oceanic arrivals and ensure there will be no conflict with RAIDR arrivals in SFO_APP airspace. Hand to SFO_APP at 6000 with an assigned speed of 210 knots.

3. RAIDR2 arrivals are received from OAK_C_CTR with instructions to “descend at pilot’s discretion, maintain FL240”. STS_APP shall instruct aircraft to cross RAIDR at 5000. Ensure there will be no conflict with OAK HADLY arrivals in SFO_APP airspace and handoff to SFO_APP on the RAIDR arrival (or direct SAU if vectored off the arrival track) with an assigned speed of 210 knots.

4. STINS1 arrivals for SFO are received from OAK_C_CTR with instructions to “descend at pilot’s discretion, maintain FL240”. STS_APP shall instruct aircraft to cross PYE at 9000 (jets) or 7000 (props); handle these aircraft as follows:

a. SFO arrivals landing 19L/R – Merge these aircraft with any HADLY or oceanic arrivals. Descend these aircraft to 6000 and about 10 miles west of SFO assign a heading of 010 and hand to SFO_APP with an assigned speed of 210 knots.

b. SFO arrivals landing 10L/R – This configuration is very rare, the preferred east ops configuration is landing 19L/R. If winds require the use of 10L/R, vector these aircraft to final reference other arrivals.

5. Oceanic arrivals for SFO / OAK are received from OAK_A_CTR with instructions to cross SAU at 6000; handle these aircraft as follows:

a. OAK arrivals – Leave these aircraft routed over SAU. Sequence with any HADLY arrivals and ensure there will be no conflict with RAIDR arrivals in SFO_APP airspace. Hand to SFO_APP at 6000 with an assigned speed of 210 knots.

b. SFO arrivals landing 19L/R – Merge these aircraft with any HADLY or STINS arrivals. Hand these arrivals to SFO_APP on a heading of 010 with an assigned speed of 210 knots.

c. SFO arrivals landing 10L/R – This configuration is very rare, the preferred east ops configuration is landing 19L/R. If winds require the use of 10L/R, vector these aircraft to final reference other arrivals.

6. When landing on runways 10L/R, arrivals from the east are received from SFO_APP on a heading of 200 descending to 5000. Vector these aircraft to final reference other traffic.

7. BRINY1 arrivals to SJC are received from OAK_C_CTR with instructions to “descend at pilot’s discretion, maintain FL240”. STS_APP shall instruct aircraft to “cross FATHM at 11000' and 250 knots, and BRINY at 5000” and hand off to MRY_APP.

i. East Flow Operations – Bay Departures

1. MOLEN3 departures from SFO are received from HWD_APP on course. Separate these aircraft from arrivals and pass to OAK_C_CTR.

2. Other bay departures may be received from or pointed out by MRY_APP depending on routing.

j. STS Arrivals:

1. During west operations, IFR Arrivals for runway 32...

i. from the north (ENI, V494), and can accept a full approach, shall be instructed to "cross STS at or above 4000" and cleared for the ILS 32 prior to STS.

ii. from east (POPES, SGD), and can accept a full approach, shall be instructed to "cross SGD at 3600" and cleared for the ILS 32 prior to SGD.

iii.  from the southwest (PYE), and can accept a full approach, shall be instructed to "cross PYE at or above 3000" and cleared for the ILS 32 prior to PYE.

iv. from the south (SAU), and can accept a full approach shall be instructed "cross SAU at 4000" and cleared for the ILS 32 prior to SAU.

2. During east operations, under IMC, IFR arrivals for runway 14 should be routed via direct STS (or vectored onto the final approach course) and cleared for the VOR/DME 14.

3. Missed Approach instructions may be assigned per the published procedures or alternately climbed to 2000' on runway heading to be given a right or left turn as appropriate for re-sequencing downwind, and climbed to 4000. NOTE: Mountains (as high as 4482 ft) north and east of the airport.

k. STS Departures:

1. FREES5 and STS5 departures shall proceed under pilot navigation.

2. Aircraft on the STS5.SGD should be handed off to CCR_APP (120.90) prior to SNUPY.

3. Departures climbing above TRACON ceiling shall be handed to OAK_C_CTR (128.80).

4. Obstacle Departure procedure "Rwy 1, 19 and 32 climb to 1800' then climbing left turn; Rwy 14, climb to 1800 then climbing right turn. All aircraft climb direct STS VOR," shall be given out as the Santa Rosa Published Departure Procedure.

l. IFR Low Altitude Routing:

From STS:

SFO, SQL and PAO arrivals via PYE V25-27 V199 SFO

Oakland arrivals via SGD V108 V195 OAK

Sacramento arrivals via STS V494 SAC

East Bay arrivals via SGD V108 CCR

Valley sector arrivals via SGD V108 LIN

San Jose arrivals via PYE V25-27 V199 SFO V25-87 OSI

Monterey arrivals via PYE V27 SHOEY

m. Additional Comments:

1. Oceanic arrivals to SMF will be routed over OAK. A fixed pointout exists during west ops in STS_APP airspace for these aircraft descending to 15000.

END