ZLA Information:
VATSIM Disclaimer
ZLA Home Page
ZLA Crew Roster
ZLA Staff Members
News Archive
Pending Events
VATSIM Awards
Other ARTCCs
ZLA Forum

For Pilots:
Pilot Certifications
VFR/IFR Enroute Maps
Airports & Charts
ZLA TEC Routes
SimRoutes.com
Military Airfields
ZLA Weather
Submit Feedback

For Controllers:
Welcome to ZLA!
Become a Visitor
ATC Downloads
ATC Training Program
ZLA Test Study Guide
SOPs & LOAs
Position Restrictions
Global Rating Airports
TEC Route Lookup
Vectoring Diagrams
Airspace Maps
ZLA Mentor List
Top Ten Controllers
Controller Login




Center Sector 'B'

POC: Facility Advisory Board

Date: 2009-08-27

Code: ZLA-801

Version: 1.50

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:

B_CTR shall use 127.10 as its normal frequency.

b. Airspace:

B_CTR shall own all airspace depicted on the L.A. Center Sector Map. The airspace is shelved in the SW corner with B_CTR owning the airspace up to FL230 to work LOOP departures off LAX. E_CTR owns the airspace above. The shelved area is depicted in the sector file with a dashed line.

The airspace in the sector file shown as belonging to NLC_APP and FAT_APP is delegated to either Oakland Center, or NLC APP or FAT APP from the surface to 10,000' MSL.

c. LAX/SMO Arrivals:

(1) Routing:

Aircraft inbound to KLAX are not normally routed via B_CTR airspace, with the exception of KIMMO arrivals, which should be used for propeller aircraft landing at KLAX. Aircraft inbound to KSMO should be routed via the KIMMO STAR.

(2) Altitudes:

Aircraft inbound from LHS on the KIMMO STAR shall be handed off to BUR_APP, and should be descended to 14,000', or remain level at filed altitude, whichever is lower.

Aircraft inbound from PMD shall be handed off to PMD_APP descending to 14,000'. If PMD_APP is not staffed, aircraft inbound from PMD shall be assigned an altitude between 8000' and 14,000', with SMO arrivals below LAX arrivals, and handed off to BUR_APP.

d. LAX Departures:

(1) LOOP Departures

Aircraft on the LOOP departure will be climbing to 15,000 once B_CTR accepts the handoff and will have commenced their turn direct LAX prior to transfer of communications. LAX_DEP is responsible for ensuring that aircraft do not climb above 13,000 until within the lateral limits of B_CTR.

B_CTR must point out any departures to BUR_APP that will not be higher than 14,000 by the LAX_APP/BUR_APP sector boundary.

(2) GMN Departures

Aircraft on the GMN departure will come to B_CTR from BUR_APP on a heading to intercept the LAX323 radial outbound, or the GMN142 radial inbound.

e. ONT arrivals:

(1) Routing:

Aircraft inbound to KONT shall be routed via the ZIGGY STAR.

(2) Altitudes:

Aircraft inbound on the ZIGGY STAR shall be cleared to cross MAJEK at 14,000 and 250 KTS prior to handoff.

(3) Handoffs:

ZIGGY arrivals shall be handed off to ONT_APP prior, with transfer of communications occurring prior to the lateral boundaries of ONT_APP.

f. BUR Arrivals:

LYNXX STAR Arrivals

(a) If PMD APP is open, B_CTR shall instruct all LYNXX arrivals to cross WOOLI at and maintain 14,000 and handoff these arrivals to PMD_APP prior to WOOLI.

(b) If PMD APP is not open, B_CTR shall instruct all LYNXX arrivals to cross JANNY at and maintain 8000, and ensure handoff is complete prior to entering SOCAL airspace.

g. LAS Arrivals:

(1) Turbojet/Turboprop Arrivals:

(a) CLARR STAR arrivals shall be instructed after MISEN to cross CLARR at and maintain 13000 and 250 KTS.

(b) KEPEC STAR arrivals shall be instructed after MISEN to cross CLARR at and maintain 13000 and 250 KTS.

(c) When LAS_APP is sectorized, see the LAS_APP SOP for information on handling arrivals.

(2) Prop Arrivals:

Props shall be issued the CRESO STAR, and shall be instructed to cross WHIGG at and maintain 12000 and 250 KTS or less.

h. Other Information

BUR_APP may clear aircraft for an approach to L70 airport so long as an automated pointout is performed prior to clearing the aircraft for the approach. See the pointout SOP for more details.



Copyright © laartcc.org 2006-2010. The information contained on all pages of this website is to be used for flight simulation purposes only on the VATSIM network. It is not intended nor should it be used for real world navigation. This site is not affiliated with the FAA, the actual Los Angeles ARTCC or any governing aviation body. All content contained herein is approved only for use on the VATSIM network.


Click here for ZLA Credits, Copyrights and Acknowledgements