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

Departures (38)

Callsign Dep Arr Status ETA
DAL65 KLAX NZAA Enroute 2327
ANZ5 KLAX NZAA Arriving
LAN603 KLAX SCEL Enroute 0143
QFA12 KLAX YSSY Enroute 0943
CAL15 KLAX RCTP Enroute 0740
BAW4E KLAX EGLL Enroute 0440
THY12E KLAX LTFM Enroute 1157
DAL2335 KLAX KBNA Enroute 2339
UAL451 KLAX KIAH Enroute 2330
FDX623 KLAX CYVR Enroute 1600
DAL2198 KLAX KMSP Enroute 0020
UAL1339 KLAX KDEN Enroute 0800
DAL38 KLAX KSAN Enroute 1600
QFA12A KLAX YSSY Enroute 1358
ASA138 KLAX KSFO Enroute 0941
UAL2019 KLAX KSFO Enroute 1026
AAL1589 KLAX KBOS Enroute 0101
VIR8Y KLAX EGLL Enroute 1013
UAL1168 KLAX KSFO Enroute 0907
ACA2016 KLAX CYVR Enroute 1112
DAL428 KLAX PHLI Enroute 0916
FDX1801 KLAX KOAK Enroute 0853
BAW47 KLAX EGLL Enroute 0124
QTR228 KLAX OTHH Enroute 1754
DAL9286 KLAX KIND Enroute 1600
BAW25K KLAX EGLL Enroute 0914
CSN328 KLAX ZGGG Enroute 1855
UAL1170 KLAX PHNL Enroute 0612
DAL986 KLAX KAUS Arriving
DLH453 KLAX EDDM Enroute 1600
SWA3888 KLAX KPHX Enroute 1600
SWA2125 KLAX PHKO Enroute 1600
DAL1080 KLAX KMEM Enroute 2341
UAL1832 KLAX PHNL Enroute 1600
UAL2711 KLAX PHLI Enroute 0841
DAL1231 KLAX KLAS Enroute 1600
DAE1245 KLAX KBOS Enroute 1600
SWA3713 KLAX KPHX Enroute 1600

Arrivals (37)

Callsign Dep Arr Status ETA
AAL137 EGLL KLAX Enroute 0905
BOX586 VHHH KLAX Enroute 1124
CSN439 ZSPD KLAX Enroute 1030
BOX500 VHHH KLAX Enroute 1056
AAL341 KJFK KLAX Enroute 0910
PAC1547 NSFA KLAX Enroute 0532
DLH456 EDDF KLAX Enroute 1613
AAL3 KJFK KLAX Enroute 0854
DAL908 KDTW KLAX Enroute 1023
DLH391 EDDF KLAX Enroute 1545
DAL2122 KMSP KLAX Enroute 0941
GTI2713 PANC KLAX Enroute 0959
SIA36 WSSS KLAX Enroute 1310
FDX1508 KMEM KLAX Enroute 0916
DAL40 YSSY KLAX Departing
DAL1691 KMSP KLAX Enroute 0935
GTI3512 VHHH KLAX Enroute 1331
CPA884 VHHH KLAX Enroute 1324
DAL301 KATL KLAX Enroute 0834
LOBO55 KSAN KLAX Enroute 1822
DAL14 NFFN KLAX Enroute 0532
FDX779 KSEA KLAX Enroute 1600
AAL306 KJFK KLAX Enroute 1044
AAL2031 KSEA KLAX Enroute 0958
FFT2090 KLAS KLAX Enroute 1600
N377WE KABQ KLAX Enroute 2316
FDX2006 KLAS KLAX Enroute 1600
UAL426 KSFO KLAX Enroute 1600
DAL118 KDEN KLAX Enroute 1756
FDX218 KSEA KLAX Enroute 0854
SKW3480 KBOI KLAX Enroute 1823
KAL011 RKSI KLAX Departing
DAL91 KATL KLAX Departing
DAL2914 KSEA KLAX Enroute 1600
AAL772 KSAN KLAX Enroute 1600
FDX204 KSEA KLAX Enroute 1600
DAL1511 KLAS KLAX Enroute 1600

Los Angeles (SoCal) 75

Departures (2)

Callsign Dep Arr Status ETA
HAL79 KONT PHNL Enroute 0706
SWA752 KONT KSJC Enroute 0927

Empire (SoCal) 2

Departures (11)

Callsign Dep Arr Status ETA
UAL005 KSAN EDDF Enroute 2325
ASA17 KSAN KBWI Enroute 0101
ASA1456 KSAN KSEA Enroute 1104
LOBO55 KSAN KLAX Enroute 1822
N66M KSAN KDAG Enroute 1600
DAL2006 KSAN KSLC Enroute 1600
FFT1470 KSAN KLAS Enroute 1600
N257MC KSAN KLAS Enroute 0239
SWA1966 KSAN KOAK Enroute 1600
AAL772 KSAN KLAX Enroute 1600
DLH2P KSAN EDDM Enroute 1600

Arrivals (8)

Callsign Dep Arr Status ETA
BAW82P EGLL KSAN Enroute 0936
DLH5RL EDDM KSAN Enroute 1233
DAL38 KLAX KSAN Enroute 1600
DLH466 EDDM KSAN Enroute 1332
ASA33 KOAK KSAN Enroute 0835
SWA1450 KMIA KSAN Departing
SWA2755 KMDW KSAN Enroute 0925
QXE2103 KSFO KSAN Enroute 0944

San Diego (SoCal) 19

Departures (2)

Callsign Dep Arr Status ETA
GEC9613 KLGB EDDF Enroute 0250
AAY238 KLGB KFAT Enroute 1020

Arrivals (4)

Callsign Dep Arr Status ETA
N329CC KSNA KSNA Enroute 1600
SWA2091 KRNO KLGB Enroute 1600
N312NW KTUS KTOA Enroute 1600
SWA914 KRNO KLGB Enroute 1600

Coast (SoCal) 6

Arrivals (8)

Callsign Dep Arr Status ETA
SWA156 KLAS KBUR Enroute 1600
SWA230 KLAS KBUR Enroute 1219
SKW213 KSTS KBUR Enroute 0835
TWA283 KSTL KBUR Departing
TWA321 KSTL KBUR Departing
N1202R KMRY KVNY Enroute 0004
N777DN KSDL KVNY Enroute 1600
TRS238 KSTL KBUR Departing

Burbank (SoCal) 8

Arrivals (2)

Callsign Dep Arr Status ETA
N517CF CYVR KPSP Enroute 0842
UAL717 KSFO KPSP Enroute 1710

Palm Springs (SoCal) 2

Departures (13)

Callsign Dep Arr Status ETA
FHV1124 KLAS KBNA Enroute 0256
AAY69 KLAS KSMX Enroute 1600
SWA1732 KLAS KABQ Enroute 1731
SWA156 KLAS KBUR Enroute 1600
SWA230 KLAS KBUR Enroute 1219
JANET33 KLAS KXTA Enroute 1600
UAL2047 KLAS KSFO Enroute 1600
FFT2090 KLAS KLAX Enroute 1600
FDX2006 KLAS KLAX Enroute 1600
BAW4LV KLAS EGLL Enroute 2205
N200JT KLAS KMFE Enroute 0104
N69U KLAS Enroute 0437
DAL1511 KLAS KLAX Enroute 1600

Arrivals (9)

Callsign Dep Arr Status ETA
ASA876 PHNL KLAS Enroute 0802
EJA853 KLIT KLAS Enroute 0945
N1AW KTUP KLAS Enroute 0921
UAL2236 KIAH KLAS Enroute 0945
PSA145 MMMY KLAS Enroute 0833
DAL305 KBIL KLAS Enroute 0940
FFT1470 KSAN KLAS Enroute 1600
N257MC KSAN KLAS Enroute 0239
DAL1231 KLAX KLAS Enroute 1600

Las Vegas 22

Arrivals (1)

Callsign Dep Arr Status ETA
AAL2143 KPHX KSBP Enroute 1317

Santa Barbara 1

Arrivals (1)

Callsign Dep Arr Status ETA
N1653F KBFL Enroute 1600

Bakersfield 1

Departures (1)

Callsign Dep Arr Status ETA
BOE403 KVCV KBFI Enroute 1600

Edwards 1

Arrivals (3)

Callsign Dep Arr Status ETA
AAY69 KLAS KSMX Enroute 1600
N5950E KSLC KSGU Enroute 0931
N66M KSAN KDAG Enroute 1600

Other 3
  • Flights To/From ZLA: 140
  • Flights in ZLA Airspace: 50
  • Controller Schedule

    April 5th, 2026

    Socal Approach (Combined)
    Matthew Goldsmith

    Session with ER

    1730 - 1900 PDT / 0030 - 0200 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!