1. PURPOSE.

This Standard Operating Procedure (SOP) outlines the procedures to be used by controllers working Norcal Approach "Laguna Seca" Sector, the primary airport KMRY, 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 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 "Laguna Seca" sector airspace, as well as controllers working at positions interfacing with Norcal TRACON "Laguna Seca" 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 MRY arrivals and separate MRY departures.

2. Sequence SNS arrivals and separate SNS departures.

3. Sequence WVI arrivals and separate WVI departures

4. Sequence and route aircraft inbound to the bay area from the sector.

6. PROCEDURES.

a. Frequencies and Callsigns

1. Norcal approach "Laguna Seca" Sector shall use 127.15 as its frequency, MRY_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. MRY_APP shall own the airspace within the lateral limits depicted on this graphic in west ops and this graphic in east ops, from surface to FL190, except all manned Class D airspace within the lateral limits.

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 MRY will be determined by MRY_TWR per SOP_050. Normal prevailing winds are from the west using runway 28L/R.

2. Departure release procedures with MRY_TWR will only be in use upon request by MRY_APP.

d. Special Instructions:

1. Aircraft arriving on flight plans indicating “NO STAR” (or those that have not filed for an approved STAR) shall have their clearances amended 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.

e. SFO/SJC Arrivals – West Flow Operations:

1. BSR2 arrivals are received from OAK_A_CTR with instructions to descend to “descend at pilot’s discretion, maintain FL200”. MRY_APP shall instruct aircraft to “cross SKUNK at or below 12000 and BOLDR at 10000” (with a charted 250 knot speed restriction). Descend these aircraft to 6000 and hand off to SFO_APP.

2. ROBIE3 arrivals may briefly pass through MRY_APP airspace on a fixed pointout north of SNS descending out of 16000.

f. SFO/OAK/SJC Arrivals – East Flow Operations:

1. HADLY2 arrivals for SFO and OAK are received from OAK_A_CTR with instructions to “descend at pilot’s discretion, maintain FL200”. STS_APP shall instruct aircraft to “cross EUGEN at 11000” (there is also a charted 250 speed restriction). Descend these aircraft to 6000 reference BRINY1 and Oceanic arrivals to SJC and hand off to STS_APP.

2. BRINY1 arrivals to SJC are received from STS_APP with instructions to cross BRINY at 5000. Merge these arrivals with any oceanic arrivals and pass to SJC_APP.

3. Oceanic arrivals to SJC are received routed BRINY.OSI with instructions to cross BRINY at 5000. Merge these arrivals with any BRINY1 arrivals and pass to SJC_APP.

4. JAWWS2 arrivals to SJC overflying SNS are received from MOD_APP with instructions to “cross JAWWS at 8000”. Ensure these arrivals are separated from any other traffic in MRY_APP airspace. Pass these arrivals to SJC_APP as soon as possible prior to the SJC airspace boundary so that SJC_APP can resolve any conflicts with arrivals from HYP.

g. SFO/OAK Departures – East Flow Operations:

1. SFO/OAK departures overflying OSI are received from SJC_APP on course. Ensure separation from HADLY, BRINY and SJC oceanic arrivals and pass to OAK_A_CTR or STS_APP as appropriate.

h. WVI Departures / Arrivals:

1. In west ops, WVI is within MRY_APP airspace and MRY_APP handles all WVI operations.

2. In east ops, WVI is within SJC_APP airspace. MRY_APP will still work all WVI operations. MRY_APP has a fixed “your control” pointout which extends into SJC_APP airspace 5 miles north and east of WVI, at/below 4000.

i. MRY Arrivals

1. PEBB1 arrivals are received from OAK_A_CTR with instructions to cross CARME at 7000. Aircraft shall be sequenced into Monterey airport via vectors.

2. Landing west...

i. IFR arrivals from the North (SNS) able to accept a full approach shall be instructed to "cross CHRLE at or above 6000" and cleared for the LOC/DME 28L approach prior to CHRLE.

ii. IFR arrivals from the East/Southeast (WIGGL) able to accept a full approach shall be instructed to "cross WIGGL at or above 6000" and cleared for the LOC/DME 28L approach prior to WIGGL.

iii. Vectored IFR arrivals for runway 28L shall be descended to 6000 and vectored to final approach between CHRLE and WIGGL. Light aircraft may be vectored for runway 28R east of LLYNN.

iv. During daylight VMC, V27 arrivals may be issued the Carmel Visual Rwy 28L approach. These aircraft shall be descended to 3000 prior to MUNSO.

3. Landing east...

i. IFR arrivals from north and southeast crossing SNS able to accept a full approach shall be instructed to "cross SNS at or above 3000" and cleared for the ILS 10R approach prior to SNS.

ii. IFR arrivals from the northwest (V25, V27) able to accept a full approach shall be instructed to "cross SANTY at or above 3000" (V25) or "cross SHOEY at or above 2100" (V27) and cleared for the ILS 10R approach prior to SANTY/SHOEY.

iii. Vectored IFR arrivals for runway 10R shall be descended to 2100 once offshore, and vectored to the final approach course at least 6nm from MUNSO.

iv. During daylight VMC the Lobos Visual Rwy 10R approach may be issued and these aircraft shall be descended to 2000 prior to joining the procedure.

4. Missed Approaches shall be handled as described in SOP_050, then vectored for another approach.

j. MRY Departures:

1. MRY9 departures shall depart under pilot navigation on the charted runway instructions and shall be vectored to the transition.

2. MR2 departures shall depart under pilot navigation. Departures for the OSI and SNS transitions shall continue on pilot navigation. Departures for all other transitions shall be vectored once crossing the 010 bearing from the MUNSO NDB.

3. SECA2 departures shall depart under pilot navigation to SNS vor and thence vectored to the transition.

4. TORO5 departures shall depart under pilot navigation until crossing the SNS R-210 and thence shall be vectored to transition.

5. Departures climbing above TRACON ceiling shall be handed to OAK_A_CTR.

k. IFR Low Altitude Routing:

i. Aircraft inbound to SJC from MRY Should be routed SNS V111 V485 SJC

ii. Aircraft inbound to SFO from MRY Should be routed SNS V25 OSI

iii. Aircraft inbound to OAK from MRY Should be routed SNS V111 V301 SUNOL

l. Additional Comments:

1. The MOSS LANDING VISUAL RWY 28L for MRY should not be issued, as the supporting visual fixes are not modeled in the simulator scenery.

END