Hello everyone,

it's just a few months that I'm using the Navigraph data for my payware planes (wilco e-jets and 737) and I'm having some doubts about it.
Sometimes happens that my plane aren't able to get the localizer signal and to perform an ILS landing and I need to land manually: I always thought it was a problem of the planes (since wilco says there are some compatibilities issues when not using Win7 https://freedownload.s3.amazonaws.com/W8_1.pdf), but today I realized that could be something else.

I update the database to cycle 1912 and performed a flight KSLC - KSAN: landing was on runaway 09 with the localizer frequency 111.55 (ILS Y or LOC Y RWY 9). 
After tuning NAV 1 and NAV 2 to 111.55, the plane wasn't able to get the LOC signal (and follow the G/S), therefore I had to land manually, again. After arriving to the gate, I opened the FSX map and checked the default ILS frequency: it was completely different from the one reported on the Navigraph ILS chart and, after changing NAV1/NAV2 to that value, the plane got the LOC signal!

Therefore, do I need to update the FSX database too, after I update the FMC database?

NAV frequency from Navigraph: https://imgur.com/a/GeSGJZd

NAV frequency from FSX: https://imgur.com/a/IEZBIGH

That is the downside of using real world, up to date FMC data.
The data in the scenery .bgls must match the FMC data..
The scenery .bgls have the control of the actual radio transmitter, not the FMC data.
You could try this - https://www.aero.sors.fr/navaids3.html 

Another solution is to use updated AFCADs or Scenery for the airport you're flying to/from.  There are free AFCAD updates and freeware scenery available for a great many airports. Also note that for the vast majority of airports the LOC/ILS Frequencies remain the same.

Best wishes!

 

 

10 hours ago, spokes2112 said:

The scenery .bgls have the control of the actual radio transmitter, not the FMC data.
You could try this - https://www.aero.sors.fr/navaids3.html 

I suspected this, but I wasn't sure how to fix this issue.

 

9 hours ago, DaveCT2003 said:

Also note that for the vast majority of airports the LOC/ILS Frequencies remain the same.

And I think this happens where my planes get the LOC/ILS signal correctly 🙃

Thank you very much for your help.

Well, it's a choice between pest and cholera, since the in-game dataset doesn't match real world conditions in many cases. If the ILS frequencies have changed, your best bet is to find out what the original frequency was and then entering it manually into the FMS. The other possibility is - as others have mentioned - to update the ingame dataset.

Because of this, Navigraph is less useful for FSX/FSX-Steam users, especially if you don't fly online.

On 11/7/2019 at 4:15 PM, spokes2112 said:

That is the downside of using real world, up to date FMC data.
The data in the scenery .bgls must match the FMC data..
The scenery .bgls have the control of the actual radio transmitter, not the FMC data.
You could try this - https://www.aero.sors.fr/navaids3.html 

I use these three every month:

https://www.aero.sors.fr/navaids3.html

-World Navaids Package

-ILS/Rwy Regional Updates

https://www.aero.sors.fr/navint.html

-Fixes update

 

Every January I also get the Magvar update

https://www.aero.sors.fr/navaids.html

 

I've never had a problem with the sim not matching FMC data with the above updates.  Enjoy.

I updated fsx and now there aren't problems anymore.
Thanks.

5 hours ago, Ricardo41 said:

especially if you don't fly online.

Not at the moment, but this is what I want to do soon. 

Edited November 11, 20196 yr by Mirach