Standard Operating Procedures and Letters of Agreement

ZOA Primary Airports

Date	Code	Version	Contact
2012-01-13	SOP-050	1.33	Facility Advisory Board (FAB)

PURPOSE:

This Standard Operating Procedure (SOP) outlines the procedures to be used by controllers working clearance delivery, ground control, and tower at primary airports with ZOA ARTCC. 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 canceled 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 primary airports within ZOA, as well as controllers working at positions interfacing with primary airport positions.

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 Clearance Delivery, Ground, Tower, TRACON and 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.

PROCEDURES:

APC - Napa County
1. The following frequencies and text call signs are assigned to APC:
2. When winds are from 331 thru 099 above 10 knots, the field shall use runways 36L/R and/or 6. At all other times the airport shall use runways 18L/R and/or 24.
3. Initial climbs for IFR departures from APC filed for altitudes at or above 5000 shall be to 5000.
4. Departure releases must be obtained from CCR_APP only when CCR_APP requests release procedures to be in effect.
5. Missed approaches reported to tower when radar facilities are manned shall be instructed to climb to 3000 on runway heading and transferred to the radar facility. When no radar facility is online, missed approach shall be handled in accordance with ZOA SOP-003.

BAB - Beale AFB
1. The following frequencies and text call signs are assigned to BAB:
2. When winds are from 241 thru 059 above 7 knots, the field shall use runway 33. At all other times the airport shall use runway 15.
3. Initial climbs for IFR departures from BAB filed for altitudes at or above 9000 shall be to 9000.
4. Departure releases must be obtained from SMF_APP only when SMF_APP requests release procedures to be in effect.
5. Missed approaches reported to tower when radar facilities are manned shall be instructed to climb to 5000 on runway heading and transferred to the radar facility. When no radar facility is online, missed approach shall be handled in accordance with ZOA SOP-003.

CCR - Buchanan Field
1. The following frequencies and text call signs are assigned to CCR:
2. If winds at Concord are variable, favoring no particular runway more than another, controller may choose what runways are in use. Calm wind runways suggested are 32L/R and 19L/R.
3. Initial climbs for IFR departures from CCR filed for altitudes at or above 5000 shall be to 5000.
4. Departure releases must be obtained from CCR_APP only when CCR_APP requests release procedures to be in effect.
5. Missed approaches reported to tower when radar facilities are manned shall be instructed to climb to 2000 on runway heading and transferred to the radar facility. When no radar facility is online, missed approach shall be handled in accordance with ZOA SOP-003.

FAT - Fresno Yosemite Intl
1. The following frequencies and text call signs are assigned to FAT:
2. When winds are from 021 thru 199 above 10 knots, the field shall use runways 11L/R. At all other times the airport shall use runways 29L/R.
3. Initial climbs for IFR departures from FAT filed for altitudes at or above 5000 shall be to 5000.
4. Departure releases must be obtained from FAT_APP only when FAT_APP requests release procedures to be in effect.
5. Missed approaches reported to tower when radar facilities are manned shall be instructed to climb to 2000 on runway heading and transferred to the radar facility. When no radar facility is online, missed approach shall be handled in accordance with ZOA SOP-003.

HWD - Hayward Exec
1. The following frequencies and text call signs are assigned to HWD:
2. HWD shall comply with the runway use plan as set by OAK_TWR. When OAK_TWR is in "west flow" HWD shall use runways 28L/R. When OAK_TWR is in "east flow", HWD shall use runways 10R/L.
3. Departure releases must be obtained only when releases are requested, in West Ops by Norcal Departure 'Grove' Sector (OAK_APP 135.40) or in East Ops by Norcal Departure 'Niles' Sector (HWD_APP 134.50).
4. IFR departures on RWY 28L/R shall be directed to "fly runway heading until reaching 400, then turn left heading 160, vectors XXX, maintain 2000, expect XXX one zero minutes after departure" For east-bound departures, a 270 degree left turn with a mid-field crossing is preferred.
5. IFR departures on RWY 10L/R shall be directed to "turn right c/m 2500 via direct OAK VORTAC and OAK R-288. Aircraft SE bound and capable of climbing 250' per NM to 4500 may proceed direct MABRY int via OAK R-114"
6. Traffic Pattern Altitude for all aircraft is 650' MSL on RWY 10R-28L & 850' MSL for RWY 10L-28R.
7. Missed approaches reported to tower when radar facilities are manned shall be instructed to climb to 2000 on runway heading and transferred to the radar facility. When no radar facility is online, missed approach shall be handled in accordance with ZOA SOP-003.

LVK - Livermore Muni
1. The following frequencies and text call signs are assigned to LVK:
2. When winds are from 341 thru 159 above 10 knots, the field shall use runways 7L/R. At all other times the airport shall use runways 25L/R.
3. Initial climbs for IFR departures from LVK filed for altitudes at or above 5000 shall be to 5000.
4. Departure releases must be obtained from OAK_APP (West Ops) or CCR_APP (East Ops) only when releases are requested.
5. Missed approaches reported to tower when radar facilities are manned shall be instructed to climb to 5000 on runway heading and transferred to the radar facility. When no radar facility is online, missed approach shall be handled in accordance with ZOA SOP-003.
MOD - Modesto Harry Sham Field
1. The following frequencies and text call signs are assigned to MOD:
2. When winds are from 011 thru 189 above 10 knots, the field shall use runways 10L/R. At all other times the airport shall use runways 28L/R.
3. Initial climbs for IFR departures from MOD filed for altitudes at or above 5000 shall be to 5000.
4. Departure releases must be obtained from MOD_APP only when MOD_APP declares release procedures to be in effect.
5. Missed approaches reported to tower when radar facilities are manned shall be instructed to climb to 5000' on runway heading and transferred to the radar facility. When no radar facility is online, missed approach shall be handled in accordance with ZOA SOP-003.
6. During Normal Ops: Aircraft may be placed on Right or Left traffic for 28R, Left Traffic for 28L. Aircraft remaining in the pattern (aka "Closed Traffic") should expect runway 28R with Right traffic. Left traffic runway 28L may be used simultaniously at the controller's discreation.

MRY - Monterey Peninsula
1. The following frequencies and text call signs are assigned to MRY:
2. When winds are 10 knots or less in any direction the preferred configuration is to use runways 28L/R for departures and arrivals. This shall be referred to as "Normal Ops". When winds are above 10 knots, the runway most aligned with the winds shall be used ("East Ops" or "West Ops"). The controller may deviate from the normal ops procedure above and use runways that he/she feel would be the best for the airport, however, the CIC (Controller In Charge) must approve any deviation from the above ops.
3. If the reported visibility is less than 4 SM or the ceiling is less than 1500’ the ILS 10R approach shall be assigned, unless the pilot requests a different approach.
4. Initial climbs for IFR departures from MRY filed for altitudes at or above 5000 shall be to 5000. Departures off runways 10L/R should not be assigned runway heading due to the sharply rising terrain east of the airport.
5. During Normal Ops, departure releases must be obtained from MRY_APP.
6. Missed approaches off runways 28L/R reported to tower when radar facilities are manned shall be instructed to climb to 5000' on runway heading and transferred to the radar facility. Missed approaches off runways 10L/R reported to tower when radar facilities are manned shall be instructed to execute the published missed approach or instructed to turn left heading 030 and climb to 5000' then transferred to the radar facility to avoid high terrain off the departure end of runways 10. When no radar facility is online, missed approaches shall be handled in accordance with ZOA SOP-003.
NUQ - Moffet Federal
1. The following frequencies and text call signs are assigned to NUQ:
2. NUQ shall comply with the runway use plan as set by SFO_TWR. When SFO_TWR is in "normal ops / west flow" NUQ shall use runways 32L/R. When SFO_TWR is in "east flow", NUQ shall use runways 14L/R. If local winds make compliance with this instruction unsafe, NUQ_TWR may deviate from this procedure, but must inform all Norcal TRACON sectors and OAK CTR positions of this condition.
3. Initial climbs for IFR departures from NUQ filed for altitudes at or above 5000 shall be to 5000.
4. When using runways 32L/R, all departures off NUQ shall use either the SOLN9 DP or OSI2 DP. NUQ_TWR shall get releases for SOLN9 departures from SJC_APP and SJC_APP shall handle these departures. NUQ_TWR shall get releases for OSI2 departures from SFO_APP and SFO_APP shall handle these departures.
5. When using runways 14L/R, all departures off NUQ shall use the SOLN9 DP, HOOKS3 DP, or OSI2 DP. NUQ_TWR shall get releases from SJC_APP and SJC_APP shall handle these departures.
6. When radar facilities are manned, missed approaches off runways 32L/R shall be instructed to turn right heading 140, climb/maintain 2000 and transferred to SJC_APP; missed approaches off runways 14L/R shall be instructed to turn right heading 300, climb/maintain 2000 and transferred to SJC_APP. When no radar facility is online, missed approach shall be handled in accordance with ZOA SOP-003.

OAK - Metro Oakland Intl
1. The following frequencies and text call signs are assigned to OAK:
2. At the discretion of the Shift Supervisor or OAK_TWR, the TWR position may be split into North and South positions. OAK_N_TWR shall control operations on runways 9-27 L/R and OAK_S_TWR shall control operations on runways 11/29. When not split, OAK_TWR shall use 127.20.
3. OAK shall comply with the runway use plan as set by SFO_TWR. When SFO_TWR is in "normal ops / west flow" OAK shall use runways 27, 29, and 33. When SFO_TWR is in "east flow", OAK shall use runways 9, 11, and 15. If local winds make compliance with this instruction unsafe, OAK_TWR will contact SFO_TWR and ask SFO_TWR to change its configuration to match OAK. If SFO_TWR is unable, OAK_TWR may deviate from this procedure, but must inform all Norcal TRACON sectors and OAK CTR positions of this condition. (That SFO is Normal Ops / OAK using Rwys 11, 9L/R & 15.)
4. OAK_TWR owns the airspace within 5 NM of the airport at and below 3000. OAK_TWR is responsible for the separation of all aircraft within this airspace including overflights, arrivals, departures and missed approaches. OAK_TWR may use radar or non-radar procedures to separate aircraft. Careful attention must be paid to the performance capabilities of departures to ensure there is not a loss of separation with a faster aircraft overtaking a slower aircraft. If it appears that an aircraft will lose separation with an aircraft ahead, OAK_TWR may assign a heading to avoid loss of separation and advise the appropriate departure controller.
5. Initial climbs for IFR departures from OAK filed for altitudes at or above 5000 shall be to 5000.
6. Except as provided in paragraph 8, departure releases must be obtained from the departure radar facility only when the facility declares release procedures to be in effect.
7. Missed approaches reported to tower when radar facilities are manned shall be instructed to climb to 5000' on runway heading and, once separation from other aircraft in OAK_TWR airspace is assured, transferred to the radar facility (HWD_APP in east ops, CCR_APP in west ops) for resequencing. When no radar facility is online, missed approaches shall be handled in accordance with ZOA SOP-003.
8. During East Ops departures are handed to HWD_APP. During West Ops, departures are split between CCR _APP and STS_APP. Departure Procedures are handled as follows:
  
  Northbound/Eastbound: departure controller CCR_APP 120.90
  - Normal Ops: The preferred departure procedure is the OAK5. Aircraft unable to accept the OAK5 shall be instructed to fly runway heading and expect radar vectors to their first fix. The NIMITZ departure may be assigned at the controller's discreation to keep aircraft departing runway 27 L/R from converging with aircraft departing runway 29 on the OAK5 DP. Any other DP requires a release from CCR_APP.
  - East Ops: Aircraft bound for ECA, LIN, SAC should be assigned the MARINA DP in lieu of the OAK DP. Aircraft bound for SGD or RBL should be assigned the SGD1 DP in lieu of the OAK DP. (SGD1.RBL is called the "Scaggs Island One Departure, Lake Transition.") Any other DP requires a release from HWD_APP.
  Westbound/Southbound: departure controller STS_APP 135.10
  - Normal Ops: These departures may be assigned the COAST, NUEVO, OAK, or SKYL DPs. Any other DP requires a release from STS_APP.
  - East Ops: The COAST DP is unusable in East Ops, and the SKYL DP should be used instead. The MARI DP, OSI transition, should be used in lieu of the NUEVO DP. Oceanic departures on the OAK DP going to ALCOA or BEBOP should be assigned the MARI DP, OSI transition, radar vectors to ALCOA or BEBOP, then as filed. Any other DP requires a release from HWD_APP.
9. Noise abatement procedures shall be utilized between the hours of 2200 - 0700 local time, as follows:
  - The SLNT7 DP should be used in lieu of the OAK DP.
  - The SALAD1 DP should be assigned to Catagory A & B prop aircraft between 2200-0600L bound for ALTAM or ECA, in lieu of the OAK DP.

RNO - Reno-Taho Intl
1. The following frequencies and text call signs are assigned to RNO:
2. RNO shall use runway 16L/R when winds are 10 knots or less from any direction. This plan shall be designated "Normal Ops". If winds are greater than 10 knots from 251 thru 069 degrees the airport shall be in the "North Ops" plan and runways 34L/R shall be in use.
3. Initial climbs for IFR departures from RNO filed for altitudes at or above 15000 shall be to 15000.
4. Departure releases must be obtained from RNO_APP only when RNO_APP requests release procedures to be in effect.
5. Missed approaches reported to tower when radar facilities are manned shall be instructed to climb to 9000 (prop) / 12000 (turbojet) on runway heading and transferred to the radar facility. When no radar facility is online, missed approach shall be handled in accordance with ZOA SOP-003.
SCK - Stockton Metro
1. The following frequencies and text call signs are assigned to SCK:
2. When winds are from 021 thru 199 above 10 knots, the field shall use runways 11L/R. At all other times the airport shall use runways 29L/R.
3. Initial climbs for IFR departures from SCK filed for altitudes at or above 5000 shall be to 5000.
4. IFR Departure releases must be obtained from MOD_APP only when MOD_APP requests release procedures to be in effect.
5. Missed approaches reported to tower when radar facilities are manned shall be instructed to climb to 2000 on runway heading and transferred to the radar facility. When no radar facility is online, missed approach shall be handled in accordance with ZOA SOP-003.

SFO - San Francisco Intl
1. The following frequencies and text call signs are assigned to SFO:
2. At the discretion of the Shift Supervisor, SFO_TWR, or SFO_GND, the GND position may be split into East and West positions. Ground Control shall be split along an imaginary line bisecting the field through taxiway Delta. SFO_E_GND shall control all movements east of the extended line through taxiway Delta. SFO_W_GND shall control all movements on taxiway Delta and west of the extended line.
3. SFO_TWR is responsible for determining the active runway use plan for SFO, OAK and SJC, although OAK or SJC TWR may deviate from the plan when local safety conditions demand. It is quite inefficient for the operations at OAK and/or SJC to be split with SFO (i.e. some airports west ops, some east). If SJC or OAK deviate from SFO’s runway plan, SFO_TWR may follow if conditions permit and inform the other facilities affected.
4. SFO_TWR owns the airspace within 5 NM of the airport at/below 3000. SFO_TWR is responsible for the separation of all aircraft within this airspace including overflights, arrivals, departures and missed approaches. SFO_TWR may use radar or non-radar procedures to separate aircraft. Careful attention must be paid to the performance capabilities of departures to ensure there is not a loss of separation with a faster aircraft overtaking a slower aircraft. If it appears that an aircraft will lose separation with an aircraft ahead, SFO_TWR may assign a heading to avoid loss of separation and advise the appropriate departure controller.
5. Runway use: A controller may not assign a runway which has a tailwind component greater than 10 knots or a crosswind component greater than 20 knots; however, a pilot may request the use of such a runway, and the controller may grant such a request. Runways shall be assigned as follows:
6. Initial climbs for IFR departures from SFO filed for altitudes at or above 5000' shall be to 5000'.
7. Caution must be exercised in use of runways 19L/R due to steeply rising terrain to 2000' immediately south of the airport. During IMC conditions or at night, pilots shall be advised to review published SID runway departure instructions from the appropriate chart, or issued them in the departure clearance.
8. Except as provided in paragraph 10, departure releases must be obtained from the departure radar facility only when the facility declares release procedures to be in effect.
9. Missed approaches off instrument approaches to runways 28L/R reported to tower when radar facilities are manned shall be instructed to climb to 5000' on runway heading. Missed approaches off instrument approaches to runways 19L/R or 10L/R reported to tower when radar facilities are manned shall be instructed turn left heading 090 and climb/maintain 5000 to avoid terrain south of the airport. Once missed approach instructions are issued and separation from other aircraft in SFO_TWR airspace is assured, the aircraft shall be transferred to the appropriate radar facility (STS_APP off 28L/R, HWD_APP off 10L/R or 19L/R) for resequencing. When no radar facility is online, missed approaches shall be handled in accordance with ZOA SOP-003.
10. During East Ops, departures are handed to HWD_APP. During West Ops, departures are split between CCR _APP and STS_APP. Departure Procedures are handled as follows:
11. Noise abatement procedures shall be utilized between the hours of 2200 - 0700 local time, as follows:
  
  Arrivals:
  1. Runway 28R is preferred. During visual meteorological conditions (VMC) arriving aircraft should be assigned the Quiet Bridge charted visual approach.
  2. Runway 28L.
  3. Other runways as wind permits.
  Departures:
  
  Between 2200-0100 local time, and also between 0600-0700 local time:
  1. Runways 1L/R preferred. The CUIT3 DP ("Quiet 3 Departure") should be used in lieu of the SFO8 DP.
  2. Runways 28L/R with an immediate turn to the right. The CUIT3 DP should be used in lieu of the SFO8 DP.
  3. Other runways as wind permits. Runways 28L/R straight-out departure (e.g. GAPP3) is discouraged if it can be avoided.
  Between 0100-0600 local time:
  1. Runways 10L/R preferred. The DUMB6 DP should be used in lieu of the SFO8 DP. Note that in this configuration SFO will be landing runways 28L/R, and departing runways 10L/R, wind and traffic permitting. This is sometimes referred to as "suicide ops."
  2. Runways 28L/R with an immediate turn to the right. The CUIT3 DP should be used in lieu of the SFO8 DP.
  3. Runways 1L/R. The CUIT3 DP should be used in lieu of the SFO8 DP.
  4. Other runways as wind permits. Runways 28L/R straight-out departure (e.g. GAPP3) is discouraged if it can be avoided.

SJC - Mineta San Jose Intl
1. The following frequencies and text call signs are assigned to SJC:
2. SJC shall comply with the runway use plan as set by SFO_TWR. When SFO_TWR is in "Normal Ops / West Flow" SJC shall use runways 30L/R and 29. When SFO_TWR is in "East Ops", SJC shall use runways 12L/R and 11. If local winds make compliance with this instruction unsafe, SJC_TWR will contact SFO_TWR and ask SFO_TWR to change its configuration to match SJC. If SFO_TWR is unable, SJC_TWR may deviate from this procedure, but must inform all Norcal TRACON sectors and OAK CTR positions of this condition.
3. Initial climbs for IFR departures from SJC filed for altitudes at or above 5000 shall be to 5000.
4. Departure releases must be obtained from SJC_APP only when SJC_APP requests release procedures to be in effect.
5. Missed approaches reported to tower when radar facilities are manned shall be instructed to climb to 5000' on runway heading and transferred to SJC_APP. When no radar facility is online, missed approach shall be handled in accordance with ZOA SOP-003.
6. The SUNOL6 departure is restricted to prop aircraft and these departures will be handed to OAK_APP in west ops or HWD_APP in east ops.
7. The LOUPE1 and DANV2 departures are restricted to jet aircraft only.

SMF - Sacramento Intl
1. The following frequencies and text call signs are assigned to SMF:
2. SMF DEL, GND and TWR shall use the voice call sign "Capitol".
3. The following runway plans are in use for SMF:
4. Initial climbs for IFR departures shall be:
5. Departures to the North (to RBL) shall be given the following in their IFR clearance during South Ops: "After takeoff turn left heading 010, expect radar vectors to RBL, then as filed." This ensures that they'll make a climbing left turnout to the east and protects the WRAPS5 arrivals descending west of the field.
6. Departure releases must be obtained from SMF_APP only when SMF_APP requests release procedures to be in effect.
7. Missed approaches reported to tower when radar facilities are manned shall be instructed to climb to 3000' on runway heading and transferred to the radar facility. When no radar facility is online, missed approach shall be handled in accordance with ZOA SOP-003.
SNS - Salinas Muni
1. The following frequencies and text call signs are assigned to SNS:
2. When winds are 031 thru 169 above 10 knots the filed shall use runways 8 and 13. All other times the field shall use runway 31 and 26.
3. Initial climbs for IFR departures from SNS filed for altitudes at or above 5000 shall be to 5000.
4. Departure releases must be obtained from MRY_APP only when MRY_APP declares release procedures to be in effect.
5. Missed approaches reported to tower when radar facilities are manned shall be instructed to climb to 5000' on runway heading and transferred to the radar facility. When no radar facility is online, missed approach shall be handled in accordance with ZOA SOP-003.
SQL - San Carlos
1. The following frequencies and text call signs are assigned to SQL:
2. When winds are less than 5 knots, runway 12 shall be used. With wind above 5 knots, use the runway most aligned with the wind.
3. Initial climbs for IFR departures from SQL filed for altitudes at or above 2000 shall be to 2000.
4. IFR aircraft departing via runway 12 shall be instructed in their IFR clearance "fly runway heading, radar vectors (route/fix)...". Aircraft departing runway 30 shall be instructed in their clearance "fly runway heading until abeam the diamond shaped waterway, then turn right heading 120, radar vectors (assigned route/fix), maintain VFR at or below 1100' until the OAK 165 radial, maintain 2000..." SEE GRAPHIC.
5. Departure releases must be obtained from SFO_APP at all times.
6. Missed approaches reported to tower when radar facilities are manned shall be instructed to climb to 2000' on runway heading and transferred to the radar facility. When no radar facility is online, missed approach shall be handled in accordance with ZOA SOP-003.
STS - Schultz Sonoma County
1. The following frequencies and text call signs are assigned to STS:
2. When winds are from 241 thru 089 above 10 knots, the field shall use runways 32 and 1. At all other times the airport shall use runways 19 and 14.
3. Initial climbs for IFR departures from STS filed for altitudes at or above 5000 shall be to 5000.
4. Departure releases must be obtained from STS_APP only when STS_APP requests release procedures to be in effect.
5. Missed approaches reported to tower when radar facilities are manned shall be instructed to climb to 2000 on runway heading and transferred to the radar facility. When no radar facility is online, missed approach shall be handled in accordance with ZOA SOP-003.
SUU - Travis AFB
1. The following frequencies and text call signs are assigned to SUU:
2. SUU shall comply with the runway use plan as set by SFO_TWR. When SFO_TWR is in "Normal Ops / West Flow" SUU shall use runways 21L/R. When SFO_TWR is in "East Flow", SUU shall use runways 3L/R. If local winds make compliance with this instruction unsafe, SUU_TWR may deviate from this procedure, but must inform all Norcal TRACON sectors and OAK CTR positions of this condition.
3. Initial climbs for IFR departures from SUU filed for altitudes at or above 5000 shall be to 5000.
4. Departure releases must be obtained from CCR_APP only when CCR_APP requests release procedures to be in effect.
5. Missed approaches reported to tower when radar facilities are manned shall be instructed to climb to 5000' on runway heading and transferred to the radar facility. When no radar facility is online, missed approach shall be handled in accordance with ZOA SOP-003.