ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (11)

Callsign Dep Arr Status ETA
CCA984 KLAX ZBAA Enroute 1743
KAL012 KLAX RKSI Enroute 1748
AAL9811 KLAX VHHH Enroute 1956
SWA1320 KLAX PHNL Enroute 1947
UAL21 KLAX PHNL Enroute 1930
AXX256 KLAX PHNL Enroute 2055
UAE149 KLAX VHHH Enroute 0157
DLH455 KLAX EDDM Enroute 1420
AAL2024 KLAX KDFW Enroute 1436
ASA2662 KLAX KSFO Enroute 0802
SAS932 KLAX EKCH Enroute 2226

Arrivals (16)

Callsign Dep Arr Status ETA
QTR90B OTHH KLAX Enroute 0814
SJX2 RCTP KLAX Enroute 2308
JAL16 RJTT KLAX Enroute 2230
AAL135 EGLL KLAX Enroute 0245
MLP500F LIMC KLAX Enroute 0348
MSR22 HECA KLAX Enroute 0714
EIN9PE EIDW KLAX Enroute 0514
DAL12 YMML KLAX Enroute 1943
DAL800 KFLL KLAX Enroute 2243
FBU47G LFPO KLAX Enroute 0646
EVA190 VHHH KLAX Enroute 0450
CFG080 EDDF KLAX Enroute 0253
UAL1737 KIAH KLAX Enroute 2329
AAR204 RKSI KLAX Departing
DAL8001 KFLL KLAX Departing
PAL420 RPLL KLAX Departing

Los Angeles (SoCal) 27

Arrivals (1)

Callsign Dep Arr Status ETA
SWA672 KHOU KONT Enroute 2236

Empire (SoCal) 1

Departures (1)

Callsign Dep Arr Status ETA
SWA325 KSAN KDEN Enroute 1600

Arrivals (2)

Callsign Dep Arr Status ETA
MXY706 KJAX KSAN Departing
BAW265 EGLL KSAN Departing

San Diego (SoCal) 3

Departures (1)

Callsign Dep Arr Status ETA
TPC25 KSNA KHND Enroute 0835

Coast (SoCal) 1

Departures (1)

Callsign Dep Arr Status ETA
WJA1723 KPSP CYVR Enroute 0319

Palm Springs (SoCal) 1

Departures (2)

Callsign Dep Arr Status ETA
ASA366 KLAS KSEA Enroute 0041
UAL406 KLAS KEWR Enroute 1600

Arrivals (4)

Callsign Dep Arr Status ETA
SWA4040 KDAL KLAS Enroute 1600
AMX486 MMMY KLAS Enroute 0121
TPC25 KSNA KHND Enroute 0835
KLM635 EHAM KLAS Departing

Las Vegas 6
  • Flights To/From ZLA: 39
  • Flights in ZLA Airspace: 9
  • Controller Schedule

    August 15th, 2026

    Socal Approach (West)
    David Rothmuller

    Session with RR

    1100 - 1230 PDT / 1800 - 1930 Zulu

    Socal Approach (Combined)
    Jacob Ball

    Session with LL

    1730 - 1900 PDT / 0030 - 0200 Zulu

    Yuma Approach (NYL)

    DATE VERSION CONTACT
    2024-06-20 1.10 Facility Advisory Board
    1. PURPOSE.
    This Standard Operating Procedure (SOP) outlines the procedures to be used by controllers working Yuma Approach to ensure that arrival flows are handled in as efficient and timely a manner as possible.

    2. ROLES AND RESPONSIBILITIES.
    The Office of Primary Responsibility (OPR) for this SOP is the ZLA Senior Staff. This SOP was originally signed by Chris Kelly, ZLA Training Administrator, and Ethan Bernstein, ZLA Air Traffic Manager on April 13, 2015. This SOP shall be maintained, revised, updated or cancelled by the ZLA Senior Staff and Facility Engineering Team. Any suggestions for modification/amendment to this SOP should be sent to the OPR for review.

    3. DISTRIBUTION.
    This SOP is intended for use by controllers staffing Yuma Approach.

    4. BACKGROUND.
    This SOP will be the primary outline of Yuma Approach procedures

    5. REQUIREMENTS.
    1. Frequencies
      1. Yuma Approach 124.70
      2. Yuma Departure 125.55
      3. Yuma Tower 119.30
      4. Yuma Ground 121.90
      5. Yuma Clearance Delivery 118.00
    2. Airspace
      1. Yuma Approach owns the airspace as shown on the RAPCON graphic from SFC-FL230
    3. Special Instructions
      1. KNYL Arrivals
        1. Arrivals from the west will be received from ZLA Sector 31 routed via IPL V66 BZA crossing ARGUS at or below 14000’
        2. Arrivals from the northeast will be received from ZAB Sector 42 routed via JUDTH V66 BZA crossing JUDTH at or below 14000’
        3. Arrivals from the north will be received from ZLA Sector 60 routed via BLH V135 BZA crossing BLH at or below 14000’
      2. KNYL Departures
        1. Initial climb in Yuma Approach airspace is 5000’
        2. Once airborne, Yuma Departure should instruct departures to climb to FL230 or their requested cruise altitude, whichever is lower
        3. All departures must be monitored closely while below 14000’ and vectored off the SID if a potential conflict could occur with arriving traffic
        4. ARGUS SID departures will be vectored to join the BZA255 radial and
          V66/458.
        5. HEEDS SID departures will be navigating to BZA then on course to HEEDS via V66/458.This departure is preferred over the ARGUS SID as the departures have more time to climb whilst nearer the airport
        6. MOHAK SID departures will either be direct BZA or on a heading to join the BZA075 radial direct WARTT.
        7. PICACHO SID departures will either be direct BZA or on a heading to join the BZA337 radial and V135.
        8. CARGO SID is for aircraft not carrying external ordinance when radar services are not available therefore will not be assigned by ATC when Yuma Departure is online