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

Departures (17)

Callsign Dep Arr Status ETA
DAL3684 KLAX PHNL Enroute 0326
DAL41 KLAX YSSY Enroute 2035
UAL98 KLAX YMML Enroute 2319
UAE216 KLAX OMDB Enroute 0315
BAW52 KLAX SBCF Enroute 0240
SWA2848 KLAX PHNL Enroute 0339
SIA37 KLAX WSSS Enroute 0958
KAL018 KLAX RKSI Enroute 0718
FFT2564 KLAX KDFW Enroute 2039
UAL32 KLAX RJAA Enroute 0611
UAL1546 KLAX KLAS Enroute 0457
DAL1714 KLAX KSEA Enroute 1600
DLH443 KLAX EDDM Enroute 1602
UAL143 KLAX KSFO Enroute 1926
DAL2230 KLAX KJFK Enroute 1600
SIA35 KLAX WSSS Enroute 1014
BOX35F KLAX KLAS Enroute 0517

Arrivals (11)

Callsign Dep Arr Status ETA
DLH457 EDDF KLAX Enroute 0710
AAL1511 KMIA KLAX Enroute 0458
FDX3951 KEWR KLAX Enroute 0740
DAL301 KATL KLAX Enroute 0613
ASA696 KSEA KLAX Enroute 1600
AMX646 MMMX KLAX Enroute 0419
UAL1362 KSJC KLAX Enroute 1600
AAL3 KJFK KLAX Enroute 0812
DLH4ET EDDH KLAX Departing
CPA3280 PANC KLAX Enroute 1744
SKW4781 KSBP KLAX Enroute 1600

Los Angeles (SoCal) 28

Departures (3)

Callsign Dep Arr Status ETA
CAL023 KONT RCTP Enroute 0044
AAL4143 KONT KPHX Enroute 1600
FDX1381 KONT KMEM Enroute 2257

Arrivals (3)

Callsign Dep Arr Status ETA
SWA1706 KSMF KONT Enroute 0853
FDX1853 KOAK KONT Enroute 1600
DAL1614 KSLC KONT Enroute 0809

Empire (SoCal) 6

Departures (1)

Callsign Dep Arr Status ETA
SWA276 KSAN KSFO Enroute 1454

Arrivals (4)

Callsign Dep Arr Status ETA
BAW82P EGLL KSAN Enroute 0824
SWA4369 KSMF KSAN Enroute 0622
UAL179 KDEN KSAN Enroute 1600
ETX5725 KDAL KCRQ Departing

San Diego (SoCal) 5

Arrivals (2)

Callsign Dep Arr Status ETA
WAT1820 KJFK KSNA Enroute 0746
FFL1201 KTIW KSNA Enroute 0647

Coast (SoCal) 2

Arrivals (1)

Callsign Dep Arr Status ETA
AMF876 KSBA KBUR Enroute 0947

Burbank (SoCal) 1

Departures (1)

Callsign Dep Arr Status ETA
WGN618 KPSP KSJC Enroute 1600

Palm Springs (SoCal) 1

Departures (4)

Callsign Dep Arr Status ETA
DAL417 KLAS KATL Enroute 2028
UAL1660 KLAS KIAH Arriving
ALX656 KLAS KMMH Enroute 0808
SWA3018 KLAS KPHX Enroute 1600

Arrivals (5)

Callsign Dep Arr Status ETA
SWA2257 PHNL KLAS Enroute 0448
USC702 KDCA KLAS Enroute 0814
UAL1546 KLAX KLAS Enroute 0457
SWA665 KPHX KLAS Enroute 0750
BOX35F KLAX KLAS Enroute 0517

Las Vegas 9

Departures (2)

Callsign Dep Arr Status ETA
AMF876 KSBA KBUR Enroute 0947
SKW4781 KSBP KLAX Enroute 1600

Santa Barbara 2
  • Flights To/From ZLA: 54
  • Flights in ZLA Airspace: 22
  • Controller Schedule

    April 16th, 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.