|
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 'F'
POC: Facility Advisory Board |
Date: 2008-02-11 |
Code: ZLA-805 |
Version: 1.21 |
1. PURPOSE.
This Standard
Operating Procedure (SOP) outlines the
procedures to be used by controllers working Center positions to ensure that
handoffs to adjacent facilities 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 October 15, 2002. 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 adjacent
control 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:
F_CTR shall use 127.35 as its normal frequency.
b. Airspace:
F_CTR shall own all airspace depicted on the
L.A. Center
Sector Map, except for airspace owned by LAS APP if that facility is
open.
c. LAX Arrivals:
(1) Routing:
(a.) During normal airport operations at KLAX,
inbounds from the northeast over HEC shall be routed via HEC and the
RIIVR STAR.
(b.) During night-time operations, aircraft shall
be routed via the REDEYE STAR.
(c.) During east operations, aircraft shall be
routed via the BASET STAR.
(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 RIIVR arrivals shall be GRAMM RUSTT RIIVR =IAF= LAX, with =IAF= representing the appropriate runway's initial appch fix for landing at LAX.
d. LAS arrivals:
(1) Routing - non FMS aircraft:
(a.) Aircraft inbound to LAS from the east or
southeast shall be routed via the KADDY STAR and instructed to cross KADDY
at and maintain 12,000 and 250 knots.
(b.) Aircraft without the STAR on board shall be
issued the same routing manually read to the pilot.
(2) Routing - FMS/RNAV/GPS-equipped aircraft:
Aircraft inbound to LAS from the east or
southeast who request it may be routed via the TYSSN STAR, and shall be instructed
to cross KADDY at and maintain 12,000 and 250 knots.
(3) LAS_APP sectorized
When LAS_APP is sectorized, see the LAS_APP SOP for more information on arrivals and departures.
e. ZAB and ZDV
arrivals:
Refer to the respective Letters of Agreement.
|  |