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

Departures (31)

Callsign Dep Arr Status ETA
ETD172H KLAX OMAA Enroute 0421
AAL2675 KLAX KBOS Enroute 0013
DAL39 KLAX ZSPD Enroute 0600
N757RR KLAX KRDU Enroute 0024
DAL1426 KLAX KJFK Enroute 0437
SWA2848 KLAX PHNL Enroute 0744
BAW451 KLAX EGCC Enroute 0753
SCX426 KLAX KMSP Enroute 0125
WAT672 KLAX YSSY Enroute 1158
DAL480 KLAX PHNL Enroute 0910
UAL1412 KLAX KIAH Enroute 0055
DAL9754 KLAX KSEA Enroute 1225
DLH468 KLAX EDDF Enroute 0829
SIA26 KLAX KSEA Enroute 1159
FDX116 KLAX KDEN Enroute 1031
VIR24M KLAX EGLL Enroute 0917
DAL64D KLAX LPPT Enroute 1112
UAE42 KLAX OEJN Enroute 1543
UAL402 KLAX KDEN Enroute 1101
DAL1515 KLAX KLAS Enroute 1333
UAE985 KLAX EGKK Enroute 0922
DAL430 KLAX KMSP Enroute 0237
UAL1783 KLAX KBOS Enroute 0536
SWA2731 KLAX KLAS Enroute 1002
UAL2318 KLAX CYVR Enroute 1341
CAL5117 KLAX RCTP Enroute 0330
AAL2654 KLAX KRDU Enroute 0014
LOT2PA KLAX EPWA Enroute 1600
AAL3521 KLAX KSFO Enroute 2025
CCA770 KLAX ZGSZ Enroute 1155
SKW6208 KLAX KAUS Enroute 1600

Arrivals (24)

Callsign Dep Arr Status ETA
AFR24 LFPG KLAX Enroute 1322
DLH456 EDDF KLAX Enroute 0856
JBU7172 KSLC KLAX Enroute 1600
AAL3288 KMIA KLAX Enroute 1038
DAL40 YSSY KLAX Enroute 0743
WJA1102 CYVR KLAX Enroute 1613
DAL2551 KPDX KLAX Enroute 1119
ASA1411 KSEA KLAX Enroute 1341
QFA107 YSSY KLAX Enroute 0700
JBU487 KBOS KLAX Enroute 0452
QFA11 YSSY KLAX Enroute 0756
UAL1527 KSLC KLAX Enroute 0835
MZN2184 KRDU KLAX Enroute 1018
JBU217 KTUL KLAX Enroute 1344
JBU5952 KSAN KLAX Enroute 1515
JSX1180 KLAS KSMO Enroute 1403
DAL8877 KBFI KLAX Enroute 1600
LXJ171 KLAS KLAX Enroute 0912
SKW3743 KSAN KLAX Enroute 2029
N48MQ KSEE KSMO Enroute 2316
DAL1087 KSLC KLAX Enroute 1253
ASA3 KLAS KLAX Enroute 1600
UAL184 KSAN KLAX Enroute 1711
AAL524 KJFK KLAX Departing

Los Angeles (SoCal) 55

Arrivals (1)

Callsign Dep Arr Status ETA
FDX5025 VHHH KONT Enroute 1321

Empire (SoCal) 1

Departures (11)

Callsign Dep Arr Status ETA
SWA4132 KSAN KSMF Enroute 1023
NKS223 KSAN KPHX Enroute 1312
JBU5952 KSAN KLAX Enroute 1515
CGF26 KSAN KLAS Enroute 1113
SKW3743 KSAN KLAX Enroute 2029
N48MQ KSEE KSMO Enroute 2316
N44CK KSAN KAPC Enroute 1836
UAL184 KSAN KLAX Enroute 1711
FDX448 KSAN KPSP Enroute 1600
SWA3195 KSAN KRNO Enroute 1600
N355CP KSEE KLPC Enroute 1600

Arrivals (9)

Callsign Dep Arr Status ETA
SWA3541 KMDW KSAN Enroute 0843
SWA3194 KMCO KSAN Enroute 1001
DAL369 KDTW KSAN Enroute 0918
AAL2210 KDFW KSAN Enroute 0941
ASA433 KTPA KSAN Enroute 1600
PAA1822 CYVR KSAN Enroute 1600
ASA307 KPHX KSAN Enroute 1344
N312YH KSAN Enroute 0601
KLM640 EHAM KSAN Enroute 0926

San Diego (SoCal) 20

Departures (2)

Callsign Dep Arr Status ETA
EJM912 KSNA KNEW Enroute 0250
DAL367 KSNA KLAS Enroute 1600

Coast (SoCal) 2

Arrivals (1)

Callsign Dep Arr Status ETA
KAI2 KBFI KVNY Enroute 1600

Burbank (SoCal) 1

Arrivals (1)

Callsign Dep Arr Status ETA
FDX448 KSAN KPSP Enroute 1600

Palm Springs (SoCal) 1

Departures (9)

Callsign Dep Arr Status ETA
N624JX KLAS KIAD Enroute 0432
UAL2047 KLAS KSFO Enroute 1840
HAL807 KLAS PHNL Enroute 0656
JANET44 KLAS KXTA Enroute 1621
JSX1180 KLAS KSMO Enroute 1403
LXJ171 KLAS KLAX Enroute 0912
NKS9909 KLAS KGYR Enroute 1600
ASA3 KLAS KLAX Enroute 1600
SWA893 KLAS KSAT Enroute 0811

Arrivals (11)

Callsign Dep Arr Status ETA
SWA1100 KTPA KLAS Enroute 1600
WLF505 KDEN KLAS Enroute 1305
DAL1515 KLAX KLAS Enroute 1333
NKS1137 KMCO KLAS Enroute 1131
SWA611 KDEN KLAS Enroute 1014
UAL6555 KDEN KLAS Enroute 0941
CGF26 KSAN KLAS Enroute 1113
SWA2731 KLAX KLAS Enroute 1002
FFT777 KDEN KLAS Enroute 1600
UAL777 KORD KLAS Departing
DAL367 KSNA KLAS Enroute 1600

Las Vegas 20

Arrivals (1)

Callsign Dep Arr Status ETA
N355CP KSEE KLPC Enroute 1600

Other 1
  • Flights To/From ZLA: 101
  • Flights in ZLA Airspace: 45
  • Controller Schedule

    May 6th, 2026

    Socal Approach (Combined)
    Bryce Hudson

    Session with ER

    1930 - 2100 PDT / 0230 - 0400 Zulu

    The First Session at ZLA

    Welcome to ZLA!

    Now that you have passed your ZLA Basic Written Test and your clearance delivery test, you have now been assigned operating initials and can request training.

    Before you request training though, this guide will help you to come to the session prepared in order to not waste any time and help you spend more time working aircraft.

    The first thing that you'll need to do is donwload Teamspeak, a program used by ZLA controllers to communicate off frequency. It is free to download and install (Teamspeak Downloads). Once installed, you'll need the server connection details, found here: ZLA Teamspeak Info. Your nickname will be in this format: FirstName Lastname (Operationg Initials). Example: John Smith (JS). Feel free to log on at anytime and chat with other ZLA controllers.

    Next, you will want to review all the SOPs/LOAs at KLAX:
      After you have reviewed the SOPs and LOAs, you will need to download and install VRC, which can be downloaded here. After the installation, look through the VRC Documentation to setup as an observer. Considering you have been assigned operating initials as a ZLA controller, your callsign will be as follows: ZLA_OperatingIntials_OBS (i.e: ZLA_ZZ_OBS). Lastly, you'll want to setup and configure your microphone and speakers as well as your comms panel (specific directions on this can be found in the VRC documentation).

    You will need to the following information for the comms panel:
    • For LAX TWR: Position Name - LAX TWR, Frequency - 120.950, Vox Server - rw.liveatc.net, Vox Channel - 120.95
    • For LAX GND: Position Name - LAX GND, Frequency - 121.650, Vox Server - rw.liveatc.net, Vox Channel - 121.65
    • For LAX CTR: Position Name - LAX CTR, Frequency - 125.800, Vox Server - rw.liveatc.net, Vox Channel - 125.80
    Once you have done that, you will know if you have successfully set everything up if you can check the RX and HDST box next to a position that is being manned and can hear people talking. If there is no one controlling those positions, then you will not hear anyone. And of course, you must be logged on with your OBS call sign.

    VATSIM has strict regulations concerning visibility ranges when controlling. The maximum for delivery or ground positions is 20 nm. You will want to set this when you first logon to the position. For any ground positions in ZLA, you do not need to have a visibility range set higher then 10 nm.

    During your session, you might also encounter text only pilots. VRC has a great tool to help you respond to those pilots in a quick fashion. If you practice these before your first session, you will already be ahead of the ballgame.

    How to Use Aliases
     
    • .cor clearance on request, standby...
    • .cor# clearance on request, standby, you are number $1 in sequence...
    • .pref preferred route to $arr is
    • .can - can you accept?
    • .cd cleared to $arr airport; $uc($1) departure, then as filed;
    • .calt maintain 5,000, expect $cruise 5 minutes after departure, departure frequency $freq($1), squawk $squawk
    • .push pushback and start-up at pilot’s discretion; advise when ready to taxi
    • .tx Runway $1, taxi at pilot discretion wind $wind($dep), altimeter $altim($dep)
    • .txv Runway $1 taxi via $2 $3 $4 $5 $6 $7 $8 $9, wind $wind($dep), altimeter
    • $altim($dep)
    • .tx@ taxi to runway $1 intersection $2, wind $wind($dep), altimeter $altim($dep)
    • .txhs wind $wind($dep), altimeter $altim($dep), runway $1, taxi via $2 $3 $4 $5 $6 $7 $8 $9
    • .txg taxi to your gate, so long
    • .txp taxi to parking, so long
    • .lw runway $1, line up and wait;
    • .lwint runway $1 at $2, line up and wait;
    • .mid traffic crossing the runway
    • .pos traffic holding in position
    • .tfcdep traffic departing
    • .to wind $wind($dep), runway $1, cleared for takeoff
    • .land wind $wind($arr), runway $1, cleared to land

    These aliases take some getting used to. Above, the period at the beginning with the letters directly after it is the actual command you type in. The phrase after the space is what the dot command will spit out. The $ signs are variables meaning, if you want to use the .tx command to taxi an aircraft to a runway, you must input what runway they are to taxi to. So, you would type ".tx 24L" without the quotes to taxi an aircraft to 24L. Another helpful one is the clearance delivery alias. The one above only works if the pilot has filed a good flight plan with a SID and transition.

    Say a pilot filed LOOP6 DAG CLARR2 to KLAS and he's text only. Open his flight plan, assign him a squawk, verify his cruise altitude for direction of flight is correct, then at the bottom of VRC, type ".cdt LOOP6 DAG .calt 1w" without the quotes. Now, this will spit out the entire clearance on text. Note that 1w at the end of what you are to type in. This is the departure controller. 1W is the code for LAX_APP and 20 is the code for LAX_CTR. Type in the correct code in that spot depending on who the departure controller is. The controller codes can be found to the left of the controller callsign in the Controllers & Chat window.

    The only way to learn these is to play around with them. You can practice with them in a private message to nobody by typing ".chat nobody" without the quotes and hit enter. This will literally bring up a chat window to nobody. Here you can test your aliases in private and get used to them. See a mentor or instructor if you have trouble with these.

    TEC Routes Being in Southern California, the FAA has devised Tower Enroute Control routes, or TEC routes, in order to increase the efficient flow of aircraft throughout the busy SOCAL airspace. When an aircraft flies between two airports that have a TEC route, they must fly that TEC route. It is the controller’s responsibility to ensure they have the correct route. Luckily, the ZLA alias file for VRC contains all the TEC routes to ensure a quick route change if necessary.

    To use this feature, first, ensure you have the aircraft selected (the plane is yellow on your screen). Second, open up the flight strip. Third, in the command line (again verifying that the aircraft you are dealing with is listed to the left), type .laxn11 (or the appropriate TEC route number) and press enter. This will modify the flight strip to the correct route for the next controller. This will not modify the other boxes on top. Those must be reviewed and corrected as needed. This is a must!
    If you do not know the TEC route by heart, you can either look it up on the ZLA website, or, following the same steps above, instead type .laxsanj. This will produce the same route. The top boxes of the flight strip must still be reviewed. You can do this with every TEC type of aircraft by replacing the last letter with the correct type of aircraft. Remember, J = Jet, M = Turboprop + 190 knots, P = propeller aircraft + 190 knots, Q = Propeller aircraft - 189 knots. So, if an EMB120 was flying KLAX to KSAN, you would type .laxsanm.

    If it comes back and does not change anything, then there is not a TEC route. This is common with KLAX-KPSP. Of note, you cannot practice this on your OBS account, but if you know the process before logging on, you will be able to work TEC routes faster.

    Pilot Certifications Finally, the Los Angeles ARTCC has made available a voluntary testing and training program for VATSIM pilots to help improve their skills. The certifications represent a formal attempt to help pilots improve their flying abilities in a more structured setting as well as a fun environment. From simple VFR pattern work to advanced IFR ARC Approaches, these 14 certs test pilot skills and teach them a lot about advanced flying too.

    You as a controller MUST register here. If a pilot ever requests to do an certification exam, this is what they are referring to. The exams are called the V-1, V-2, V-3, and I-1, I-2, I-3, I-4, and so on all the way to the I-11. In order for the pilot to complete the cert, they must have full ATC the entire flight. When a pilot requests a specific exam, go to the http://www.pilotcerts.laartcc.org site, click "ratings" on the left and click the appropriate rating that the pilot requests. Then evaluate what controller(s) must be on for this rating (note: if LAX_CTR is online, any rating may be completed since CTR covers everything). Then, verify with the correct controller(s) that they are able to accommodate such rating and if so, approve the rating to the pilot and get him on his way like you would with any other flight. However, remember to pass on the information that the pilot is doing a pilot cert rating to the next controller.

    It is the last controller's job who controls the arrival airport to enter in the pass/fail. Because of this, you could potentially have to enter in the pass/fail for the V-3 rating that ends at KLAX or the I-9 that also ends at KLAX. If this is the case, another controller should PM you the information about the pilot's attempt at the cert (whether he passed or failed). Then, log in here and hit "Sumbit Rating" on the left. Enter in the pilot's information as needed (you may PM him if you have a question about his info) then hit submit at the bottom. Let me know if you have any questions regarding this whole process.

    Visit the main site: here for more details about the program including how you can join it as a pilot on the network.

    Conclusion During your first session, you will be on the live network talking to real pilots. Review the STM once over before the session paying attention to clearances and ground phraseology and you will be all set. Again, welcome to ZLA and the training staff looks forward to working with you on the scopes!