ZLA Logo
Who's Online
Online Controllers

No controllers online

Flights to/from ZLA

Departures (13)

Callsign Dep Arr Status ETA
HVN99 KLAX VVTS Enroute 2053
UAL9618 KLAX MPTO Arriving
AFR216 KLAX KJFK Enroute 2009
ASA149 KLAX PANC Enroute 1312
UAL2277 KLAX KORD Enroute 2114
GTI832 KLAX KMEM Enroute 2124
UAL1165 KLAX PHKO Enroute 0441
ASA545 KLAX PHLI Enroute 0555
KLM604 KLAX EHAM Enroute 0447
UAL917 KLAX NZAA Arriving
AAL459 KLAX KDFW Enroute 2200
UAL608 KLAX CYVR Enroute 1600

Arrivals (10)

Callsign Dep Arr Status ETA
LOT21 EPWA KLAX Enroute 0519
LOT21E EPWA KLAX Enroute 0507
SWA3401 KSAT KLAX Enroute 0548
UAL552 KSFO KLAX Enroute 2340
SWA232 KLAS KLAX Enroute 1600
DAL1876 MMSD KLAX Enroute 0505
UAL2339 KLAS KLAX Enroute 0719
ASA7332 KJFK KLAX Departing
SPK248 PHNL KLAX Enroute 0653
SWA2765 KDEN KLAX Enroute 1600

Los Angeles (SoCal) 23

Departures (1)

Callsign Dep Arr Status ETA
UPS2907 KONT KSDF Enroute 2206

Empire (SoCal) 1

Departures (4)

Callsign Dep Arr Status ETA
BAW96R KSAN MZBZ Enroute 2052
AAL2743 KSAN KDFW Enroute 2010
DAL4134 KSAN KSFO Enroute 1044
JBU620 KSAN KBOS Enroute 0812

Arrivals (2)

Callsign Dep Arr Status ETA
UAL231 KIAD KSAN Enroute 0850
BAW23BV PHNL KSAN Enroute 0336

San Diego (SoCal) 6

Departures (1)

Callsign Dep Arr Status ETA
WAT1820 KSNA KDEN Enroute 0509

Arrivals (1)

Callsign Dep Arr Status ETA
N27Y KSLC KSNA Enroute 1507

Coast (SoCal) 2

Departures (3)

Callsign Dep Arr Status ETA
EJA429 KBUR KPDX Enroute 0825
N2022J KVNY KAUS Enroute 1600
FDX1273 KBUR KASE Enroute 1600

Burbank (SoCal) 3

Departures (7)

Callsign Dep Arr Status ETA
NKS2228 KLAS KPDX Enroute 1719
NKS2252 KLAS KCLT Enroute 2239
SWA232 KLAS KLAX Enroute 1600
N738DC KLAS KTPA Enroute 2251
UAL2339 KLAS KLAX Enroute 0719
SWA10 KLAS KBLI Enroute 1600
UAL3016 KLAS KORD Enroute 2233

Arrivals (5)

Callsign Dep Arr Status ETA
UAL255 KAUS KLAS Enroute 0658
SWA2471 KMSY KLAS Enroute 0600
JANET4422 KPAE KLAS Enroute 0453
ECHEL KMEE KLAS Enroute 1341
UAL679 KEWR KLAS Enroute 0737

Las Vegas 12
  • Flights To/From ZLA: 47
  • Flights in ZLA Airspace: 21
  • Controller Schedule

    November 26th, 2022

    Socal Approach (West)
    Dylan Keetle

    Session with BB

    1330 - 1500 PST / 2130 - 2300 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)
    • [email protected] 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!