ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (10)

Callsign Dep Arr Status ETA
SIA11 KLAX RJAA Enroute 1252
BAW4X KLAX EGLL Enroute 1245
GTI9013 KLAX VHHH Enroute 1918
EVA15 KLAX RCTP Enroute 1730
DAL37 KLAX RJTT Enroute 1603
AUA82 KLAX LOWW Enroute 1601
DLH451 KLAX EGLL Enroute 1713
UAE216 KLAX OMDB Enroute 1519
ASA1317 KLAX KSEA Enroute 2300
AAL900 KLAX KSLC Enroute 1600

Arrivals (15)

Callsign Dep Arr Status ETA
DAL40 YSSY KLAX Enroute 1918
UAE83M OMDB KLAX Enroute 0300
THY8MT LTFM KLAX Enroute 0021
SWA2861 PHNL KLAX Enroute 0117
VIR97K YMML KLAX Enroute 1751
AFR020 LFPG KLAX Enroute 0407
FDX291 EGLL KLAX Enroute 0349
AUA81 LOWW KLAX Enroute 0640
KAL74 RKSI KLAX Enroute 0404
PTI737 VHHH KLAX Enroute 0416
VIR31M EGLL KLAX Enroute 0718
QFA93 YMML KLAX Enroute 2058
DAL724 KATL KLAX Departing
PAL478 RPLL KLAX Enroute 0251
KAL213 RKSI KLAX Enroute 2227

Los Angeles (SoCal) 25

Departures (4)

Callsign Dep Arr Status ETA
QFA903 KSAN YSSY Enroute 1853
SWA2116 KSAN KCOS Enroute 1600
SWA2245 KSAN KLAS Enroute 2150
UPS1026 KSAN MMMX Enroute 1421

Arrivals (1)

Callsign Dep Arr Status ETA
DLH484 EDDM KSAN Enroute 2308

San Diego (SoCal) 5

Arrivals (1)

Callsign Dep Arr Status ETA
SWA1890 KDEN KPSP Enroute 2151

Palm Springs (SoCal) 1

Departures (2)

Callsign Dep Arr Status ETA
BAW270 KLAS EGLL Enroute 1843
BAW4LV KLAS EGLL Enroute 2140

Arrivals (6)

Callsign Dep Arr Status ETA
KHY69 RPLL KLAS Enroute 2332
BAW2MW EGLL KLAS Enroute 2311
ROU1705 CYYZ KLAS Enroute 2220
SWA2245 KSAN KLAS Enroute 2150
JBU611 KJFK KLAS Departing
JBU1577 KBOS KLAS Departing

Las Vegas 8

Arrivals (1)

Callsign Dep Arr Status ETA
MOOSE77 KLTS KLSV Departing

Nellis 1
  • Flights To/From ZLA: 40
  • Flights in ZLA Airspace: 4
  • Controller Schedule

    June 2nd, 2025

    Los Angeles Tower
    Anthony Ferrando

    1700 - 2000 PDT / 0000 - 0300 Zulu

    Lindbergh Tower
    James Dresden

    Session with BY

    1900 - 2030 PDT / 0200 - 0330 Zulu

    Los Angeles Tower
    Jerome Sudhakar

    2000 - 2230 PDT / 0300 - 0530 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.