ZLA Logo
Who's Online
Online Controllers Flights to/from ZLA

Departures (13)

Callsign Dep Arr Status ETA
ANA125 KLAX RJTT Enroute 1455
KAL012 KLAX RKSI Enroute 1638
DLH45R KLAX EDDM Arriving
CPA883 KLAX VHHH Enroute 2115
JAL05 KLAX RJTT Enroute 2257
DAL2123 KLAX LROP Enroute 1836
ACA553 KLAX CYVR Enroute 0205
FDX77 KLAX PHNL Enroute 2313
BAW6013 KLAX EGLL Enroute 1453
BOX585 KLAX KCVG Enroute 1716
JBU67 KLAX KJFK Enroute 1807
KLM15 KLAX EHAM Enroute 1458
PAA831 KLAX RJTT Enroute 1748

Arrivals (9)

Callsign Dep Arr Status ETA
DAL40 YSSY KLAX Enroute 2133
BAW21B EGLL KLAX Enroute 0500
VIR7B EGLL KLAX Enroute 0352
SAS931 EKCH KLAX Enroute 0533
CPA882 VHHH KLAX Enroute 0359
SWA4445 KSJC KLAX Enroute 1600
SWA1423 KLAS KLAX Enroute 0155
BOX582 VHHH KLAX Departing
SIA12 RJAA KLAX Enroute 0112

Los Angeles (SoCal) 22

Departures (4)

Callsign Dep Arr Status ETA
BXS1836 KSAN PHNL Enroute 2126
KLM3360 KSAN HAAB Enroute 2102
AAL1946 KSAN KDFW Enroute 1600
UAL1457 KSAN KORD Enroute 1600

Arrivals (3)

Callsign Dep Arr Status ETA
BAW82P EGLL KSAN Enroute 0246
AWE2362 KDFW KSAN Enroute 0046
TSC154 SBBR KSAN Departing

San Diego (SoCal) 7

Departures (2)

Callsign Dep Arr Status ETA
SWA1987 KLGB PHNL Enroute 2247
DAL1116 KLGB KSLC Enroute 1600

Arrivals (1)

Callsign Dep Arr Status ETA
AAL8934 KCRP KSNA Enroute 2346

Coast (SoCal) 3

Departures (1)

Callsign Dep Arr Status ETA
N750XL KVNY KAUO Enroute 1723

Burbank (SoCal) 1

Arrivals (1)

Callsign Dep Arr Status ETA
N500WN KHND KTRM Enroute 0216

Palm Springs (SoCal) 1

Departures (5)

Callsign Dep Arr Status ETA
SWA1881 KLAS PHNL Enroute 2216
DAL2674 KLAS KSLC Enroute 0130
N500WN KHND KTRM Enroute 0216
SWA1423 KLAS KLAX Enroute 0155
FDX3072 KLAS KMEM Enroute 1759

Arrivals (2)

Callsign Dep Arr Status ETA
DAL466 KATL KLAS Departing
ROU1701 CYYZ KLAS Departing

Las Vegas 7
  • Flights To/From ZLA: 41
  • Flights in ZLA Airspace: 9
  • Controller Schedule

    April 8th, 2026

    Socal Approach (Combined)
    Matthew Goldsmith

    Session with ER

    1830 - 2000 PDT / 0130 - 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