ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (14)

Callsign Dep Arr Status ETA
DAL39A KLAX ZSPD Enroute 1600
SIA35 KLAX WSSS Enroute 1508
DAL1014 KLAX YPPH Enroute 2116
UAL6517 KLAX VHHH Enroute 2058
EVA5 KLAX RCTP Arriving
BOX585A KLAX KCVG Enroute 1503
ACA774 KLAX CYUL Enroute 1736
CES0729 KLAX ZSPD Enroute 0156
AAL73 KLAX YSSY Enroute 0309
VRG1026 KLAX PHNL Enroute 2311
DAL1421 KLAX KSFO Enroute 0040
UAL2742 KLAX KDEN Enroute 0238
VIR8Y KLAX EGLL Enroute 1348
AAL2129 KLAX KMIA Enroute 1600

Arrivals (13)

Callsign Dep Arr Status ETA
GEC8405 ZSPD KLAX Enroute 0809
CFG080 EDDF KLAX Enroute 0115
KLM601 EHAM KLAX Enroute 0410
ANA126 RJTT KLAX Enroute 2351
UAL1636 PHNL KLAX Enroute 1600
JBU323 KJFK KLAX Enroute 0227
UVT370 PHNL KLAX Enroute 2259
QTR90B EGLL KLAX Departing
UAL1737 KIAH KLAX Enroute 0041
AAL117 KJFK KLAX Departing
BAW7D EGLL KLAX Departing
DAL888 KMSY KLAX Departing
DAL883 KDTW KLAX Enroute 0001

Los Angeles (SoCal) 27

Departures (3)

Callsign Dep Arr Status ETA
WAT3558 KSAN SAEZ Enroute 1745
ITY7637 KSAN KLAS Enroute 0354
AAL405 KSAN SAEZ Enroute 2225

Arrivals (3)

Callsign Dep Arr Status ETA
AAL8471 SKBO KSAN Enroute 2150
WAT2918 KOAK KSAN Enroute 2309
DAL2508 KSEA KSAN Enroute 2052

San Diego (SoCal) 6

Arrivals (2)

Callsign Dep Arr Status ETA
UAL543 KEWR KSNA Enroute 0002
DAL556 KATL KSNA Enroute 0102

Coast (SoCal) 2

Arrivals (1)

Callsign Dep Arr Status ETA
SWA2824 KLAS KBUR Enroute 1600

Burbank (SoCal) 1

Departures (1)

Callsign Dep Arr Status ETA
ROU1769 KPSP CYVR Enroute 1011

Palm Springs (SoCal) 1

Departures (2)

Callsign Dep Arr Status ETA
N680GR KLAS KTPA Enroute 1600
SWA2824 KLAS KBUR Enroute 1600

Arrivals (5)

Callsign Dep Arr Status ETA
AIC1 SPJC KLAS Enroute 2234
UAL2099 KIAD KLAS Enroute 2346
BAW2MW EGLL KLAS Enroute 0547
DAL777 KATL KLAS Enroute 0208
ITY7637 KSAN KLAS Enroute 0354

Las Vegas 7
  • Flights To/From ZLA: 44
  • Flights in ZLA Airspace: 11
  • Controller Schedule

    November 9th, 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