|
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 'D'
POC: Facility Advisory Board |
Date: 2008-01-31 |
Code: ZLA-801 |
Version: 1.30 |
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 20, 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 LAS Approach
and Departure 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:
D_CTR shall use 135.25 as its normal frequency.
b. Airspace:
D_CTR shall own all airspace depicted on the
L.A. Center
Sector Map, except for airspace owned by LAS_APP if it is open. If
LAS Approach is open, LAS Approach/Departure own the airspace within its
lateral boundaries and up to and including FL190.
c. Special
considerations:
LAS Arrivals and Departures will need
to be kept separated in the area South East of BTY.
d. LAS Arrivals:
(1) Routing:
Aircraft inbound to KLAS from BTY shall be issued
the FUZZY or SUNST STARS.
Aircraft inbound to KLAS from the North East shall
be issued the LUXOR or GRNPA STARS.
Aircraft without the published STARs shall be
manually read the routing, or issued vectors to follow the appropriate STAR route.
(2) Altitudes:
Aircraft inbound via FUZZY shall be instructed to cross FUZZY at and maintain 16000 and 250 KTS.
Aircraft inbound via LUXOR shall be instructed to cross LUXOR at and maintain 12000 and 250 KTS.
(3) Handoffs:
Aircraft shall be handed off and shall have radio
communications transferred to LAS Approach prior to reaching FUZZY or LUXOR.
(4) Sequence:
Aircraft landing LAS shall be speed matched, and
10 miles in trail at the time of handoff to LAS Approach.
e. LAS Departures:
LAS
Departures should be on course by the time they are handed off from LAS
Departure. If not, they shall be
vectored to their departure transition, and climbed to their cruising altitude.
f. LAS_APP sectorized
When LAS_APP is sectorized, see the LAS_APP SOP for information on handling arrivals and departures.
|  |