I just subscribed to Navigraph to update the “NAV DATA OUT OF DATE” issue with the FMS. I was able to installed all the tools and upgrade but “NAV DATA OUT OF DATE” is still showing on the FMS. The X plane path is correct. I can also see the file “cycle_info” created in the “Custom Data” folder with the new valid date (10/JUL/2025 - 07/AUG/2025).
Hi,
Please can you upload the x-plane_install_12.txt file in your %localappdata% folder?
Thank you very much,
Richard
Thank you Richard for the quick respons.
Where can I find this file “x-plane_install_12.txt” to upload to “%localappdata%”?
Hi again,
Open the file explorer and copy and paste %localappdata% into the folder line, pressing Enter. Scroll down, and you will find the file x-plane_install_12.txt. Please upload this file here. Thank you!
Cheers,
Richard
Not a Navigraph issue. Here’s what’s happening:
This file is taking precedence over Navigraph-installed data. See:
Regards,
Tim
1 Like
Tim is right. Thank you Tim for your help! Great finding … good stuff, thank you very much!
Cheers,
Richard
Thank you for the update. What should I do? Should I remove this file “earth_424”
Yes, then Navigraph data should be used instead of it.
Regards,
Tim
Thank you for the GREAT Support!!!
Also, you probably got this file using erroneous instructions such as those:
If you read the official documentation (and provided I understand it correctly), you can use the FAACIFP file but don’t actually have to (and shouldn’t) rename it:
The file
- FAACIFP18
must be located in $X-Plane/Custom Data/
This file is not shipped with X-Plane but can be obtained from the FAA website free of charge.
With the non-renamed file, the terminal procedures and related records for the specific airports covered by the FAACIFP18 file will override Navigraph data, but the rest of the database will still use Navigraph data.
There is a caveat:
Note that for integrity reasons, the cycle number of the FAA data must always match the cycle number of the underlying layer. Terminal procedures do reference waypoints out of the terminal area, therefore, the data source for global waypoints must be at the same cycle number.
So you would have to update the FAACIFP18 file manually with each cycle; also, Navigraph’s database already contains up-to-date records for the entire world so as far as I can tell, this makes the override in question a bit pointless.
Since this is getting a bit complex, I would like to please ask @PhilippM to possibly chime in just to make sure I understand it correctly?
Regards,
Tim
Edit: making progress (wish I had figured it out before posting, but better late than never).
Because of:
Note that for integrity reasons, the cycle number of the FAA data must always match the cycle number of the underlying layer. Terminal procedures do reference waypoints out of the terminal area, therefore, the data source for global waypoints must be at the same cycle number.
This makes the override only usable when the global waypoints are already updated (and in turn, makes it unnecessary in most cases as a side-effect).
The instructions at the beginning of the post make it possible to have up-to-date data for the US for free (at the expense of having little to no data for the rest of the world); but since you have a Navigraph subscription, you no longer need this hack (and it’s actually interfering with global navdata updates, hence the need for the file to be removed).
Thank you for the support!!!. It is updating now after removing the file.
1 Like