ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (12)

Callsign Dep Arr Status ETA
DLH453 KLAX EDDM Enroute 1806
DLH236 KLAX EGLL Enroute 1633
DAL65 KLAX NZAA Enroute 1928
BAW47Q KLAX EGLL Enroute 1657
ANZ5 KLAX NZAA Enroute 2147
NKS739 KLAX KSEA Enroute 0651
FDX446 KLAX KMEM Enroute 1635
SHK463 KLAX CYYC Enroute 0133
UAL2237 KLAX KIAH Enroute 1703
DAL3406 KLAX KBOS Enroute 2113
DAL2253 KLAX KLAS Enroute 1600
SAS932 KLAX EKCH Enroute 1538

Arrivals (5)

Callsign Dep Arr Status ETA
BAW283 EGLL KLAX Enroute 0434
SSA995 KMIA KLAX Enroute 0035
AAR204 RKSI KLAX Enroute 0349
TAM8086 SBGR KLAX Enroute 0111
VIR7B EGLL KLAX Enroute 0219

Los Angeles (SoCal) 17

Departures (1)

Callsign Dep Arr Status ETA
SWA2126 KONT KLAS Enroute 0447

Empire (SoCal) 1

Departures (1)

Callsign Dep Arr Status ETA
TPC802 KRNM KSEZ Enroute 1339

Arrivals (2)

Callsign Dep Arr Status ETA
BAW82P EGLL KSAN Enroute 0220
SWA3140 KSJC KSAN Enroute 0037

San Diego (SoCal) 3

Departures (1)

Callsign Dep Arr Status ETA
N511EM KBUR KEGE Enroute 0233

Burbank (SoCal) 1

Departures (3)

Callsign Dep Arr Status ETA
WWA3311 KHND KFLL Enroute 1706
JBU44 KLAS KDFW Enroute 1536
SWA4400 KLAS KSFO Enroute 0245

Arrivals (5)

Callsign Dep Arr Status ETA
AAL2972 KPHL KLAS Enroute 0256
BAW2MW EGLL KLAS Enroute 0641
SWA2126 KONT KLAS Enroute 0447
WJA1448 CYEG KLAS Enroute 0215
DAL2253 KLAX KLAS Enroute 1600

Las Vegas 8

Departures (1)

Callsign Dep Arr Status ETA
SABRE10 KLSV PHNL Enroute 2318

Nellis 1

Departures (1)

Callsign Dep Arr Status ETA
UAL2097 KSBA KSFO Enroute 1054

Santa Barbara 1

Departures (1)

Callsign Dep Arr Status ETA
SAM3117 KEDW KADW Enroute 1831

Arrivals (1)

Callsign Dep Arr Status ETA
AAL3 KMSY KMHV Departing

Edwards 2
  • Flights To/From ZLA: 34
  • Flights in ZLA Airspace: 9
  • Controller Schedule

    February 10th, 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.