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

Departures (11)

Callsign Dep Arr Status ETA
AFR28G KLAX NTAA Enroute 1904
HFY85T KLAX RJTT Enroute 2143
SWA1171 KLAX KBNA Enroute 1748
DAL93 KLAX YBBN Enroute 0251
SIA37 KLAX WSSS Enroute 0024
DAL781 KLAX KATL Enroute 1816
DLH452 KLAX EDDF Enroute 1600
UAE85K KLAX OMDB Enroute 0432
AAL113 KLAX KLAS Enroute 1751
CAO8442 KLAX ZYTX Enroute 1751
ITY420 KLAX LIPZ Enroute 1600

Arrivals (15)

Callsign Dep Arr Status ETA
DLH135 YSSY KLAX Enroute 0030
VIR7C EGLL KLAX Enroute 0055
KAL9207 RKSI KLAX Enroute 0113
KLM3650 NZAA KLAX Enroute 2213
UAL1321 KEWR KLAX Enroute 0114
SAS931 EKCH KLAX Enroute 0259
AAR204 RKSI KLAX Enroute 0430
SJX2 RCTP KLAX Enroute 0353
CES583 ZSPD KLAX Enroute 0353
VIR7 EGLL KLAX Enroute 0814
KAL8203 RKSI KLAX Enroute 0348
BIRD227 KJFK KLAX Departing
UAL1921 KEWR KLAX Departing
OAL463 CYVR KLAX Enroute 0225
BAW4C KLAS KLAX Enroute 1600

Los Angeles (SoCal) 26

Departures (1)

Callsign Dep Arr Status ETA
PCM8688 KONT KSBP Enroute 1639

Arrivals (1)

Callsign Dep Arr Status ETA
SWA1278 KBWI KONT Enroute 0320

Empire (SoCal) 2

Departures (1)

Callsign Dep Arr Status ETA
N2131X KSAN NONE Enroute 1600

Arrivals (2)

Callsign Dep Arr Status ETA
SWA1335 KMCO KSAN Departing
AAL2247 KPHX KSAN Enroute 1600

San Diego (SoCal) 3

Arrivals (3)

Callsign Dep Arr Status ETA
AAY643 KBOI KSNA Enroute 0136
AAL240 KDFW KSNA Enroute 0124
AAL2142 KDFW KSNA Departing

Coast (SoCal) 3

Arrivals (1)

Callsign Dep Arr Status ETA
AAY3890 KPVU KBUR Enroute 0941

Burbank (SoCal) 1

Departures (1)

Callsign Dep Arr Status ETA
AAL1321 KPSP KPHX Enroute 1600

Palm Springs (SoCal) 1

Departures (7)

Callsign Dep Arr Status ETA
DAL6441 KLAS KICT Enroute 1715
NKS1248 KLAS KSTL Enroute 1749
BAW4LV KLAS EGLL Enroute 2349
FFT1102 KLAS KSTL Enroute 1744
UAL1054 KLAS KSTL Enroute 1737
SWA1495 KLAS KSTL Enroute 1759
BAW4C KLAS KLAX Enroute 1600

Arrivals (5)

Callsign Dep Arr Status ETA
EDW189 LSZH KLAS Enroute 0338
AAL2177 KMIA KLAS Enroute 0107
DLH1551 EDDM KLAS Enroute 0756
SWA2722 KSMF KLAS Enroute 0208
AAL113 KLAX KLAS Enroute 1751

Las Vegas 12

Arrivals (12)

Callsign Dep Arr Status ETA
ZAPPR21 KLSV KLSV Enroute 0819
FAZER12 KLSV KLSV Enroute 0115
KONG1 KLSV KLSV Enroute 0709
SILVER1 KLSV KLSV Enroute 0326
FLNKR51 KLSV KLSV Enroute 0113
MIG42 KLSV KLSV Enroute 2353
FLNKR52 KLSV KLSV Enroute 0147
MONSE11 KLSV KLSV Enroute 1600
EVIL3 KLSV KLSV Enroute 0316
FAZER11 KLSV KLSV Enroute 0124
HRLEY41 KLSV KLSV Enroute 2316
MONSE12 KLSV KLSV Enroute 1600

Nellis 12

Arrivals (2)

Callsign Dep Arr Status ETA
PCM8688 KONT KSBP Enroute 1639
UAL1799 KSFO KSBA Enroute 1600

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

    March 20th, 2026

    Los Angeles Center (25)
    Tom Solon

    CTR Session wtih MM - will need T/D

    1700 - 1830 PDT / 0000 - 0130 Zulu

    Los Angeles Tower
    Alston Hao

    OTS with BY

    1800 - 1930 PDT / 0100 - 0230 Zulu

    Los Angeles Tower
    Jaden Schaffer

    Session with LL

    1930 - 2100 PDT / 0230 - 0400 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.