FMC vs autopilot explained: see which system plans the route, which flies the aircraft, and why LNAV or VNAV may fail to engage.
In an airliner, the flight management computer (FMC) calculates and stores the planned route, performance data and vertical profile; the autopilot moves the flight controls to follow selected guidance. The FMC supplies navigation commands and targets, but it does not physically fly the aircraft, and the autopilot can operate without it.
FMC vs autopilot at a glance
In Aviation & Real-World Flying, the simplest distinction is that the FMC handles planning, prediction and navigation guidance, while the autopilot handles aircraft control.
| Function | FMC | Autopilot |
|---|---|---|
| Main job | Calculates the route, speeds, fuel predictions and vertical profile | Controls pitch, roll and sometimes yaw to follow active guidance |
| Typical inputs | Route, aircraft position, navigation database and performance data | Aircraft sensors plus targets from the FMC or mode-control panel |
| Typical outputs | Lateral path, vertical path, speed targets and predictions | Commands sent to flight-control servos |
| Can work without the other? | Yes; pilots can follow its guidance manually | Yes; it can hold heading, altitude or vertical speed without following an FMC route |
The autothrottle or autothrust system is another separate component. It may use FMC speed targets, but engaging the autopilot does not necessarily engage automatic thrust control.
Are the FMC and FMS the same thing?
Strictly, the flight management system is the complete navigation and performance system, while the FMC is its computing unit. Pilots and simulator documentation often use FMC loosely for the whole system or for the control display unit used to enter data.
Terminology varies by aircraft. Boeing cockpits commonly refer to the FMC and CDU, while Airbus uses terms such as FMGS and MCDU. The underlying division remains similar: the flight-management system calculates guidance, and the autoflight system follows it.
How does the FMC make the autopilot follow a route?
The FMC does not normally drive the control surfaces directly. Its guidance passes to the flight-guidance or autoflight system, which converts the desired path into roll and pitch commands; the autopilot then corrects deviations using aircraft sensor data.
- Enter and verify the route. The route must be complete, correctly sequenced and activated. Our practical FMC programming walkthrough for FS2004 illustrates the core route-entry process, although individual aircraft use different pages and prompts.
- Engage the required guidance mode. Depending on the aircraft, this may be called LNAV, NAV, VNAV or managed guidance. Merely entering a route does not select these modes.
- Wait for mode capture. An armed mode is waiting to meet its engagement conditions; it is not yet controlling the aircraft.
- Check the flight mode annunciator. The FMA on the primary flight display is the authoritative indication of what the autoflight system is actually doing. A lit panel button alone can be misleading.
This is a closed-loop process: the aircraft deviates, sensors detect the error, and the autopilot commands a correction. Our explanation of closed-loop autopilot control in flight simulators covers that control logic in more detail.
Does an autopilot need an FMC?
No. An autopilot can usually fly selected modes such as heading or track hold, altitude hold, vertical speed, flight-path angle, and IAS or Mach-based climb modes without following an FMC route.
The reverse is also true: the FMC can calculate and display guidance while the autopilot is disengaged. The flight director presents that guidance as command bars for the pilot to follow manually; our comparison of flight-director guidance and autopilot control explains where those roles separate.
Why is the autopilot not following the FMC route?
The usual cause is an incorrect or inactive guidance mode, not a failed FMC. A mistake we see constantly in airliner simulation is assuming that a route drawn on the navigation display must already be controlling the aircraft.
- The route was not activated or executed: confirm that the intended flight plan is active rather than stored as a secondary or modified route.
- LNAV or NAV is only armed: establish a suitable intercept heading so the system can capture the route. Capture limits vary between aircraft.
- A discontinuity or wrong active leg exists: inspect the next waypoint and remove only those discontinuities that should genuinely be closed.
- Heading or track mode is active: selected lateral guidance normally takes priority over FMC lateral guidance.
- The altitude selector blocks VNAV: many systems will not climb or descend beyond the altitude set on the MCP or FCU, even when the FMC profile continues farther.
- Performance data are incomplete: missing weights, speeds, thrust settings or cruise information can prevent valid vertical guidance.
- The autopilot is not engaged: LNAV or VNAV may still command the flight director, but the pilot must hand-fly those commands until an autopilot channel is engaged.
Read the FMA before changing anything in the FMC. It tells you which lateral, vertical and thrust modes are active, armed or reverting to another mode.
Can an FMC perform an automatic landing?
No, not by itself. An automatic landing uses a certified combination of navigation receivers, flight-guidance computers, autopilot channels, radio-altimeter inputs, automatic thrust and aircraft-specific control logic. The FMC may supply approach data or help tune navigation aids, but having the runway in the flight plan does not give the aircraft autoland capability.