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

Departures (19)

Callsign Dep Arr Status ETA
MSR14 KLAX HECA Enroute 0755
JAL15 KLAX RJTT Enroute 1146
DAL100 KLAX FACT Enroute 1332
HWL2401 KLAX KBOS Enroute 0726
MXY705 KLAX KORF Enroute 0756
EIN9MY KLAX EIDW Enroute 1246
DAL443 KLAX PHNL Enroute 1144
QFA94 KLAX YMML Enroute 0336
AAL1998 KLAX KORD Enroute 0637
SWA1320 KLAX PHNL Enroute 1410
UAE2806 KLAX OMDB Enroute 1815
AAL12 KLAX KBOS Enroute 1002
FFT2857 KLAX KSFO Enroute 1818
UAL436 KLAX KSFO Enroute 1657
MSR984 KLAX HECA Enroute 0845
GTI732 KLAX VHHH Enroute 1600
BAW219 KLAX EGLL Enroute 1407
SWA2415 KLAX KSLC Enroute 1600
SKW6190 KLAX KLAS Enroute 2016

Arrivals (10)

Callsign Dep Arr Status ETA
AAL82 NZAA KLAX Enroute 1015
THT2 NTAA KLAX Enroute 1037
AAL500 KORD KLAX Enroute 1547
AAL598 KORD KLAX Enroute 1532
SWA1642 KSJC KLAX Enroute 1717
FFT4856 KSAN KLAX Enroute 0755
DLH452 EDDM KLAX Departing
DAL4077 KPHX KLAX Enroute 1601
SKW8245 KSGU KLAX Enroute 1701
AAL72 YSSY KLAX Enroute 1147

Los Angeles (SoCal) 29

Arrivals (1)

Callsign Dep Arr Status ETA
TXG901 KMIA KSBD Enroute 1458

Empire (SoCal) 1

Departures (6)

Callsign Dep Arr Status ETA
QQE912 KSAN ZGSZ Enroute 1330
DAL142 KSAN KPDX Enroute 1920
FFT4856 KSAN KLAX Enroute 0755
SWA209 KSAN KOAK Enroute 1600
FFT1257 KSAN KLAS Enroute 1517
SWA4293 KSAN KOAK Enroute 2029

Arrivals (5)

Callsign Dep Arr Status ETA
VCV315 MMMX KSAN Enroute 1314
DAL105 MMMX KSAN Enroute 1333
AAL454 KPDX KSAN Enroute 1605
BAW272 EGLL KSAN Departing
N501A KSAN Enroute 1600

San Diego (SoCal) 11

Arrivals (1)

Callsign Dep Arr Status ETA
SWA3640 KSJC KSNA Enroute 1022

Coast (SoCal) 1

Departures (1)

Callsign Dep Arr Status ETA
N5411T KVNY KPSP Enroute 1600

Burbank (SoCal) 1

Arrivals (1)

Callsign Dep Arr Status ETA
N5411T KVNY KPSP Enroute 1600

Palm Springs (SoCal) 1

Departures (4)

Callsign Dep Arr Status ETA
KLM636 KLAS EHAM Enroute 0733
KLM637 KLAS EHAM Enroute 0729
BAW4LV KLAS EGLL Enroute 1119
SWA1969 KLAS KAUS Arriving

Arrivals (6)

Callsign Dep Arr Status ETA
TFF488 MMUN KLAS Enroute 1600
AAY3180 KATW KLAS Enroute 1817
UAL408 KDEN KLAS Enroute 1600
FFT1257 KSAN KLAS Enroute 1517
OTA800 EDDS KLAS Departing
SKW6190 KLAX KLAS Enroute 2016

Las Vegas 10

Departures (1)

Callsign Dep Arr Status ETA
SKW8245 KSGU KLAX Enroute 1701

Other 1
  • Flights To/From ZLA: 55
  • Flights in ZLA Airspace: 17
  • Controller Schedule

    September 3rd, 2026

    Los Angeles Center
    Jerome Sudhakar

    Session with AT

    1530 - 1700 PDT / 2230 - 0000 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.