ZLA Information:
VATSIM Disclaimer
ZLA Home Page
ZLA Crew Roster
ZLA Staff Members
News Archive
Event Archive
Site Credits
Other ARTCC's
ZLA Forum

For Pilots:
VFR/IFR Enroute Maps
Airports & Charts
TEC Routes
SimRoutes.com
Military Airfields
Pilot Certifications
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




SOCAL Approach Empire Area (ONT)

POC: Facility Advisory Board

Date: 2008-07-25

Code: ZLA-300

Version: 1.22

1. PURPOSE:

This Standard Operating Procedure (SOP) outlines the general procedures to be used by controllers working any SOCAL Approach - Empire Area position to ensure safe and efficient handling of air traffic into, out of and through the SOCAL Approach - Empire Area airspace. By specifying standard phraseology and procedure, this SOP provides for the use of common air traffic handling language and operations.

2. ROLES AND RESPONSIBILITIES:

The Office of Primary Responsibility (OPR) for this SOP is ZLA1. This SOP was originally proposed by Josh Hjemvick, SOCAL Approach - Empire Area Lead, and was approved by the Los Angeles Center Chief (ZLA1), David Hendleman on November 23, 2002.

3. DISTRIBUTION:

This SOP is intended for use by controllers staffing any position within SOCAL Approach - Empire Area.

4. BACKGROUND:

This SOP will be the primary outline of SOCAL Approach - Empire Area procedures.

5. REQUIREMENTS:

a. Ontario Runway Use program

1. Ontario International shall normally use runway 26R for departures and RWY26L for arrivals unless the wind is out of the east at 15 knots or greater at which time runway 8L for departures and runway 8R will be used for arrivals.

2. If the visibility decreases to less than 3 statue miles visibility, or if the ceiling decreases to less than 1000' AGL, and if the winds are out of the east at 10 knots or greater, RWY8L will be used for both arrivals and departures.

3. From 2200-0700 local time, Runways 8L/R are used for departures, and Runways 26L/R are used for arrivals due to local noise abatement procedures.

b. Ontario Sector Frequency Use

The following frequencies are designated for use at SOCAL Approach - Empire Area positions:

SOCAL Approach - Empire Area 127.25
Ontario Tower 120.60
Ontario Ground 121.90
Ontario Clearance 118.10
Socal Departure - Empire Area 125.50

c. Ontario Airspace:

SOCAL Approach - Empire Area shall own all airspace at and below 13,000 MSL inside the lateral boundaries as depicted on the TRACON Graphic, with the exception of Los Angeles Feeder Approach airspace. SOCAL Approach - Empire Area shall own all airspace below 10,000 MSL within the lateral boundaries of LAX FE approach control as depicted on the TRACON Graphic. LAX_FE_APP has a permanent pointout for aircraft to descend via the RIIVR1 and SEAVU1 arrivals to LAX. Aircraft on these arrivals will descend below 10,000', into ONT_APP airspace, west of KRAIN or SKOLL intersection. ONT_APP may use Feeder airspace for the HEC.KAYOH4 arrival stream, between 13,000 and 10,000 MSL, if an automated pointout is performed as described in the Pointout SOP.

d. IFR Departures

(1) Altitude Assignment

(a) Initial Climbs off all runways:

ONT TWR shall assign an initial altitude of 5,000' or their requested cruise altitude, whichever is lower to all departing IFR aircraft.

(b) Final climb within Ontario airspace:

When traffic flow permits, all departures shall be climbed to 13000' or their requested cruise altitude, whichever is lower, by ONT DEP/APP and shall be handed off to the respective Center sector.

(2) Routing

(a) If a Departure Route is filed:

Ensure the proper departure route is filed for the destination departure fix. The table below shows departure routes and their respective fixes.

(b) If a Departure Route is not filed:

Request if the pilot has one available for his exit fix. If not, assign a route that closely approximates the DP routing, and advise the next controller of the route assigned.

(c) If the pilot files no DP's on the flight plan:

Route the pilot via the Standard Departure or according to the following table:

Departure Fix Route
DAG
AVE
EHF
POMONA (normal ops)
ONTARIO (LAX and ONT east ops)
DAG
PMD
HASSA (LAX east and ONT west ops)
MZB
TRM
PRADO

e. KAYOH Arrivals into SNA

ONT APP shall instruct KAYOH4 arrivals landing SNA to cross KAYOH at 8,000 and 190kts. KAYOH4 arrivals landing LGB shall be instructed to cross KAYOH at 8,000 and 210kts.

Transfer of communication to SNA APP shall be completed no later than 10nm east of KAYOH intersection.

SNA_APP has control on contact with all KAYOH arrivals.

f. Additional Comments

ONT_APP is affected by permanent and prearranged pointouts; see the pointout SOP for details.



Copyright © laartcc.org 2007, 2008. 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