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

Departures (12)

Callsign Dep Arr Status ETA
DLH455 KLAX EDDM Enroute 1854
CSG5222 KLAX ZSPD Enroute 2137
DAL005 KLAX EDDL Enroute 2154
DAL749 KLAX KTPA Enroute 1652
UAE402 KLAX OMDB Enroute 0508
DAL8178 KLAX YSSY Enroute 0215
THY03 KLAX KJFK Enroute 1748
DAL2010 KLAX KLAS Enroute 1600
ASA223 KLAX PHNL Enroute 0100
DAL9915 KLAX KJFK Enroute 2003
FDX135 KLAX KJFK Enroute 2006
DAL2253 KLAX KLAS Enroute 0649

Arrivals (12)

Callsign Dep Arr Status ETA
AFR026 LFPG KLAX Enroute 0246
ANZ6 NZAA KLAX Enroute 2236
UAL38 RJTT KLAX Enroute 0329
THT8 NTAA KLAX Enroute 2203
UAL2431 KIAH KLAX Enroute 0635
DAL40 YSSY KLAX Enroute 2224
SWA2103 KDEN KLAX Enroute 1615
DLH456 EDDF KLAX Enroute 0808
AAL43 YBBN KLAX Enroute 1610
QFA21 YSSY KLAX Enroute 0024
EVA16 RCTP KLAX Enroute 0623
N2ZH KSPK KHHR Enroute 1602

Los Angeles (SoCal) 24

Departures (1)

Callsign Dep Arr Status ETA
UAL2363 KONT KSFO Enroute 0314

Empire (SoCal) 1

Departures (1)

Callsign Dep Arr Status ETA
SPK37 KSAN PHOG Enroute 2358

Arrivals (2)

Callsign Dep Arr Status ETA
SWA4458 KBWI KSAN Enroute 0309
DAL864 PHNL KSAN Enroute 0110

San Diego (SoCal) 3

Departures (1)

Callsign Dep Arr Status ETA
N4213X KLGB KHAF Enroute 1600

Arrivals (1)

Callsign Dep Arr Status ETA
FFL67 KASE KLGB Enroute 0808

Coast (SoCal) 2

Arrivals (1)

Callsign Dep Arr Status ETA
ASA692 KSEA KPSP Enroute 1600

Palm Springs (SoCal) 1

Departures (2)

Callsign Dep Arr Status ETA
EDW3 KLAS LSZH Enroute 2057
N851TB KLAS KJAC Enroute 1010

Arrivals (4)

Callsign Dep Arr Status ETA
DAL2010 KLAX KLAS Enroute 1600
SWA3356 KPHX KLAS Enroute 0711
SWA4818 KPDX KLAS Enroute 0834
DAL2253 KLAX KLAS Enroute 0649

Las Vegas 6

Arrivals (2)

Callsign Dep Arr Status ETA
RRR4104 KPSM KSBP Enroute 0452
AAL125 KEGE KSBA Enroute 1600

Santa Barbara 2

Arrivals (1)

Callsign Dep Arr Status ETA
TWA123 KPHX KNYL Enroute 1600

Yuma 1
  • Flights To/From ZLA: 40
  • Flights in ZLA Airspace: 11
  • Controller Schedule

    January 20th, 2026

    Socal Approach (West)
    Yahya Awais

    Session with SR

    1630 - 1800 PST / 0030 - 0200 Zulu

    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.