How do I program the FMS in X-Plane?
To program the FMS in X-Plane, power the avionics, enter the origin and destination, add route waypoints or airways, select departure and arrival procedures, check every leg, then activate and execute the route. Select FMS/GPS guidance and use LNAV or NAV; use VNAV only after completing the required performance data.
Which X-Plane FMS are you programming?
X-Plane does not have one universal FMS interface; the aircraft determines the pages, buttons and level of automation. FMS refers to the complete flight-management system, while FMC or CDU commonly describes the computer and keypad used to control it.
| Avionics type | How it is programmed | Main difference |
|---|---|---|
| Default Boeing-style CDU | RTE, DEP/ARR, LEGS and performance pages | Route changes normally require activation and EXEC |
| Custom airliner FMC | Aircraft-specific pages and procedures | May have its own route importer, performance model and navigation-data requirements |
| Garmin G1000 or GNS | Flight Plan, Procedures and direct-to controls | Uses GPS/VLOC source selection rather than Boeing-style LNAV logic; see our dedicated G1000 operating guide |
The following sequence applies most closely to the default Boeing-style FMS and similar airliner units. Page names may differ in detailed add-on aircraft, so do not force Boeing instructions onto an Airbus-style MCDU or Garmin panel.
How do I enter a route into the X-Plane FMS?
The reliable sequence is position, route, procedures, leg verification, execution and then performance data. Entering waypoints without completing those later stages can leave a route displayed but unusable.
- Supply electrical power. Start with the engines running or configure the battery, external power or APU as required by the aircraft. A blank CDU is usually an electrical-state problem, not an FMS fault.
- Initialise the position when requested. On aircraft that model position initialisation, enter the reference airport or copy the displayed GPS position into the required field. Detailed airliners may also require IRS alignment before navigation guidance becomes available.
- Enter the origin and destination. Open the route page and type the ICAO identifiers into the appropriate fields. Add the flight number and departure runway if the unit provides those fields.
- Build the en-route section. Enter direct fixes in the TO column. For an airway, enter the airway under VIA and its exit waypoint under TO. If route design or importing is the difficult part, use our route-building and import workflow for X-Plane 12 rather than guessing waypoint order.
- Select the departure and arrival. Use the procedure pages to choose the runway, SID, transition, STAR and approach that match the route and ATC clearance. Our explanation of selecting SIDs, STARs and transitions covers that procedure workflow in detail.
- Inspect every leg. Check waypoint names, track changes, distances and altitude constraints on the LEGS or flight-plan page. Duplicate waypoint identifiers are common, so use the region, coordinates or surrounding fixes to select the correct one.
- Resolve discontinuities deliberately. Join legs only when the route should be continuous. A discontinuity after a vector instruction can be intentional; deleting it blindly may create an unrealistic turn directly towards the next fix.
- Activate and execute the route. A Boeing-style CDU normally requires ACTIVATE followed by EXEC. Later edits remain modifications until EXEC is pressed; erasing the modification restores the previously active route.
- Complete performance pages if needed. VNAV-capable aircraft may require gross weight, reserves, cruise altitude, cost index and take-off data. Exact requirements depend on the aircraft. These entries are not normally needed merely to obtain lateral LNAV guidance.
How do I make the autopilot follow the FMS route?
Activate the route, make a sensible leg ahead of the aircraft active, select FMS or GPS as the navigation source where required, and arm LNAV or NAV. Loading a route alone does not command the autopilot to fly it.
- Confirm that the flight plan is active rather than shown as a temporary or modified route.
- Check that the first active leg leads forwards from the aircraft. Use direct-to for the next suitable fix if the FMS is trying to return to a waypoint behind you.
- Turn on the flight directors and use heading mode to establish a reasonable intercept with the magenta course if LNAV will not capture immediately.
- Arm LNAV or NAV and watch the flight-mode annunciator. The annunciator, not the illuminated button, shows which mode is actually controlling the aircraft.
- Use VNAV only after entering its required performance and altitude data. Keep the selected altitude controls configured as the aircraft expects; many systems will not climb or descend through a restrictive selected altitude.
For an ILS, the FMS can sequence the arrival and position the aircraft for the approach, but localiser and glideslope guidance normally require a tuned ILS, the correct course and APP mode. Some aircraft change from GPS/FMS to VLOC automatically; others require a manual source change.
Why is the FMS route not working?
Most FMS failures come from an unexecuted modification, the wrong navigation source, an unsuitable active leg or incompatible navigation data. These checks resolve the faults we see most often.
| Symptom | Likely cause and fix |
|---|---|
| Route is entered but LNAV does nothing | Press ACTIVATE and EXEC where applicable, select FMS/GPS guidance, then confirm that a forward leg is active. |
| Aircraft turns back after take-off | The active waypoint is behind the aircraft. Select a sensible forward fix with direct-to, verify the resulting path and execute it. |
| LNAV remains armed | The aircraft may be too far from the course or approaching it at a poor angle. Use heading mode to intercept, then arm LNAV again. |
NOT IN DATABASE or invalid waypoint | Check the identifier and navigation-data cycle. A flight plan made with newer data may contain fixes or procedures absent from the aircraft's database. |
| Route contains a discontinuity | Confirm whether it represents vectors or a genuine break. Close it only when the next leg should follow directly. |
| VNAV is unavailable | Complete the route and required performance entries, execute all changes and check the cruise altitude. The installed FMS may not model full VNAV. |
| Garmin displays the route but will not follow it | Check CDI source, OBS/SUSP state, active-leg selection and NAV capture using our checks for a G1000 that will not follow its flight plan. |
Can I load a saved flight plan into the X-Plane FMS?
Yes—aircraft supporting X-Plane's standard flight-plan format can load .fms files placed in the Output/FMS plans folder inside the X-Plane installation. The loading command may appear as co-route, company route, flight-plan load or a similar aircraft-specific option.
Custom airliners may use a different file format or import location, so consult the aircraft's own documentation before moving files. After importing any route, inspect the LEGS page and procedures: missing waypoints, changed runway selections and navigation-data mismatches can alter what the FMS actually loaded.