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

Departures (16)

Callsign Dep Arr Status ETA
THY12E KLAX LTFM Enroute 1239
VIR24M KLAX EGLL Enroute 0953
AFR25 KLAX LFPG Enroute 1125
UAL703 KLAX KDEN Enroute 1600
UAE9GR KLAX OMDB Enroute 1704
JAL15 KLAX RJTT Enroute 1200
KLM602 KLAX EHAM Enroute 1217
CXA830 KLAX ZSAM Enroute 1116
CES443 KLAX ZSPD Enroute 1321
SIA7403 KLAX PHNL Enroute 1202
DAL782 KLAX KATL Enroute 0658
UAL2056 KLAX KSFO Enroute 1600
DAL291 KLAX RJTT Enroute 0600
CCA984 KLAX ZBAA Enroute 1658
AAL136 KLAX EGLL Enroute 1405
SWA1522 KLAX KLAS Enroute 1536

Arrivals (12)

Callsign Dep Arr Status ETA
CPA883 VHHH KLAX Enroute 1652
PUA2419 KDEN KLAX Enroute 1600
NWA3223 KDEN KLAX Enroute 0025
ANZ615 KDEN KLAX Enroute 1827
FDX232 KRNO KLAX Enroute 1537
AAL552 KSAN KLAX Enroute 2004
DLH450 EDDF KLAX Enroute 1647
UAL1577 KJFK KLAX Departing
DLH456 EDDF KLAX Enroute 1655
UAL1152 PHNL KLAX Enroute 1436
DAL122 PHOG KLAX Enroute 1734
SWA1623 KTUS KLAX Enroute 1600

Los Angeles (SoCal) 28

Departures (1)

Callsign Dep Arr Status ETA
N230VY KONT KELD Enroute 1009

Empire (SoCal) 1

Departures (1)

Callsign Dep Arr Status ETA
AAL552 KSAN KLAX Enroute 2004

Arrivals (3)

Callsign Dep Arr Status ETA
AIC185 OMDB KSAN Enroute 1602
SWA3408 KDEN KSAN Enroute 2336
N26XY KIZA KSEE Enroute 2159

San Diego (SoCal) 4

Departures (3)

Callsign Dep Arr Status ETA
UAL1309 KSNA KSFO Enroute 2352
UAL2124 KSNA KSFO Enroute 0248
SWA3851 KSNA KPHX Enroute 0352

Coast (SoCal) 3

Arrivals (2)

Callsign Dep Arr Status ETA
SWA1050 KLAS KBUR Enroute 2055
SWA1515 KBOI KBUR Enroute 1600

Burbank (SoCal) 2

Departures (1)

Callsign Dep Arr Status ETA
AAL761 KPSP KDFW Arriving

Palm Springs (SoCal) 1

Departures (3)

Callsign Dep Arr Status ETA
UAL2840 KLAS KIAH Enroute 0551
SWA2271 KLAS KDAL Enroute 0715
SWA1050 KLAS KBUR Enroute 2055

Arrivals (2)

Callsign Dep Arr Status ETA
OCN11 EDDF KLAS Enroute 2337
SWA1522 KLAX KLAS Enroute 1536

Las Vegas 5

Departures (1)

Callsign Dep Arr Status ETA
N26XY KIZA KSEE Enroute 2159

Other 1
  • Flights To/From ZLA: 45
  • Flights in ZLA Airspace: 14
  • Controller Schedule

    October 30th, 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.