ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (13)

Callsign Dep Arr Status ETA
THY180 KLAX LTFM Enroute 2007
DAL041 KLAX YSSY Enroute 1555
PAL103 KLAX RPLL Enroute 1745
CPA883 KLAX VHHH Enroute 1923
DAL301 KLAX UDYZ Enroute 1912
AAL9973 KLAX YSSY Enroute 1957
DAL41 KLAX YSSY Enroute 2003
DAL126 KLAX EPKT Enroute 2011
SAS932 KLAX EKCH Enroute 2011
THY1623 KLAX LTFM Enroute 1805
DAL428 KLAX PHLI Enroute 1233
WZZ172 KLAX KOAK Enroute 1600
DAL1231 KLAX KLAS Enroute 1600

Arrivals (12)

Callsign Dep Arr Status ETA
VRG7111 SBGR KLAX Enroute 2028
VRG9552 SBGR KLAX Enroute 2002
VRG4809 SBGR KLAX Enroute 2034
VRG9550 SBGR KLAX Enroute 2018
VRG0410 SBGR KLAX Enroute 2201
UAE83M OMDB KLAX Enroute 0428
CPA884 VHHH KLAX Enroute 2331
DAL112 KBRO KLAX Enroute 2106
VTK501 EDDF KLAX Enroute 0803
BOX474 EDDF KLAX Enroute 0549
AAL3075 KORD KLAX Enroute 0256
WFL1890 EGLL KLAX Departing

Los Angeles (SoCal) 25

Departures (4)

Callsign Dep Arr Status ETA
BAW264 KSAN EGLL Enroute 1425
NASA958 KMYF PAJN Enroute 0349
SWA3430 KSAN KMDW Enroute 1600
ACA899 KSAN EDDF Enroute 1633

Arrivals (3)

Callsign Dep Arr Status ETA
MXY324 PHNL KSAN Enroute 1600
DLH5Y EDDM KSAN Enroute 0456
SWA3678 KMCO KSAN Departing

San Diego (SoCal) 7

Arrivals (3)

Callsign Dep Arr Status ETA
HIA101 PHOG KLGB Enroute 2003
TFS701 KIDA KLGB Enroute 1600
SKW5405 KSFO KSNA Enroute 2126

Coast (SoCal) 3

Departures (1)

Callsign Dep Arr Status ETA
OAL883 KVNY KPHX Enroute 2226

Burbank (SoCal) 1

Departures (2)

Callsign Dep Arr Status ETA
KAL006 KLAS RKSI Enroute 1852
GEC86G KLAS KMEM Enroute 1336

Arrivals (3)

Callsign Dep Arr Status ETA
BAW271 EGLL KLAS Enroute 2344
ROU1709 CYUL KLAS Enroute 2307
DAL1231 KLAX KLAS Enroute 1600

Las Vegas 5

Departures (1)

Callsign Dep Arr Status ETA
N6BQ KBFL KTEB Enroute 1526

Bakersfield 1

Arrivals (3)

Callsign Dep Arr Status ETA
JBU147 KDFW KGCN Enroute 2132
AAL109 KDFW KGCN Enroute 2114
DAL6924 KDFW KGCN Enroute 2100

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

    September 5th, 2026

    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