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

Departures (23)

Callsign Dep Arr Status ETA
UAL32 KLAX RJAA Enroute 0149
AFR26 KLAX NTAA Enroute 2356
DAL371 KLAX PHNL Enroute 0354
DAL1556 KLAX PHOG Enroute 0345
DAL481 KLAX PANC Enroute 1526
DAL515 KLAX KATL Enroute 2237
UAL461 KLAX KRNO Enroute 2148
BOX383 KLAX EDDP Enroute 0554
BAW34 KLAX EGLL Enroute 2241
AAL1972 KLAX KDFW Arriving
DLH4847 KLAX EDDF Enroute 0608
UAL1476 KLAX KSAN Enroute 1600
DAL189 KLAX RPLL Enroute 1200
ANA511 KLAX RJAA Enroute 0436
AAL2755 KLAX KDFW Enroute 0029
DAL842 KLAX SKBO Enroute 0345
N470CP KLAX KTEX Enroute 1600
DLH453 KLAX EDDM Enroute 1600
PAY7260 KLAX KDEN Enroute 0736
SWA1048 KLAX KLAS Enroute 1600
N725DT KLAX KTEX Enroute 0846
AAL2789 KLAX KPHX Enroute 1600
BAW215 KLAX EGLL Enroute 1600

Arrivals (14)

Callsign Dep Arr Status ETA
FIN1 EFHK KLAX Enroute 1003
BAW269 EGLL KLAX Enroute 1103
AAL1618 KCLT KLAX Enroute 1059
DLH452 EDDM KLAX Enroute 1737
WGN212 PANC KLAX Enroute 0733
CLX5TY PHNL KLAX Enroute 0635
UAL1157 PHNL KLAX Enroute 0654
GTI316 KORD KLAX Enroute 0942
LOBO55 KSAN KLAX Enroute 1600
AAL2005 LEBL KLAX Enroute 0837
AAL216 KSFO KLAX Enroute 1827
AAL3290 KMIA KLAX Enroute 0710
KAL17 RKSI KLAX Departing
FDX183 KOAK KLAX Enroute 1600

Los Angeles (SoCal) 37

Arrivals (3)

Callsign Dep Arr Status ETA
FFT1499 KDEN KONT Enroute 0953
N531BM KCRQ KPOC Enroute 0112
DAL3064 KRNO KONT Enroute 1600

Empire (SoCal) 3

Departures (5)

Callsign Dep Arr Status ETA
DAL85XP KSAN LKPR Enroute 2230
UAL1067 KSAN KBOS Enroute 2358
LOBO55 KSAN KLAX Enroute 1600
N531BM KCRQ KPOC Enroute 0112
N963SG KCRQ KMYF Enroute 2350

Arrivals (6)

Callsign Dep Arr Status ETA
DLH5Y EDDM KSAN Enroute 1156
UAL1476 KLAX KSAN Enroute 1600
ACA3321 CYVR KSAN Enroute 1600
ASA389 KBOS KSAN Enroute 1124
HAL816 PHNL KSAN Enroute 1600
N963SG KCRQ KMYF Enroute 2350

San Diego (SoCal) 11

Departures (2)

Callsign Dep Arr Status ETA
WJA1581 KSNA CYYC Enroute 0931
AWE263 KSNA KRNO Enroute 0846

Arrivals (2)

Callsign Dep Arr Status ETA
UAL1847 KEWR KSNA Enroute 1135
SWA2169 KSJC KLGB Enroute 1600

Coast (SoCal) 4

Departures (1)

Callsign Dep Arr Status ETA
UAL488 KBUR KSFO Enroute 1052

Burbank (SoCal) 1

Departures (11)

Callsign Dep Arr Status ETA
DAL8652 KLAS KMSP Arriving
JBU956 KLAS KEWR Enroute 2308
SWA1927 KLAS KMEM Enroute 2253
UAL1799 KLAS KSFO Enroute 0821
DLH521 KLAS KSFO Enroute 1213
SWA2187 KLAS KRNO Enroute 2119
DAL1925 KLAS KATL Enroute 0102
WJA1059 KLAS CYVR Enroute 1743
FFT1728 KLAS KMCO Enroute 0432
AAL2720 KLAS KORD Enroute 0100
UAL2356 KLAS KSFO Enroute 1600

Arrivals (5)

Callsign Dep Arr Status ETA
ENY4102 KRDM KLAS Enroute 0927
AAL2732 KPHX KLAS Enroute 1625
SWA665 KPHX KLAS Enroute 1600
JBU177 KBOS KLAS Enroute 1108
SWA1048 KLAX KLAS Enroute 1600

Las Vegas 16

Departures (1)

Callsign Dep Arr Status ETA
PLW991 KMHV CYYR Enroute 0014

Edwards 1

Departures (1)

Callsign Dep Arr Status ETA
VCP264P KNYL KTUS Enroute 0448

Yuma 1
  • Flights To/From ZLA: 74
  • Flights in ZLA Airspace: 26
  • Controller Schedule

    February 17th, 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.