Center Sector 'A'

POC: Facility Advisory Board	Date: 2008-07-25
Code: ZLA-800	Version: 1.12

1. PURPOSE

This Standard Operating Procedure (SOP) outlines the procedures to be used by controllers working Center positions to ensure that handoffs to SOCAL approach sectors are done in as efficient and timely a manner as possible. By specifying standard handoff points, and arrival routes, coordination between the two sectors can be greatly minimized.

2. ROLES AND RESPONSIBILITIES

The Office of Primary Responsibility (OPR) for this SOP is the ZLA Facility Advisory Board. This SOP was originally signed by Jeff Clark, ZLA Facility Chief on June 18, 2001. This SOP shall be maintained, revised, updated or cancelled by the ZLA Facility Advisory Board or any organization that supersedes, replaces or assumes the FAB responsibilities. 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 CTR positions at ZLA, as well as controllers working at SOCAL Approach positions.

4. BACKGROUND

Over time, controllers have found that having aircraft arrive between CTR and APP via pre-approved arrival points (or "gates") provides for a more orderly traffic flow, and reduces the need for communication between CTR positions and APP positions. It is also vitally important that both facilities understand what an airplane is going to do (i.e., what altitude he has been cleared to) when he approaches an adjoining controller's airspace. These procedures outline what instructions pilots will be issued as they go from CTR to APP.

5. REQUIREMENTS

a. Frequency:

A_CTR shall use 135.30 as its normal frequency.

b. Airspace:

A_CTR shall own all airspace depicted on the L.A. Center Sector Map, except for airspace owned by NTD_APP or SBA_APP if either of those facilities is open.

c. LAX Arrivals:

(1) Routing:

(a.) During normal airport operations at LAX

1. Turbojets inbound from the north and northwest shall be routed via AVE transition SADDE STAR

2. Turbojets inbound from oceanic airspace shall be routed via:

a. ELKEY transition SADDE STAR

b. FICKY transition LEENA STAR

3. Turbojets/Turboprops inbound from the west shall be routed via VTU transition SADDE STAR

(b.) During east airport operations at LAX

1. Turbojets inbound from the north and northwest shall be routed via AVE transition MOORPARK STAR

2. Turbojets inbound from oceanic airspace shall be routed via direct EXERT intersection direct LAX

3. Turboprops inbound from the west and northwest shall be routed via RZS V25 LAX

(c) During noise abatement operations at LAX

1. Turbojets inbound from the north and northwest shall be routed via AVE transition MOORPARK STAR

2. Turbojets inbound from oceanic airspace shall be routed via direct LAX

3. Turboprops inbound from the west and northwest shall be routed via RZS V25 LAX

(2) Altitudes:

(a.) During normal airport operations at LAX issue the following altitude restrictions prior to handoff:

1. AVE transition SADDE STAR: cross SYMON at and maintain 12,000. LAX_A_CTR has a permanent pointout for these aircraft to operate within BUR_APP airspace at/above 12,000'. LAX_A_CTR must ensure separation between SADDE6 and FERN5 traffic until the SADDE6 traffic enters LAX_W_APP airspace. See the pointout SOP for more information.

2. RZS/DINTY/ELKEY/VTU transition SADDE STAR: cross VTU at and maintain 11,000.

3. FICKY transition LEENA STAR: cross GOATZ at and maintain 12,000.

(b.) During east and noise abatement operations at LAX issue the following altitude restrictions prior to handoff:

1. AVE transition MOORPARK STAR: cross PAULA at and maintain 11,000. LAX_A_CTR has a permanent pointout for these aircraft to operate within BUR_APP airspace at/above 11,000'. LAX_A_CTR must ensure separation between MOOR3 and FERN5 traffic until the MOOR3 traffic enters LAX_W_APP airspace. See the pointout SOP for more information.

2. Arrivals routed via RZS V25 LAX: cross VTU at and maintain 6,000.

3. OCEANIC arrivals: cross 30 miles west of LAX at and maintain 6,000.

(3) Speed Restriction:

Issue speed restrictions according to the requirements of the individual arrivals at their indicated transition or fix.

(4) Handoffs:

Transfer of aircraft identification and control (handoff) must be completed prior to the arrival crossing the lateral boundary of SCT, or descending through 14,000, whichever comes first.

(5) Sequence:

LAX_A_CTR is responsible for merging the two arrival streams into one single stream with adequate IFR spacing between them. Any exceptions must be coordinated with LAX_APP.

For each arrival stream, Center shall provide a minimum of 10 NM in-trail spacing between successive LAX arrivals.

d. Other L.A. Basin arrivals:

(1) Routing:

(a) Aircraft inbound SNA, LGB or TOA shall be routed via the FLW or VTU transition TANDY STAR.

(b) Departures from OAK or SFO to SNA, LGB or TOA shall be routed via the OFFSHORE or COAST DP’s.

(c) Other basin arrivals originating in the Southern California Area shall be routed via the appropriate TEC routing.

(2) Altitudes:

(a) OFFSHORE and COAST DP’s: cross BENET at and maintain 11,000.

(b) TANDY STAR: cross MERMA at and maintain 14,000.

(3) Speed Restrictions

N/A

(4) Handoffs:

(a)Transfer of aircraft identification and control (handoff) must be completed prior to the arrival crossing the lateral boundary of SCT, or descending through 14,000, whichever comes first.

(b) TANDY arrivals and OFFSHORE / COAST DPs from the Bay Area shall be handed to LAX_DEP.

e. San Diego Arrivals

(1) Routing:

(a.) During normal airport operations at SAN

1. Turbojets inbound from the north and northwest shall be routed via LAX transition HUBRD STAR

(b.) During east airport operations at SAN

1. Turbojets inbound from the north and northwest shall be routed via LAX transition SHAMU STAR

(2) Handoffs:

Transfer of aircraft identification and control (handoff) must be completed prior to the arrival crossing the lateral boundary of SCT, or descending through 14,000, whichever comes first.

f. Valley arrivals:

(1) Routing:

Aircraft inbound to BUR, SMO or VNY shall be routed via the FERN STAR.

(2) Altitudes:

FERN STAR. AVE/FLW transitions: cross PIRUE/BAILL at and maintain 11,000'; OHIGH transition: cross CANYN at and maintain 9,000'.

(3) Handoffs:

Transfer of aircraft identification and control (handoff) must be completed prior to the arrival crossing the lateral boundary of SCT, or descending through 14,000, whichever comes first.

(4) Sequence:

LAX_A_CTR is responsible for sequencing all FERN STAR arrivals as a single stream, providing adequate IFR spacing between the successive arrivals merging at FIM VORTAC.

g. LAX Departures:

(1) VTU DP

(a) VTU Jet departures will be on a 250 heading when they are handed off from LAX_DEP. VTU Prop departures may be direct VTU or heading 250.

(b) A_CTR is responsible for separating VTU departures from any arrivals inbound from VTU.

(c) A_CTR has control on contact to turn VTU departures towards VTU or RZS, but no further north.

(2) PERCH DP

(a) PERCH departures will be on a 250 heading when they are handed off from LAX_DEP.

(b) A_CTR is responsible for separating PERCH departures from any arrivals inbound from VTU.

(c) A_CTR has control on contact to turn PERCH departures towards DINTY or FICKY intersections.

h. Special Instructions:

A_CTR is responsible for handling approaches into airports which do not have open approach facilities such as Santa Barbara, Vandenberg, etc.

Area A is responsible for ensuring that all oceanic flights are sent out onto the oceanic routes with correct oceanic spacing. Please see the Oakland Oceanic FIR for information on handling oceanic flights. TWRs should always ask LAX_A_CTR for an IFR release time for all oceanic aircraft to allow Center to plan the non-radar route, establish appropriate spacing, and get permission for the route from Oceanic.