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

Departures (7)

Callsign Dep Arr Status ETA
DAL89 KLAX VHHH Enroute 0840
SWR41T KLAX LSZH Enroute 0816
SWR41G KLAX LSZH Enroute 0827
BAW4E KLAX EGLL Enroute 1055
DLH451 KLAX EDDF Enroute 1549
ACA551 KLAX CYVR Enroute 1600
DAL65 KLAX NZAA Enroute 1600

Arrivals (10)

Callsign Dep Arr Status ETA
SIA38 WSSS KLAX Enroute 1803
DAL88 VHHH KLAX Enroute 1837
SVQ6 PANC KLAX Enroute 1513
UAL753 KDEN KLAX Enroute 2111
DAL9 RJTT KLAX Enroute 1744
FDX9900 KELP KLAX Enroute 1414
QFA90 YMML KLAX Enroute 1348
AAL72 YSSY KLAX Enroute 1318
UAL4078 KIAD KLAX Enroute 0749
AVA1 KLAX KLAX Enroute 1600

Los Angeles (SoCal) 17

Departures (1)

Callsign Dep Arr Status ETA
EAL3094 KRIV KMDT Enroute 0636

Empire (SoCal) 1

Departures (6)

Callsign Dep Arr Status ETA
ASA1449 KSAN KSJC Enroute 0802
SWA2511 KSAN KBNA Enroute 1600
N2KH KSAN RJBB Enroute 1506
N770XJ KSAN PHNL Enroute 1336
N817Z KSAN Enroute 1600
JTC445 KSAN KCYS Enroute 1554

Arrivals (2)

Callsign Dep Arr Status ETA
SWA1738 KPHX KSAN Enroute 1605
DAL685 KJFK KSAN Enroute 1614

San Diego (SoCal) 8

Arrivals (2)

Callsign Dep Arr Status ETA
JBU101 KGCN KLGB Enroute 1720
N444PG NONE KSNA Enroute 2258

Coast (SoCal) 2

Arrivals (1)

Callsign Dep Arr Status ETA
AAL1884 KPHX KPSP Enroute 2252

Palm Springs (SoCal) 1

Departures (2)

Callsign Dep Arr Status ETA
BAW4LV KLAS EGLL Enroute 1803
CFG641 KLAS EDDF Enroute 1600

Arrivals (1)

Callsign Dep Arr Status ETA
DAL659 KATL KLAS Enroute 1926

Las Vegas 3

Departures (1)

Callsign Dep Arr Status ETA
REACH17 KLSV EGUL Enroute 1322

Nellis 1

Departures (1)

Callsign Dep Arr Status ETA
JBU101 KGCN KLGB Enroute 1720

Other 1
  • Flights To/From ZLA: 34
  • Flights in ZLA Airspace: 17
  • Controller Schedule

    September 1st, 2026

    No sessions found for selected date

    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.