ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (11)

Callsign Dep Arr Status ETA
PAL103 KLAX RPLL Enroute 1350
BAW28F KLAX EGLL Enroute 1217
AAL3010 KLAX RJTT Enroute 1327
N233CL KLAX PHNL Enroute 1540
AAL73 KLAX YSSY Enroute 1605
QTR740 KLAX OTHH Enroute 1952
DLH453 KLAX EDDM Enroute 1726
SIA39 KLAX WSSS Enroute 2300
UAE37V KLAX OMDB Enroute 1148
SAS88B KLAX CYVR Enroute 2107
DAL547 KLAX KMCO Enroute 1022

Arrivals (6)

Callsign Dep Arr Status ETA
PAC962 RJAA KLAX Enroute 2024
DAL1008 KSLC KLAX Enroute 2022
CPA880 VHHH KLAX Departing
DLH452 EDDM KLAX Enroute 1107
AUA98 LOWW KLAX Departing
DLH254 EDDM KLAX Departing

Los Angeles (SoCal) 17

Arrivals (1)

Callsign Dep Arr Status ETA
UPS225 VHHH KONT Enroute 2225

Empire (SoCal) 1

Arrivals (1)

Callsign Dep Arr Status ETA
SWA91 KLAS KSNA Enroute 2006

Coast (SoCal) 1

Departures (1)

Callsign Dep Arr Status ETA
SWA91 KLAS KSNA Enroute 2006

Arrivals (2)

Callsign Dep Arr Status ETA
PRNCO MPTO KLAS Enroute 1910
UAL686 KIAH KLAS Departing

Las Vegas 3
  • Flights To/From ZLA: 22
  • Flights in ZLA Airspace: 2
  • Controller Schedule

    November 21st, 2024

    Los Angeles Tower
    Jay Smith

    Session with RK

    1700 - 1830 PST / 0100 - 0230 Zulu

    TEC Routes

    DATE VERSION CONTACT
    2024-05-25 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. Only aircraft departing and arriving within the same TRACON 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.
        2. A prop that files from SMX to ONT at 7,000 is required to use a TEC route
      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.