1.  PURPOSE.

This Standard Operating Procedure (SOP) outlines the procedures to be used by controllers working Norcal Approach "Grove" Sector, the primary airport 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 "Grove" sector airspace, as well as controllers working at positions interfacing with Norcal TRACON "Grove" 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. During east flow operations OAK_APP does not exist, refer to other SOPs for guidance.

2. During normal (west flow) operations, sequence OAK arrivals.

3. During west flow operations, sequence MOD3 arrivals to SFO.

4. During west flow operations, sequence and separate LVK arrivals and departures.

5. During west flow operations, sequence and separate HWD arrivals and departures.

6. PROCEDURES.

a. Frequencies and Callsigns

1. Norcal approach "Grove" Sector shall use 135.40 as its frequency and OAK_APP as its text callsign.

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

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

4. During west ops, if OAK_TWR is not on line, OAK_APP will assume control of OAK_TWR.

b. Airspace and Sectorization Plan:

1. OAK_APP shall own the airspace within the lateral limits depicted on this graphic in west ops, from surface to FL230, except all actively manned Class D airspace within the lateral limits. SFO_APP has a shelf from 5000-11000 over a small portion of OAK_APP to facilitate vectoring arrivals “down the bay.” See the graphic for details; OAK arrivals must enter this area at/below 4000. OAK_APP does not exist in east operations.

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  

1. The active runway plan for OAK will be determined by OAK_TWR in consultation with SFO_TWR per SOP_050. Normal prevailing winds are from the west.

2. The active runway plan for LVK will be determined by LVK_TWR per SOP_050. Normal prevailing winds are from the west.

3. The active runway plan for HWD will be determined by HWD_TWR per SOP_050. Normal prevailing winds are from the west.

4. Departure release procedures with HWD_TWR or LVK_TWR will only be in use upon request by OAK_APP.

d. 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. SJC SUNOL6 departures are restricted to prop aircraft and departure control of these aircraft will be with OAK_APP.

4. During normal/west ops, if OAK_TWR is not online, OAK_APP shall assume control of the OAK_TWR position.

5. During normal/west ops, if LVK_TWR is not online, OAK_APP shall assume control of the LVK_TWR position.

6. During normal/west ops, if HWD_TWR is not online, OAK_APP shall assume control of the HWD_TWR position.

e. BAY Arrivals - Normal (West Flow) Operations:

1. MADWN4 arrivals are received from MOD_APP with instructions to cross CATTY 8000.  Aircraft will be descended reference the MVAs and vectored to the final approach course.

2. MARVN1 arrivals are received from MOD_APP with instructions to "cross CATTY 8000.” Aircraft will be descended reference the MVAs and vectored to the final approach course.

3. PXN2 arrivals are received from SJC_APP with instructions to cross BORED 10000 at 250 knots (jet)  / 8000 (prop). Aircraft will be descended reference the MVAs and vectored to the final approach course.

4. Oceanic arrivals are received from CCR_APP at 6000 routed SALAD.SUNOL. Aircraft will be sequenced with the merged stream from CATTY. Aircraft will be descended reference the MVAs and vectored to the final approach course.

5. RAIDR2 arrivals are received from CCR_APP, vectored north of the field on heading 110 at an altitude of 5000. This heading puts the aircraft on a wide right downwind for runway 29. Descend them to 4000 prior to mid-field (and insure there's no conflict with SFO8 departures climbing to 5000), then they can either be vectored onto a right base to join the localizer for the ILS approach - or - cleared for the visual approach (from as early as right downwind, traffic permitting), with instructions to "Cross the Oakland VOR 100 Radial at or above 3000." (This is for noise abatement and to protect the approaches to runway 27R.)

6. MOD3 arrivals for SFO are received from MOD_APP with instructions to cross CEDES at 11000.  OAK_APP shall instruct aircraft to descend and maintain 7000 and allowed to continue to fly the arrival as published (heading of 236 off of CEDES). Aircraft shall be handed off to SFO_APP after they're clear of PXN2 traffic.

7. RISTI4 arrivals for SFO are received from MOD_APP at 11000.  OAK_APP shall instruct aircraft to depart CEDES heading 240 Vectors for Final Approach Course, descend and maintain 7000.   The aircraft shall be strachpadded "H24" and a temp alt of 070 issued and handed off to SFO_APP after the aircraft's clear of PXN2 traffic.  

8. YOSEM1 arrivals for SFO are received from MOD_APP crossing the BONNS intersection at 11000 and 250 knots.  OAK_APP shall instruct aircraft to cross FAITH at 7000 and 210 knots.   The aircraft shall be handed off to SFO_APP after the aircraft's clear of PXN2 traffic.  YOSEM1 traffic has a fixed pointout with SJC_APP.  

9. Missed Approaches are passed by OAK_TWR to CCR_APP for resequencing.

f. LVK Arrivals

1. During west operations, IFR arrivals for runway 25R...

i. from the north (ALTAM), and can accept a full approach, shall be instructed to "cross REIGA at or above 3000" and cleared for the ILS 25R prior to REIGA.

ii. from the east (TRACY), and can accept a full approach, shall be instructed to "cross FOOTO at or above 3300" and cleared for the ILS 25R prior to TRACY.

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

2. During east operations, under IMC, IFR arrivals for runway 7L/R should be routed as listed above in (5)(g)(i..iv)  and cleared for the ILS 25R for a circle-to-land approach.

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

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

1. Departures from OAK during west flow operations departing north/east are handled by CCR_APP.

2. Departures from OAK during west flow operations departing west/south are handled by STS_APP.

h. LVK Departures:

1. BYRON1 and LIVR1 departures shall proceed under pilot navigation.

2. Obstacle Departure Proceedure, "Rwy 7R/L climb direct LV LOM, then climbing left turn via the 030 bearing from LV LOM to intercept V109, then proceed on course. Rwy 25R/L climb rwy heading to 1200', then climbing right turn via 020 heading and OAK VOR R-060 to ALTAM INT, then proceed on course," shall be given out as the Livermore Published Departure Procedure

i. IFR Low Altitude Routing:

ECA V195 SUNOL Is common used for all aircraft inbound and outbound(For Bay) with the Valley Sector(MOD_APP)

j. Additional Comments:

1. A fixed pointout exists for SJC LOUPE1 departures which might pass through OAK_APP airspace climbing to 15000 while these aircraft await climb clearance from OAK_B_CTR.

END