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

Departures (17)

Callsign Dep Arr Status ETA
FDX2904 KLAX SAEZ Enroute 1535
AAL315 KLAX KMIA Enroute 1514
DLH453 KLAX EDDM Enroute 2006
GEC26 KLAX KMIA Enroute 1721
CFG081 KLAX EDDF Enroute 2330
DAL515 KLAX KATL Enroute 1655
DLH457 KLAX EDDF Enroute 2322
ANZ9651 KLAX SBGR Enroute 2201
DLH2016 KLAX EDDF Enroute 0034
SQC7327 KLAX EHAM Arriving
ASA332 KLAX MMSD Enroute 2238
BER739 KLAX OMDB Enroute 1750
CFG281 KLAX EDDF Enroute 1514
UAL2647 KLAX KSFO Enroute 0106
FDX1379 KLAX KMEM Enroute 1812
UPS135 KLAX KJFK Enroute 2039
FDX3901 KLAX KEWR Enroute 1600

Arrivals (15)

Callsign Dep Arr Status ETA
CAL008 RCTP KLAX Enroute 2341
DAL38 ZSPD KLAX Enroute 2330
LOT21 EPWA KLAX Enroute 0155
DHK51 ZSPD KLAX Enroute 0016
PAL112 RPLL KLAX Enroute 0132
DAL57 EDDF KLAX Enroute 0436
AFR24 LFPG KLAX Enroute 0548
DAL69 PHNL KLAX Enroute 2200
DAL441E KJFK KLAX Enroute 0326
SIA38 WSSS KLAX Enroute 0554
SWA2621 KLAS KLAX Enroute 0026
AAL598 KDFW KLAX Enroute 0200
SIA36 WSSS KLAX Enroute 0120
BAW7D EGLL KLAX Departing
TWB546 RKSI KLAX Departing

Los Angeles (SoCal) 32

Arrivals (2)

Callsign Dep Arr Status ETA
DAL475 KSLC KONT Enroute 0054
UPS81 PANC KONT Enroute 1600

Empire (SoCal) 2

Departures (2)

Callsign Dep Arr Status ETA
FFT2818 KSAN KDEN Enroute 1449
WAT7577 KSAN PHNL Enroute 1600

Arrivals (3)

Callsign Dep Arr Status ETA
SWA3549 KDAL KSAN Enroute 0146
UAL1302 KDEN KSAN Enroute 0037
BAW82P EGLL KSAN Enroute 0619

San Diego (SoCal) 5

Departures (2)

Callsign Dep Arr Status ETA
AXX256 KLGB KIND Enroute 1538
SWA1987 KLGB PHNL Enroute 2221

Coast (SoCal) 2

Arrivals (1)

Callsign Dep Arr Status ETA
UAL2363 KSFO KBUR Enroute 1600

Burbank (SoCal) 1

Departures (4)

Callsign Dep Arr Status ETA
FFT78 KLAS MMSD Enroute 2305
AXY1F KLAS KMIA Enroute 1746
SWA2621 KLAS KLAX Enroute 0026
DAL962 KLAS KSEA Enroute 0241

Arrivals (6)

Callsign Dep Arr Status ETA
N388LS KPBI KLAS Enroute 0255
AFR1091 LFMN KLAS Enroute 0601
MTN001 KGEG KLAS Enroute 0051
MTN005 KGEG KLAS Enroute 0026
BVR114 KDEN KLAS Enroute 0231
WJA1086 CYYC KLAS Enroute 0118

Las Vegas 10

Arrivals (1)

Callsign Dep Arr Status ETA
UAL1685 KSFO KSBA Enroute 1600

Santa Barbara 1

Departures (1)

Callsign Dep Arr Status ETA
FCW9111 KGCN KTEX Enroute 1801

Other 1
  • Flights To/From ZLA: 54
  • Flights in ZLA Airspace: 13
  • Controller Schedule

    April 30th, 2026

    Los Angeles Tower
    Marc Bracco

    Session with AK

    1700 - 1830 PDT / 0000 - 0130 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.