# FMS Design and Architecture: Dual FMC Logic and 4D Trajectory Management

> Understand FMS/FMGS architecture, dual/independent/single operation modes, sensor fusion for position computation, and integration with autoflight systems.

- **Subject:** 022 — Instrumentation
- **Section:** 022-11 — Flight Management System (FMS)-Flight Management and Guidance System (FMGS)
- **Topic code:** 022-11-01
- **Last reviewed:** 2026-03-27
- **Author:** Pablo Asensio Martínez
- **HTML version:** https://pilotsyllabus.com/en/instrumentation/flight-management-system-fms-flight-management-and-guidance-system-fmgs/design/

---

## Overview

The **Flight Management System (FMS)** is a fundamental component of modern avionics that reduces crew workload by automating navigation, performance optimization, and flight planning tasks. In Airbus terminology, it is often referred to as the **Flight Management Guidance System (FMGS)**.

The system's core functionality involves managing the aircraft's **4D trajectory** (Lateral, Vertical, and Time) and optimizing performance (fuel, speed, altitude).

## Dual FMS Architecture

Modern commercial aircraft typically employ a **Dual FMS** architecture, consisting of two Flight Management Computers (FMCs) and two Control Display Units (CDUs/MCDUs).

### Modes of Operation

1.  **Dual Mode (Normal):**
    *   Both FMCs compute data independently and synchronize via a **cross-talk bus**.
    *   One FMC acts as **Master**, the other as **Slave**.
    *   Data entered into one MCDU is propagated to both.
    *   The Master FMC sends commands to the autopilot, flight director, and autothrottle.

2.  **Independent Mode:**
    *   Automatically selected if there is a **significant disagreement** between the two FMCs (e.g., different database versions).
    *   The cross-talk bus is effectively disconnected; there is **zero cross-checking**.
    *   Each FMC drives its own side's displays (ND/PFD) independently.

3.  **Single Mode:**
    *   Automatically selected if **one FMC fails**.
    *   The remaining operational FMC drives both sides' displays and peripherals.
    *   *Implication:* Redundancy is lost, and some operations (like certain RNP/RNAV procedures or Autoland categories) may be downgraded.

### Failure Scenarios

*   **FMC Failure:** System reverts to **Single Mode**. The crew uses the remaining FMC for both sides.
*   **CDU/MCDU Failure:** The system usually remains in **Dual Mode**. The crew can control both FMCs using the remaining functional CDU.
*   **Cross-talk Bus Failure:** System reverts to **Independent Mode**.

## Core Functions

The FMS provides four major categories of assistance:

1.  **Navigation & Guidance:**
    *   Lateral and Vertical navigation (LNAV/VNAV).
    *   Definition of a 4D trajectory (Latitude, Longitude, Altitude, Time).
    *   Automatic tuning (**Autotuning**) of radio navigation frequencies (VOR, DME, ILS).
    *   **Overfly Function:** Forces the aircraft to fly directly over a waypoint before turning, rather than leading the turn to cut the corner (Fly-by).

2.  **Flight Planning:**
    *   Creation and modification of flight plans (waypoints, airways, procedures).
    *   Trajectory prediction.

3.  **Performance Computations:**
    *   Optimization of speeds, altitudes, and fuel consumption.
    *   Calculations for specific configurations (e.g., Engine Out).
    *   Determination of V-speeds and Center of Gravity (on some systems).

4.  **Position Determination:**
    *   The FMS calculates a "Mix IRS/GPS/Radio" position using a **Kalman Filter**.
    *   **Inputs:** IRS (Inertial, most reliable/available), GPS (Most accurate), DME/DME, VOR/DME, LOC.
    *   Priority is typically given to **GPS** updating due to its high accuracy.

## Aircraft Integration

*   **Autothrottle:** The FMS requires an autothrottle system to fully manage vertical navigation (VNAV) profiles (managing speed and thrust targets).
*   **Databases:** The FMS relies on navigation and performance databases which must be current (AIRAC cycles).
*   **Datalink:** While the MCDU often serves as an interface for ACARS/CPDLC, these are separate communication functions, not core FMS navigation functions.

## Summary Table: FMS Modes

| Mode | Trigger Condition | Status |
| :--- | :--- | :--- |
| **Dual** | Normal Operation | Master/Slave logic, synchronized via cross-talk. |
| **Independent** | Data Disagreement | Decoupled, no cross-talk, separate calculations. |
| **Single** | FMC Failure | One FMC drives both sides (Redundancy lost). |

---

Free study notes from pilotsyllabus.com. Not a substitute for training at an approved ATO.