|
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 'C'
POC: Facility Advisory Board |
Date: 2008-07-25 |
Code: ZLA-802 |
Version: 1.22 |
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:
C_CTR shall use 133.20 as its normal frequency.
b. Airspace:
C_CTR shall own all airspace depicted on the
L.A.
Center Sector Map, except for airspace owned by ONT_APP, LAX_FE_APP and
PSP_APP if any of those facilities is open.
c. LAX Arrivals:
(1) Routing:
(a.) During normal airport operations at
KLAX, turbojets/turboprops
from the northeast over HEC shall be routed via HEC.RIIVR1
arrival.
(b.) During normal airport operations at
KLAX, turbojets/turboprops
inbounds from the east shall be routed via TNP.SEAVU1
arrival.
(c.) During normal airport operations at
KLAX, props shall be routed as
follows:
(i.) from HEC:
direct
PDZ.V16.LAHAB
(ii.) from the
east:
direct
PSP.V388.PDZ.V16.LAHAB
(d.) During night-time operations, aircraft
shall be routed via the REDEYE2 arrival.
(e.) During east operations, aircraft shall
be routed via the BASET3 arrival.
(f.) 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 approach fix for landing at LAX
NOTE: The manual routing for SEAVU arrivals shall be TNP
KONZL CATAW LUVYN =IAF= LAX with =IAF= representing the appropriate runway's initial approach fix for landing at LAX.
(g.) Restricted area R2501 is normally in
operation 24 hours a day, at all altitudes, and J128 is not normally
available for arrivals into KLAX.
(2) Altitudes:
Before handing aircraft off to LAX_FE_APP,
LAX arrivals shall be issued the following altitudes:
(a.) RIIVR arrivals: cross GRAMM at/maintain
FL180, (or next higher FL if FL180 not available due to
altimeter)
(b.) SEAVU arrivals: cross
KONZL at and maintain 17,000.
(c.) BASET3 arrivals:
HEC, PGS transitions, descending to FL180, (or next higher FL if
FL180 not available due to altimeter); TNP transition, to cross TRTLE at
and maintain 16000.
(d.) REDEYE2 arrivals:
HEC, PGS transitions, descending to FL180, (or next higher FL if
FL180 not available due to altimeter); TNP transition, to cross TRTLE at
and maintain 16000.
(e.) Props 12000.
(3) Handoffs:
All arrivals shall be handed off, and
communications transferred to LAX_FE_APP prior to crossing the lateral
limits of the LAX_FE_APP airspace.
(4) Airspeed:
All BASET3, REDEYE2 arrivals
shall be instructed to reduce speed to 250 knots by CIVET or TRTLE.
(5) Sequence:
During Normal Operations, C_CTR must provide
two single streams of arrivals to LAX_FE_APP, one on the RIIVR routing,
and the other on the SEAVU, each clearly sequenced. Exceptions or
unclear sequences must be coordinated with LAX_FE_APP prior to
handoff.
During East-Operations, C_CTR must provide three single streams of
arrivals to LAX_FE_APP, one on the HEC transition, one on the PGS
transition, and the other on the TNP transition.
During Noise-Abatement Operations, C_CTR must provide three single
streams of arrivals to LAX_FE_APP, one on the HEC transition, one on the
PGS transition, and the other on the TNP transition.
LAX_FE_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. ONT arrivals:
(1) Routing:
Aircraft inbound to KONT shall be routed via
the SETER2 arrival routing from the east, or the ZIGGY4 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 ONT APP, ONT arrivals shall be issued the
following altitudes:
(a.) SETER2: Crossing BANDS at and maintain 14,000
(b.) ZIGGY4: Crossing DAWNA at and maintain 12,000
(3) Airspeed
All SETER2, ZIGGY4 arrivals must be instructed to reduce speed to 280
knots by BANDS, and 250 knots by DAWNA.
(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.
e. Other L.A. Basin arrivals:
(1) Routing:
(a) Via HEC
Aircraft inbound to SNA, LGB, or TOA shall
be routed via the KAYOH4 arrival. Aircraft without the STAR onboard
shall be issued the same routing manually read to the pilot.
(b) Via PSP
(1) Turbo-jets, Turbo-props
Turbo-jets, Turbo-props inbound to SNA, LGB,
or TOA shall be routed via the KAYOH4 arrival. Aircraft without the
STAR onboard shall be issued the same routing manually read to the
pilot.
(2) Props
Props inbound to SNA, LGB, or TOA shall be
routed via:
PSP V388 ACINS V283 SLI
(2) Altitudes:
Before handing off to ONT APP, L.A. Basin arrivals shall be issued the
following Altitudes:
Via HEC: Crossing DAWNA at 13,000 (Turbojet, Turbo-props) or
12,000 (Props).
Via PSP: Crossing BANDS at 14,000
(3) Airspeed:
All KAYOH4 arrivals shall be instructed to reduce speed to 250 knots by
DAWNA or BANDS.
(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.
f. SAN arrivals
(1) Routing:
Aircraft inbound to KSAN shall be routed via the BARET4 arrival
routing. Aircraft without the STAR onboard shall be issued the same
routing manually read to the pilot.
(2) Altitudes:
Before handing off to E CTR, SAN Arrivals shall be issued the following
altitudes.
(a) BARET4: Crossing SALTN at or below FL240.
g. PSP arrivals
(1) Routing:
Aircraft inbound to KPSP via the standard terminal arrivals shall be instructed as follows:
(2) Altitudes:
Before handing off to PSP APP, arrivals shall be issued the following altitudes:
(a) SBONO: Crossing CLOWD at and maintain 11,000
(a) CLOWD: Crossing CLOWD at and maintain 11,000
(3) Airspeed:
All SBONO and CLOWD arrivals must be instructed to reduce speed to 250 KIAS by CLOWD
(4) Handoffs:
All aircraft shall be handed off, and communications transferred to PSP APP prior to crossing the lateral limits of the PSP APP airspace.
|  |