ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (10)

Callsign Dep Arr Status ETA
DAL39 KLAX ZSPD Enroute 1519
AAL136 KLAX EGLL Enroute 1311
BOX473 KLAX EDDF Enroute 1531
ITY621 KLAX LIRF Enroute 1808
ANZ5 KLAX NZAA Enroute 1934
CAL5137 KLAX RCTP Enroute 2003
AAL27 KLAX RJTT Enroute 1609
UAL185 KLAX KSEA Enroute 1036
CSN242 KLAX KLAS Enroute 2117
AAL963 KLAX KDFW Enroute 1424

Arrivals (10)

Callsign Dep Arr Status ETA
AAL135 EGLL KLAX Enroute 0026
JAL16 RJTT KLAX Enroute 2156
BEL063 EBBR KLAX Enroute 0147
CFG080 EDDF KLAX Enroute 0500
DLH452 EDDM KLAX Enroute 0709
FDX1026 KEWR KLAX Enroute 2325
KLM52E MMGL KLAX Enroute 2025
DAL393 KCVG KLAX Enroute 0026
DAL1824 MMSD KLAX Enroute 2022
AAL1399 KLAS KLAX Enroute 2246

Los Angeles (SoCal) 20

Departures (1)

Callsign Dep Arr Status ETA
SJX9 KONT RCTP Enroute 1347

Empire (SoCal) 1

Departures (3)

Callsign Dep Arr Status ETA
SWA1887 KSAN KELP Enroute 2022
AAL654 KSAN KPHX Enroute 2129
BAW272 KSAN EGLL Enroute 1227

Arrivals (4)

Callsign Dep Arr Status ETA
AAY312 KPDX KSAN Enroute 1600
JBU189 KJFK KSAN Enroute 2221
VCP860 KPWA KMYF Enroute 2210
DLH5Y EDDM KSAN Enroute 1748

San Diego (SoCal) 7

Departures (1)

Callsign Dep Arr Status ETA
DAL952 KSNA KSEA Enroute 1600

Arrivals (1)

Callsign Dep Arr Status ETA
SWA1092 KSLC KLGB Enroute 1600

Coast (SoCal) 2

Arrivals (1)

Callsign Dep Arr Status ETA
TKY531 KDTW KPSP Enroute 2208

Palm Springs (SoCal) 1

Departures (2)

Callsign Dep Arr Status ETA
DAL28 KLAS KSEA Enroute 1600
AAL1399 KLAS KLAX Enroute 2246

Arrivals (1)

Callsign Dep Arr Status ETA
CSN242 KLAX KLAS Enroute 2117

Las Vegas 3

Departures (1)

Callsign Dep Arr Status ETA
N77147 KPMD KDVT Enroute 1934

Palmdale 1
  • Flights To/From ZLA: 35
  • Flights in ZLA Airspace: 6
  • Controller Schedule

    June 17th, 2026

    Socal Approach (West)
    William Collister

    Session with AT

    1530 - 1630 PDT / 2230 - 2330 Zulu

    Socal Approach (Combined)
    Jerome Sudhakar

    Session with LL

    1630 - 1800 PDT / 2330 - 0100 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