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

Departures (12)

Callsign Dep Arr Status ETA
ANA105 KLAX RJTT Enroute 0424
SWR108 KLAX LSZH Enroute 0918
AAL4 KLAX KJFK Enroute 0455
FDX10 KLAX PHOG Enroute 1005
MSR95EM KLAX HECA Enroute 1634
UAL1584 KLAX YSSY Enroute 1533
EJA823 KLAX KBFI Enroute 0340
SWA3126 KLAX KMCI Enroute 0534
FFT1062 KLAX KPHX Enroute 2215
AAL774 KLAX KPHX Enroute 1318
UAL772 KLAX KMCO Enroute 0414
SWA223 KLAX KHOU Enroute 1044

Arrivals (16)

Callsign Dep Arr Status ETA
IBE03ZB LEMD KLAX Enroute 1410
AFR22 LFPG KLAX Enroute 1551
RAM250 GMMN KLAX Enroute 1951
DAL500 KATL KLAX Enroute 1334
DAL720 KLAS KLAX Enroute 1600
NWA7489 KMSP KLAX Enroute 1354
DAL763 KATL KLAX Enroute 1419
SKW5426 KFAT KLAX Enroute 1600
AAL521 KLAS KLAX Enroute 1600
IBE351 LEMD KLAX Enroute 1600
UAE83M OMDB KLAX Departing
DAL1397 KBOS KLAX Enroute 1501
UAL995 KSFO KLAX Enroute 1600
UAL1506 KSFO KLAX Enroute 0833
KAL017 RKSI KLAX Departing
BAW426 PHNL KLAX Enroute 0720

Los Angeles (SoCal) 28

Arrivals (1)

Callsign Dep Arr Status ETA
SAM36 KBLV KNZY Enroute 0215

San Diego (SoCal) 1

Departures (1)

Callsign Dep Arr Status ETA
N254SB KSNA KLAS Enroute 1704

Arrivals (1)

Callsign Dep Arr Status ETA
ACA7085 KMDW KLGB Enroute 2048

Coast (SoCal) 2

Arrivals (2)

Callsign Dep Arr Status ETA
SWA3840 KSFO KBUR Enroute 1923
UAL626 KSFO KBUR Enroute 2156

Burbank (SoCal) 2

Departures (10)

Callsign Dep Arr Status ETA
MET2105 KLAS KORD Enroute 0415
BAW4LV KLAS EGLL Enroute 1133
DAL720 KLAS KLAX Enroute 1600
UAL706 KLAS KORD Enroute 0553
SWA45 KLAS KDAL Enroute 0512
BAW4LVA KLAS EGLL Enroute 1600
D2112 KLAS KSLC Enroute 0605
AAL521 KLAS KLAX Enroute 1600
DAL1690 KLAS KSLC Enroute 1802
OCN12 KLAS EDDF Enroute 1600

Arrivals (4)

Callsign Dep Arr Status ETA
DAL989 KDEN KLAS Enroute 2336
HIA9757 KGEG KLAS Enroute 0910
N254SB KSNA KLAS Enroute 1704
DAL702 KPHX KLAS Enroute 1838

Las Vegas 14
  • Flights To/From ZLA: 47
  • Flights in ZLA Airspace: 18
  • Controller Schedule

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