Center Sector 'E'

POC: Facility Advisory Board	Date: 2010-01-28
Code: ZLA-802	Version: 1.41

1. PURPOSE.

This Standard Operating Procedure (SOP)outlines the procedures to be used by controllers working Center positions to ensure that handoffs to 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 David Hendleman, ZLA Facility Chief on January 12, 2003. 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 underlying 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:

Los Angeles Center Sector E shall use 119.95 as its normal frequency.

b. Airspace:

E_CTR shall own all airspace depicted on the L.A. Center Sector Map. The airspace is shelved in the area over LAX, where E_CTR owns the airspace at/above FL240; B_CTR owns the airspace below. The shelved area is depicted in the sector file with a dashed line.

c. LAX Arrivals:

(1) Routing:

(a.) During normal airport operations at LAX turbojets from the south over JLI shall be routed via JLI.OLDEE arrival or JLI.VISTA arrival. Propeller aircraft shall be routed via JLI.VISTA arrival.

(b.) During night-time operations, aircraft shall be routed via JLI.REDEYE arrival.

(c.) During east operations, aircraft shall be routed via the OCEAN arrival.

(d.) Aircraft without the published STARS on board shall be routed via the same routing, manually read to the pilot.

NOTE: The manual routing for JLI.OLDEE arrival shall be JLI WYVIL OLDEE SEAVU.

The manual routing for OCEAN arrival shall be JLI CYNDE OCN BIGJO SHILY DOYLE EXERT direct LAX.

NOTE: The manual routing for REDEYE arrival shall be JLI PDZ BASET DOWNE SMO WAKER direct LAX.

(2) Altitudes:

Before handing aircraft off to LAX_FE_APP, LAX arrivals shall be issued the following altitudes:

(a.) OLDEE arrivals: cross WYVIL at and maintain 16000.

(b.) OCEAN/VISTA arrivals: cross CYNDE at and maintain 12000.

(c.) REDEYE arrivals: cross JLI at FL240, descend and maintain 16000.

(3) Handoffs:

OLDEE arrivals shall be handed off, and communications transferred to LAX_FE_APP prior to WYVIL. OCEAN/VISTA arrivals shall be handed to SAN_APP prior to aircraft descending through 14000.

(4) Sequence:

During Normal Operations, Los Angeles Center Sector E must provide one single stream of LAX arrivals to LAX_FE_APP on the JLI.OLDEE clearly sequenced. Exceptions or unclear sequences must be coordinated with LAX_FE_APP prior to handoff.

During East-Operations, Los Angeles Center Sector E must provide one single stream of LAX arrivals to SNA_APP.

During Noise-Abatement Operations, Los Angeles Center Sector E must provide one single stream of arrivals to LAX_FE_APP.

LAX_FE_APP and SNA_APP must be notified prior to handoff if the sequences described herein will not be adhered to.

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

d. SAN arrivals:

(1) Routing:

During west operations aircraft inbound to SAN shall be routed via the BARET arrival routing from the east and northeast, or the HUBRD arrival from the north. During east operations aircraft inbound to SAN shall be routed via the BARET or LYNDI arrivals from the east and northeast or the SHAMU arrival from the north. Aircraft without the STAR on board shall be issued the same routing manually read to the pilot.

(2) Altitudes:

Before handing off to SAN_APP, SAN arrivals shall be issued the following altitudes:

(a.) BARET arrival:

1. TNP, EED, PKE Transitions: Cross 25 miles northeast of PGY at and maintain 12,000.

2. IPL Transition: cross PILLO at and maintain 10,000.

(b.) HUBRD arrival: Cross CARDI at and maintain 15,000.

(c.) SHAMU arrival: Cross SHAMU at and maintain 15,000.

(d.) LYNDI arrival:

1. TNP, PKE, EED transitions: Cross TRIXI at and maintain 12000.

2. IPL transition: Cross GREED at and maintain 12000.

(3) Airspeed:

HUBRD and SHAMU arrivals must be instructed to cross CARDI and SHAMU at 250 knots respectively.

(4) Handoffs:

All aircraft shall be handed off, and communications transferred to SAN APP prior to crossing the lateral limits of the SAN APP airspace or for HUBRD and SHAMU arrivals prior to CARDI and SHAMU.

e. Other San Diego area arrivals:

(1) Routing:

NZY arrivals shall be route via the BARET arrival.

(2) Altitudes:

Before handing off to SAN APP, NZY arrivals shall be issued the following Altitudes:

BARET arrival:

1. TNP, EED, PKE Transitions: Cross 25 miles northeast of PGY at and maintain 12,000.

2. IPL Transition: Cross PILLO at and maintain 10,000.

(3) Airspeed:

BARET arrivals shall be instructed to cross PILLO at 250 knots.

(4) Handoffs:

All aircraft shall be handed off and communications transferred to SAN APP prior to crossing the lateral limits of the SAN APP airspace.

f. ONT arrivals:

(1) Routing:

Aircraft inbound to KONT shall be routed via the SETER arrival routing from the south. Aircraft without the STAR on board shall be issued the same routing manually read to the pilot.

(2) Altitudes:

Before handing off to Ontario Approach, ONT arrivals shall be issued the following altitudes:

SETER2: cross ROTHY at and maintain 12,000.

(3) Airspeed:

SETER2 arrivals must be instructed to reduce speed to 250 knots by ROTHY.

(4) Handoffs:

All aircraft shall be handed off, and communications transferred to ONT APP, prior to crossing the lateral limits of the ONT APP airspace.

g. LAX Departures:

(1) Routings:

a. During normal airport operations at LAX:

1. Northeast departures shall be assigned either the SEBBY, HOLTZ, OSHNN, or LOOP departures. LOOP departures will remain in B_CTR airspace and be handed by LAX_DEP to B_CTR. SEBBY, HOLTZ, and OSHNN departures will be handed to E_CTR, who must sequence them with departures from other airports.

2. East or Southeast departures shall be assigned either the LAXX, HOLTZ, or KARVR departure procedures:

(a) LAXX.TRM departures shall be vectored direct to TRM.

(b) LAXX.IPL departures shall be vectored to OCN.

(c) LAXX.MZB departures shall be vectored to MZB.

b. During east airport operations at LAX:

1. Northeast departures shall be assigned the GABRE departure procedure and will be handed off from LAX_DEP to B_CTR.

2. East or Southeast departures shall be assigned either the OCN or the SNGO departures:

(a) OCN departures shall be vectored to OCN.

(b) SNGO departures shall be vectored to join the DP routing prior to CARDI.

c. During noise abatement operations at LAX:

Northeast/east departures shall be assigned either the SEBBY, LAXX, OSHNN, or KARVR departure procedures and will be handed off from LAX_DEP to E_CTR.

(a) SEBBY.DAG departures shall be vectored by center direct to DAG.

(b) All other departures shall proceed on course.

(2) Altitudes:

a. SEBBY.DAG, LAXX.TRM, HOLTZ and OSHNN departures will be assigned 13,000 and may be cleared to 17,000 once E_CTR accepts the handoff.

b. Other departures will be assigned 13000.

(3) Airspeed:

No airspeed restrictions shall be placed on departures without prior coordination between LAX_DEP and E_CTR.

h. San Diego Departures:

(1) Routings:

a. During West airport operations at SAN:

1. Northwest departures shall be assigned the PEBLE departure procedure.

2. East departures shall be assigned the BORDR or POGGI departure procedure.

b. During east airport operations at SAN

1. Northwest departures shall be assigned the LYNSY departure procedure.

2. East departures shall be assigned the BORDR departure procedure.

(2) Altitudes:

All departures will be assigned 13,000 by SAN_DEP.

(3) Airspeeds:

No airspeed restrictions shall be placed on departures without prior coordination between SAN_DEP and E_CTR.

i. Santa Ana/Long Beach Departures:

(1) Routings:

During normal airport operations at LGB:

East or Northeast departures shall be assigned radar vector TRM or SLI.SEBBY.DAG respectively. RNAV aircraft may be assigned the SENIC departure procedure.

During normal airport operations at SNA:

1. East or Northeast departures shall be assigned the MUSEL or DUUKE departure procedure.

2. Northwest departures shall be assigned the CHANNEL departure procedure.

(2) Altitudes:

Departures via SLI and TRM (excluding MUSEL6.TRM) will be assigned 17,000 by LAX_DEP once E_CTR accepts the handoff, 13,000 otherwise. All other routes will be assigned 13,000.

(3) Airspeeds:

No airspeed restrictions shall be placed on departures without prior coordination between SNA_DEP and E_CTR.

j. Ontario Departures:

(1) Routings:

East and Southeast departures shall be assigned the PRADO departure procedure.

(2) Altitudes:

All departures will be assigned 13,000 by ONT_DEP.

(3) Airspeeds:

No airspeed restrictions shall be placed on departures without prior coordination between ONT_DEP and E_CTR.

k. Flights entering or exiting Mexican Airspace:

(1) All flights exiting USA airspace shall have radar service terminated, and shall be instructed to contact Metro Mazatlan Center.

(2) All flights entering USA airspace from Mexican Airspace shall be issued a new beacon code, and shall be radar identified.