ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (8)

Callsign Dep Arr Status ETA
IBE0353 KLAX LEMD Enroute 1054
IBE0352 KLAX LEMD Enroute 1101
UAL60C KLAX EGLL Enroute 1131
UAL839 KLAX YSSY Enroute 1804
GTI3595 KLAX ZHEC Enroute 0312
AAL982 KLAX KJFK Enroute 1116
DAL41 KLAX YSSY Enroute 2012
CFG081 KLAX EDDF Enroute 1810

Arrivals (10)

Callsign Dep Arr Status ETA
AAL1050 RJTT KLAX Enroute 1749
AAL9811 VHHH KLAX Enroute 1851
DHK053 ZSPD KLAX Enroute 2317
MXY780 KPVD KLAX Enroute 2005
CPA625 RJAA KLAX Enroute 2357
AAL295 RJAA KLAX Enroute 2255
AUA51 LOWW KLAX Enroute 0411
AAL848 RJAA KLAX Enroute 0005
CFG080 EDDF KLAX Departing
GEC8320 EDDF KLAX Departing

Los Angeles (SoCal) 18

Departures (3)

Callsign Dep Arr Status ETA
JAL65 KSAN RJAA Enroute 1317
JBU2120 KSAN KBOS Arriving
SSR772 KSAN KBED Enroute 1159

Arrivals (2)

Callsign Dep Arr Status ETA
DLH467 EDDM KSAN Enroute 1907
ACA112 KSEA KSAN Enroute 1600

San Diego (SoCal) 5

Arrivals (1)

Callsign Dep Arr Status ETA
SWA1189 PHNL KLAS Enroute 1813

Las Vegas 1

Arrivals (1)

Callsign Dep Arr Status ETA
LEO507 LIEE KGCN Departing

Other 1
  • Flights To/From ZLA: 25
  • Flights in ZLA Airspace: 2
  • Controller Schedule

    August 13th, 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