ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (13)

Callsign Dep Arr Status ETA
CES586 KLAX ZSPD Enroute 1740
CPA41 KLAX VHHH Enroute 1913
CES567 KLAX ZSPD Enroute 1755
UAL260 KLAX EDDF Enroute 1548
AAL136 KLAX EGLL Enroute 1506
AAL31 KLAX PHNL Enroute 2314
UAL1158 KLAX PHNL Enroute 2111
SWA3538 KLAX KDEN Enroute 0016
AAL36T KLAX EGLL Arriving
SWA8601 KLAX KSMF Enroute 0003
AAL1254 KLAX KLAS Enroute 0538
VIR8Y KLAX EGLL Enroute 1433
FFT3156 KLAX KDEN Enroute 1600

Arrivals (16)

Callsign Dep Arr Status ETA
DAL64 NZAA KLAX Enroute 1949
DAL242 KATL KLAX Enroute 0028
DLH456 EDDF KLAX Enroute 0318
QFA11 YSSY KLAX Enroute 2021
SWR40 LSZH KLAX Enroute 0528
AAL137 EGLL KLAX Enroute 0517
AAL1660 KDFW KLAX Enroute 1835
APZ103 RKSI KLAX Enroute 0209
ANZ6 NZAA KLAX Enroute 1920
TWA761 EGLL KLAX Departing
UAL1363 KORD KLAX Departing
DAL8 RJTT KLAX Departing
DAL553 KLAS KLAX Enroute 1600
SWA1297 KSFO KLAX Enroute 1600
BAW21B EGLL KLAX Departing
DHK053 ZSPD KLAX Departing

Los Angeles (SoCal) 29

Departures (2)

Callsign Dep Arr Status ETA
CST84 KONT PHNL Enroute 2036
UAL2363 KONT KSFO Enroute 1600

Empire (SoCal) 2

Departures (2)

Callsign Dep Arr Status ETA
BAW9SW KSAN EGLL Arriving
FDX158 KSAN KMEM Enroute 1755

San Diego (SoCal) 2

Departures (1)

Callsign Dep Arr Status ETA
DCA5H KPSP KEGE Enroute 1600

Palm Springs (SoCal) 1

Departures (5)

Callsign Dep Arr Status ETA
UAL406 KLAS KEWR Enroute 1459
DAL1539 KLAS KMSP Enroute 2252
DAL553 KLAS KLAX Enroute 1600
JANET59 KLAS KXTA Enroute 1716
BON966 KLAS VHHH Enroute 1600

Arrivals (3)

Callsign Dep Arr Status ETA
FFT4144 KSMF KLAS Enroute 0801
CPA172 PANC KLAS Enroute 0233
AAL1254 KLAX KLAS Enroute 0538

Las Vegas 8

Arrivals (3)

Callsign Dep Arr Status ETA
N226SB KGCN KGCN Enroute 1600
N777A KGCN KGCN Enroute 1600
N200JT KMSN KIFP Departing

Other 3
  • Flights To/From ZLA: 45
  • Flights in ZLA Airspace: 14
  • Controller Schedule

    January 21st, 2026

    No sessions found for selected date

    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