ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (12)

Callsign Dep Arr Status ETA
QFA12 KLAX YSSY Enroute 1609
DAL87 KLAX VHHH Enroute 2150
DAL24 KLAX VHHH Enroute 2222
UNI3085 KLAX YSSY Enroute 0105
CES0729 KLAX ZSPD Enroute 0116
DAL5276 KLAX KJAC Enroute 0406
DAL1772 KLAX PHOG Enroute 0045
SWA2542 KLAX KSMF Enroute 0458
UAE9GR KLAX OMDB Enroute 2109
DAL392 KLAX KDCA Enroute 1017
DAL639 KLAX KBOS Enroute 1600
UAL1416 KLAX KIAH Enroute 1600

Arrivals (17)

Callsign Dep Arr Status ETA
UAE83M OMDB KLAX Enroute 0054
DLH452 EDDM KLAX Enroute 0340
JBU1001 KFLL KLAX Enroute 0202
SWA1100 KBWI KLAX Enroute 0156
DLH456 EDDF KLAX Enroute 0424
SWA1267 PHNL KLAX Enroute 2324
DAL673 KATL KLAX Enroute 0246
UAL2445 KEWR KLAX Enroute 0247
DLH177 LEPA KLAX Enroute 1600
ACA785 CYYZ KLAX Enroute 0317
ASA1354 MGGT KLAX Enroute 2358
NOO347 KDFW KLAX Enroute 0332
DAL2933 LIMC KLAX Enroute 0222
AAL2497 KDFW KLAX Departing
CFG80 EDDF KLAX Enroute 0127
NOO859 KDFW KLAX Enroute 0344
DAL2512 KSEA KLAX Enroute 1600

Los Angeles (SoCal) 29

Departures (1)

Callsign Dep Arr Status ETA
FDX1215 KONT KMEM Enroute 1747

Empire (SoCal) 1

Departures (4)

Callsign Dep Arr Status ETA
AAY1594 KSAN KTEX Enroute 0057
ASA399 KSAN KPDX Enroute 1600
UAL2124 KSAN KIAD Enroute 0426
QXE2134 KSAN KEUG Enroute 1600

Arrivals (3)

Callsign Dep Arr Status ETA
BAW273 EGLL KSAN Enroute 0607
AAL8215 MKJS KSAN Enroute 0111
N961BS KSDL KCRQ Enroute 1600

San Diego (SoCal) 7

Arrivals (1)

Callsign Dep Arr Status ETA
DAL329 KATL KSNA Enroute 0209

Coast (SoCal) 1

Departures (5)

Callsign Dep Arr Status ETA
QFA56 KLAS YSSY Enroute 2202
WAT6055 KLAS KATL Enroute 1558
KAL006 KLAS RKSI Enroute 0410
DAL2520 KLAS KATL Enroute 1825
JANET27 KLAS KXTA Enroute 1600

Arrivals (7)

Callsign Dep Arr Status ETA
SWA2073 KDEN KLAS Enroute 0635
SWA365 KSEA KLAS Enroute 0220
AAL1592 KORD KLAS Enroute 0208
SWA1702 KSAT KLAS Enroute 0158
AFR56U LFPG KLAS Enroute 0840
JANET55 XSD KLAS Enroute 0241
AAY86 KMRY KLAS Enroute 0350

Las Vegas 12

Departures (1)

Callsign Dep Arr Status ETA
RRR4141 KSBP KOSH Enroute 1806

Santa Barbara 1

Departures (1)

Callsign Dep Arr Status ETA
REAPR10 KEDW KDYS Arriving

Edwards 1

Arrivals (1)

Callsign Dep Arr Status ETA
N116AH KEED KEED Enroute 0653

Other 1
  • Flights To/From ZLA: 53
  • Flights in ZLA Airspace: 16
  • Controller Schedule

    November 2nd, 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.