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

Departures (30)

Callsign Dep Arr Status ETA
DAL64 KLAX NZAA Enroute 0105
CES586 KLAX ZSPD Enroute 0231
UAL839 KLAX VHHX Enroute 1814
AAL73 KLAX YSSY Enroute 1008
AAL1200 KLAX KIAD Enroute 0115
NGA41N KLAX DNMM Enroute 1600
DAL1619 KLAX KDTW Enroute 0108
VIR8Y KLAX EGLL Enroute 1459
DAL589 KLAX KATL Enroute 0240
DAL811 KLAX KMIA Enroute 0220
AFR1611 KLAX LFPG Enroute 0743
LRC641 KLAX MGGT Enroute 0222
AAL204 KLAX KCLT Enroute 0218
FDX347 KLAX KBOS Enroute 0507
AAL1537 KLAX KSLC Enroute 1132
SAS931 KLAX EKCH Enroute 1003
RPV101 KLAX KDEN Enroute 0939
CES586D KLAX ZSPD Enroute 1347
FIN2 KLAX EFHK Enroute 1043
DAL2153 KLAX KSFO Enroute 1253
ACA220 KLAX CYYC Enroute 1036
DAL78Y KLAX KSAN Enroute 0204
AMX643 KLAX MMMX Enroute 0432
DAL324 KLAX KLAS Enroute 1535
DAL991 KLAX KJFK Enroute 1626
DAL314 KLAX KSFO Enroute 1741
GTI233 KLAX KDEN Enroute 1600
AAL2818 KLAX KPHX Enroute 1600
AAL06 KLAX KPHX Enroute 1600
DAL494 KLAX KDTW Enroute 0255

Arrivals (21)

Callsign Dep Arr Status ETA
AAL72 YSSY KLAX Enroute 0706
PAL100 RPLL KLAX Enroute 1026
DAL62 KTPA KLAX Enroute 0849
GTI8173 KORD KLAX Enroute 2242
DAL8891 KEWR KLAX Enroute 0906
AUA51 LOWW KLAX Enroute 1542
UAL1743 KIAH KLAX Enroute 0852
UAL517 KORD KLAX Enroute 0730
AAL315 KMIA KLAX Enroute 0856
AAL2732 KDFW KLAX Enroute 0817
UAL1157 PHNL KLAX Enroute 0750
MXY704 KORF KLAX Enroute 0931
AAL966 KDFW KLAX Enroute 1111
AAL3972 KPDX KLAX Enroute 0929
FFT264 KDFW KLAX Enroute 1030
UAL1754 KSFO KLAX Enroute 1619
CPA885 VHHH KLAX Departing
CXA673 KSLC KLAX Enroute 1426
DAL22 LOWW KLAX Enroute 1244
DAL908 KDTW KLAX Departing
PAL112 RPLL KLAX Enroute 1023

Los Angeles (SoCal) 51

Departures (5)

Callsign Dep Arr Status ETA
DAL2172 KSAN KDTW Enroute 0033
SSR772 KSAN KTEB Enroute 0213
SWA4873 KSAN KBOI Enroute 2052
BAW7L KSAN EGLL Enroute 0817
SWA4111 KSAN KLAS Enroute 1632

Arrivals (12)

Callsign Dep Arr Status ETA
SWA1849 KBOS KSAN Enroute 1127
SSR412 KATL KSAN Departing
AAL2458 KDFW KSAN Enroute 0836
N728QL KJAN KCRQ Enroute 0816
CXK425 KLGB KCRQ Enroute 1103
DAL3293 KAUS KSAN Enroute 0818
ACA278 CYVR KSAN Enroute 1000
DAL78Y KLAX KSAN Enroute 0204
CXK69 KPHX KSAN Enroute 0838
BAW273 EGLL KSAN Enroute 0836
UAL5055 MMMX KSAN Departing
BAW82P EGLL KSAN Enroute 0821

San Diego (SoCal) 17

Departures (2)

Callsign Dep Arr Status ETA
CXK425 KLGB KCRQ Enroute 1103
AAL279 KSNA KASE Enroute 1600

Coast (SoCal) 2

Departures (3)

Callsign Dep Arr Status ETA
UAL1191 KBUR KDEN Enroute 0645
UAL2187 KBUR KDEN Enroute 0954
AXI753 KVNY KLEX Enroute 0009

Burbank (SoCal) 3

Departures (7)

Callsign Dep Arr Status ETA
SWA975 KLAS KCAK Enroute 0007
SWA1782 KLAS KDTW Enroute 0005
AAY3185 KLAS KATW Enroute 0115
BAW1014 KLAS KSFO Enroute 1354
UAL523 KLAS KSFO Enroute 0906
NASA807 KLAS KSFO Enroute 0953
UAL505 KLAS KSFO Enroute 1007

Arrivals (6)

Callsign Dep Arr Status ETA
DAL711 KATL KLAS Enroute 0946
SWA4111 KSAN KLAS Enroute 1632
DAL324 KLAX KLAS Enroute 1535
DAL319 KDEN KLAS Enroute 1600
ASA612 KSEA KLAS Enroute 1607
CFG062 EDDF KLAS Departing

Las Vegas 13
  • Flights To/From ZLA: 86
  • Flights in ZLA Airspace: 33
  • Controller Schedule

    August 3rd, 2026

    Socal Approach (Combined)
    Jerome Sudhakar

    OTS with CH

    1830 - 2000 PDT / 0130 - 0300 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!