Fix Navigraph crashing in MSFS 2024 by isolating Simlink, navdata and panel faults, removing duplicate packages and testing add-on conflicts.
Navigraph usually crashes in Microsoft Flight Simulator 2024 because an outdated or duplicated in-game panel or navdata package is loading, its Charts or Simlink installation is damaged, or another Community add-on conflicts with it. Update every component, remove legacy duplicates, test MSFS in Safe Mode, then reinstall Navigraph components one at a time.
Which part of Navigraph is actually crashing?
Navigraph is not one component, so the decisive first step is identifying whether MSFS, Charts, Simlink, the in-game panel or an aircraft integration is failing.
| Symptom | Likely fault | Best test |
|---|---|---|
| MSFS closes during startup or flight loading | Duplicate navdata or panel package, or a Community conflict | Start in Safe Mode or temporarily empty the active Community folder |
| MSFS crashes only when the Navigraph panel opens | In-game panel package, overlay or display-driver conflict | Uninstall only the panel and use the external Charts application |
| Navigraph Charts closes while MSFS keeps running | Charts application installation, security software or graphics issue | Launch Charts with MSFS and Simlink closed |
| The moving map stops but nothing closes | Simlink connection or permission problem | Check whether Simlink is running in the notification area |
| Only one aircraft crashes or freezes | Aircraft avionics integration or another aircraft package | Repeat the flight in a default aircraft |
A missing aircraft symbol or disconnected moving map is usually not a crash. It points to Simlink, its simulator connector or a blocked network process.
How do you fix Navigraph crashes in MSFS 2024?
The reliable fix is a clean baseline followed by a staged reinstall, rather than reinstalling the entire simulator immediately.
- Close every related process. Exit Microsoft Flight Simulator 2024, Navigraph Charts and Navigraph Hub. Also quit Simlink from the Windows notification area; closing its window may leave the background process running.
- Install available updates. Update MSFS 2024 first, then Charts, Simlink, Navigraph Hub and the affected aircraft. Do not let Hub change simulator packages while MSFS is open.
- Remove Navigraph packages through Hub. Uninstall the MSFS 2024 navdata and in-game panel components. Check that Hub is targeting the active MSFS 2024 package location rather than an old MSFS 2020 installation.
- Remove stale duplicates. Inspect the active
Communityfolder after using Hub and move any leftover Navigraph packages to a temporary backup location. Do not copy Navigraph folders from MSFS 2020 into MSFS 2024, and do not keep two packages that both replace simulator-wide navdata. - Test a clean simulator. Start MSFS in Safe Mode after the crash prompt, or temporarily move all Community packages elsewhere. Load a default aircraft at a default airport without Charts or Simlink running. If it still crashes, follow our Safe Mode and Community-package crash checklist; Navigraph may only have exposed an unrelated MSFS, driver or hardware fault.
- Reinstall one component at a time. Install navdata first and test a flight. Add the in-game panel and test opening it. Start Simlink last, followed by any aircraft-specific integration. The component that makes the fault return identifies the branch to repair.
- Check the failing branch. For Simlink, keep it and MSFS at the same Windows privilege level, normally standard user, and check security-software permissions using our Simlink process and connector troubleshooting. If only one complex aircraft fails, update that aircraft and isolate its packages; a reported module fault may require the steps for testing a suspected WASM conflict.
Can Navigraph navdata itself crash MSFS 2024?
An old AIRAC cycle normally causes procedure, runway or route discrepancies rather than a crash. A crash tied to navdata usually means the package is corrupted, duplicated, installed in the wrong MSFS library or conflicting with another simulator-wide navigation-data replacement.
Remove every competing simulator-wide navdata package, reinstall only the Navigraph package through Hub and confirm that Hub detects MSFS 2024 correctly. Our navdata installation and verification procedure covers the repair without disturbing unrelated aircraft and scenery.
Why does the Navigraph in-game panel crash but Charts works?
If external Charts works but opening the toolbar panel causes a crash to desktop, the panel package or something interacting with the simulator interface is the likely culprit. Remove and reinstall only that panel, then test it with a default aircraft and no recording, monitoring or graphics overlays.
A blank panel, endless sign-in screen or missing map is different from a crash. Those symptoms more often indicate authentication, connectivity or a blocked embedded interface. The external Charts application with Simlink is a practical temporary alternative while the panel remains uninstalled.
What should you avoid deleting?
Do not delete the simulator's Official packages, arbitrary application-data folders or the whole MSFS installation as a first response. The Rolling Cache stores streamed world data rather than AIRAC navdata, so clearing it is unlikely to repair a Navigraph-specific failure.
On Windows, Reliability Monitor can help establish what actually closed and at what time. A generic MSFS executable or graphics-driver fault does not prove Navigraph caused the crash; the clean-package test is stronger evidence.
What about Xbox and PlayStation 5?
The Hub, Simlink and Community-folder procedure is primarily for PC. Consoles do not expose the PC package folders, so update or disable the affected add-on through the simulator's own library controls, test a default aircraft, and treat a crash in Charts on a separate device as an independent application problem.