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

Departures (13)

Callsign Dep Arr Status ETA
DAL7 KLAX RJTT Enroute 0524
MSR984 KLAX HECA Enroute 1019
KLM274 KLAX EHAM Enroute 0808
QTR738 KLAX OTBD Enroute 1433
AAL1433 KLAX KORD Enroute 0523
UAL2373 KLAX PHKO Enroute 1306
EJA460 KLAX KJAC Enroute 1534
AAL10 KLAX KJFK Enroute 1012
AEJ299 KLAX VTBS Enroute 1912
SWA2456 KLAX KABQ Enroute 0543
AAL876 KLAX KSAN Enroute 1941
SWA2487 KLAX KMCO Enroute 0826
CPA885 KLAX VHHH Enroute 1600

Arrivals (14)

Callsign Dep Arr Status ETA
DAL9512 KDTW KLAX Enroute 1532
DLH452 EDDM KLAX Enroute 2005
UAE83M OMDB KLAX Enroute 2334
CCA071 ZGGG KLAX Enroute 1634
AAL137 EGLL KLAX Enroute 1741
SWA2106 KDEN KLAX Enroute 0353
AAL261 KSEA KLAX Enroute 1440
AAL306 KJFK KLAX Enroute 1552
UAL214 KSFO KLAX Enroute 1848
DAL463 PHOG KLAX Enroute 1248
UAL542 KORD KLAX Enroute 1817
SWA320 KLAS KLAX Enroute 1444
SWA493 KPHX KLAX Enroute 1600
UAL38 RJTT KLAX Departing

Los Angeles (SoCal) 27

Arrivals (1)

Callsign Dep Arr Status ETA
UPS1040 KABQ KONT Enroute 1417

Empire (SoCal) 1

Departures (4)

Callsign Dep Arr Status ETA
SWA957 KSAN KSAT Enroute 0615
AAL1584 KSAN KPHX Enroute 2239
AAL432 KSAN KPHX Enroute 1600
N211TD KSAN Enroute 2028

Arrivals (4)

Callsign Dep Arr Status ETA
AAL1862 KPHX KSAN Enroute 1354
N254SB KLAS KSAN Enroute 1516
AAL876 KLAX KSAN Enroute 1941
PCM7730 KIPL KSAN Enroute 1600

San Diego (SoCal) 8

Arrivals (2)

Callsign Dep Arr Status ETA
SWA2616 KLAS KSNA Enroute 0852
UAL1632 KSFO KSNA Enroute 1600

Coast (SoCal) 2

Departures (2)

Callsign Dep Arr Status ETA
DCM2899 KVNY KDAL Enroute 0637
NDA950 KBUR KCOS Enroute 1417

Burbank (SoCal) 2

Departures (3)

Callsign Dep Arr Status ETA
SWA2616 KLAS KSNA Enroute 0852
N254SB KLAS KSAN Enroute 1516
SWA320 KLAS KLAX Enroute 1444

Arrivals (1)

Callsign Dep Arr Status ETA
SWA2205 PHTO KLAS Enroute 2113

Las Vegas 4

Arrivals (1)

Callsign Dep Arr Status ETA
UAL1008 KORD KSBA Enroute 0423

Santa Barbara 1

Departures (1)

Callsign Dep Arr Status ETA
PCM7730 KIPL KSAN Enroute 1600

Other 1
  • Flights To/From ZLA: 46
  • Flights in ZLA Airspace: 24
  • Controller Schedule

    October 29th, 2026

    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.