|
ZLA Information:
VATSIM Disclaimer
ZLA Home Page
ZLA Crew Roster
ZLA Staff Members
News Archive
Event Archive VATSIM Awards
Site Credits
Other ARTCC's
ZLA Forum
For Pilots:
Pilot Certifications
VFR/IFR Enroute Maps
Airports & Charts
TEC Routes
ZLA TEC Finder
SimRoutes.com
Military Airfields
ZLA Weather
Submit Feedback
For Controllers:
Welcome to ZLA!
ZLA Test Study Guide
ATC Downloads
ATC Training Program
SOPs & LOAs
ZLA Exam Center
Position Restrictions
Global Rating Airports
Vectoring Diagrams
Airspace Maps
ZLA Mentor List
Top Ten Controllers
Controller Login



|
 |
Center Sector 'B'
POC: Facility Advisory Board |
Date: 2008-07-25 |
Code: ZLA-801 |
Version: 1.31 |
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, except for airspace owned by BFL_APP or EDW_APP (including
airspace in the Edwards Military complexes) if either of those facilities is
open.
The airspace on the sector file shown as belonging to NLC_APP and FAT_APP at
Oakland 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 on the KIMMO STAR shall be handed off to BUR_APP. Aircraft inbound from LHS should be descended to 14,000', or remain level at filed altitude,
whichever is lower. Aircraft inbound from PMD shall be assigned an altitude between 8000' and 14,000', with SMO arrivals below LAX arrivals.
(3) Handoffs:
KIMMO arrivals shall be handed off to BUR_APP
prior to crossing the lateral boundary of BUR_APP airspace.
d. LAX Departures:
(1) LOOP/KWYET 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 performing a automated pointout with LAX_E_CTR
at least one minute prior to the aircraft entering his airspace.
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 EDW APP is open, B_CTR shall instruct all
LYNXX arrivals to cross WOOLI at and maintain 14,000 and handoff these arrivals
to EDW_APP prior to WOOLI.
(b) If EDW 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.
|  |