ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (15)

Callsign Dep Arr Status ETA
BAW4E KLAX EGLL Enroute 1432
AAL83 KLAX NZAA Enroute 1722
BAW4K KLAX EGLL Enroute 1530
DAL7 KLAX RJTT Enroute 1858
IBE0352 KLAX LEMD Enroute 1821
AUA52 KLAX LOWW Enroute 2019
ACA557 KLAX CYVR Enroute 0218
AAL1313 KLAX PHNL Enroute 2137
AAL8820 KLAX PHNL Enroute 2211
VIR142 KLAX EGLL Enroute 2158
SKW4121 KLAX KPSP Enroute 2358
DLH451 KLAX EDDF Enroute 1430
UAE69 KLAX KATL Enroute 1600
UAL4620 KLAX KABQ Enroute 1600
AAL2 KLAX KJFK Enroute 1600

Arrivals (12)

Callsign Dep Arr Status ETA
SJX2 RCTP KLAX Enroute 2204
GTI81 YSSY KLAX Enroute 1954
BKC709 ZSPD KLAX Enroute 0811
ANZ6 NZAA KLAX Enroute 1842
UAL2390 PHNL KLAX Enroute 0555
AAL3283 KDCA KLAX Enroute 2302
TFY676 LOWW KLAX Enroute 0530
UAE83M OMDB KLAX Enroute 0057
DAL439 KDFW KLAX Enroute 2219
ITY654 LIML KLAX Enroute 0817
UAL12 KLAS KLAX Enroute 1452
AAL1154 KDFW KLAX Departing

Los Angeles (SoCal) 27

Departures (1)

Callsign Dep Arr Status ETA
ATN3353 KONT KAFW Enroute 1600

Arrivals (1)

Callsign Dep Arr Status ETA
SVA6992 SCFA KHMT Enroute 1827

Empire (SoCal) 2

Departures (4)

Callsign Dep Arr Status ETA
DLH467 KSAN EDDM Enroute 1445
FAD205 KSAN EGLL Enroute 1909
DLH19Q KSAN MMUN Enroute 1333
UAL2274 KSAN KSFO Enroute 2243

San Diego (SoCal) 4

Arrivals (1)

Callsign Dep Arr Status ETA
FFL471 KJWY KSNA Enroute 1600

Coast (SoCal) 1

Arrivals (1)

Callsign Dep Arr Status ETA
SKW4121 KLAX KPSP Enroute 2358

Palm Springs (SoCal) 1

Departures (3)

Callsign Dep Arr Status ETA
UAL408 KLAS KIAH Enroute 1413
UAL2145 KLAS KSFO Enroute 1600
UAL12 KLAS KLAX Enroute 1452

Arrivals (5)

Callsign Dep Arr Status ETA
CFG062 EDDF KLAS Enroute 0136
DLH2062 EDDF KLAS Departing
AWE110 KDEN KLAS Enroute 0322
AFR56T LFPG KLAS Enroute 0527
DAL2880 KSEA KLAS Enroute 0016

Las Vegas 8

Departures (1)

Callsign Dep Arr Status ETA
SWA4125 KSBA KDEN Enroute 1600

Santa Barbara 1

Arrivals (1)

Callsign Dep Arr Status ETA
GGA3799 KMEB KVCV Enroute 2303

Edwards 1
  • Flights To/From ZLA: 45
  • Flights in ZLA Airspace: 13
  • Controller Schedule

    July 15th, 2026

    Socal Approach (West)
    William Collister

    Session with AT

    1600 - 1730 PDT / 2300 - 0030 Zulu

    Los Angeles Center
    Mohammad Mirza

    Session with TY

    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.