ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (10)

Callsign Dep Arr Status ETA
ITY621 KLAX LIRF Enroute 0614
AAL297 KLAX PHNL Enroute 1305
UAL184 KLAX KSAN Enroute 1600
VIR142 KLAX EGLL Enroute 1356
JAL69 KLAX RJBB Enroute 1509
DLH453 KLAX EDDM Enroute 0850
ASA1234 KLAX KDFW Enroute 0734
DLH451 KLAX EDDF Enroute 0544
DAL65 KLAX NZAA Enroute 1818
CFG081 KLAX EDDF Enroute 0601

Arrivals (12)

Callsign Dep Arr Status ETA
ANZ6 NZAA KLAX Enroute 2032
KLM603 EHAM KLAX Enroute 2053
VIR7B EGLL KLAX Enroute 1547
DLH57EL EDDF KLAX Enroute 2221
ANZ6K NZAA KLAX Enroute 0946
DAL1876 MMSD KLAX Enroute 1803
VOI711 MMSD KLAX Enroute 1600
AFR026 LFPG KLAX Enroute 1600
DAL8 RJTT KLAX Enroute 1943
CFG080 EDDF KLAX Enroute 1525
VOI617 MMSD KLAX Enroute 2243
PAL112 RPLL KLAX Enroute 1454

Los Angeles (SoCal) 22

Arrivals (1)

Callsign Dep Arr Status ETA
FDX508 KMEM KONT Enroute 1424

Empire (SoCal) 1

Departures (1)

Callsign Dep Arr Status ETA
DAL8995 KSAN KPDX Enroute 1625

Arrivals (4)

Callsign Dep Arr Status ETA
UAL184 KLAX KSAN Enroute 1600
AAL1011 KDFW KSAN Departing
DAL223 KSFO KSAN Enroute 2034
FDX332 KSFO KSAN Enroute 1332

San Diego (SoCal) 5

Arrivals (1)

Callsign Dep Arr Status ETA
N227WC KSEA KSNA Enroute 1852

Coast (SoCal) 1

Departures (1)

Callsign Dep Arr Status ETA
EJA990 KVNY KTEB Enroute 0801

Burbank (SoCal) 1

Departures (9)

Callsign Dep Arr Status ETA
BAW270 KLAS EGLL Enroute 0706
ASA807 KLAS PHNL Enroute 1230
BAW4LV KLAS EGLL Enroute 1422
UAL2047 KLAS KSFO Enroute 1834
SWA2307 KLAS KPDX Enroute 1705
SWA3176 KLAS KPDX Enroute 1604
MXY658 KLAS KACV Enroute 1600
N798LG KLAS KSDL Enroute 1954
SWA4590 KLAS KMCO Enroute 1600

Arrivals (3)

Callsign Dep Arr Status ETA
FDX12 KAUS KLAS Departing
WAT2055 KAUS KLAS Departing
WAT1072 KAUS KLAS Departing

Las Vegas 12
  • Flights To/From ZLA: 42
  • Flights in ZLA Airspace: 14
  • Controller Schedule

    July 16th, 2026

    Socal Approach (Combined)
    Jacob Ball

    Session with LL

    1900 - 2000 PDT / 0200 - 0300 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