ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (13)

Callsign Dep Arr Status ETA
UAE216 KLAX OMDB Enroute 0913
AAL27 KLAX RJTT Enroute 0625
JBU36A KLAX PHNL Enroute 1051
MJX543 KLAX EDDF Enroute 0944
JBU288 KLAX KBOS Enroute 0703
NKS271 KLAX KORD Enroute 0510
ASA1240 KLAX KPDX Enroute 1628
FJI811 KLAX NFFN Enroute 1455
SVA42 KLAX OEJN Enroute 1731
AAL1923 KLAX KMIA Enroute 0747
AAL1675 KLAX KPHX Enroute 1502
PAL113 KLAX RPLL Enroute 1703
DAL41 KLAX YSSY Enroute 1600

Arrivals (6)

Callsign Dep Arr Status ETA
BAW451 EGCC KLAX Enroute 1644
JBU187 KBOS KLAX Enroute 1600
DAL763 KATL KLAX Enroute 1553
UAL1321 KEWR KLAX Enroute 1600
DAL1988 KSLC KLAX Enroute 1917
UAL2282 KLAS KLAX Enroute 1539

Los Angeles (SoCal) 19

Departures (6)

Callsign Dep Arr Status ETA
UAL504 KSAN KIAH Arriving
DLH427 KSAN EDDM Enroute 1429
ASA1199 KSAN KSEA Enroute 1453
DLH132 KSAN KSEA Enroute 1552
DAL2508 KSAN KSEA Enroute 1530
DAL2613 KSAN KSEA Enroute 1533

Arrivals (1)

Callsign Dep Arr Status ETA
AAL813 KTUS KSAN Enroute 1554

San Diego (SoCal) 7

Departures (4)

Callsign Dep Arr Status ETA
9VDAN KVNY KOPF Enroute 0743
N683MB KBUR KBFL Enroute 1600
N505XT KBUR KSBA Enroute 1600
UAL283 KBUR KDEN Enroute 0746

Arrivals (1)

Callsign Dep Arr Status ETA
PSRND PANC KVNY Enroute 1525

Burbank (SoCal) 5

Departures (1)

Callsign Dep Arr Status ETA
N505CF KPSP MMSF Enroute 0211

Palm Springs (SoCal) 1

Departures (5)

Callsign Dep Arr Status ETA
BAW3309 KLAS EGLL Enroute 0749
AAY12 KLAS KBZN Enroute 1800
VIR156T KLAS EGLL Enroute 1352
UAL2282 KLAS KLAX Enroute 1539
UAL1267 KLAS KSFO Enroute 1600

Arrivals (2)

Callsign Dep Arr Status ETA
BAW2277 EGKK KLAS Enroute 1451
AAL2800 KPHX KLAS Enroute 1436

Las Vegas 7

Arrivals (1)

Callsign Dep Arr Status ETA
N505XT KBUR KSBA Enroute 1600

Santa Barbara 1

Arrivals (1)

Callsign Dep Arr Status ETA
N683MB KBUR KBFL Enroute 1600

Bakersfield 1

Departures (1)

Callsign Dep Arr Status ETA
C2004 KNTD KLBB Enroute 1713

Point Mugu 1
  • Flights To/From ZLA: 42
  • Flights in ZLA Airspace: 16
  • Controller Schedule

    September 17th, 2025

    Lindbergh Tower
    Joseph Liu

    1500 - 1630 PDT / 2200 - 2330 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.