Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Question on ATIS frequency

Featured Replies

Dear All,Happily enough, I can see that most of the frequencies published on the NDAC charts are working perfectly in FSX, namely the ground stations and the ATIS frequencies. To my understanding, the ground stations should be tuned on the VHF NAV radio, while the ATIS frequency should be tuned on the VHF COM radio, which both of them operate on same type of waves (VHF) but in different ranges (although quite near to each other).Now, while preparing to descent to Larnaca (LCLK), I should be tuning ATIS on the VHF COM radio to hear about the weather and available runways for landing. I do that using the VHF COM 2 radio. The chart - for some reason - says that the ATIS frequency is 112.8, which seems like a NAV frequency that cannot be tuned on the COM radio.Even when I tried to tune it on the NAV radio, while turning on the NAV speaker, I get nothing except the MORSE audio code of the LCA station which has the same frequency 112.8!!!Anybody got a clue on how this should be handled with radios?

a few years ago, they started using the lower part of the freq range for ATIS as well as nav aids, unfortunate this is one of the problems with FSX it is unable to go thet low

Dave

  • Author

So in real world, if I tube 112.8 on NAV while turning on the NAV speaker, I would get the ATIS instead of the Morse code? What about the Morse then?

its a problem with FS, real world you would just get the ATIS

Dave

  • Author

And how in real world I get to listen to the Morse? I think it is essential to verify the Morse against the station name.

This topic is the reason for the V B R selector on the audio control panel. If you want the her the Voice, select V, morse code R (voR) or Both.

And how in real world I get to listen to the Morse? I think it is essential to verify the Morse against the station name.
Technically, the letters displayed on your ND suffice for identification.

Matt Cee

So in real world, if I tube 112.8 on NAV while turning on the NAV speaker, I would get the ATIS instead of the Morse code? What about the Morse then?
no you'd put 112.8 into the com radiomitch bowman

Mitch Brown

Private Pilot | Aerospace Engineering Major

no you'd put 112.8 into the com radiomitch bowman
Try your suggestion and let us know how it turns out.

Matt Cee

Maybe I will talk a little bit about technik if you don't mind. At 107.900 MHz the radio broadcast frequencies end and at 108.000 MHz the VOR frequencies beginn. At 118.000 MHz the COM frequencies beginn. Unlike NDBs the VORs frequency spectrum is practically not affected by weather or other electromagnetic waves. The electromagnetic waves in the frequenzy range of the VOR travel optically. This means when your line of sight to the VOR is disturbed by something like a mountain or the ground itself (we remeber, the earth is a ball...) we can't recive the VOR. A VOR is theoretically nearly unlimited in range, however our passenger aircraft are too low to notice that. The range of the VOR depends unlike the range of the NDB only onto the recievers altitude. A little formula to finde out the VOR range is:Range [NM] = 1.23 * square root of (altitude [ft]) At 40.000 ft we can calculate that the range of the VOR is arround 246 NM. It is the same thing with the COMs. Yesterday after touch and go from EDNL we turned back to LOIH. As we where at the frequency of EDNL we heard a aircraft wich took of right behind us. We listened to them and as we changed to Munich Information the other aircraft did the same. We heard the pilot talkin to Munich Information and we heard Munich Information answer, however than they changed to Munich Radar. We did the same to listen to them. And now we heard the other aircraft again. However from our point of view the pilot keept a monolog. At least it seemed so. Ofcourse the reason for that, that nobody answered that we were just too low (3500 ft) and our distance to the COM beacon was just to large to Munich Radar. Okay, no back to the VORs. As the airspace got more croudy every day we started to run out of COM frequencies. However some clever people knew that a VOR isn't any thing else than a normal COM beacon with some handy dandy features. And so the idea was born to play the ATIS on those some of those frequencies. You tune the VOR on your NAV frequency pannel (you can't tune it into the COM pannel) and normaly than you would do the same as you would do when you want to listen to the identifier and you can hear the ATIS.I hope I was able to make some things more clear. Best regards,Jonathan

John Rubens
PMDG_ngx_T7_sig.jpg

Also remember that FSX is using very OLD information and thus the frequencies in your charts will not always match up to whats in FSX

Gary Tekulsky

Thank you for that, Jonathan — you have answered a question I always wondered about! :Party:Cheers,Brian

spacer.png

 

 

Just to clarify/reiterate:Look at your ACP, your Audio Contrrol Panel. You'll see a V-B-R selector. If your are listening to a navaid and want to hear the Voice saying the ATIS, you select V. R is so you can hear the morse code of the navaid or Range, and B is to hear Both. ATIS isn't the only info transmitted over navaids. In the States toy can hear HIWAS, VOMETs, listen to FSS, etc.

Matt Cee

  • Author

Thank you very much guys for the comprehensive responses. This was pretty useful.

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.