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

Departures (8)

Callsign Dep Arr Status ETA
CPA883 KLAX VHHH Enroute 1206
AFR27 KLAX LFPG Enroute 1701
GTI6524 KLAX EGNX Enroute 1741
DLH453 KLAX EDDM Enroute 1858
KLM220 KSMO KNFW Enroute 1214
CTN287 KLAX KDEN Enroute 2159
FIN2 KLAX EFHK Enroute 1600
SWA224 KLAX KOAK Enroute 1600

Arrivals (11)

Callsign Dep Arr Status ETA
QTR739 OTHH KLAX Enroute 2224
THY8MT LTFM KLAX Enroute 2305
JAL16 RJTT KLAX Enroute 2123
CAL6 RCTP KLAX Enroute 2302
FIN1 EFHK KLAX Enroute 0630
CKS285 VHHH KLAX Enroute 0132
BAW320 CYVR KLAX Enroute 2243
CPA55 KSEA KLAX Enroute 2243
CPA135 RJTT KLAX Enroute 2011
SAS931 EKCH KLAX Departing
VIR149 RPLL KLAX Departing

Los Angeles (SoCal) 19

Departures (1)

Callsign Dep Arr Status ETA
BAW9SW KSAN EGLL Enroute 2034

Arrivals (1)

Callsign Dep Arr Status ETA
HAL38 PHOG KSAN Enroute 1916

San Diego (SoCal) 2

Arrivals (1)

Callsign Dep Arr Status ETA
N15VJ KFLG KSNA Enroute 0912

Coast (SoCal) 1

Arrivals (1)

Callsign Dep Arr Status ETA
ACL709 KORD KBUR Departing

Burbank (SoCal) 1

Departures (2)

Callsign Dep Arr Status ETA
BAW4LV KLAS EGLL Enroute 2257
BAW274 KLAS EGLL Enroute 0526

Arrivals (2)

Callsign Dep Arr Status ETA
BAW2MW EGLL KLAS Enroute 2357
SWA2586 KICT KLAS Enroute 2335

Las Vegas 4
  • Flights To/From ZLA: 27
  • Flights in ZLA Airspace: 8
  • Controller Schedule

    March 12th, 2025

    No sessions found for selected date

    TEC Routes

    DATE VERSION CONTACT
    2024-05-25 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. Only aircraft departing and arriving within the same TRACON 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.
        2. A prop that files from SMX to ONT at 7,000 is required to use a TEC route
      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.