ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (12)

Callsign Dep Arr Status ETA
LSP603 KLAX SCEL Enroute 1539
DLH457 KLAX EDDF Enroute 1615
KAL012 KLAX RKSI Enroute 1819
CPA883 KLAX VHHH Enroute 2018
KLM604 KLAX EHAM Enroute 1746
AAL213 KLAX KSEA Enroute 0839
N421SV KHHR KABQ Enroute 1255
AAL1876 KLAX KDFW Enroute 1542
AZA621 KLAX LIRF Enroute 1428
DAL8635 KLAX KLAS Enroute 2339
BAW765 KLAX KSFO Enroute 1600
MPH6911 KLAX KGCN Enroute 1600

Arrivals (14)

Callsign Dep Arr Status ETA
CPA882 VHHH KLAX Enroute 2348
WAT3650 RJAA KLAX Enroute 2307
DLH456 EDDF KLAX Enroute 0302
BOX474 EDDF KLAX Enroute 0246
FJI810 NFFN KLAX Enroute 2037
IBE03ZB LEMD KLAX Enroute 0404
TWA802 RKSI KLAX Enroute 0305
DAL773 KJFK KLAX Enroute 0047
ITY674 LIMC KLAX Enroute 1109
BKN2320 KMCO KLAX Enroute 2304
BOX478 EDDF KLAX Enroute 0039
CCA983 ZBAA KLAX Departing
JBU1537 KSFO KLAX Enroute 1600
DAL763 KATL KLAX Departing

Los Angeles (SoCal) 26

Departures (1)

Callsign Dep Arr Status ETA
N198N KSBD LFLX Enroute 1704

Empire (SoCal) 1

Departures (2)

Callsign Dep Arr Status ETA
UAL7 KSAN KDEN Enroute 0036
ASA512 KSAN KSEA Enroute 1104

Arrivals (1)

Callsign Dep Arr Status ETA
SWA712 KBOI KSAN Enroute 2349

San Diego (SoCal) 3

Arrivals (2)

Callsign Dep Arr Status ETA
SWA3291 KOAK KLGB Enroute 1600
N216HP KFUL KFUL Enroute 1600

Coast (SoCal) 2

Departures (1)

Callsign Dep Arr Status ETA
NCHHJ KVNY MMLT Enroute 2138

Burbank (SoCal) 1

Arrivals (1)

Callsign Dep Arr Status ETA
ASA692 KSEA KPSP Enroute 0146

Palm Springs (SoCal) 1

Departures (4)

Callsign Dep Arr Status ETA
VIR1 KLAS EGCC Enroute 1903
UAL1088 KLAS KBNA Enroute 1516
VIR86 KLAS EGCC Enroute 2219
SWA2576 KLAS KSEA Enroute 1600

Arrivals (3)

Callsign Dep Arr Status ETA
VIR85 EGCC KLAS Enroute 0732
SWA434 KDFW KLAS Enroute 2348
DAL8635 KLAX KLAS Enroute 2339

Las Vegas 7

Departures (1)

Callsign Dep Arr Status ETA
HAWG76 KLSV KDMA Enroute 1600

Nellis 1

Arrivals (1)

Callsign Dep Arr Status ETA
MPH6911 KLAX KGCN Enroute 1600

Other 1
  • Flights To/From ZLA: 43
  • Flights in ZLA Airspace: 9
  • Controller Schedule

    July 18th, 2026

    Socal Approach (Combined)
    Jerome Sudhakar

    Session with LL

    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.