1. PURPOSE.

This Standard Operating Procedure (SOP) outlines the procedures to be used by controllers working Norcal Approach "Richmond" Sector, the primary airport KSFO, 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 "Richmond" sector airspace, as well as controllers working at positions interfacing with Norcal TRACON "Richmond" sector facilities.

4. BACKGROUND.

Over time, controllers have found that having aircraft arrive via pre-approved arrival routes, either by STAR (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. During normal (west) operations, sequence and separate north/east bound departures from the Bay Area.

2. During east operations, sequence and separate north/east bound departures from Bay Area, and arrivals from the east to the Bay Area.

3. Sequence and separate SMF CCR1 arrivals.

4. Sequence and separate SUU arrivals and departures.

5. Sequence and separate CCR arrivals and departures.

6. Sequence and separate APC arrivals and departures.

7. During east ops, sequence and separate LVK arrivals and departures.

6. PROCEDURES.

a. Frequencies and Call Signs

1. Norcal Approach "Richmond" sector shall use 120.90 as its frequency and CCR_APP as text call sign.

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. CCR_APP shall own the airspace within the lateral limits depicted on this graphic in west ops, and this graphic in east ops, from the surface to FL190, 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. CCR_APP and STS_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 north/east departures to specific DPs/routing. Releases are required for other DPs due to the need for coordination between CCR and STS_APP to avoid conflicts with other SFO/OAK departures. Releases may be required at other times at CCR_APP's discretion.

3. At OAK, departures will be handled as set forth in SOP_050. SOP_050 restricts north/east departures to specific DPs/routing. Releases are required for other DPs due to the need for coordination between CCR and STS_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 SUU will be determined by SUU_TWR per SOP_050. Normal prevailing winds are from the west, using runways 21.

2. The active runway plan for CCR will be determined by CCR_TWR per SOP_050. Normal prevailing winds are from the west, using runways 32 and runways 1, but CCR often gets variable winds, and should assign runways based on wind direction.

3. The active runway plan for APC will be determined by APC_TWR per SOP_050. Normal prevailing winds are from the west, using runways 36.

4. The active runway plan for LVK will be determined by LVK_TWR per SOP_050. Normal prevailing winds are from the west, using runways 25.

5. Departure release procedures with SUU, APC, LVK and / or CCR Towers will only be in use upon request by CCR_APP.

6. No other airport will need to have a runway in use plan inside the "Richmond" sector as all other fields are class E.

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 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 listed in this SOP, so that all traffic is placed on consistent departure streams.

3. During all ops, if SUU_TWR is not online, CCR_APP shall assume control of the SUU_TWR position.

4. During all ops, if CCR_TWR is not online, CCR_APP shall assume control of the CCR_TWR position.

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

6. During east ops, if LVK_TWR is not online, CCR_APP shall assume control of the LVK_TWR position.

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

1. SFO arrivals via RISTA4 SAC transition are received from OAK_B_CTR with instructions to "descend at pilot's discretion, maintain FL200”. CCR_APP shall descend them to 15000 then handed off to MOD_APP. ECA transitions are passed from B_CTR to MOD_APP.

2. SJC arrivals are received from OAK_B_CTR on the CAPO3 arrival with clearance to FL200. CCR_APP shall descend them to 15000 then handed off to MOD_APP.

3. OAK arrivals routed via the RAIDR2 STAR are received from OAK_C_CTR with instructions to “descend at pilot’s discretion, maintain FL200”. These aircraft shall be instructed to “cross RAIDR at 7000” and merged with any oceanic arrivals and vectored north of OAK reference the departure traffic. Assign a heading of 110 prior to RAIDR (to put the aircraft on a wide right downwind for runway 29 - Scratched with "H11") and descended to 6000 prior to handoff to OAK_APP.

4. Oceanic arrivals to OAK are received from STS_APP routed via PYE.SALAD.SUNOL at 7000. These aircraft shall be merged with RAIDR2 arrivals and descended to 6000 prior to handoff to OAK_APP.

5. Missed approaches off OAK are received from OAK_TWR with instructions to "Fly runway heading, climb and maintain 5000." These aircraft will be vectored reference the MVAs, sequenced with other OAK arrivals, and passed to OAK_APP.

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

1. SFO SHOR1 departures will be received from SFO_TWR, and should be vectored on course and handed off to Oakland B (126.85) or C (128.80) Center based on route of flight.

2. SFO SFO8 departures from runways 1L/R will be received from SFO_TWR on a heading of 030; they should be vectored on course and handed off to Oakland B (126.85) or C (128.80) Center based on route of flight. Departures from runways 28L/R will generally be avoided due to the coordination required. When needed, these departures require coordination with STS_APP and a release (see 6(c) above and SOP_050); they will be received from SFO_TWR. Hand them off to Oakland B (126.85) or C (128.80) Center based on route of flight.

3. SFO GAPP3 departures to the north and east will generally be avoided due to the coordination required. When needed, these departures require coordination with STS_APP and a release (see 6(c) above and SOP_050); they will be received from SFO_TWR. Hand them off to Oakland B (126.85) or C (128.80) Center based on route of flight.

4. Use of any other DP off SFO for north/eastbound aircraft shall require SFO_TWR to obtain a release from CCR_APP and prior to releasing these departures; CCR_APP must point them out to STS_APP to avoid conflict with other SFO and OAK departures.

5. OAK NIMI2 departures to the north/east will be received from OAK_TWR and should be vectored on course and handed off to Oakland B (126.85) or C (128.80) Center based on route of flight.

6. OAK OAK5 departures to the north/east will be received from OAK_TWR and should be vectored on course and handed off to Oakland B (126.85) or C (128.80) Center based on route of flight.

7. OAK SGD1 departures will be received from OAK_TWR and should be vectored on course and handed off to Oakland C (128.80) Center.

8. OAK SALAD1 departures will be received from OAK_TWR. This is a pilot nav DP.

9. Use of the OAK SLNT7 DP requires CCR_APP to point them out to STS_APP due to possible conflict with SFO departures.

10. West/Southbound departures off OAK are handled by STS_APP. These departures shall be assigned the SKYL3, COAST5, NUEVO5, or OAK5 DP. Use of any other DP for west/southbound departures requires STS_APP to point them out to CCR_APP.

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. COMMO1, LOCKE1, and ECA1 arrivals for SFO and OAK are received from MOD_APP at 9000 or 10000 depending on the arrival. Deconflict these arrivals with Bay departures. Then, handle the arrivals as follows:

a. OAK arrivals: About 10 miles from UPEND assign a heading of 240, descend to 6000, and assign a speed of 210 knots (SFO_APP may contact CCR_APP to have CCR_APP issue a different speed assignment based on traffic). Pass these arrivals to SFO_APP.

b. SFO arrivals landing 19L/R: About 10 miles from UPEND assign a heading of 220 to join the SFO 19L localizer. Descend these aircraft to 5000, assign a speed of 210 knots (SFO_APP may contact CCR_APP to have CCR_APP issue a different speed assignment based on traffic), and pass to SFO_APP.

c. SFO arrivals landing 10L/R: This configuration is very rare; the preferred east ops configuration is landing 19L/R. When the winds require this configuration, about 10 miles from UPEND clear the aircraft direct SAU and descend to 8000. Pass these arrivals to SFO_APP.

3. CAPO3 arrivals for SJC are received from OAK_B_CTR with instructions to “descend at pilot’s discretion, maintain FL200”. CCR_APP shall descend them to 15000 then handed off to MOD_APP.

i. East Flow Operations - Bay Departures:

1. DUMB6, MARI4, and SGD1 departures from SFO and OAK are received from HWD_APP on course climbing to 15000. There is a charted "At or above 11000" restriction near the CCR/HWD boundary to protect SFO and OAK arrivals. Ensure compliance with this restriction and separation from arrivals.

j. SUU Operations:

1. OAKEY2 arrivals are received from OAK_B_CTR with instructions to "cross OAKEY at 10000." These aircraft may briefly pass through MOD_APP airspace on a fixed point out descending to 10000. The STAR course after OAKEY is dependent on runway in use. On initial contact advise arrivals of runway in use. Vector these aircraft to final reference the MVAs.

2. SWR1 arrivals are received from OAK_C_CTR with instructions to "Cross PEELS at 11000." These arrivals may briefly pass through SMF_APP airspace on a fixed pointout at 11000. Vector these aircraft to final reference the MVAs.

3. SEATO2 arrivals are received from OAK_C_CTR (SGD transitions may be received from STS_APP depending on altitude) descending to 10000. Aircraft on SGD transitions have instructions to "Cross SGD 10000." Vector these aircraft to final reference to the MVAs.

k. SMF Arrivals:

1. CCR1 arrivals for SMF in south ops should be instructed to descend and maintain 10000 and handed off to SMF_APP. The descent instructions should be made early enough so the aircraft crosses the SAC R-257 at 10000. When SMF is in north ops, aircraft should be handed off to SMF with instructions to "descend and maintain 6000, depart ISYOH heading 020."

2. Oceanic arrivals for SMF are received from OAK_A_CTR routed OAK.CCR.CCR1 with instructions to cross OAK at 15000. They may briefly pass through STS_APP (west ops) or SFO/HWD_APP (east ops) on a fixed pointout descending to 15000. These aircraft must remain at 15000 until within CCR_APP airspace. Handle these aircraft as described in paragraph 1 of this section.

l. SMF Departures:

None.

m. CCR Arrivals:

1. CCR IFR arrivals should normally use the LDA 19R approach; handle these arrivals as follows:

i. From the north (SAC), and can accept a full approach, shall be routed via V6 to REJOY and instructed to "Descend and maintain 2000" and cleared for the LDA 19R prior to REJOY.

ii. From the east (LODDI, LIN), and can accept a full approach, shall be routed via LODDI REJOY and instructed to "cross REJOY 2000" and cleared for the LDA 19R prior to REJOY.

iii. From the south (OAK, V6), and can accept a full approach, shall be instructed to "cross COLLI 5100" and cleared for the LDA 19R prior to KANAN (CC, LOM).

iv. From the west (SGD, SAU), and can accept a full approach, shall be routed via CROIT KANAN (CC, LOM) with instructions to "Cross KANAN at or above 4000" and cleared for the LDA 19R prior to KANAN.

v. That can not accept the full approach shall be vectored to the final approach course and descended in accordance with MVAs.

2. If a runway other than 19R is to be used, issue appropriate circle-to-land instructions.

3. Missed Approach instructions may be assigned per the published procedures or alternately climbed to 3500' on runway heading to be given a right or left turn (thru 900') as appropriate for re-sequencing downwind.

n. CCR Departures:

1. BCHN9 and KANA2 departures shall proceed under pilot navigation.

2. Departures climbing above TRACON ceiling shall be handed to OAK_C_CTR (128.80) westbound, or OAK_B_CTR (126.85) eastbound.

o. APC Arrivals:

1. When using the east ops airspace configuration, use of the LOC 36L approach requires coordination with SFO_APP. Aircraft may be vectored to the VOR or RNAV approaches to runway 6 without the need for coordination (if full approach used, procedure turn requires coordination with STS_APP). Therefore, in east ops, the VOR 6 and RNAV 6 are the preferred approaches.

2. During normal operations, IFR arrivals for runway 36L...

i. from the north (STS), and can accept a full approach, shall be routed via SGD LYLLY and instructed to "Cross LYLLY at or above 2800" and cleared for the LOC 36L prior to LYLLY.

ii. from the east (CCR), and can accept a full approach, shall be routed via V108 V150 REBAS (CCR. CROIT. REBAS) and instructed to "cross REBAS 1800" and cleared for the LOC 36L prior to REBAS.

iii. from the south (SAU, SFO), and can accept a full approach, shall be cleared/vectored direct REBAS and instructed to "cross REBAS 1800" and cleared for the LOC 36L prior to REBAS.

iv.from the west (PYE), and can accept a full approach, shall be routed via V107 V150 REBAS (COMMO. REBAS) with instructions to "cross REBAS 1800" and cleared for the LOC 36L prior to REBAS.

v.that cannot accept the full approach shall be vectored to the final approach course and descended in accordance with MVAs.

3. During south operations, under IMC, IFR arrivals for runway 18L/R should be routed via the VOR RWY6 and cleared for a circle to land approach to runways 18L/R.

4. Runway 6/24 may be used at the controller's discretion.

5. Missed Approach instructions may be assigned per the published procedures or alternately told to turn to a heading of 190 and climbed to 3000' to await vectors for re-sequencing.

p. APC Departures:

1. LIZRD3 departures shall proceed under pilot navigation.

2. Departures climbing above TRACON ceiling shall be handed to OAK_C_CTR (128.80) westbound, or OAK_B_CTR (126.85) eastbound.

q. IFR Low Altitude Routing:

1. APC/CCR to Bay Airports - via CROIT or SABLO. V195.

2. APC to Sacramento Area - via CROIT. V150. SAC.

3. CCR to Sacramento Area - via REJOY. V6. SAC.

r. Additional Comments:

Departing aircraft may be vectored off their departures for separation, but MUST be told to "Resume own navigation" prior to handoff unless otherwise coordinated with center.

END