Fix a Navigraph flight plan not loading in X-Plane 12: correct .fms format and folder, AIRAC mismatches, missing procedures and add-on FMS issues.
Navigraph flight plans usually fail in X-Plane 12 because the wrong export format or folder is used, the simulator and aircraft have different AIRAC cycles, or a third-party FMS expects its own route format. Export an X-Plane .fms file to Output/FMS plans, then load it through the aircraft’s FMS.
How do I load a Navigraph flight plan correctly?
- Export the X-Plane format. Choose the X-Plane
.fmsexport. In some Navigraph tools, the compatible option may be labelled for X-Plane 11; X-Plane 12 can read that standard format. A PDF, route string, Microsoft.plnfile or another aircraft’s company-route format will not work in the standard X-Plane loader. - Check the destination folder. For X-Plane’s standard GPS and FMS units, save the file in
X-Plane 12/Output/FMS plans/. Make sure it has not gone into an older X-Plane installation, a second copy of X-Plane 12 or a similarly named folder. - Verify the extension. The filename must end in
.fms, not.fms.txt. Operating systems that hide known extensions can make this mistake difficult to spot. - Load it from the cockpit avionics. Open the aircraft’s flight-plan catalogue, route page or co-route function and select the saved plan. If the aircraft was already running when the file was copied, refresh the list or reload the aircraft.
- Match the navigation data. Check that X-Plane, the aircraft and the Navigraph-generated route use compatible AIRAC data. Updating only one of them can leave procedures or waypoints unavailable.
- Check the aircraft documentation. A custom FMS may require a different export profile, folder or import method. Renaming another format to
.fmsdoes not convert it.
For the standard folder structure and cockpit import sequence, see our X-Plane 12 flight-plan creation and loading walkthrough.
What does each loading problem mean?
| Symptom | Likely cause | What to check |
|---|---|---|
| Plan is absent from the list | Wrong folder, installation or extension | Confirm Output/FMS plans and inspect the complete filename |
| Invalid waypoint or route error | AIRAC mismatch or unsupported waypoint | Compare the navigation-data cycles and rebuild unavailable legs |
| Only the en-route section loads | Procedure mismatch or aircraft import limitation | Enter the SID, STAR and approach in the cockpit |
| Plan works in a default aircraft but not an add-on | Aircraft-specific format or database | Use that aircraft’s export target and documented import method |
| Route appears in Navigraph but not the cockpit | The chart display and aircraft FMS are separate | Export the route or use an integration explicitly supported by the aircraft |
Why are waypoints, SIDs or STARs missing?
Missing fixes and procedures usually mean the route was created against different navigation data from the database being read by the aircraft. The same identifier can also change between cycles, while a procedure may be renamed, withdrawn or tied to a runway unavailable in the installed data.
Install Navigraph data into the actual X-Plane 12 directory, then check whether the add-on aircraft maintains its own separate database. Our Navigraph installation and navdata guidance covers that setup. Do not edit the AIRAC number in the file merely to make it match; changing the header does not add missing waypoints.
If the en-route legs load but the departure or arrival does not, select those procedures manually in the cockpit using the installed database. This is often the cleanest solution because runway and transition choices can change. We cover the specific failure points in our SID and STAR compatibility checks.
How can I tell whether the aircraft is the problem?
Load the same .fms file in a default X-Plane aircraft fitted with a standard GPS or FMS. If it appears there, the file and standard folder are valid; the add-on’s importer, route format or private navdata installation is the likely cause.
Custom airliners may accept only their own company-route format, import only the en-route portion, or require the route to be transferred through an EFB or aircraft-specific function. Follow the aircraft’s documented method rather than forcing the standard file into an unrelated folder.
Why is the route visible in Navigraph but absent from the FMS?
A route displayed in Navigraph Charts or an in-simulator chart panel is not automatically inserted into the aircraft’s avionics. The chart layer, moving map and cockpit FMS can operate independently. Unless that particular aircraft supports direct route transfer, export the correct file and import it through the cockpit.
What if the plan loads but the autopilot ignores it?
That is a guidance problem rather than a file-loading problem. Confirm that a leg is active, the CDI or navigation source is set to GPS/FMS rather than a radio source, there is no route discontinuity, and NAV mode has captured the course. Garmin users can follow our G1000 active-leg, GPS-source and NAV-capture checks.