1.  PURPOSE.

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

a. During normal (west flow) operations, HWD_APP does not exist, refer to other SOPs for guidance.

b. During east flow operations, separate and sequence SFO and OAK departures.

c. During east flow operations, handle and resequence SFO and OAK missed approaches.

d. During east flow operations, Sequence and separate HWD arrivals and departures.

e. During east flow operations, When HWD_TWR is not manned, HWD_APP shall operate HWD_TWR, workload permitting.

f. During east flow operations, When SQL_TWR is not manned, HWD_APP shall operate SQL_TWR, workload permitting.

6. PROCEDURES.

a. Frequencies and Callsigns

1. Norcal approach "Niles" Sector shall use 134.50 as its frequency, HWD_APP as text callsign.

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

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

b. Airspace and Sectorization Plan:

1. HWD_APP shall own the airspace within the lateral limits depicted on this graphic in east ops, from surface to FL190, except all actively manned Class D airspace within the lateral limits. HWD_APP does not exist in west ops.

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 SQL will be determined by SQL_TWR.

2. The active runway plan for HWD will be determined by HWD_TWR per SOP_050.

3. Departure release procedures with SFO_TWR, OAK_TWR, HWD_TWR or SQL_TWR will only be in use upon request by HWD_APP.

d. Special Instructions:

1. 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.

2. SJC_APP will handle SQL arrivals. These arrivals will be coordinated with HWD_APP because of the proximity to SFO.

e. SFO/OAK Departures - East Flow Operations:

1. DUMB6 (from SFO), MARI4 (from OAK) and SGD1 (from OAK) departures should proceed under pilot navigation. Except for OSI transitions (see 3 below), merge these departures into a single stream and pass to CCR_APP. There is a charted crossing restriction of at/above 11000 at the OSI 24 mile fix; monitor departures to ensure compliance with this restriction to protect Bay area arrivals in CCR_APP airspace. If it appears that an aircraft will not comply with this restriction, advise CCR_APP.

2. PORTE3 (from SFO) and SKYL3 (from OAK) departures should proceed under pilot navigation. Ensure there will be no conflict at the point where the SKYL and PORTE departures merge (the merge point is in SJC_APP airspace) and hand to SJC_APP. There is a charted “at or above 5000” crossing restriction on both DPs to protect SJC arrivals, although the location is a little different on each. Monitor these departures and advise SJC_APP if they will cross the SJC sector boundary below 5000'.

3. DUMB6.OSI (from SFO), MARI4.OSI (from OAK), and GAPP3 (from SFO) departures should proceed under pilot navigation. Merge these departures into a single stream and hand to SJC_APP. Advise SJC_APP if these departures will cross the SJC_APP sector boundary below 5000'.

4. MOLEN3 departures from SFO should proceed under pilot navigation and be handed to STS_APP.

5. LUVVE3 departures from SFO proceed via pilot navigation to LUVVE intersection. Hand these arrivals to SJC_APP prior to LUVVE.

f. SFO/OAK missed approaches – East Flow Operations

1. Missed approaches off SFO will be received from SFO_TWR on a heading of 090 climbing to 5000. Missed approaches off OAK will be received from OAK_TWR on runway heading, climbing to 5000. Vector these aircraft to enter SFO_APP airspace about 5 miles north of SFO at 5000. Hand to SFO_APP on a heading of 280 with an assigned speed of 210 knots.

g. SJC Departures – East Flow Operations:

1. SJC ALTAM7 and DANV2 departures are received from SJC_APP with instructions to climb to FL190. Ensure separation from other departures.

2. SJC SUNOL6 departures are received directly from SJC_TWR; this departure instructs a heading of 300 for vector to the SJC R-009. These aircraft may be vectored on a fixed pointout in SJC_APP airspace. However, any assigned headings to join the DP must be a right turn from the initial 300 heading to protect SJC arrivals.

h. HWD Arrivals

1. All instrument approaches to HWD approach from the southeast. These approaches may have to circle to land on runways 10. Due to its proximity to HWD, consideration should be given to stopping departures off OAK while an aircraft is cleared for an approach to HWD.

i. SQL Arrivals

1. Arrivals to SQL are worked by SJC_APP. However, SJC_APP must coordinate these arrivals with HWD_APP due to the proximity to SFO departures. As stated above, HWD_APP works SQL_TWR when it is not manned.

j. Additional Comments:

1. CCR_APP has a fixed pointout in HWD_APP airspace for arrivals to SMF routed OAK.CCR.CCR1. These aircraft will cross OAK at 15000.

END