What is an FMS and how do you use it in a flight simulator?

An aircraft flight management system (FMS) combines a navigation database, planned route, position inputs and performance data to calculate guidance, speeds, fuel estimates and arrival predictions. In Aviation & Real-World Flying and detailed flight simulators, pilots initialise it, verify every entry, then select flight-guidance modes that use its commands.

What does FMS mean in aviation?

In aviation, FMS means flight management system: the aircraft function that manages the flight plan, calculates navigation and performance information, and supplies guidance to cockpit displays and flight-control systems.

Depending on the aircraft and how fully it is modelled, an FMS can:

• Determine aircraft position from inertial, satellite and radio-navigation sources.
• Store and sequence waypoints, airways, departures, arrivals and approaches.
• Calculate lateral tracks and, where supported, a vertical flight path.
• Apply speed and altitude constraints contained in procedures or entered by the crew.
• Predict times, fuel remaining and distance to destination.
• Send commands to the flight director, autopilot and related display systems.

An FMS-equipped aircraft is not a separate type of plane. It simply has a flight-management installation; the capability ranges from basic route sequencing to detailed performance and vertical-navigation functions.

What does “FMS simulator” mean?

An FMS simulator can mean a cockpit trainer that reproduces an aircraft’s flight-management pages, or an FMS fitted to a simulated aircraft. The phrase is also associated with an older radio-controlled-aircraft application called Flying-Model-Simulator, which is unrelated to airliner avionics.

Searches for “FMS model”, “FMS Models”, “FMS plane” or “FMS aircraft” can likewise refer to radio-controlled model products. Within cockpit simulation, an FMS model means the software implementation of the flight-management system and how faithfully it reproduces the real unit.

FMS, FMC, CDU and FMGS: what is the difference?

The FMS is the overall flight-management function, the FMC performs many of its calculations, and the CDU is an interface through which the pilot enters and reviews data. These terms are related but not interchangeable.

How is a Boeing FMS presented?

A Boeing FMS commonly presents its functions through FMC pages on one or more CDUs, although the architecture and page layout depend on the aircraft. Route changes normally remain pending until they are executed, and the pilot must still complete the relevant performance pages and verify every leg.

Our Boeing 737 FMC programming workflow covers the typical page-by-page sequence without treating it as universal to every Boeing type.

FMGS vs FMS: are they the same?

FMGS is broader Airbus terminology that combines flight-management and flight-guidance functions, while FMS is the general industry term for flight management. An MCDU is an interface to those functions, not the entire FMGS.

Airbus and Boeing systems solve many of the same problems, but their pages, terminology and activation logic differ. Boeing commonly uses commands such as EXEC, LNAV and VNAV; Airbus commonly uses temporary flight plans, INSERT, and managed or selected guidance. Do not transfer keystrokes from one type to another without checking the aircraft’s documentation.

Is an FMS the same as GPS?

An FMS is not the same as GPS: GPS supplies position data, while the FMS combines position, route, aircraft and performance information to produce guidance and predictions.

A general-aviation GPS navigator can store a flight plan and command an autopilot, so it performs some FMS-like tasks. An airliner FMS usually adds aircraft-specific performance calculations, procedure handling and vertical-path management. Our explanation of how GPS position and route guidance work in flight simulators covers that relationship in more detail.

How much of the FMS does a flight simulator model?

A flight simulator may reproduce anything from a basic waypoint sequencer to an aircraft-specific FMS with detailed route, performance and VNAV logic.

Choose a basic system when the aim is straightforward route following. Choose an aircraft-specific implementation when practising airline procedures, route revisions or managed descent. A detailed-looking CDU does not prove that every page, leg type, hold, offset or VNAV calculation works.

What FMS entries are needed before departure?

An FMS needs correct position, route and performance entries before its guidance or predictions can be trusted.

• Origin and destination airports, plus an alternate where the system requests one.
• Initial position and any required inertial-reference alignment.
• Departure runway, SID and transition.
• En-route waypoints and airways.
• STAR, arrival transition, approach and landing runway.
• Zero-fuel weight, fuel, reserves and loading information.
• Cruise altitude, economy or cost-index setting, and forecast winds where supported.
• Take-off, climb, descent and approach information required by that aircraft model.

On a conventional CDU or MCDU, data is usually typed into the scratchpad and transferred into a field with the adjacent line-select key. Touchscreen and integrated systems use different controls, but the principle is the same: enter the value, place it in the correct field, then check that the system accepted it.

A mistake we see constantly is entering gross weight in a zero-fuel-weight field, mixing pounds and kilograms, or treating reserve fuel as total fuel. If speeds, fuel predictions or the calculated vertical path look absurd, check the units and source fields before blaming VNAV.

How do you use an FMS in a flight simulator?

Use the aircraft’s own checklist and terminology, but follow the same broad sequence: initialise, build the route, enter performance data, verify it, activate it and monitor the resulting guidance.

1. Power and initialise the system. Supply the required electrical power, confirm the initial position and complete any inertial-reference alignment. Some simulator aircraft automate this; more detailed models require coordinates and a simulated alignment period.
2. Enter the route endpoints. Add the origin, destination and any other basic route information requested by that FMS. Confirm that the identifiers refer to the intended airports.
3. Select the departure and build the route. Choose the runway, SID and transition, then enter airways and waypoints in cleared order. Add the arrival and approach when known, but expect to revise them if the runway or clearance changes.
4. Handle discontinuities deliberately. A discontinuity is a break between legs. Join the legs only when the route should be continuous; vectors, manual legs and the ends of procedures can create intentional gaps.
5. Complete the performance entries. Enter the weights, fuel, reserves, cruise altitude and economy settings required by the model. Do not invent a value merely to remove a scratchpad warning.
6. Verify the route leg by leg. Compare the waypoint order, tracks, distances and altitude constraints with the planned route. Use the navigation display to find doubled-back paths, implausible turns and waypoints selected from the wrong region.
7. Execute or insert the plan. Boeing-style systems commonly require an execute action, while Airbus-style systems may show a temporary flight plan that must be inserted. Until that happens, the edited route may not command guidance.
8. Select and monitor the flight modes. Set the cleared altitude, establish a suitable intercept and arm or select the appropriate lateral and vertical modes. Confirm the result on the flight mode annunciator (FMA); pressing a button does not guarantee that its mode became active.

For actual aircraft operations, use the approved documentation and training for that type. Desktop simulator implementations can omit pages, protections and operational checks even when their cockpit appearance is convincing.

Should you enter an FMS route manually or import it?

Manual entry is better for learning and fault-finding, while importing saves time on long routes but still requires a complete cockpit check.

An imported plan may use navigation data from a different cycle, omit runway procedures, select the wrong transition or populate only the simulator’s flight-planning system rather than the aircraft’s own FMS. Importing also does not complete position, weight, fuel or performance entries.

If the runway, SID, STAR or approach changes, edit the cockpit route and inspect the affected legs again. Never assume that an external plan or simulator map has been updated merely because the FMS route changed.

Does the FMS fly the aircraft automatically?

The FMS calculates guidance but does not by itself move the flight controls; the autopilot or flight director must be using a compatible lateral or vertical mode.

LNAV, NAV or managed lateral guidance can follow the calculated route. VNAV or managed climb and descent can use the vertical profile, but selected altitude, thrust, speed controls, aircraft configuration and modelled system limitations may restrict what happens.

Read the FMA after every mode selection. If the route is valid but the aircraft remains in heading mode, it will continue following the selected heading rather than the FMS path. The practical steps for setting the navigation source and making the autopilot follow a programmed route explain the next checks.

Why will the FMS not follow the route?

An FMS usually fails to follow the intended route because the plan is inactive, the wrong leg or navigation source is selected, the aircraft has not intercepted the path, or the required flight-guidance mode is not active.

Deleting every discontinuity is one of the most damaging shortcuts. It can connect legs that were never intended to meet, producing an abrupt reversal or an unsafe track across terrain.

How does FMS use change for an approach?

For an approach, the runway, procedure, transition, final track, altitude restrictions and missed-approach legs must all be checked before the aircraft intercepts final guidance.

Loading an approach does not necessarily activate it, authorise a descent or select the required autopilot mode. An ILS uses localiser and glideslope signals rather than an FMS-generated vertical path, although the FMS may sequence the arrival and assist with radio tuning where the aircraft supports it. An RNAV approach relies on the aircraft’s approved navigation and approach-guidance logic, which is not modelled equally in every simulator aircraft.

Check the active waypoint, distance to final, guidance source, selected altitude and FMA before interception. If the procedure changes, review the missed approach as well as the inbound legs; replacing an approach can leave an unexpected transition or discontinuity behind.