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

Departures (14)

Callsign Dep Arr Status ETA
QFA96 KLAX YMML Enroute 2351
UAL39 KLAX RJTT Enroute 0452
AAL136 KLAX EGLL Enroute 0456
UAL1069 KLAX KORD Arriving
ASA1451 KLAX KPAE Enroute 0549
AAL285 KLAX PHNL Enroute 0856
JBU2985 KLAX KMIA Enroute 0142
DAL890 KLAX KSAT Enroute 0028
DAL220 KLAX KSEA Enroute 1048
UAL0608 KLAX PHNL Enroute 0838
SKW3755 KLAX KSMF Enroute 1127
AAL4660 KLAX KLAS Enroute 1600
DAL233 KLAX PANC Enroute 2042
DLH457 KLAX EDDF Enroute 1600

Arrivals (28)

Callsign Dep Arr Status ETA
KAL8203 RKSI KLAX Enroute 0757
QFA153 EGKK KLAX Enroute 1429
DAL2145 EGLL KLAX Enroute 1456
SWA1021 PHNL KLAX Enroute 0716
UAL1400 KSEA KLAX Enroute 0823
NRT687 PHNL KLAX Enroute 1600
SWA2695 KSLC KLAX Enroute 0123
SWQ1814 KPHX KLAX Enroute 1600
DAL1695 KSEA KLAX Enroute 0856
DAL500 KATL KLAX Enroute 1027
DAL4385 PHNL KLAX Enroute 0841
ASA1453 KLAS KLAX Enroute 0939
SWA535 KFAT KLAX Enroute 0447
UPS12 KATL KLAX Enroute 1018
SUR4155 KMCO KLAX Enroute 0949
UPS51 KLAS KLAX Enroute 1450
CPA2084 PANC KLAX Enroute 1226
DAL6312 KSAN KLAX Enroute 1235
UAL2679 KEWR KLAX Departing
SCX2807 KSAN KLAX Enroute 1946
DAL1143 KIAH KLAX Enroute 0721
UAL1221 PHNL KLAX Enroute 0634
JBU943 KRNO KLAX Enroute 1241
AAL514 KPHX KLAX Enroute 1600
UAL611 KDEN KLAX Enroute 1600
DAL314 KATL KLAX Departing
JBU2735 KSFO KLAX Enroute 1600
ASA1391 MMLT KLAX Enroute 1600

Los Angeles (SoCal) 42

Departures (1)

Callsign Dep Arr Status ETA
FDX3072 KONT KOAK Enroute 0948

Arrivals (3)

Callsign Dep Arr Status ETA
UPS1006 KPHX KONT Enroute 0316
UPS560 KMSP KONT Departing
UPS921 KOAK KONT Enroute 2321

Empire (SoCal) 4

Departures (11)

Callsign Dep Arr Status ETA
AAL1950 KSAN KPHX Enroute 1222
UAL1660 KSAN KORD Enroute 0057
SWA5721 KSAN KDEN Enroute 0826
SWA738 KSAN KSAT Enroute 0103
N4480W KSAN Enroute 1600
N39ZP KSAN Enroute 1600
N32AB KSAN KL35 Enroute 1712
DAL6312 KSAN KLAX Enroute 1235
SCX2807 KSAN KLAX Enroute 1946
DAL9551 KSAN KBUR Enroute 1600
N586LS KSAN KLAS Enroute 1600

Arrivals (11)

Callsign Dep Arr Status ETA
WWA1103 KSEA KSAN Enroute 1600
UAL1281 KDEN KSAN Enroute 1106
DAL947 KATL KSAN Enroute 0953
UPS922 KSDF KSAN Enroute 1600
FDX587 KSJC KSAN Enroute 0516
SWA1260 KOAK KSAN Enroute 0748
ETD2945 CYVR KSAN Enroute 0940
NKS741 KLAS KSAN Enroute 1025
SWA2627 KSCK KSAN Enroute 0805
N252RP KSAN KSAN Enroute 1600
DAL2614 KMCO KSAN Departing

San Diego (SoCal) 22

Arrivals (2)

Callsign Dep Arr Status ETA
N33ZF KORD KLGB Enroute 0945
SWA3782 KDAL KLGB Enroute 1012

Coast (SoCal) 2

Departures (4)

Callsign Dep Arr Status ETA
VXP117 KBUR KEUG Enroute 1306
SWA2170 KBUR KLAS Enroute 0801
SKW456 KBUR KSLC Enroute 1600
NKS597 KBUR KOAK Enroute 1600

Arrivals (3)

Callsign Dep Arr Status ETA
UPS914 KSDF KBUR Enroute 1019
UAL617 KDEN KBUR Enroute 1738
DAL9551 KSAN KBUR Enroute 1600

Burbank (SoCal) 7

Departures (1)

Callsign Dep Arr Status ETA
AAL2425 KPSP KDFW Enroute 0007

Arrivals (3)

Callsign Dep Arr Status ETA
WJA1474 CYYC KPSP Enroute 1600
SWA5203 KLAS KPSP Enroute 1754
WAT3972 KDEN KPSP Enroute 1139

Palm Springs (SoCal) 4

Departures (13)

Callsign Dep Arr Status ETA
SWA3176 KLAS KBLI Enroute 1600
NKS510 KLAS KSMF Enroute 1600
ASA725 KLAS KSEA Enroute 1928
UAL751 KLAS KIAH Enroute 0034
MXY291 KLAS KSEA Enroute 1340
UAL1051 KLAS KIAH Enroute 0030
SWA799 KLAS KAUS Enroute 0037
VXP219 KLAS KSLE Enroute 1009
ASA1453 KLAS KLAX Enroute 0939
NKS741 KLAS KSAN Enroute 1025
UPS51 KLAS KLAX Enroute 1450
SWA5203 KLAS KPSP Enroute 1754
N52LM KLAS KGPI Enroute 1125

Arrivals (8)

Callsign Dep Arr Status ETA
UPS186 KPHX KLAS Enroute 1600
DAL1544 KOKC KLAS Enroute 1032
ROU1701 CYYZ KLAS Enroute 1153
SWA2484 KRNO KLAS Enroute 0946
AAL4660 KLAX KLAS Enroute 1600
SWA2170 KBUR KLAS Enroute 0801
MTN324 KICT KLAS Enroute 1009
N586LS KSAN KLAS Enroute 1600

Las Vegas 21

Departures (1)

Callsign Dep Arr Status ETA
N316PR KNYL KFHU Enroute 0626

Yuma 1
  • Flights To/From ZLA: 103
  • Flights in ZLA Airspace: 44
  • Controller Schedule

    April 14th, 2024

    Lindbergh Tower
    Braden Thompson

    Session with NS

    1800 - 1930 PDT / 0100 - 0230 Zulu

    Tips on Recording Your ATIS

    In an effort to assist those of you guys looking to record your ATIS with a bit of a more professional flavor, I'm going to include some tips for how to properly translate the METAR to voice format and make it sound a bit more realistic.

    I had taken the time to write some detailed ATIS policies for airports in Chicago during my time there and have spent a considerable amount of time listening to actual ATIS recordings and reading up on how to properly record them.

    This is just to help those of you guys out, like myself, who strive for that ultimate perfection while you control . I've tried to dumb this down a bit for VATSIM applicability - feel free to review the links I've posted to delve further in depth at your discretion!

    Let's start by taking an example ATIS to work with:

    KLAX 281750Z 24006KT 10SM SCT250 33/M03 A2995 RMK AO2 SLP141 T03281033 10339 20206 51003

    First portion of the ATIS, a decoding of the METAR and how to pronounce the parts of the coding while recoding. I have broken this down into 12 parts to explain a bit about each.
     

    1. The beginning of your ATIS should begin with the official facility name of the airport you are working, followed by the current information code. KLAX 281750Z 24006KT 10SM SCT250 33/M03 A2995 RMK AO2 SLP141 T03281033 10339 20206 51003.

      For instance, with Los Angeles, it should read as follows:

      "Los Angeles International Airport information CHARLIE" - the full facility name can be found on the charts of the airport as well as in an airport facility directory or airnav.com (or some other airport information sites). Replace CHARLIE with the current ATIS code, whatever that may be, via stating the appropriate letter in the aviation phonetics format (ie: ALPHA, BRAVO, CHARLIE, DELTA, etc...). For the purpose of VATSIM, it does not make a difference what letter you begin on or when (when you log in to control) - just ensure you follow up with the next letter in alphabetical order for the next update.
       
    2. Include the time of the observation in zulu. KLAX 281750Z 24006KT 10SM SCT250 33/M03 A2995 RMK AO2 SLP141 T03281033 10339 20206 51003

      "one-seven-five-zero zulu" - 1750z - pronouncing each digit separately at the time of the observation. The date (in the example above 28 ) should not be recorded in the ATIS. A routine observation is the normal time the ATIS is updated (for LAX, this is 50 minutes after each hour). A special observation occurs during adverse weather conditions and may be updated a number of times between routine observations. This should be stated as such when applicable "XXXX zulu special".
       
    3. Wind direction comes next, gusts shall be reported after wind as “Gusts XX” when applicable (replacing XX with the gust in the METAR). KLAX 281750Z 24006KT 10SM SCT250 33/M03 A2995 RMK AO2 SLP141 T03281033 10339 20206 51003 

      "wind two-three-zero at six" - Due to magnetic variation, here at ZLA we subtract ten degrees from the wind direction within the METAR to be more exact (as in this example). Note that there is only ONE wind. Stating "winds" is incorrect and a common mistake made by many. Gusts would be included right after the wind as "gusts XX" (not "gusting") replace XX with the Gust in the METAR where applicable (indicated by a G after the wind direction and speed).
       
    4. Visibility is next. KLAX 281750Z 24006KT 10SM SCT250 33/M03 A2995 RMK AO2 SLP141 T03281033 10339 20206 51003

      "Visibility one-zero" - Note this is ASSUMED to be in statute miles ALWAYS (SM) - no need to include "statute miles" in the recording itself. If visibility is listed as something like 1/4SM or 1 1/2SM it would be read, respectively as "visibility one-quarter" or "visibility one and one-half". If VVXXX (Vertical Visibility) is noted in the METAR, then “indefinite ceiling XXX” shall be included after the visibility is issued, replacing XXX with the height in feet. When the visibility is less than 7SM, included in the METAR will be the reason why (an obscuration) which should also be stated directly after the visibility in the ATIS (ie: "visibility five, mist"). There are many other factors for visibility beyond the scope of this discussion as well, but you can read up here on other types or reported visibility which can also be noted in the METAR here: http://www.met.tamu.edu/class/METAR/metar-pg7-vis.html 
       
    5. Clouds are next. KLAX 281750Z 24006KT 10SM SCT250 33/M03 A2995 RMK AO2 SLP141 T03281033 10339 20206 51003

      "Two-five thousand scattered" - report as applicable beginning with the lowest cloud layer. Few cloud layers should be read as “few clouds at XXXX.” Scattered, broken, or overcast cloud layers should be read as “XXXX scattered/broken/overcast.” The lowest broken/overcast layer constitutes a ceiling and must be reported as such within the ATIS, “ceiling XXXX broken” or “ceiling XXXX overcast.” Replace XXXX with the altitude in thousands of feet (EX: three-thousand or six-thousand five-hundred). If CLR is noted within the METAR, then issue the cloud report as “Clear below 12,000” as this is the maximum height the weather equipment is considered to be valid at Los Angeles International Airport (this is noted by the type of weather reporting equipment at the end of the METAR).
       
    6. Temperature and dewpoint. KLAX 281750Z 24006KT 10SM SCT250 33/M03 A2995 RMK AO2 SLP141 T03281033 10339 20206 51003

      "Temperature three-three, Dewpoint Minus three" - Note, again, that the digits are pronounced individually, not as whole numbers. This is for the sake of clarity. If you note an M in front of something, that is pronounced as "Minus" such as in this example METAR report.
       
    7. Altimeter setting. KLAX 281750Z 24006KT 10SM SCT250 33/M03 A2995 RMK AO2 SLP141 T03281033 10339 20206 51003

      "Altimeter two-niner-niner-five" - As above, each number pronounced individually, without the decimal as it is a given.
       
    8. The next portion of the recording shall include the advertised instrument approach(s) in use at the airport. The following list is an example of how this may be recorded:

      "Simultaneous ILS approaches in progress to runways 25L and 24R" 
      "ILS runway 9 approach in use" 
      "Localizer and visual approach runway 27 in use" 
      "V-O-R Alpha approach in use, circle to land runway 27" 
      "RNAV runway 6R approach in use" 


      Note that all runways shall be read out as individual numbers while recording (EX: 25L – Two-Five Left). Instrument approaches should always be listed prior to visual approaches in use - when applicable.

      Also, when applicable, LAHSO (Land and Hold Short Operations) shall be stated. "Land and hold short operations are in effect"

      Be sure to include the applicable LAHSO runways in use, stating the available landing distance for the LAHSO runway. (ie: "Runway 15 arrivals may be asked to hold short of runway 8 for landing traffic, available landing distance on runway 15 six-thousand, five-hundred feet"). The available landing distance is very important as the pilot needs to know the stopping distance he has and whether or not he/she can accept the restriction. 

      Additionally - when applicable, include RVR (Runway Visibility Range - during low visibility operations - ie: fog/mist) and any braking action reports - although this should also be issued to the pilot from approach and the tower in the landing clearance. 
       
    9. The departure and landing runways in use.

      "Departing runways 24L and 25R" 
      "Landing and departing runway 27" 


      Pretty self-explanatory - again, pronounce the runway numbers individually for clarity. 
       
    10. NOTAMs (Noticed To AirMen) that may apply to your airport.

      "Notices to Airmen, runway 25L closed" 
      "Airport closed to traffic pattern operations"
      "Parallel approaches in use between Los Angeles International Airport and Hawthorne Airport" 


      Anything else you can think of that may apply to the airport you are working... these are just examples. 
       
    11. The fifth section of the ATIS shall consist of the following to conclude the recording:

      "All departures contact [CURRENT CLEARANCE/DELIVERY POSITION AND FREQUENCY] prior to taxi" (or something to this tune so the pilot knows who to call for their clearance).

      "Read back all runway hold short instructions [and runway assignments]"

      "Advise controller on initial contact you have information [ATIS CODE]"
       (or again, something close to this tune works fine).

      This way the pilot knows to call you with the information. (and gives you a reason to instruct the pilot to listen to the ATIS when they don't call with it). 
       
    12. LASTLY (finally right?), and if you remember nothing else from this lengthy article, I ask you to PLEASE REMEMBER THIS PART!

      A pause must be included to clearly define the beginning and end of the ATIS for a period of three to five (3-5) seconds at the end of the recording to prevent an “endless recording” when pilots listen to the frequency (or what I like to refer to as the "endless ATIS recording of DEATH". 

     

    So, to sum up above, here is a typed version of what would be read for the ATIS recording on this METAR.

    "Los Angeles International Airport information CHARLIE, one-seven-five-zero zulu observation, wind two-three-zero at six, visibility one-zero, two-five thousand scattered, temperature three-three, dew-point minus three, altimeter two-niner-niner-five, simultaneous I-L-S and visual approaches in progress to runways two-five left and two-four right, departing runways two-five right and two-four left, parallel approaches in use between Los Angeles International Airport and Hawthorne Airport, read back all runway hold short instructions and runway assignments, all departures contact Los Angeles Tower one-two-zero point niner-five prior to taxi, advise controller on initial contact you have information CHARLIE (pause for 3-5 seconds)”. 

    All can be read within a period of about 30-45 seconds on average!

    I also took the liberty of creating an ATIS quick reference table:

    ATIS QUICK REFERENCE TABLE
     

    [OFFICIAL AIRPORT NAME] information [ATIS CODE] 
    (Time) - XXXXz observation/special
    Wind - XXX@YY
    Visibility - XX 
    (Sky Conditions) – XXX 
    Temperature – XX
    Dewpoint – YY 
    Altimeter – XXXX 
    ILS/VIS runway XX approach in use [Simultaneous approaches/LAHSO operations] Departing runways YY. 

    [INSERT NOTAMS AS APPROPRIATE] 
    Read back all runway hold short instructions [and runway assignement]. All departures contact [CURRENT CLEARANC/DELIVERY POSITION AND FREQUENCY] prior to taxi. 
    Advise on initial contact you have information [ATIS CODE].

     

    Keep in mind your ATIS must be in compliance with the VATSIM EC Global ATIS Policy in which it cannot exceed 1 minute in length (so, practice your recordings to get them done quickly!) and that the textual ATIS should still be in compliance with ZLA's policy found here:http://www.laartcc.org/operating_procedures/36/Requirements+for+Controllers+ATIS

    I have received many wonderful comments from pilots on having a clean-cut and professional sounding ATIS and I wanted to provide this information that has helped me attain this to you all to help further advance the professionalism of ZLA. 

    I hope this article helps some of you out! Feel free to comment and add in on anything I may have missed! Again, just trying to provide some assistance and further insight on the matter. Finally SX has written an excellent article about Decoding METARs.