1. PURPOSE.

This Standard Operating Procedure (SOP) outlines the procedures to be used by controllers working Norcal Approach "Licke" Sector, the primary airport KSJC, 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 "Licke" Sector airspace, as well as controllers working at positions interfacing with Norcal TRACON "Licke" 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. Sequence SJC arrivals and separate SJC departures (except SUNOL departures, which are handled by OAK_APP [west ops] or HWD_APP [east ops]).

2. Separate traffic to/from secondary airports within SJC_APP airspace.

6. PROCEDURES.

a. Frequencies and Callsigns

1. Norcal approach "Licke" Sector shall use 120.10 as its frequency, SJC_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. SJC_APP shall own the airspace within the lateral limits depicted on this graphic in west ops and on this graphic in east ops, from surface to FL190, except all actively manned Class D airspace within the lateral limits. Also, during west ops, SJC_APP owns a “shelf” above SFO_APP between 12,000 MSL and FL190.

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 SJC will be determined by SJC_TWR per SOP_050. Normal prevailing winds are from the west.

2. The active runway plan for NUQ will be determined by NUQ_TWR per SOP_050. Normal prevailing winds are from the west. Releases are always required for NUQ departures.

d. Special Instructions:

1. Aircraft arriving on flight plans indicating “NO STAR” (or those that have not filed for an approved STAR) will have their clearances amended by OAK_CTR 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. During normal (west flow) runway plan, insure that aircraft are climbed above 5000' as soon as clear of SFO arrivals to runways 28L/R and SFO_APP airspace due to rising terrain.

4. SUNOL6 departures are restricted to prop aircraft only and departure control of these aircraft will be with OAK_APP in west ops and HWD_APP in east ops.

5. LOUPE1 and DANV2 departures are restricted to jet aircraft only.

6. When SJC_TWR is not online, SJC_APP shall assume control of the position.

7. When RHV_TWR is not online, SJC_APP shall assume control of the position.

8. When NUQ_TWR is not online, SJC_APP shall assume control of the position.

9. During east ops, when PAO_TWR is not online, SJC_APP shall assume control of the position.

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

1. ROBIE3 arrivals are received from OAK_A_CTR with instructions to “cross GOALI at FL200”. Issue clearance to cross GILRO at 8000. These aircraft may briefly pass through MRY_APP on a fixed pointout. Aircraft shall be merged with the HYP5 arrival stream and vectored to the final approach course from GILRO.

2. HYP5 arrivals are received from MOD_APP with instructions to cross GILRO at 8000. This arrival crosses the PXN arrival to OAK. Aircraft shall be merged with the ROBIE3 arrival stream and vectored to the final approach course from GILRO.

3. CAPO3 arrivals are received from MOD_APP with instructions to descend and maintain 6000. Prior to LICKE, aircraft shall be vectored to the final approach course.

4. GOLDN5 arrivals are received from STS_APP at 12000, with instructions to depart SFO on heading 120. Once clear of the underlying SFO_APP airspace aircraft shall be descended and vectored to a downwind leg. A pointout may be requested from SFO_APP to descend the GOLDN5 below the shelf over "Woodside" sector to 6000 for a visual approach to runway 30L from the left downwind, but only if it will not conflict with BSR2 arrivals to SFO.

5. Oceanic arrivals are received from STS_APP with instructions to cross SFO 12000 and depart SFO on heading 120. STS_APP will have merged these aircraft with any GOLDN5 arrivals.

6. Missed Approach instructions may be assigned per the published procedures or alternately climbed to 5000 and turned to heading 150 to re-enter a left downwind for re-sequencing.

f. OAK Arrivals – Normal (West Flow) Operations

1. PXN2 arrivals are received from OAK_A_CTR with instructions to “descend at pilot’s discretion, maintain FL200”. Descend these aircraft as able reference the HYP5 arrival stream so that jets reach 10000 at BORED and props are at 8000 at BORED. There is a charted 250 knot speed restriction at BORED. Hand these arrivals to OAK_APP.

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

1. LOUPE1 departures are restricted to jet aircraft and shall proceed under pilot navigation; These aircraft must remain at or below 5000 per the departure instructions to pass beneath the SFO runway 28 final approach stream. These aircraft may pass briefly through SFO_APP airspace on a fixed pointout at or below 5000. Downwind and clear of the SFO 28 approach stream and SFO_APP airspace, aircraft shall be cleared to climb to FL190 and vectored to SJC and instructed to resume own navigation once direct SJC. These departures may pass briefly through OAK_APP climbing to FL190 on a fixed pointout before climb clearance is issued by OAK_B_CTR.

2. SJC9 departures must remain at or below 5000 per the published runway departure instructions to pass beneath the SFO runway 28 final approach stream. These aircraft may pass briefly through SFO_APP airspace on a fixed pointout at or below 5000. Once clear of the SFO 28 approach stream and SFO_APP airspace, aircraft shall be cleared to climb to FL190.

3. SUNOL6 departures are restricted to prop aircraft only and control shall pass directly to OAK_APP upon departure.

4. Departures to AVE, PXN transitions shall be handed to OAK_A_CTR.

5. Departure to SAC, ECA, LIN, and RBL transitions shall be handed to OAK_B_CTR.

6. Insure separation of departures on AVE transitions from the merged arrival stream from GILRO and the CAPO3 arrival stream.

h. SJC Arrvials - East Flow Operations:

1. JAWWS2 arrivals are received from either MOD_APP (those aircraft overflying HYP) or MRY_APP (those aircraft overflying SNS) with instructions to cross JAWWS 8000. Monitor the merge of the two streams at JAWWS. Aircraft shall be descended and vectored into a downwind from PUCKK.

2. BRINY1 arrivals are received from MRY_APP with instructions to cross BRINY 5000 to pass below the HADLY2 arrival stream. Separate these aircraft from SFO/OAK departures overflying OSI and merge with arrivals from the southeast.

3. Oceanic arrivals are received from MRY_APP with instructions to cross BRINY 5000 to pass below the HADLY2 arrival stream. Aircraft are merged with the BRINY1 stream by MRY_APP. Separate these aircraft from SFO/OAK departures overflying OSI and merge with arrivals from the southeast.

4. CAPO3 arrivals are received from MOD_APP with instructions to descend and maintain 6000. Prior to LICKE, aircraft shall be vectored to the final approach course.

5. Missed Approach should be assigned runway heading, climbed to 5000, and given a right turn and merged with arrivals on the JAWWS2 arrival path. Monitor aircraft climbs to insure terrain clearance.

i. SJC Departures - East Flow Operations:

1. ALTAM7 DEP shall be used for slower climbing turbojets. Aircraft shall be instructed to proceed under pilot navigation. Aircraft approaching the SJC_APP border shall be handed to HWD_APP for merging with SFO DUMB6 and OAK MARI4 departures. Turbojets must comply with the published climb restriction to be 11000 by 16 SJC DME.

2. DANV2 aircraft shall depart on runway heading until reaching 5000 and then be vectored to SJC and instructed to resume own navigation when direct SJC. Aircraft shall be handed HWD_APP to monitor separation with SFO and OAK departures. Turbojets must comply with the published climb restrictions to cross SJC 12000 and at or above 14000 by 8 SJC DME.

3. MOONY3 departures shall proceed under pilot navigation. Insure aircraft remain below 7000 on PXN transition and 12000 on AVE transition until they have passed beneath JAWWS2 arrivals.

4. SUNOL6 departures pass directly to HWD_APP upon departure. HWD_APP controls these aircraft on a fixed pointout in SJC_APP airspace. Any headings assigned must be a right turn from the initial heading of 300.

j. SFO / OAK Departures – East Flow Operations:

1. SFO/OAK departures overflying OSI are received from HWD_APP on course. Ensure these aircraft are separated from BRINY and Oceanic arrivals and pass them to MRY_APP. Advise MRY_APP if these aircraft will cross the airspace boundary below 10000' to protect HADLY2 arrivals.

2. SFO/OAK departures on the PORTE3 or SKLY3 DPs are received from HWD_APP on course. HWD_APP is responsible for deconflicting the merge of these two departure streams. Each departure has a charted “at or above 5000” crossing restriction near the SJC/HWD boundary to protect SJC arrivals. Monitor these departures for separation from SJC arrivals.

k. NUQ Arrivals / Departures:

1. All NUQ departures require a release from the appropriate radar controller.

2. During west ops, all departures off NUQ shall use either the SOLN1 DP or OSI1 DP. NUQ_TWR shall get releases for SOLN departures from SJC_APP and SJC_APP shall handle these departures. NUQ_TWR shall get releases for OSI departures from SFO_APP and SFO_APP shall handle these departures.

3. During east ops, all departures off NUQ pass to SJC_APP. NUQ_TWR shall get releases for these departures from SJC_APP.

4. Instrument approaches to 14L/R during east ops must be coordinated with HWD_APP. Approaches may need to be coordinated at other times due to the proximity to other airspace.

l. SQL Arrivals – East Flow Operations:

1. During east ops, SQL sits very close to the SJC/HWD boundary. SJC_APP will work these arrivals and they must be coordinated with HWD_APP due to the proximity to SFO departures. When SQL_TWR is not manned HWD_APP works SQL_TWR.

m. WVI Operations – East Flow Operations

1. WVI is within SJC_APP airspace in east ops. However, MRY_APP works these arrivals on a “your control” fixed pointout in SJC_APP airspace at/below 4000. These operations must not go further than 5 miles north and east from WVI.

n. IFR Low Altitude Routing:

None.

o. Additional Comments:

1. During west ops, OAK_APP/SFO_APP has a fixed pointout on the YOSEM1 arrival between STEEV to FAITH and the SFO Airport at/above 6000. Compliance with this SOP will ensure separation from these aircraft.