Learn how to update Prepar3D NAV data with Navigraph, map each aircraft correctly, verify the AIRAC cycle and fix common update failures.
To update Navigraph navdata in Prepar3D, close the simulator, use Navigraph FMS Data Manager to detect or manually map each supported aircraft or add-on, then install the selected AIRAC cycle. Restart Prepar3D and confirm the cycle on the aircraft FMC's IDENT or STATUS page. This does not normally update Prepar3D's base navigation database.
What does Navigraph actually update in Prepar3D?
Navigraph normally updates the separate databases used by supported add-on aircraft, gauges and flight-planning utilities. Prepar3D does not have one universal navdata folder which updates every aircraft and simulator function.
| Navigation component | Updated by FMS Data Manager? |
|---|---|
| Supported add-on aircraft FMC or FMS | Yes, when its exact data format and installation are mapped |
| Supported planning or avionics add-on | Yes, but it needs its own mapping |
| Prepar3D default GPS, map and ATC data | Normally no |
| Runways, ILS facilities and airport layouts stored in scenery | No |
This distinction explains why an updated FMC can contain a procedure or waypoint that Prepar3D's default GPS cannot find. AIRAC data is licensed material; our guide to legal AIRAC update options explains what may be obtained and shared legitimately.
Prepar3D Navigraph update procedure
- Identify every navdata user. List the add-on aircraft, avionics and planning tools that need the new cycle. Updating one aircraft format does not update the others.
- Back up custom entries. Preserve any user waypoints or manually edited files before replacing a database. Do not mix files from different AIRAC cycles.
- Close Prepar3D. Close the simulator, aircraft configuration tools and any planner that could be reading the database. An open file can cause an access error or incomplete installation.
- Open FMS Data Manager. Sign in with an account that has access to the required AIRAC cycle. For most Prepar3D-era formats, FMS Data Manager is the relevant Navigraph application; merely installing Navigraph Hub does not prove that a P3D aircraft has been updated.
- Scan for add-ons. Use the manager's scan or detection function. Check that each result names the correct aircraft or product, Prepar3D generation and installation path.
- Add missing mappings manually. Select the profile made for that particular add-on and point it to the location expected by the profile. Do not select the Prepar3D root folder unless the profile specifically calls for it. A non-standard aircraft location or multiple P3D installations often defeats automatic detection.
- Install the AIRAC cycle. Update every required mapping, wait for each entry to report completion, then restart Prepar3D. Load a fresh aircraft session so the avionics read the replacement database.
If the manager cannot find the aircraft at all, first confirm that it is installed and functioning in Prepar3D. Our Prepar3D add-on aircraft installation steps cover the package and path problems that commonly prevent detection.
How do I verify the new AIRAC cycle?
The reliable check is the cycle shown inside the aircraft, not the updater's completion message or the Windows file date.
- Open the FMC or FMS IDENT, STATUS or database information page.
- Confirm the four-digit AIRAC code and, where displayed, its validity period.
- Load a known departure or arrival and check that its waypoints appear in the expected order.
- Verify every separately mapped aircraft; two add-ons can display different cycles on the same Prepar3D installation.
Your flight planner should use the same cycle as the aircraft whenever possible. If you plan with Little Navmap, follow our guide to set up Little Navmap and check its databases; its Prepar3D scenery database and Navigraph procedure data are separate sources and can disagree.
Why does the FMC still show the old cycle?
An old cycle after a successful update usually means the manager wrote to the wrong copy of the add-on or the aircraft uses a different database format.
- Wrong Prepar3D installation: remove or correct mappings left from another P3D version or an old drive.
- Duplicate aircraft folders: identify which copy Prepar3D actually loads and map that installation.
- Unsupported avionics: some aircraft use proprietary, embedded or manually installed data that FMS Data Manager cannot replace.
- Files remained open: close Prepar3D completely, run the update again and reload the aircraft. A panel reload alone may retain cached data.
- Access denied: check folder permissions and security software before resorting to administrator mode. Confirm that the mapping is not pointing to a read-only or obsolete folder.
- Mixed database files: restore a clean backup and reinstall one complete cycle rather than copying individual files between aircraft.
If the FMC shows the correct cycle but a runway or procedure is absent, compare the AIRAC data with the installed airport scenery. The airport may depict an older runway designation, moved localiser or retired procedure; reinstalling the same FMC database will not correct that mismatch.
Can Navigraph update Prepar3D's default GPS and navaids?
Navigraph does not normally replace the scenery-based navigation facilities used by Prepar3D's default GPS, map and ATC system. Those facilities are stored with the simulator world and scenery rather than in an add-on aircraft's FMC database.
For procedure-based flying, keep the aircraft and planner on the same AIRAC cycle and treat scenery discrepancies separately. If the simulator-level navaids or airport layout must change, use a Prepar3D-compatible scenery or navigation-facility update from a trusted source, preserve a backup and observe scenery priority. Never copy an aircraft navdata package into Prepar3D's scenery folders.