ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (11)

Callsign Dep Arr Status ETA
SAS932 KLAX EKCH Arriving
DAL93 KLAX YBBN Enroute 1223
KAL012 KLAX RKSI Enroute 1236
SJX1 KLAX RCTP Enroute 1328
DLH457 KLAX EDDF Enroute 1322
LPE2479 KLAX SPJC Enroute 2034
UAL1647 KLAX KDEN Enroute 1600
BAW4E KLAX EGLL Arriving
UAL1597 KLAX KSFO Enroute 1600
DAL224 KLAX OMDB Enroute 1225
AAL39EF KLAX CYUL Enroute 1600

Arrivals (13)

Callsign Dep Arr Status ETA
FFP76R EPWA KLAX Enroute 0609
AAL72 YSSY KLAX Enroute 1837
QTR9V OTHH KLAX Enroute 0142
AAL700 YSSY KLAX Enroute 1816
QFA11 YSSY KLAX Enroute 1806
UPS5255 KMIA KLAX Enroute 2021
DAL40 YSSY KLAX Enroute 1838
DAL42 YSSY KLAX Enroute 1747
AAL135 EGLL KLAX Enroute 0137
AFR22J LFPG KLAX Enroute 0351
AFR72PY LFPG KLAX Departing
SIA38 WSSS KLAX Departing
AAL171 KJFK KLAX Departing

Los Angeles (SoCal) 24

Departures (1)

Callsign Dep Arr Status ETA
PCM8983 KONT KBFL Enroute 1600

Empire (SoCal) 1

Departures (1)

Callsign Dep Arr Status ETA
WAT3018 KSAN KSEA Enroute 0109

Arrivals (3)

Callsign Dep Arr Status ETA
DLH466 EDDM KSAN Enroute 1944
SWA3274 KLAS KSAN Enroute 2010
JAL66 RJAA KSAN Departing

San Diego (SoCal) 4

Arrivals (1)

Callsign Dep Arr Status ETA
SWA4368 KSMF KLGB Enroute 1600

Coast (SoCal) 1

Arrivals (1)

Callsign Dep Arr Status ETA
SKW2411 KDEN KBUR Enroute 2119

Burbank (SoCal) 1

Departures (2)

Callsign Dep Arr Status ETA
DAL220 KLAS KPHX Enroute 0130
SWA3274 KLAS KSAN Enroute 2010

Arrivals (3)

Callsign Dep Arr Status ETA
DAL777 KATL KLAS Enroute 2143
SWA4816 KGEG KLAS Enroute 2033
AAL2742 KORD KLAS Enroute 2342

Las Vegas 5

Departures (1)

Callsign Dep Arr Status ETA
N4LN KSBA KHSA Enroute 2126

Santa Barbara 1

Arrivals (1)

Callsign Dep Arr Status ETA
PCM8983 KONT KBFL Enroute 1600

Bakersfield 1
  • Flights To/From ZLA: 38
  • Flights in ZLA Airspace: 10
  • Controller Schedule

    December 29th, 2025

    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.