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

Departures (11)

Callsign Dep Arr Status ETA
DLH457 KLAX EDDF Enroute 1807
BAW28F KLAX EGLL Enroute 1758
DAL2626 KLAX PHNL Enroute 2117
JAL61 KLAX RJAA Enroute 2206
DAL664 KLAX KDTW Enroute 1609
ANZ286 KLAX NZAA Enroute 1439
AAL845 KLAX SBGR Enroute 2121
AAL1763 KLAX KDCA Enroute 2257
SAS38 KLAX EKCH Enroute 1404
AAL1451 KLAX KTUL Enroute 1600
AAL1015 KLAX KLAS Enroute 0243

Arrivals (16)

Callsign Dep Arr Status ETA
AAL137 EGLL KLAX Enroute 0000
CAO8417 ZSPD KLAX Enroute 2214
NBT54 EGKK KLAX Enroute 0240
BAW73 EGKK KLAX Enroute 0156
BAW11H EGKK KLAX Enroute 0348
UAL333 KBOS KLAX Enroute 0202
AFR156 LFPG KLAX Enroute 0236
BAW283 EGLL KLAX Enroute 0550
BAW21B EGLL KLAX Enroute 0547
FDX944 KMEM KLAX Enroute 2254
BAW7D EGLL KLAX Enroute 0520
FDX946 KMEM KLAX Enroute 2351
AAL2364 KORD KLAX Enroute 0208
CES583 ZSPD KLAX Enroute 2204
DAL374 KATL KLAX Departing
AAL5626 KLAS KLAX Enroute 0102

Los Angeles (SoCal) 27

Arrivals (1)

Callsign Dep Arr Status ETA
UPS343 KDFW KONT Departing

Empire (SoCal) 1

Departures (8)

Callsign Dep Arr Status ETA
UPS1457 KSAN OMDB Enroute 1541
ASA709 KSAN KSEA Enroute 0201
DLH2P KSAN EDDM Enroute 2256
SWA2289 KSAN KLAS Enroute 1600
DAL1413 KSAN KSEA Enroute 0051
SWA1646 KSAN PHNL Enroute 2200
N5817F KSAN KBUR Enroute 1038
AAL625 KSAN KPHX Enroute 1600

Arrivals (2)

Callsign Dep Arr Status ETA
UAL2309 KDEN KSAN Enroute 0022
DAL125 KFLL KSAN Enroute 0113

San Diego (SoCal) 10

Departures (1)

Callsign Dep Arr Status ETA
UAL525 KSNA KOAK Enroute 0156

Arrivals (1)

Callsign Dep Arr Status ETA
UAL5960 KDEN KSNA Enroute 0159

Coast (SoCal) 2

Departures (2)

Callsign Dep Arr Status ETA
SWA554 KBUR KSMF Enroute 0001
N540WJ KBUR KSAC Enroute 0634

Arrivals (4)

Callsign Dep Arr Status ETA
SWA2667 KMDW KBUR Enroute 0055
SWA3123 KLAS KBUR Enroute 0355
SWA1894 KLAS KBUR Enroute 0322
N5817F KSAN KBUR Enroute 1038

Burbank (SoCal) 6

Arrivals (2)

Callsign Dep Arr Status ETA
DAL349 KATL KPSP Departing
DAL1668 KSEA KPSP Enroute 1600

Palm Springs (SoCal) 2

Departures (6)

Callsign Dep Arr Status ETA
DLH456 KLAS EDDM Enroute 2053
SWA3123 KLAS KBUR Enroute 0355
SWA1223 KLAS KDAL Enroute 1529
SWA1894 KLAS KBUR Enroute 0322
N388LS KLAS KNYL Enroute 1156
AAL5626 KLAS KLAX Enroute 0102

Arrivals (5)

Callsign Dep Arr Status ETA
TNO1171 KFLL KLAS Enroute 2237
SWA2289 KSAN KLAS Enroute 1600
UAL2316 KDEN KLAS Enroute 0048
UAL314 KDEN KLAS Enroute 0407
AAL1015 KLAX KLAS Enroute 0243

Las Vegas 11

Arrivals (1)

Callsign Dep Arr Status ETA
N388LS KLAS KNYL Enroute 1156

Yuma 1
  • Flights To/From ZLA: 60
  • Flights in ZLA Airspace: 20
  • Controller Schedule

    April 12th, 2026

    Las Vegas Approach
    Nick Stevens

    Session with AK

    1500 - 1630 PDT / 2200 - 2330 Zulu

    Los Angeles Tower
    Kademon Cotton

    OTS with CH

    1530 - 1700 PDT / 2230 - 0000 Zulu

    Socal Approach (Combined)
    Matthew Goldsmith

    Session with ER

    1630 - 1800 PDT / 2330 - 0100 Zulu

    Socal Approach (Combined)
    Satvir Gill

    OTS with AT

    1830 - 2000 PDT / 0130 - 0300 Zulu

    TEC Routes

    DATE VERSION CONTACT
    2025-04-22 1.10 Facility Advisory Board
    1. PURPOSE.
    This document will define TEC routes and explain when to use them for aircraft within ZLA airspace

    2. ROLES AND RESPONSIBILITIES.
    The Office of Primary Responsibility (OPR) for this Mission Statement is the ZLA Senior Staff. This Mission Statement was originally drafted by Tim Roden, ZLA Training Administrator, on March 22, 2017. This document shall be maintained, revised, updated or cancelled by the ZLA Senior Staff or any organization that supersedes, replaces or assumes the Staff responsibilities.

    3. DISTRIBUTION.
    This SOP is intended for use by controllers staffing Positions within SCT, NTD, and SBA TRACONs.

    4. BACKGROUND.
    This document was crafted in order to explain TEC routes, what they are, and how they are utilized within ZLA.

    5. REQUIREMENTS.
    1. The FAA has created a set of routes used for aircraft flying between most Southern California Airports. These are called Tower Enroute Control (TEC) Routes. If a TEC route is available between two airports, aircraft may use the route without filing a flight plan.
    2. ZLA TEC Routes can be found on the ZLA TEC Routes page
    3. TEC Routes are broken down into the following aircraft classes. A list of aircraft classes can be found in 7110.65 Appendix A
      1. J Class - Jet aircraft
      2. M Class - Turboprop aircraft
      3. P Class - Piston aircraft
      4. Q Class - Piston aircraft (slowest of the 4 classifications)
    4. If an aircraft files the coded name of a TEC Route, the full route must be input into the aircraft’s flight plan.
      1. Ex: CSTN41 should be input as V23.OCN.V165.SARGS
      2. Controllers can quickly change an aircraft’s route in one of the following ways:
        1. By typing “.TEC” into the command bar with an aircraft’s flight plan open and the aircraft selected, where “TEC” is the TEC route code
        2. By typing “.DEPARRC” into the command bar with an aircraft’s flight plan open and the aircraft selected, where “DEP” is the three-letter departure airport identifier, “ARR” is the three-letter arrival airport identifier, and “C” is the TEC class. Note that this does not work for Q class aircraft, as P and Q class share the same TEC routes.
    5. IFR Aircraft departing and arriving within the same TRACON, and/or aircraft remaining in the TRACON envrionnment are required to use a TEC route.
      1. For example: 
        1. A jet that files from SBA to SAN at FL210 is not required to use a TEC route (climbes above TRACON)
        2. A prop that files from SMX to ONT at 7,000 is required to use a TEC route (stays within TRACONs)
        3. A Jet that files SAN to VNY at FL200 must be routed via a TEC route (same TRACON, SCT)
      2. Aircraft requesting routes in the low en route structure may be subject to additional delays due to traffic volume. Controllers should suggest the TEC route structure to pilots in such cases.
    6. While some TEC routes include a SID, routes that do not include one require the controller to issue a departure instruction, such as a heading within the DVA, a SID, or an ODP.