ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (10)

Callsign Dep Arr Status ETA
BOX383 KLAX EDDP Enroute 1827
KAL4522 KLAX RJFR Enroute 2254
JBU588 KLAX KBOS Enroute 1840
AFR018 KLAX NTAA Enroute 1920
DAL792 KLAX KMSP Enroute 1649
AAL59 KLAX PHKO Enroute 1600
SWA2475 KLAX KHOU Enroute 1856
N1RS KLAX PHNL Enroute 0028
SKW5066 KLAX KPRC Enroute 0405
UAL1941 KLAX KORD Enroute 1600

Arrivals (15)

Callsign Dep Arr Status ETA
AAL216 SBGR KLAX Enroute 0016
AAL10 EDDM KLAX Enroute 0337
BAW269 EGLL KLAX Enroute 0238
BAW23PG EGLL KLAX Enroute 0257
BAW28K EGLL KLAX Enroute 0415
DAL827 KATL KLAX Enroute 0203
MAS02 WBGG KLAX Enroute 0734
AAL3007 KDFW KLAX Enroute 0144
CPA881 VHHH KLAX Enroute 0549
DAL2119 KMSP KLAX Enroute 0433
HAL810 PHNL KLAX Enroute 0347
UAL2156 KABQ KLAX Enroute 0244
N620ZU KHND KHHR Enroute 0946
AAL2727 KPHX KLAX Enroute 1600
AAL1610 KDFW KLAX Departing

Los Angeles (SoCal) 25

Departures (4)

Callsign Dep Arr Status ETA
JBU920 KSAN KBOS Enroute 2114
UAL5320 KSAN KSFO Enroute 1600
SWA893 KSAN KTUS Enroute 1600
SWA3167 KSAN KABQ Enroute 1702

Arrivals (4)

Callsign Dep Arr Status ETA
BAW273 EGLL KSAN Enroute 0737
SWA16 KDAL KSAN Enroute 0205
SIA32T RKSI KSAN Enroute 0055
AAL559 KPHX KSAN Enroute 1600

San Diego (SoCal) 8

Departures (2)

Callsign Dep Arr Status ETA
N64264 KPSP KSBA Enroute 1600
N787NA KPSP KSBA Enroute 1600

Palm Springs (SoCal) 2

Departures (3)

Callsign Dep Arr Status ETA
EDW3A KLAS LSZH Enroute 2031
AAY478 KLAS KMRY Enroute 0302
N620ZU KHND KHHR Enroute 0946

Arrivals (4)

Callsign Dep Arr Status ETA
AAL1584 KDFW KLAS Enroute 0530
AAY73 KGEG KLAS Enroute 1600
SWA2227 KSEA KLAS Enroute 1600
ASA757 KPDX KLAS Enroute 1600

Las Vegas 7

Departures (1)

Callsign Dep Arr Status ETA
RIP7424 KLSV KAFF Enroute 0421

Nellis 1

Arrivals (2)

Callsign Dep Arr Status ETA
N64264 KPSP KSBA Enroute 1600
N787NA KPSP KSBA Enroute 1600

Santa Barbara 2
  • Flights To/From ZLA: 45
  • Flights in ZLA Airspace: 16
  • Controller Schedule

    October 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.