I am using the analog C172, and am not using Navigraph. I tried recently to make a flight without the GPS, navigating from VOR to VOR. The VOR gauges are not responding to VOR signals and I am wondering if it has anything to do with AIRAC data?
I am not too familiar with AIRAC stuff, so I am a bit naive here. But should the VOR station data not be part of MSFS? How do I load it so the required data is available? As far as I know, they used to work and I have never used Navigraph so I expect they should work now.
I have read several threads similar to this and they all say something about Navigraph. I say again, I am not a Navigraph customer and would just like to fly the plain, vanilla version of MSFS.
And yes, I have the NAV/GPS set to NAV mode. And yes, I can tune an ILS and see the gauges move, but not a VOR. There are several VORs within say 50nm, and none of them respond with movement of the dials. I can receive their DME info, but no movement on the dials.
Hi @tumbiT
One thing I’d double check is that the site you’re trying to capture is actually a VOR in the sim. There are quite a few “VOR icons” that are “DME only”, which reflects the real life fact that many VOR sites are closing down the guidance part of the site, but may leave DME working (you can see if they’re DME only by clicking on the icon in the world map and seeing what they information box says about the site). Can you list a few of the VOR’s you’re having problems with and I’ll try to recreate the issue and see if we can resolve it.
Regards
VOR’s work. However to isolate your particular issue we would need the VOR’s in question, the frequencies you used and where you were located in relation to the VOR at the time of issue.
This could be a few things. As already said here not all stations are VOR’s and may only have DME but no bearing info. BTW 50nm would be out of range for a terminal VOR of which there are several in the sim. These typically max out around 35nm.
Just double checking you know VOR is line of sight and stations can have different range/distance , depending on type.
Using the most current nav data is crucial also. If a vor has been decommisioned, it will not be availble in msfs ( or won’t be as soon as nav data is updated in msfs monthly).
This Navcanada sight is a great example showing vor closures, by date
Ahhh, that answers one question I had. You say MSFS updates it’s NAV data monthly?
One VOR I was checking is Sydney YSSY 112.1 and also Williamtown YWLM 113.3. It is a while since I used them but they USED to work. Maybe my MSFS is OK and they have been decommissioned?
Thanks mate. I just expected them to work and jumped to the conclusion there was something wrong here. There are other “VORs” that are not working too, but they are probably more decommissioned sites? I should have done more homework before posting.
Thank you all for your civilised replies. Sorry to have taken your time.
I’m going to try again, because things keep changing with a refresh…
The facility at YSSY is a DME only currently it appears.
The facility at YWLM is a TACAN only now (not a VORTAC), so you won’t get a signal from it.
Regards
It’s still possible that there are VOR’s that aren’t working right, so if you do run across one after checking the WM, let us know and we’ll see if we can find the issue.
No Worries!
You have a Great Christmas, too!!
Regards
I’d suggest downloading Little NavMap. Once you’ve done that, turn off the AIRAC data from the menus and let Little NavMap import the MSFS data from your game. That’ll show you what’s working in the game and what isn’t. You can also right-click on any navaid and turn on its range circle. Then you’ll be able to see from the map whether you should be within range of that navaid.
We are still having this problem today. I have just flown Block island (KBID) to Quonset RI (Koqu) using the Sandy bay vor SEY 117.5 MHz. Norwich vor ORW 110.0 MHz and the Providence vor PVD 115.6 MHz.
All within range but only The SEY vor activated the VOR1 gauge. The other two gave correct dme but no guidance.
Hi @MuchTeacher3243
Sorry you’re having issues.
I tried locking those problematic VORs in both the TBM 930 and the 172Garmin, and as you can see from the screenshots, both VORs provided both DME and guidance information.
I’m using the standard Sim navdata. Are you using any outside navdata information?
Regards
