Standard Operating Procedures and Letters of Agreement

Oakland Center - Alpha Sector

Date	Code	Version	Contact
2010-04-12	SOP-200	1.24	Facility Advisory Board (FAB)

PURPOSE:

This Standard Operating Procedure (SOP) outlines the procedures to be used by controllers working Oakland Center, to ensure that traffic flows are handled in as efficient and timely a manner as possible, and in compliance with LOAs. By specifying standard handoff points, departure and arrival routes, coordination between adjacent facilities may be greatly reduced.

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.

DISTRIBUTION:

This SOP is intended for use by controllers staffing positions within Oakland Center and Oakland Center Alpha Sector airspace, as well as controllers working at positions interfacing with Oakland Center Alpha Sector facilities.

BACKGROUND:

Over time, controllers have found that having aircraft arrive via pre-approved arrival routes, either by STARs (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 Oakland Center and other ZOA ARTCC 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.

The primary responsibilities for this position are sequencing arrivals to the Bay Area from the Los Angeles Basin and establishing departures from the Bay Area to the Los Angeles Basin.

PROCEDURES:

Frequencies and Callsigns.
1. When not sectorized, OAK_CTR shall use 132.20 as its frequency.
2. Oakland Center Alpha sector shall use 128.70 as its frequency, OAK_A_CTR as text callsign, and "Oakland Center" as voice callsign.
3. Frequencies for secondary airports not covered in SOP_050 should be determined from appropriate publications.
Airspace and Sectorization Plan.
1. OAK_A_CTR shall own the airspace within the lateral limits depicted on this graphic, from surface to unlimited, except all airspace delegated by SOP to underlying TRACONs or towers.
2. The Sector file authorized for use in operating this sector is the certified Center sector file available on the "downloads" page of the ZOA ARTCC web site.
Airport Procedures and Runway Use Plans.

None.
Special Instructions.
1. When not manned, the following TRACONs will be operated, and the associated airspace owned by OAK_A_CTR:
  - Norcal TRACON "LICKE" Sector (SJC_APP)
  - Norcal TRACON "WOODSIDE" Sector (SFO_APP)
  - Norcal TRACON "LAGUNA" Sector (MRY_APP)
  - Lemoore TRACON (NLC_APP) when not manned by military ATC.
2. OAK_A_CTR will be responsible for obtaining all Oceanic Clearances from KZAK_FSS for those DEL positions issuing departure clearances with oceanic routings, as well as for transiting airborne aircraft. Obtain a current clearance when aircraft is at least 75nm from ALCOA (R463) or BEBOP (R464). OAK_A_CTR shall revise all oceanic clearances as required enroute. Refer to the Oceanic FSS SOP.
3. Oceanic departures shall be cleared initially to a standard IFR cruise altitude. Final oceanic altitudes on R464 are RVSM (non-standard) and will be indicated in the flight plan comments. OAK_A_CTR shall clear aircraft to climb to the oceanic cruise altitude departing BEBOP.
4. Oceanic departures shall be spaced 20 miles laterally or 2000' vertically and speed matched when appropriate. Prior to transfer-of-control to KZAK_FSS, issue beacon code 2000 and inform the pilot that radar service is terminated. Transfer control of aircraft for R463 5 min prior to ADISN. Transfer control of aircraft for R464 5 min prior to BAART.
5. Oceanic arrivals will require a squawk code assignment when received from the Oakland Oceanic FSS. Refer to the Oceanic FSS SOP.
6. Ensure SoCal-bound routings are in compliance with the applicable LOA.
7. Prop/Turboprop arrivals to SFO will be routed via CZQ.MOD, and thus be handled by OAK_B_CTR.
8. Arrivals to San Louis Obispo (KSBP) in ZLA shall be descended to 8000 or below prior to handoff to LAX_A_CTR.
Bay Area Arrivals.

During Bay Area normal / west flow:
1. SFO Turbojet arrivals from Southern California (BSR) shall be routed via the BSR STAR. Aircraft not able to accept the STAR shall have their clearance amended along the BSR route. Aircraft shall be instructed to "descend at pilot's discretion, maintain FL200" and handed off to MRY_APP.
2. SFO Oceanic arrivals on R463 shall be routed via ALCOA.OSI and arrivals on R465 shall be routed via CINNY.OSI. Any intermediate fix in between (such as BRINY, HADLY, PIRAT) is fine. Aircraft shall be instructed to "Cross BRINY at and maintain 8000", or if BRINY is not on their route, "Cross 25 miles West of OSI at and maintain 8000" and shall be handed off to STS_APP.
3. OAK arrivals from Southern California (AVE, GMN) shall be routed via the PXN or MARVN STAR. Aircraft not able to accept one of the STARs shall have their clearance route amended along the PXN route. PXN arrivals shall be instructed to "descend at pilot's discretion, maintain FL200" to pass above the SJC HYP stream and handed off to SJC_APP. MARVN arrivals shall be instructed to "descend at pilot's discretion, maintain FL200" and handed to MOD_APP. MARVN arrivals may briefly pass through SJC_APP airspace on a fixed pointout under the control of MOD_APP.
4. OAK Oceanic arrivals on R463 shall be routed via ALCOA.PYE.SALAD.SUNOL and arrivals on R465 shall be routed via CINNY.PYE.SALAD.SUNOL. Aircraft shall be instructed to "cross PYE at and maintain 7000" to pass below the PYE and GOLDN streams, and shall be handed off to STS_APP.
5. SJC arrivals from Southern California (AVE, RZS) shall be routed via the ROBIE STAR. Aircraft not able to accept the STAR shall have their clearance route amended along the ROBIE route. Aircraft shall be instructed to "cross 15 miles south of SNS at and maintain FL200" and handed off to SJC_APP. Ensure they are below FL180 in the vicinty of WAGES to pass beneath the PORTE and SKYLN departures.
6. SJC arrivals from the east or northeast (HYP.OAL, HYP.FMG) may pass briefly through OAK_A_CTR airspace from HYP to PAPEE descending to 12000 under control of MOD_APP.
7. SJC Oceanic arrivals on R463 shall be routed via ALCOA.SFO and arrivals on R465 shall be routed via CINNY.SFO. Aircraft shall be instructed to "cross SFO at and maintain 12000" to pass above the PYE stream and shall be handed off to STS_APP.
During Bay Area east flow:
1. SFO / OAK arrivals from Southern California (BSR) shall be routed via the HADLY STAR (OAK arrivals may also be routed via the COMMO STAR). Aircraft not able to accept the STAR shall have their clearance route amended along the HADLY route. At the request of STS or MRY_APP, overflows may be held at EUGEN as published from 16000. Otherwise aircraft shall be instructed to "descend pilot's discretion, maintain FL200" and handed off to MRY_APP.
2. SFO Oceanic arrivals shall be routed direct SAU. Aircraft shall be instructed to "cross SAU at and maintain 6000" and handed off to STS_APP. If an aircraft will enter MRY_APP airspace, perform a pointout with MRY_APP.
3. OAK arrivals from Southern California (AVE, GMN) shall be routed via the COMMO STAR (OAK arrivals may also be routed via the HADLY STAR). Aircraft not able to accept the STAR shall have their clearance route amended along the COMMO route. Aircraft shall be instructed to "descend pilot's discretion, maintain FL200" and handed off to MOD_APP. Aircraft may briefly pass through MRY_APP airspace on a fixed pointout under the control of MOD_APP.
4. OAK Oceanic arrivals shall be routed direct SAU. Aircraft shall be instructed to "cross SAU at and maintain 6000" and handed off to STS_APP. If an aircraft will enter MRY_APP airspace, perform a pointout with MRY_APP.
5. SJC arrivals from Southern California (AVE, RZS) shall be routed via the JAWWS STAR. Aircraft not able to accept the STAR shall have their clearance route amended along the JAWWS2 route. Aircraft shall be instructed to "cross 15 miles south of SNS at and maintain FL200" and handed off to MRY_APP.
6. SJC arrivals from the east and northeast on the JAWWS may briefly pass through OAK_A_CTR airspace on a fixed pointout under the control of MOD_APP.
7. SJC Oceanic arrivals shall be routed via BRINY.OSI. Aircraft shall be instructed to "cross BRINY at and maintain 5000" to pass below the HADLY stream and handed off to MRY_APP.
SMF Arrivals.

SMF Oceanic arrivals and other arrivals from the southwest shall be routed via OAK.CCR.CCR. Aircraft shall be instructed to "cross OAK at and maintain 15000" and handed off to CCR_APP. In west ops, the aircraft may briefly pass through STS_APP on a fixed pointout descending to 15000; in east ops, aircraft may briefly pass through HWD_APP and/or SFO_APP on a fixed pointout descending to 15000.
MRY Arrivals.

MRY arrivals from Southern California (BSR) shall be routed via the PEBB arrival. Aircraft not able to accept the STAR shall have their clearance route amended along the PEBB route. Aircraft shall be instructed to "cross CARME at and maintain 7000" and handed off to MRY_APP.
NLC Arrivals.

NLC arrivals shall be routed via PXN or ROM to the IAF as appropriate. Aircraft shall be instructed to "cross PXN/ROM at 17000, after PXN/ROM descend and maintain 15000" and handed to NLC_APP.
Additional Comments.

During Bay Area normal / west flow:
1. Ensure departures to SNS transitions cross above the descending BSR stream.
2. Ensure PORTE and SKYL departures will cross WAGES at or above FL200 to pass above the descending ROBIE stream.
During Bay Area east flow:
1. Monitor PORTE and SKYL departures on PXN and CZQ transitions for potential conflicts with the descending COMMO stream.