Standard Operating Procedures and Letters of Agreement

Oakland Center - Charlie Sector

Date	Code	Version	Contact
2011-11-26	SOP-204	1.40	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 Charlie Sector airspace, as well as controllers working at positions interfacing with Oakland Center Charlie 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 north (Seattle/Portland) and establishing departures from the Bay Area to the north (Seattle/Portland). Other responsibilities include northern Reno area and northern Sacramento area traffic management.

PROCEDURES:

Frequencies and Callsigns.
1. When not sectorized, OAK_CTR shall use 132.20 as its frequency.
2. Oakland Center Charlie sector shall use 128.80 as its frequency, OAK_C_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_C_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_C_CTR:
  - Norcal TRACON "SUTRO" Sector (STS_APP)
  - Norcal TRACON "DELTA" Sector (SMF_APP)
  - Norcal TRACON "RICHMOND" Sector (CCR_APP)
  - Reno TRACON (RNO_APP)
  - Fallon RAPCON (NFL_APP)
2. Ensure ZSE-bound routings are in compliance with the applicable LOA.
3. Ensure aircraft bound for Arcata/Eureka airport (KACV) are descended to 10,000 feet or below before handoff to SEA_CTR.
4. Ensure aircraft bound for Crescent City (KCEC), Medford (KMFR), or Klamath Falls (KLMT) airports are descended to FL200 or below before handoff to SEA_CTR.
5. When STS_APP, CCR_APP and SMF_APP are manned, southeast arrivals to SMF should be encouraged to file below CTR airspace and may be handed from CCR_APP to SMF_APP.
Bay Area Arrivals.

During Bay Area normal / west flow:
1. SFO arrivals from the north and northeast (ENI, FMG, FOT, MXW, RBG, RBL, SAC) shall be routed via the GOLDN6 STAR. Aircraft filed the PYE1 STAR should be re-routed on the GOLDN6 unless Norcal Approach requests otherwise. Aircraft not able to accept the GOLDN6 STAR shall have their clearance route amended along the GOLDN6 route. GOLDN6 and PYE1 arrivals shall be instructed to "descend pilot's discretion, maintain FL200" and handed off to STS_APP.
2. OAK arrivals from the north and northeast (RBG, RBL, FMG) shall be routed via the RAIDR2 STAR. Aircraft not able to accept the STAR shall have their clearance route amended along the RAIDR route. These arrivals shall be instructed to "descend pilot's discretion, maintain FL200" and handed off to CCR_APP.
3. SJC arrivals from the north (FOT, FMG, RBG) shall be routed via the GOLDN6 STAR. Aircraft not able to accept the STAR shall have their clearance route amended along the GOLDN6 route. Aircraft shall be instructed to "descend pilot's discretion, maintain FL200" and handed off to STS_APP.
During Bay Area east flow:
1. SFO arrivals from the north (FOT, FMG, RBG, RBL) shall be routed via the STINS2 STAR. Aircraft not able to accept the STAR shall have their clearance route amended along the STINS2 route. Aircraft shall be instructed to "cross ENI at FL240, descend and maintain FL200" and handed off to STS_APP.
2. OAK arrivals from the north and northeast (RBG, RBL, FMG) shall be routed via the RAIDR2 STAR. Aircraft not able to accept the STAR shall have their clearance route amended along the RAIDR2 route. These arrivals shall be instructed to "descend pilot's discretion, maintain FL200" and handed off to CCR_APP.
3. SJC arrivals from the north (ENI, FMG, RBL) shall be routed via the BRINY1 STAR. Aircraft not able to accept the STAR shall have their clearance route amended along the BRINY1 route. Aircraft shall be instructed to "descend pilot's discretion, maintain FL200" and handed off to STS_APP.
4. SJC arrivals from the northeast (FMG) may alternatively be routed via FMG.JAWWS2 STAR transition. Turbojet aircraft shall be climbed to or above FL240, or advised to expect "FL240 at ELCAP" to pass above the ECA and LOCKE streams. Aircraft shall be handed to OAK_B_CTR prior to the sector border.
Fallon area arrivals.
1. NFL VFR military arrivals shall be advised if the MOAs are active, and may transit MOA airspace at their discretion. Hand these aircraft to NFL_APP at the appropriate time.
2. NFL IFR military arrivals shall be routed via FMG.HZN and instructed to "cross FMG FL180, 10 DME from HZN, descend and maintain 15000". Aircraft shall then be handed-off to NFL_APP.
Reno area arrivals.

During normal / south ops:
1. RNO arrivals from the southeast (MVA) shall be received from OAK_B_CTR routed via the RYANN1 STAR crossing RYANN at 16000. Aircraft should be sequenced and overflows may be held southeast of RYANN as published from FL200 and up. Hand off arrivals to RNO_APP.
2. RNO arrivals from the northeast (GASSI, LLC) shall be routed via ANAHO2 STAR. Aircraft not able to accept the STAR shall have their clearance route amended along the ANAHO2 route. Aircraft shall be instructed to "cross ANAHO at and maintain 16000" and handed to RNO_APP.
3. RNO arrivals from the southwest (SAC) shall be received from OAK_B_CTR routed via the SIERRA3 STAR crossing HOBOA at 16000. Aircraft should be sequenced and handed off to RNO_APP.
4. RNO arrivals from the south (SWR) shall be routed via CANN2 STAR. Aircraft not able to accept the STAR shall have their clearance route amended along the CANN route. Aircraft shall be instructed to "cross TRUCK at and maintain 16000" and handed to RNO_APP.
5. RNO arrivals from the southeast (KENNO) shall be received from OAK_B_CTR and routed via KENNO1 RNAV STAR. Instructed pilots to "continue descent via the KENNO1 RNAV arrival" and hand off to RNO_APP.
During north ops:
1. RNO arrivals from the northeast (LLC) shall be routed via VIKES1 STAR. Aircraft not able to accept the STAR shall have their clearance route amended along the VIKES1 route. Aircraft shall be instructed to "cross LLC DME 40 at and maintain 16000" and handed to RNO_APP.
Sacramento and Travis area arrivals.
1. SMF arrivals from the northeast (SWR) shall be routed via the FLUNK3 STAR. Aircraft not able to accept the STAR shall have their clearance route amended along the FLUNK3 route. Aircraft shall be instructed to "cross FLUNK at and maintain 11000" and handed to SMF_APP. These aircraft may pass through OAK_B_CTR on a fixed pointout prior to entering SMF_APP airspace. Exercise caution to separate SIERR arrivals to RNO.
2. SMF arrivals from the northwest (LKV, LMT, RBL, ILA) shall be routed via the TUDOR1 STAR. Aircraft not able to accept the STAR shall have their clearance route amended along the TUDOR1 route. Aircraft on the LKV or LMT transitions shall be instructed to "cross BOWLS at and maintain 12000" aircraft on the RBL transition shall be instructed to "cross PIECH at and maintain 10000" aircraft on the ILA transition shall be instructed to "cross ILA at and maintain 10000" hand arrivals to SMF_APP.
3. SUU arrivals from the east (SWR) shall be routed via the SWR1 STAR. Aircraft not able to accept the STAR shall have their clearance route amended along the SWR1 route. Aircraft shall be instructed to "cross PEELS at and maintain 11000" and handed-off to CCR_APP. These arrivals may briefly pass through SMF_APP on a fixed pointout at 11000.
4. SUU arrivals from the north and west (ENI, FUELL, RBL, SGD) shall be routed via the SEATO2 STAR. Aircraft not able to accept the STAR shall have their clearance route amended along the SEATO route. Aircraft on RBL and FUELL transitions shall be instructed to "cross ILA at and maintain 15000". Aircraft on ENI transitions shall be instructed to "cross ENI at and maintain 17000". Aircraft on SGD transitions shall be instructed to "cross SGD at and maintain 10000". Aircraft shall be handed to the appropriate approach sector based on routing.
Bay Area Departures.
1. De-conflict Bay Area ENI, RBL, and SAC transition departures with SAC, MXW, and ENI arrivals.
Additional Comments.

None.