Importing NG ROUTE Flight Plans into X-Plane 11 and 12

X-Plane reads flight plans in .fms format from its output folder. NG ROUTE generates these files with the airway fixes in the order shown in your nav log. Loading them correctly saves tedious manual entry in the MCDU or GPS.

Download and file placement

1. Click ↓ X-Plane 11 / 12 after creating a route.
2. Move DEP-ARR.fms into:
   • X-Plane 12: X-Plane 12/Output/FMS plans/
   • X-Plane 11: X-Plane 11/Output/FMS plans/

Keep the filename — you will type it without the extension in some aircraft.

ToLiss Airbus (A319/A320/A321/A340)

Open the MCDU INIT page. In CO RTE (company route), type the filename without .fms. The route loads into the active flight plan. Cross-check FROM/TO airports match your briefing.

Zibo 737

On the CDU RTE page, enter the route name in CO ROUTE and execute. Verify legs in the LEGS page before engaging LNAV on the runway.

Default Laminar aircraft

G1000 and generic FMS units use the flight-plan menu → Load/Import. Pick the file visually from the FMS plans directory.

Runways and procedures

NG ROUTE suggests runways from live METAR. Set departure and arrival runways in the MCDU/FMS — they are not always embedded in the .fms the way SIDs are in payware databases. Add SIDs and STARs manually if your navdata includes them.

Missing waypoints

Outdated AIRAC data causes NOT FOUND IN DATABASE messages. Skip the unknown fix and enter the next valid one; the aircraft flies direct between recognized points. Updating via Navigraph resolves most gaps.

Verification habit

After loading, scroll the LEGS or ROUTE page and compare the first and last five fixes to the NG ROUTE nav log. One transposed letter in manual entry causes hours of debugging; loading from file avoids that entirely.

See also the interactive import guide linked from the planner export panel for MSFS and Aerofly formats.