A320 Aircraft Systems · Chapter 9
Flight Management System and MCDU How the two FMGCs navigate, hold the flight plan and compute performance, and how the crew talks to them through the MCDU.
FM 1 IND RDY FM 2 FROM EPL202 ←→ UTC SPD/ALT BEKIR 0712 /FL350 L333 BRG152 86NM TOMAL 0724 .78/FL350 L333 TRK152 64 RUSOK 0732 .78/FL350 38 (T/D) 0737 .78/FL350 L333 61 PENAM 0750 280/ FL240 * DEST UTC DIST EFOB VABB27 0826 412 3.9 ↑↓ 1L 1R 2L 2R 3L 3R 4L 4R 5L 5R 6L 6R DIR PROG PERF INIT DATA F-PLN RAD NAV FUEL PRED SEC F-PLN ATC COMM MCDU MENU BRT DIM AIR PORT ← ↑ → ↓ 1 2 3 4 5 6 7 8 9 . 0 +/- A B C D E F G H I J K L M N O P Q R S T U V W X Y Z / SP OVFY CLR F A I L F M M C D U M E N U © 2026 eatpl.in. For the personal study of eatpl.in students only. Do not copy or distribute.
e-books by eatpl.in · © 2026 · Do not copy or distribute
Welcome to the flight management system, the part of the A320 that most new type-rating pilots find the busiest. The good news is that it is very logical. Two computers, the FMGCs, work out where the aircraft is, store the route you load, and compute the best speeds, the top of climb and the top of descent. You talk to them through the MCDU on the pedestal. In this lesson we build the architecture first, then learn the MCDU keyboard and its colours, then navigation and position accuracy, then the flight plan and its revisions, then performance and the key pages, and finally what happens when the computers fail. By the end, the pages you meet in the simulator should feel familiar.
Flight management
Our route through ATA 22-20 INIT → CO RTE FROM/TO DELBOM01 VIDP/VABB ALTN/CO RTE INIT VAAH/BOMAMD1 REQUEST* FLT NBR EPL202 IRS INIT> WIND> COST INDEX TROPO 30 36090 CRZ FL/TEMP GND TEMP FL350/-54° 14° 1L 1R 2L 2R 3L 3R 4L 4R 5L 5R 6L 6R FROM EPL202 ←→ UTC SPD/ALT BEKIR 0712 /FL350 L333 BRG152 86NM TOMAL 0724 .78/FL350 L333 TRK152 64 RUSOK 0732 .78/FL350 38 (T/D) 0737 .78/FL350 L333 61 PENAM 0750 280/ FL240 * DEST UTC DIST EFOB VABB27 0826 412 3.9 ↑↓ 1L 1R 2L 2R 3L 3R 4L 4R 5L 5R 6L 6R TAKE OFF RWY 28 V1 FLP RETR VR SLT RETR TO SHIFT V2 CLEAN FLAPS/THS TRANS ALT FLEX TO TEMP 4000 [ ]° THR RED/ACC ENG OUT ACC 2280/2280 2280 UPLINK NEXT <TO DATA PHASE> F= 150 S= 196 [M] [ ]* O= 212 [ ]/[ ] 1L 1R 2L 2R 3L 3R 4L 4R 5L 5R 6L 6R Architecture Two FMGCs, MCDUs, databases, and the dual, independent, single and back-up modes.
MCDU Layout, page keys, colours, fonts and the rules for typing data.
Navigation MIX IRS, GPIRS and radio positions, EPU and RNP, radio tuning.
Flight plan INIT A and B, F-PLN pages, revisions, DIR TO, holds and constraints.
Performance Flight phases, cost index and ECON speeds, PERF and PROG pages.
Abnormal Resets, latches, engine out, CHECK WEIGHT and back-up navigation.
Chapter 9 · Flight Management System and MCDU
2
e-books by eatpl.in · © 2026 · Do not copy or distribute
Here is the plan for this lesson, which covers chapter twenty two twenty, flight management. We start with the architecture: what boxes make up the system, what each computer does, which databases it carries, and the four ways the pair can operate. Next comes the MCDU itself, with its keys, colours and typing rules, because every later topic happens on that screen. Then navigation: how each computer works out the aircraft's position and how sure it is about it. Then the flight plan, from initialisation through every common revision. Then performance: flight phases, cost index and the performance pages. We finish with the failures you must recognise in the simulator. The three pages above, INIT A, the flight plan page and the takeoff page, are the ones you will use on every single flight.
Part 1 · Architecture
Two FMGCs, MCDUs and the FCU FMGS = 2 FMGCs , 2 MCDUs (third optional), 1 FCU , 2 FACs FM part : navigation and radios, flight planning, performance, displaysFG part : autopilot, flight director and autothrust commandsManaged guidance follows the FMGS targets; selected follows the FCUSelected guidance always has priority over managed Either FMGC can do everything if the other fails FCU selected targets: SPD · HDG · ALT · V/S FMGC 1 FM part navigation · radios flight plan · performance displays FG part AP · FD · A/THR commands FMGC 2 FM part navigation · radios flight plan · performance displays FG part AP · FD · A/THR commands crosstalk bus MCDU 1 MCDU 2 MCDU 3 (option) + two FACs complete the flight management and guidance system
Chapter 9 · Flight Management System and MCDU
3
e-books by eatpl.in · © 2026 · Do not copy or distribute
The flight management and guidance system is built from a few boxes. There are two flight management and guidance computers, called FMGCs, two MCDUs on the pedestal, with a third as an option, one FCU on the glareshield, and two flight augmentation computers. Each FMGC has two halves. The flight management part handles navigation and the radios, the flight plan, performance predictions and what goes on the displays. The flight guidance part turns targets into autopilot, flight director and autothrust commands. The two computers talk through a crosstalk bus so they stay in step. When the aircraft follows targets computed by the system, guidance is managed. When you turn an FCU knob, guidance is selected, and selected always wins. One healthy FMGC can do the whole job alone.
Part 1 · Architecture
What each FMGC carries Database Contents Key facts Navigation Navaids, waypoints, airways, holds, airports, runways, SIDs, STARs, company routes, alternates 28-day AIRAC cycle · load 20 min, or 5 min by crossload · check validity on AIRCRAFT STATUS Airline modifiable (AMI) THR RED, ACC and EO ACC altitudes, PERF and IDLE factors, fuel policy (taxi, route reserve %), AOC options Set by the airline, not the crew Aircraft performance Engine, aerodynamic and performance models Cannot be modified by the airline Magnetic variation Variation for converting true and magnetic — Pilot-stored elements 20 waypoints, 10 runways, 20 navaids, 5 routes LIST OF 20 IN USE when full
Each FMGC has its own set; databases can be loaded independently or copied from one FMGC to the other.
Chapter 9 · Flight Management System and MCDU
4
e-books by eatpl.in · © 2026 · Do not copy or distribute
Each FMGC carries its own set of databases. The navigation database holds everything you can call up by name: navaids, waypoints, airways, holding patterns, airports, runways, procedures, company routes and preferred alternates. It follows the twenty eight day AIRAC cycle, and you confirm it is current on the AIRCRAFT STATUS page during cockpit preparation. Loading takes about twenty minutes, or five if it is copied across from the other computer. The airline modifiable information holds company choices such as the default thrust reduction and acceleration altitudes, the performance factor and the fuel policy. The performance database, the engine and aerodynamic model, is fixed. There is also a magnetic variation table. Finally, the crew can store up to twenty waypoints, ten runways, twenty navaids and five routes of their own.
Part 1 · Architecture
Dual, independent, single and back-up Master FMGC: one AP engaged → its FMGC · two APs → FMGC 1 · no AP → FD1 on: FMGC 1, else FD2: FMGC 2 · no AP/FD → A/THR by FMGC 1.
Mode When What you see and do DUAL (normal) Always, when both are healthy Synchronised by crosstalk; one master, one slave; an entry on any MCDU goes to both FMGCs INDEPENDENT Automatic, e.g. different database validity INDEPENDENT OPERATION, amber IND · on ground: crossload the database · in flight: make the same entries on both MCDUs SINGLE Automatic, one FMGC failed Failed side MCDU goes to MCDU MENU with an OPP FMGC prompt · set both NDs to the same mode and range BACK-UP NAV Selected on MCDU MENU after a dual FM failure MCDU + IRS (GPS): F-PLN on ND, sequencing, limited revisions; no NAV mode, no managed modes
Chapter 9 · Flight Management System and MCDU
5
e-books by eatpl.in · © 2026 · Do not copy or distribute
The pair of computers can work in four ways. Dual mode is normal: both compute everything, they compare through the crosstalk bus, and one is master. Whatever you type on either MCDU goes to both. The master is the computer of the engaged autopilot, or FMGC one with both autopilots, or without autopilots the side of the flight director that is on, starting with FD one. Independent mode starts by itself when the computers cannot agree, for example with different database validity. The scratchpad says INDEPENDENT OPERATION and the amber IND light comes on. On the ground you crossload the database; in flight you make every entry on both MCDUs. Single mode follows one FMGC failure. Back-up navigation, selected on the MCDU MENU, is the last resort when both FMGCs are lost.
Part 2 · MCDU
The MCDU: screen, keys and lights Screen: 14 lines × 24 characters Title, 6 label + data line pairs , then the scratchpad Line select keys 1L–6L and 1R–6R: insert data, call prompts, revise the F-PLNTop lights: FM 1 , FM 2 (amber, onside FM failed), IND (amber), RDY (green) Side lights: FAIL (amber), MCDU MENU and FM (white) BRT powers up, DIM shuts downFM 1 IND RDY FM 2 INIT → CO RTE FROM/TO ####/#### ALTN/CO RTE INIT ----/---------- REQUEST* FLT NBR IRS INIT> WIND> COST INDEX TROPO --- 36090 CRZ FL/TEMP GND TEMP -----/---° ---° 1L 1R 2L 2R 3L 3R 4L 4R 5L 5R 6L 6R DIR PROG PERF INIT DATA F-PLN RAD NAV FUEL PRED SEC F-PLN ATC COMM MCDU MENU BRT DIM AIR PORT ← ↑ → ↓ 1 2 3 4 5 6 7 8 9 . 0 +/- A B C D E F G H I J K L M N O P Q R S T U V W X Y Z / SP OVFY CLR F A I L F M M C D U M E N U 1 1 Title line 2 2 Label + data lines (6 pairs) 3 3 Scratchpad 4 4 Line select keys (1L to 6L, 1R to 6R) 5 5 Page keys (DIR, PROG, PERF, INIT...) 6 6 Slew and page keys 7 7 CLR, OVFY and SP keys 8 8 FM 1, IND, RDY, FM 2 lights
Chapter 9 · Flight Management System and MCDU
6
e-books by eatpl.in · © 2026 · Do not copy or distribute
This is the MCDU, drawn showing an empty INIT A page. The screen has fourteen lines of twenty four characters. The top line is the page title. Below it come six pairs: a small label line, then a data line. The bottom line is the scratchpad, where your typing appears and where the system writes messages. On each side are six line select keys, called one L to six L and one R to six R. They move scratchpad data into a field, call up the page named by a prompt, or open a lateral or vertical revision on the flight plan page. Above the screen are the FM one and FM two lights, amber when that side's flight management has failed, the amber IND light for independent mode, and the green ready light. On the sides are the amber FAIL light and the white MCDU MENU and FM lights.
Part 2 · MCDU
The page keys Key Calls up DIR DIR TO page: direct from present position to any waypoint F-PLN Flight plan A (→ B): left keys lateral revision, right keys vertical revision PROG Progress page of the active phase: CRZ FL, OPT, REC MAX, position update, BRG/DIST, accuracy PERF PERF page of the active phase (TAKE OFF in preflight and done; pressing it in done starts a new preflight) INIT INIT A, then INIT B (before engine start) and IRS INIT FUEL PRED Fuel at destination and alternate, FOB, GW and CG, extra fuel (after engine start) RAD NAV · DATA Navaids tuned for display · data index: position, aircraft status, stored data SEC F-PLN · MCDU MENU Secondary flight plan index · subsystems such as FMGC, ACARS, CFDS
Also: AIRPORT (jumps to the next airport in the F-PLN), slew ↑↓ and page ←→ keys, CLR, OVFY and SP.
Chapter 9 · Flight Management System and MCDU
7
e-books by eatpl.in · © 2026 · Do not copy or distribute
The page keys take you straight to the main pages. DIR opens the direct-to page. F-PLN shows the flight plan, page A with times, speeds and altitudes, and page B with fuel and winds. On that page the left keys revise the lateral path and the right keys the vertical profile. PROG gives the progress page for the current phase. PERF shows the performance page of the active phase; in the preflight and done phases it shows the takeoff page. INIT opens INIT A, and from there INIT B and the IRS INIT page. FUEL PRED becomes the live fuel page once the engines are running. RAD NAV shows the tuned navaids, DATA the reference pages, SEC F-PLN the secondary flight plan, and MCDU MENU the other systems that share the MCDU. The AIRPORT key is a quick jump to the next airport in the flight plan.
Part 2 · MCDU
Colours and fonts mean something Amber boxes : mandatory entry · blue brackets : optional entryBlue : you may change it · green : active or fixed dataWhite : titles, prompts, dashes · magenta : constraintsYellow : temporary flight planLarge font : crew entries and modifiable dataSmall font : computed, defaulted or fixed dataINIT → CO RTE FROM/TO ####/#### ALTN/CO RTE INIT ----/---------- REQUEST* FLT NBR IRS INIT> WIND> COST INDEX TROPO --- 36090 CRZ FL/TEMP GND TEMP -----/---° ---° 1L 1R 2L 2R 3L 3R 4L 4R 5L 5R 6L 6R WHITE titles, prompts < >, arrows, dashes BLUE modifiable or selectable data, brackets GREEN active and non-modifiable data AMBER mandatory boxes, action needed, missed cstr MAGENTA constraints, max altitude YELLOW temporary flight plan Large font: crew entries and modifiable data · small font: computed or default data
Chapter 9 · Flight Management System and MCDU
8
e-books by eatpl.in · © 2026 · Do not copy or distribute
The MCDU uses colour and font size as a language, and reading it fluently saves you a lot of time. Amber boxes mean the system needs this before it can work, such as a company route or a flight number on INIT A. Blue brackets mean you may enter something here if you want. Anything in blue can be modified; anything in green is active or cannot be changed. White is used for titles, prompts and dashes. Magenta marks constraints and the maximum altitude, and amber is also used for missed constraints and important messages. Yellow is reserved for the temporary flight plan, before you insert it. The font size adds one more clue: large characters are things you entered or may change, while small characters are values the computer worked out or defaulted for you.
Part 2 · MCDU
Typing data: scratchpad, keys and formats Type in the scratchpad , then press the line select key Below 1 000 ft , keep the leading zero: 0400 is 400 ftTwo-part fields use a slash ; /0400 enters only the second part CLR erases the scratchpad; CLR then LSK clears a field Type I messages: result of your action, shown at onceType II : situation or request, queue of 5; amber important, white advisory1 Type into the scratchpad CRZ FL/TEMP -----/---° FL350/-54 ← scratchpad 2 Press the line select key (here 6L) CRZ FL/TEMP FL350/-54° now blue, large Entry rules 60 → 060 leading zeros may be left out 0400 → 400 ft below 1 000 ft keep the zero (not FL 4) /0400 → 2nd half only leading slash for the second part 250 → 1st half only no slash when only the first part CLR → field cleared CLR in the scratchpad, then the LSK Bad format → FORMAT ERROR · out of range → ENTRY OUT OF RANGE
Chapter 9 · Flight Management System and MCDU
9
e-books by eatpl.in · © 2026 · Do not copy or distribute
Every entry follows the same rhythm. You type into the scratchpad, then press the line select key next to the field you want. If the format is wrong you get FORMAT ERROR, and a value outside the allowed range gives ENTRY OUT OF RANGE. Leading zeros can usually be left out, so sixty becomes zero six zero. There is one trap: an altitude below one thousand feet must keep its leading zero, typed as zero four zero zero, otherwise it would be read as a flight level. Fields with two parts use a slash. If you only want the second part, start with a slash. To clear a field, press CLR with an empty scratchpad, then the key of the field. Messages come in two types. Type one is a direct result of what you just did. Type two tells you about a situation, waits in a queue of five, and is amber if important or white if advisory.
Part 3 · Navigation
Where am I? The FM position Each FMGC computes its own FM position MIX IRS : weighted mean of the 3 IRS positions; a drifting IRS loses weightGPIRS : each IRS mixes GPS; FMGC picks onside → IRS 3 → opposite Radio position from onside navaids: DME/DME, VOR/DME, LOCBias = MIX IRS → GPIRS or radio; frozen if both are lostFM position = MIX IRS + bias ; manual update also resets the bias IRS 1 IRS 2 IRS 3 MIX IRS weighted mean GPIRS (or radio) bias FM position FM position = MIX IRS position + bias bias updated while a GPIRS or radio position exists lost? the last bias is frozen and carried on GPIRS choice: onside → IRS 3 → opposite radio: DME/DME, VOR/DME, LOC (approach)
Chapter 9 · Flight Management System and MCDU
10
e-books by eatpl.in · © 2026 · Do not copy or distribute
Each FMGC works out its own position, called the FM position. It starts with three IRS positions, and blends them into a weighted average called the MIX IRS position. If one IRS drifts abnormally, its weight is reduced, and if one fails, the computer uses its onside IRS or IRS three. Each IRS also mixes in GPS to make a GPIRS position, and the FMGC chooses the onside one, then IRS three, then the opposite one. A radio position can come from DME DME, VOR DME, or the localiser during an ILS. The yellow arrow is the bias: the vector from the MIX IRS position to the best GPIRS or radio position. The FM position is simply MIX IRS plus bias, and in flight it approaches the GPIRS or radio position. If those are lost, the last bias is frozen and carried along.
Part 3 · Navigation
Navigation modes and EPU Mode (in priority order) Estimated position uncertainty Remark 1 · IRS–GPS 0.05 NM Normal mode when GPS data is valid and tested 2 · IRS–DME/DME 0.27 to 0.37 NM Two DMEs tuned automatically, no crew indication 3 · IRS–VOR/DME 0.30 to 0.42 NM Depends on the distance to the VOR/DME 4 · IRS only +6 NM/h for 40 min, 0 for 50 min, +4 for 40 min, 0 for 45 min, then +2 NM/h EPU keeps growing ILS approach LOC gives a temporary lateral update e.g. IRS–GPS/LOC, IRS–DME/DME–LOC, IRS–LOC Reference values after IRS alignment: 5 NM · at takeoff: 0.2 NM —
Chapter 9 · Flight Management System and MCDU
11
e-books by eatpl.in · © 2026 · Do not copy or distribute
The computer always uses the best update it can get, in a fixed order. First choice is IRS with GPS. If GPS is not usable, it uses IRS with two DMEs, then IRS with a VOR DME, and last of all IRS only. With each mode comes an estimated position uncertainty, the EPU, which is the computer's honest guess of how far its position might be wrong. With GPS it is five hundredths of a nautical mile. With DME DME it is about a quarter to a third of a mile, and VOR DME is a little worse and depends on your distance from the station. With IRS only, the EPU grows with time, by six miles per hour for the first forty minutes, then in steps after that. During an ILS approach the localiser adds a temporary lateral update.
Part 3 · Navigation
Accuracy: EPU against RNP EPU ≤ RNP → accuracy HIGH ; EPU > RNP → LOW RNP: crew entry → procedure value → default Defaults: en route 2.0 , terminal 1.0 , approach 0.3 (GPS) or 0.5 NM Change: NAV ACCUR DOWNGRAD / UPGRAD on MCDU and ND GPS PRIMARY = accuracy + integrity; lost: GPS PRIMARY LOST FM vs GPS beyond 0.5 arc-minute: NAV FM/GPS POS DISAGREE 0 2 4 6 8 10 0 40 80 120 160 200 240 minutes since GPS and radio updating were lost (IRS only) EPU (NM) en route RNP 2.0 terminal RNP 1.0 RNAV(GNSS) approach 0.3 18 min: LOW en route 8 min: LOW in terminal area rates: +6, 0, +4, 0, +2 NM/h EPU above RNP → accuracy LOW (starts at 0.2 NM at takeoff)
Chapter 9 · Flight Management System and MCDU
12
e-books by eatpl.in · © 2026 · Do not copy or distribute
The computer compares its EPU with the required navigation performance, the RNP. If the EPU is within the RNP, accuracy is HIGH; if not, it is LOW, and you see NAV ACCUR DOWNGRAD on the MCDU and the ND. The RNP shown on the PROG page is the one you entered, otherwise the procedure value, otherwise a default: two miles en route, one mile in the terminal area, and for approach nought point three with GPS or nought point five otherwise. The graph shows why IRS only is limited. Starting from nought point two at takeoff and growing six miles per hour, accuracy drops to LOW for terminal use after about eight minutes, and en route after about eighteen. GPS PRIMARY adds an integrity check on top of accuracy, and when it is lost you must check accuracy regularly yourself. A disagreement between the FM and GPS positions gives an ECAM caution.
Part 3 · Navigation
Radio navaid tuning Tuned for display and for position computation Each FMGC tunes its own side ; in single mode one FMGC tunes both Manual tuning has priority ; use the ident , frequency only if not in database5 DME channels per side: display, 2 for DME/DME, 1 for VOR/DME, 1 ILS/DMEILS autotuned for the takeoff runway, or for an ILS approach in the F-PLNRMP tuning only if both FMGCs or both MCDUs failRADIO NAV VOR1/FREQ FREQ/VOR2 DPN/116.10 112.50/BBN CRS CRS 095 [ ] ILS /FREQ IBB/110.30 CRS F273 ADF1/FREQ FREQ/ADF2 [ ]/[ ] [ ]/[ ] 1L 1R 2L 2R 3L 3R 4L 4R 5L 5R 6L 6R FMGC autotuning display + position computation (VOR, DME, ILS, ADF) MCDU RAD NAV page manual tuning for display; has priority RMP (NAV) back-up tuning if both FMGCs or both MCDUs fail
Chapter 9 · Flight Management System and MCDU
13
e-books by eatpl.in · © 2026 · Do not copy or distribute
Navaids are tuned for two reasons: so you can see them, and so the computer can use them for its radio position. The FMGC does both automatically, each one on its own side. You can override the display tuning on the RAD NAV page, and manual tuning always has priority. Type the identifier where possible. If you type a frequency instead, the computer attaches the nearest identifier with that frequency, which may not be the station you meant. Behind the scenes each side uses five DME channels: one for display, two for DME DME positioning, one for VOR DME positioning and one paired with the ILS. The ILS is autotuned for the takeoff runway before departure, and for an ILS approach in the flight plan. Only if both FMGCs or both MCDUs fail do you tune on the radio management panel. Always check the decoded identifier.
Part 3 · Navigation
IRS alignment and the takeoff update IRS INIT uses the airport reference ; you may adjust it to the gate Alignment: normal 10 min , fast 30 s At takeoff the FM position jumps to the runway threshold in the database TO SHIFT on PERF TAKE OFF corrects for an intersectionNeeds the takeoff runway in the F-PLN ; inhibited in GPS PRIMARY POSITION UPDATE AT (PROG): only for a major position problemTakeoff update with a TO SHIFT threshold (database) TO SHIFT 600 m intersection departure At TOGA / FLX: FM position jumps to the threshold + TO SHIFT Needs: the takeoff runway in the F-PLN Inhibited: when GPS PRIMARY is active IRS INIT: airport reference, adjust to the gate Alignment: normal 10 min, fast 30 s ALIGN flashing: motion, or position or latitude mismatch
Chapter 9 · Flight Management System and MCDU
14
e-books by eatpl.in · © 2026 · Do not copy or distribute
Before the first flight of the day the inertial reference systems are aligned. The IRS INIT page offers the departure airport's reference coordinates, which you can adjust to the gate. A normal alignment takes ten minutes, a fast one thirty seconds. Then comes a neat trick: when you set takeoff thrust, the FM position is updated to the runway threshold stored in the database. This only works if the takeoff runway is in the flight plan, and if you start from an intersection you enter the distance as a takeoff shift, here six hundred metres. With GPS PRIMARY this update is inhibited, because GPS is already better. The manual POSITION UPDATE AT function on the PROG page is different: it depends on your judgement of when you passed a point, so use it only for a major position problem.
Part 4 · Flight plan
Active, secondary and temporary Active : guidance, MCDU and ND, autotuning, predictions, fuelSecondary : alternate runway, diversion, next flight, comparisonsEach has a primary part (to destination + missed approach) and an alternate part Build it from a company route or a city pair A discontinuity separates two points with no leg between them Capacity: 200 legs per element, else F-PLN FULL ACTIVE F-PLN RWY SID TRANS EN ROUTE STAR/VIA APPR MISSED ALTN primary: origin → destination + missed approach · alternate: dest → ALTN SECONDARY F-PLN RWY SID TRANS EN ROUTE STAR/VIA APPR MISSED ALTN primary: origin → destination + missed approach · alternate: dest → ALTN TMPY F-PLN a revised copy, checked before INSERT 5 elements × up to 200 legs each (else F-PLN FULL) 1 CO RTE known type it in INIT A 1L: the whole route loads 2 City pair, routes stored ROUTE SELECTION page appears 3 City pair, no route CO RTE shows NONE: build it by hand
Chapter 9 · Flight Management System and MCDU
15
e-books by eatpl.in · © 2026 · Do not copy or distribute
The FMGS can hold two flight plans. The active flight plan drives everything: guidance, the MCDU and ND displays, radio autotuning, predictions and fuel planning. The secondary flight plan sits in the background for you to prepare a likely runway change, a diversion, the next flight, or simply to compare predictions. Each one has a primary part, from the departure runway to the destination and its missed approach, and an alternate part from the destination to the alternate. You build the route in one of three ways: type a company route you know, type a city pair and pick a stored route from the ROUTE SELECTION page, or, when the company route field shows NONE, build it by hand. When two waypoints have no leg between them, the plan shows a discontinuity, and overflying one in NAV drops you into heading or track mode.
Part 4 · Flight plan
INIT A: the flight in one page CO RTE or FROM/TO city pair; ALTN/CO RTE follows the destinationFLT NBR , COST INDEX , CRZ FL/TEMP No CRZ FL → no predictions on the ground Cruise temperature refines predictions, otherwise ISA TROPO defaults to 36 090 ft ; GND TEMP to ISA at the airportPrompts: IRS INIT and WIND ; INIT REQUEST for an uplink INIT → CO RTE FROM/TO DELBOM01 VIDP/VABB ALTN/CO RTE INIT VAAH/BOMAMD1 REQUEST* FLT NBR EPL202 IRS INIT> WIND> COST INDEX TROPO 30 36090 CRZ FL/TEMP GND TEMP FL350/-54° 14° 1L 1R 2L 2R 3L 3R 4L 4R 5L 5R 6L 6R CRZ FL needed no predictions on the ground without it CRZ TEMP not entered → predictions for ISA TROPO default 36 090 ft ALTN/CO RTE database preferred alternate, or NONE
Chapter 9 · Flight Management System and MCDU
16
e-books by eatpl.in · © 2026 · Do not copy or distribute
INIT A is the first page of every cockpit preparation. On the left you enter the company route, which can bring in the whole flight plan, the alternate with its route, the flight number, the cost index, and the cruise flight level with the temperature at that level. On the right is the city pair, here Delhi to Mumbai, the INIT REQUEST prompt that asks the ground for a flight plan by datalink, the IRS INIT and WIND prompts, the tropopause, which defaults to thirty six thousand and ninety feet, and the ground temperature. Two details matter. Without a cruise flight level the computer gives no predictions on the ground. And if you do not enter the cruise temperature, predictions assume standard atmosphere. So take the cruise temperature from your flight plan and enter it with its sign.
Part 4 · Flight plan
INIT B and the fuel arithmetic Reached with ← → from INIT A, before engine start only Enter ZFW/ZFWCG and BLOCK fuel (mandatory) MIN DEST FOB = ALTN + FINAL EXTRA = BLOCK − (TAXI + TRIP + RTE RSV + MIN DEST FOB) FINAL: holding at 1 500 ft AGL, CONF 1, max endurance speed After first engine start → FUEL PRED , using the measured FOB INIT FUEL PREDICTION TAXI ZFWCG/ ZFW 0.2 27.0/ 56.5 TRIP /TIME BLOCK 4.6/0205 9.8 RTE RSV/% 0.2/5.0 ALTN /TIME TOW/ LW 1.4/ 0035 66.1/ 61.5 FINAL /TIME TRIP WIND 1.1/0030 HD010 MIN DEST FOB EXTRA/TIME 2.5 2.3/0103 1L 1R 2L 2R 3L 3R 4L 4R 5L 5R 6L 6R EXTRA = BLOCK − (TAXI + TRIP + RTE RSV + MIN DEST FOB) 2.3 = 9.8 − (0.2 + 4.6 + 0.2 + 2.5) tonnes MIN DEST FOB = ALTN 1.4 + FINAL 1.1 = 2.5 TOW = ZFW 56.5 + BLOCK 9.8 − TAXI 0.2 = 66.1 LW = TOW 66.1 − TRIP 4.6 = 61.5
Chapter 9 · Flight Management System and MCDU
17
e-books by eatpl.in · © 2026 · Do not copy or distribute
INIT B is the weight and fuel page, reached by the left or right arrow from INIT A, and only before engine start. You enter the zero fuel weight and its centre of gravity, and the block fuel, which is mandatory. The computer then fills in trip fuel and time, the route reserve, alternate fuel, final reserve and the minimum destination fuel, which is alternate plus final. Let us check the extra fuel. Block nine point eight tonnes, minus taxi nought point two, trip four point six, route reserve nought point two, and minimum destination fuel two point five, leaves two point three tonnes of extra. Takeoff weight is zero fuel weight plus block minus taxi, sixty six point one. As soon as the first engine starts, this page becomes FUEL PRED, and the computer stops using your block figure and uses the fuel actually measured on board.
Part 4 · Flight plan
Reading the F-PLN A page Line 1: FROM waypoint, the last one overflown Line 2: TO waypoint in white : the active leg Between lines: airway, bearing or track , distance Time, speed or Mach, altitude for every waypoint; pseudo waypoints in brackets Line 6: destination time, distance and EFOB (amber if below MIN DEST FOB) Missed approach and alternate in blue ; page B: EFOB and wind FROM EPL202 ←→ UTC SPD/ALT BEKIR 0712 /FL350 L333 BRG152 86NM TOMAL 0724 .78/FL350 L333 TRK152 64 RUSOK 0732 .78/FL350 38 (T/D) 0737 .78/FL350 L333 61 PENAM 0750 280/ FL240 * DEST UTC DIST EFOB VABB27 0826 412 3.9 ↑↓ 1L 1R 2L 2R 3L 3R 4L 4R 5L 5R 6L 6R BEKIR FROM: last waypoint overflown (green) TOMAL TO: the active leg ends here (white) (T/D) pseudo waypoint, in brackets * constraint predicted met (amber: missed) DEST line 6: time, distance, EFOB at destination
Chapter 9 · Flight Management System and MCDU
18
e-books by eatpl.in · © 2026 · Do not copy or distribute
Here is the flight plan A page in cruise. The first line is the FROM waypoint, the last one you overflew. The second, in white, is the TO waypoint, so the leg between them is the active leg. The small lines between waypoints give the airway, the bearing to the TO waypoint or the track of the next leg, and the distance. Each waypoint shows a predicted time, speed or Mach number, and altitude. Pseudo waypoints, such as the top of descent here, are events rather than places, and they appear in brackets. A star beside a value is a constraint, magenta when it will be met. The sixth line is fixed: time, distance and estimated fuel at the destination, which turns amber if it falls below the minimum destination fuel. The missed approach and alternate are drawn in blue until they become active. Page B shows fuel and wind instead.
Part 4 · Flight plan
Revisions and the temporary flight plan Left key on a waypoint opens LAT REV ; right key opens VERT REV LAT REV: departure, arrival, next waypoint, new destination, airway, hold, offset, alternate, fix info Every revision builds a yellow TMPY F-PLN ; the aircraft keeps flying the active one TMPY INSERT (6R) makes it active (green)UNDO cancels the last of several pending revisions, onceInserting a waypoint creates a discontinuity after it LAT REV FROM PENAM 19°40.2N/074°02.5E FIX INFO> NEXT WPT <HOLD [ ] ENABLE NEW DEST ←ALTN [ ] AIRWAYS> <RETURN 1L 1R 2L 2R 3L 3R 4L 4R 5L 5R 6L 6R Left key on F-PLN = LAT REV Right key on F-PLN = VERT REV TMPY: yellow on MCDU and ND <TMPY F-PLN 6L TMPY INSERT* 6R inserted: green, and the aircraft follows it
Chapter 9 · Flight Management System and MCDU
19
e-books by eatpl.in · © 2026 · Do not copy or distribute
Changes to the flight plan are called revisions. Press the left key next to a waypoint for a lateral revision, the right key for a vertical one. The lateral revision page offers everything you might need at that point: the departure or arrival, a next waypoint, a new destination, airways, a hold, an offset if you revise the FROM waypoint, the alternate, and fix information. Every revision builds a temporary flight plan, shown in yellow on both MCDUs and both NDs. The aircraft keeps flying the active plan while you check it. You may stack several revisions, and undo the last one once. When you are happy, TMPY INSERT on the six R key makes it active and green. Remember that inserting a waypoint leaves a discontinuity after it, and deleting one leaves a discontinuity in its place, which you clear before inserting.
Part 4 · Flight plan
DIR TO and its variants From present position direct to any waypoint , in the F-PLN or typed Options: DIRECT TO , ABEAM PTS , RADIAL IN / OUT Creates a DIR TO TMPY : DIR TO INSERT (6R) or ERASE (6L) Present position becomes the T-P FROM waypoint; NAV engages The only way back after a MANUAL leg, a discontinuity or a major reset Cancels an offset ; no other revision while DIR TO IN PROCESS BEKIR KOLIN TOMAL RUSOK T-P (present position) DIR TO TOMAL DIR key → choose or type the waypoint DIRECT TO · ABEAM PTS · RADIAL IN / RADIAL OUT yellow DIR TO temporary until DIR TO INSERT (6R) DIR TO ERASE (6L) cancels · NAV engages on insertion
Chapter 9 · Flight Management System and MCDU
20
e-books by eatpl.in · © 2026 · Do not copy or distribute
The DIR key is the one you will use most in flight. It builds a straight leg from your present position to any waypoint, either one already in the flight plan or one you type. The default is a plain direct to; you can also ask for abeam points, which keeps the skipped waypoints as abeam positions, or for a radial inbound or outbound at the waypoint. In this version the new leg first appears as a yellow direct-to temporary flight plan, here to TOMAL, and becomes active only when you press DIR TO INSERT. Your present position becomes the turn point, the T-P, and NAV engages. A direct to is also your exit from a MANUAL leg, from a discontinuity, or after a major reset, and it cancels any offset. While it is pending, the computer refuses other revisions with DIR TO IN PROCESS.
Part 4 · Flight plan
Holds, offsets, overfly and airways HOLD (HF · HA · HM) HM: IMM EXIT / RESUME HOLD entries: direct · teardrop · parallel L15 OFFSET 1 to 50 NM, left or right, from PPOS title shows OFST · cleared by DIR TO or 0 OVERFLY OVFY key → Δ → LSK of the waypoint grey dashed: normal fly-by turn Holds HF and HA come from procedures and exit by themselves. HM is crew-inserted at a waypoint or PPOS, exits with IMM EXIT. Default speed: lowest of max endurance, ICAO limit, constraint.
Offset LAT REV at the FROM waypoint, 1 to 50 NM left or right from PPOS. Not on approach legs. Cancel with a DIR TO or a zero entry.
Overfly OVFY key puts a triangle in the scratchpad; press the waypoint key. The aircraft passes over it instead of turning early.
Airways and waypoints Up to 5 airways by VIA. Pilot waypoints: LL, PBD, PBX, PD. When NAV is engaged, change the TO waypoint only with DIR TO.
Chapter 9 · Flight Management System and MCDU
21
e-books by eatpl.in · © 2026 · Do not copy or distribute
Here are four more lateral tools. Holds come in three kinds. Hold to fix and hold to altitude are part of database procedures and exit automatically. The hold with manual termination is the one you insert, at a waypoint or at present position, and you leave it with IMM EXIT. Its default speed is the lowest of maximum endurance speed, the ICAO limit and any constraint. An offset is entered from a lateral revision at the FROM waypoint, between one and fifty miles left or right, starting from present position; it cannot be flown on approach legs and is cancelled by a direct to. The overfly key makes the aircraft pass exactly over a waypoint before turning. Finally, you can string up to five airways with VIA, and create your own waypoints by latitude and longitude, place bearing distance, or two radials.
Part 4 · Flight plan
Constraints and the vertical plan VERT REV: speed limit , speed and altitude constraints , RTA , step, constant Mach, winds Constraint missed : altitude > 250 ft off, speed > 10 kt fast Magenta star : predicted met · amber star : predicted missedALT CSTR used in CLB, DES, APP NAV-FINAL ; SPD CSTR only with NAV + managed speed Constraints at or above CRZ FL are deleted Windows (two altitudes) come only from the database UTC SPD/ALT PENAM 0750 280/ FL240 * KIDOS 0756 250/ 9800 * ROLIP 0758 220/ 7000 * * magenta * constraint predicted to be met amber * predicted missed → error shown on VERT REV ALT CSTR missed predicted more than 250 ft away SPD CSTR missed predicted more than 10 kt faster SPD CSTR used only in NAV with managed speed ALT CSTR used in CLB, DES or APP NAV-FINAL CSTR ≥ CRZ FL deleted: CSTR DEL ABOVE CRZ FL SPD LIM one in climb, one in descent
Chapter 9 · Flight Management System and MCDU
22
e-books by eatpl.in · © 2026 · Do not copy or distribute
The vertical flight plan is shaped by constraints. From a vertical revision you can set the climb or descent speed limit, a speed or altitude constraint at a waypoint, a required time of arrival, a step climb, a constant Mach segment, or winds. Once predictions exist, a constraint shows as a star beside the predicted value. Magenta means the computer expects to meet it. Amber means it expects to miss it: for altitude that is more than two hundred and fifty feet away, for speed more than ten knots too fast. Here KIDOS shows an amber star. Altitude constraints are only flown in the managed vertical modes, climb, descent or the final approach mode. Speed constraints need NAV and managed speed. Any altitude constraint at or above the cruise level is deleted, with the message CSTR DEL ABOVE CRZ FL.
Part 5 · Performance
The eight flight phases PREFLIGHT — → TO: SRS and N1 > 85 % or GS > 90 kt TAKEOFF V2 (V2 + 10) → CLB: ACC ALT or other V mode CLIMB ECON CLB → CRZ: CRZ FL reached CRUISE ECON CRZ MACH → DES: < 200 NM, or FCU ALT < FL 200* DESCENT ECON DES → APPR: DECEL in NAV < 9 500 ft AGL, or manual APPROACH VAPP → GA: TOGA → DONE: 30 s after landing GO AROUND VAPP or current → APPR: manual → CLB: ALTN, NEW DEST DONE — → PREFLIGHT: INIT or PERF key TOGA/FLX ACC ALT T/C T/D DECEL touchdown * or below the highest descent altitude constraint, if higher Each phase has its own speed profile. The FMGS phases are not the same as the ECAM flight phases.
Chapter 9 · Flight Management System and MCDU
23
e-books by eatpl.in · © 2026 · Do not copy or distribute
The vertical plan is cut into eight flight phases, each with its own target speed. Preflight switches to takeoff when the SRS mode is engaged with N one above eighty five per cent or ground speed above ninety knots. Takeoff becomes climb at the acceleration altitude, where the target jumps from V two plus ten to the climb speed. Climb becomes cruise when the cruise level is reached. Cruise becomes descent when you start down within two hundred miles of destination, or select a low enough altitude. Descent becomes approach when you pass the DECEL point in NAV below nine thousand five hundred feet above the ground, or when you activate it manually. From approach, TOGA gives go around, and thirty seconds after landing comes done, which clears the flight data.
Part 5 · Performance
Cost index and ECON speed CI = cost of time ÷ cost of fuelCI 0 : minimum fuel (max range) · CI 999 : minimum timeECON speed depends on CI, CRZ FL, weight, wind and temperature , PERF factor ECON CLB and DES are frozen once their phase is active Cruise: Mach above FL 250 , speed below OPT FL : most economic level; needs 5 min cruise at FL 100 or aboveslower ← cruise speed → faster cost per NM ECON · CI 0 (max range) ECON · CI 40 ECON · CI 120 CI = time cost ÷ fuel cost higher CI → the minimum moves to a faster ECON speed CI 999 = minimum time · illustration, not to scale
Chapter 9 · Flight Management System and MCDU
24
e-books by eatpl.in · © 2026 · Do not copy or distribute
The cost index tells the computer how your airline values time against fuel. It is the cost of flight time divided by the cost of fuel. A cost index of zero means fuel is all that matters, giving maximum range speed. Nine hundred and ninety nine means time is all that matters. The illustration shows the idea: fuel cost per mile has a minimum at a fairly slow speed, and adding a time cost moves the cheapest point, the ECON speed, faster as the cost index rises. ECON speed also depends on cruise level, weight, wind, temperature and the performance factor. Climb and descent ECON speeds are frozen once their phase starts; cruise ECON is updated continuously. The optimum flight level on the PROG page is the most economic level, and it can jump as weight, wind and temperature change.
Part 5 · Performance
PERF TAKE OFF V1, VR, V2 are crew entries; no V2 → no SRS Checks: V1/VR/V2 DISAGREE if not V1 ≤ VR ≤ V2; TO SPEED TOO LOW F, S and green dot computed from takeoff weight THR RED / ACC : default 1 500 ft above runway (or airline), minimum 400 ft TO SHIFT , FLAPS/THS and FLEX TO TEMP Runway or shift changed later: CHECK TAKE OFF DATA TAKE OFF RWY 28 V1 FLP RETR VR SLT RETR TO SHIFT V2 CLEAN FLAPS/THS TRANS ALT FLEX TO TEMP 4000 [ ]° THR RED/ACC ENG OUT ACC 2280/2280 2280 UPLINK NEXT <TO DATA PHASE> F= 150 S= 196 [M] [ ]* O= 212 [ ]/[ ] 1L 1R 2L 2R 3L 3R 4L 4R 5L 5R 6L 6R V1 · VR · V2 amber boxes: mandatory; no V2 → no SRS THR RED / ACC default 1 500 ft above runway, min 400 ft FLEX TO TEMP sent to the FADEC, shown on the E/WD F · S · O green: computed flap, slat, green dot speeds
Chapter 9 · Flight Management System and MCDU
25
e-books by eatpl.in · © 2026 · Do not copy or distribute
The takeoff performance page is where most cockpit preparation errors happen, so learn it well. V one, V R and V two sit in amber boxes because they are mandatory, and they come from your takeoff performance calculation, not from the FMGC. Without V two the SRS mode is not available. The computer checks that V one is not more than V R, and V R not more than V two, and that the speeds are not below the minimum control speeds. In green it shows the flap retraction, slat retraction and green dot speeds. Thrust reduction and acceleration altitudes default to fifteen hundred feet above the runway, or the airline's value, and can be lowered to four hundred feet. You also enter the takeoff shift, flaps and trim setting, and the flex temperature, which goes to the engine computers.
Part 5 · Performance
PERF APPR and VAPP Inside 180 NM the QNH field turns to amber boxes Enter QNH , TEMP and MAG WIND : they shape the descent profile VAPP = VLS + ⅓ headwind , limited to VLS + 5 to VLS + 15 kt VLS = 1.23 VS1G of the landing configuration FULL is the default; select CONF 3 if neededMDA or DH for the minima; activate APPR manually if needed APPR QNH FINAL 1006 ILS27 TEMP MDA 29° [ ] MAG WIND DH 270°/021 [ ] TRANS FL LDG CONF FL100 CONF3* VAPP 138 FULL PREV NEXT <PHASE PHASE> 1L 1R 2L 2R 3L 3R 4L 4R 5L 5R 6L 6R VAPP = VLS + ⅓ headwind, between VLS + 5 and VLS + 15 kt VLS 131 kt increment VAPP calm +5 (minimum) 136 kt 20 kt headwind +7 138 kt 60 kt headwind +15 (maximum) 146 kt
Chapter 9 · Flight Management System and MCDU
26
e-books by eatpl.in · © 2026 · Do not copy or distribute
The approach performance page is completed in cruise, before descent. Beyond one hundred and eighty miles the QNH field shows brackets; inside one hundred and eighty miles it becomes amber boxes, and ENTER DEST DATA appears if you have forgotten. The QNH, temperature and magnetic wind at the destination are used to build the descent profile. The approach speed is the lowest selectable speed plus one third of the headwind, but never less than five knots or more than fifteen knots above it. With a lowest selectable speed of one hundred and thirty one knots, calm wind gives one hundred and thirty six, a twenty knot headwind gives one hundred and thirty eight, and a sixty knot headwind is capped at one hundred and forty six. Full flap is the default landing configuration; you can select configuration three here.
Part 5 · Performance
The PROG page CRZ : change the cruise level (not below the FCU altitude)OPT (green) and REC MAX (magenta)REC MAX: 0.3 g buffet margin, 300 ft/min at MAX CLB, level at MAX CRZ, between green dot and VMO/MMO; no anti-ice VDEV in descent and approachUPDATE AT , BRG/DIST TO any pointREQUIRED , ACCUR HIGH/LOW , ESTIMATED CRUISE EPL202 CRZ OPT REC MAX FL350 FL370 FL391 <REPORT UPDATE AT *[ ] BRG / DIST ---°/---- TO [ ] PREDICTIVE <GPS GPS PRIMARY REQUIRED ACCUR ESTIMATED 2.0NM HIGH 0.05NM 1L 1R 2L 2R 3L 3R 4L 4R 5L 5R 6L 6R CRZ new cruise FL (not below FCU ALT) OPT most economic FL; ≥ 5 min cruise, ≥ FL 100 REC MAX 0.3 g buffet, 300 ft/min, MAX CRZ… (max FL 398) UPDATE AT manual FM position update: last resort
Chapter 9 · Flight Management System and MCDU
27
e-books by eatpl.in · © 2026 · Do not copy or distribute
The progress page changes title with the phase, and the phase name is green. On the top line you can enter a new cruise level, see the optimum level in green and the recommended maximum in magenta. The recommended maximum is the lowest of several limits: a nought point three g buffet margin, the ability to climb at three hundred feet per minute with climb thrust, level flight at maximum cruise thrust, a speed band between green dot and the maximum operating speed, and the certified ceiling. It ignores anti-ice, so check the tables if icing is expected. In descent the page shows VDEV, your deviation from the computed descent path. Below are the manual position update, a bearing and distance to any point, and the navigation accuracy lines: required, high or low, and estimated.
Part 5 · Performance
Predictions: ND short term, MCDU long term ND : what the aircraft will do in the current modesMCDU : assumes you return to the managed flight planOff track: return at 45° or direct to the TO waypoint Selected speed kept until next limit, constraint or phase DECEL in magenta: automatic deceleration; white: noneTrust the ND for short-term, the MCDU for long-term Level-off at the FCU altitude (blue) Level-off at a constraint (magenta) Top of descent (always white) Speed change: SPD LIM, SPD CSTR, hold ALT CSTR met (magenta) / missed (amber) D DECEL: magenta = automatic 10 45 Time marker / equitime point (green) ND: what the aircraft WILL do in the current modes
Chapter 9 · Flight Management System and MCDU
28
e-books by eatpl.in · © 2026 · Do not copy or distribute
Predictions appear in two places, and they answer different questions. The ND shows what the aircraft will do in the modes that are engaged now. So the level off arrow is blue for the FCU altitude, or magenta if a constraint stops you first, the top of descent is white, and the DECEL symbol is magenta only if the deceleration will really happen automatically, meaning managed speed with NAV or approach mode. The MCDU assumes you will go back to the managed flight plan, rejoining at forty five degrees or flying direct to the TO waypoint, and that a selected speed is kept until the next limit, constraint or phase. That gives a simple rule: use the ND for the short term, and the MCDU for the long term, when managed guidance is engaged or about to be.
Part 6 · Abnormal
FMGC resets and failures Event What happens Crew action Reset + resync Automatic, 2–3 s; MAP NOT AVAIL, MCDU MENU, modes may drop Reselect the page, re-engage managed modes, AP, A/THR Single latch 5 resets in 4 min: one FMGC latched, SINGLE mode; OPP FMGC prompt, OFFSIDE FM CONTROL Same ND mode and range; any key on that MCDU; manual reset later Dual reset, data lost 4 dual resets in 3 min: F-PLN, GW, CI, CRZ FL lost; bias lost (MIX IRS); CAB PR LDG ELEV FAULT DIR TO, new DEST, ZFW/ZFWCG, CRZ FL, CI; NAV accuracy check Degraded mode FM PREDICTIONS LOST: no predictions, no managed vertical or speed; lateral still OK Fly selected vertical, or re-enter the CI Dual latch FM and FG lost: MAP NOT AVAIL on both NDs, no AP/FD/A/THR Raw data, RMP tuning, reset both; if no good: NAV B/UP, set LDG ELEV Manual reset Short 10 s keeps crew data · long 15 min clears it In flight, one FMGC at a time
Chapter 9 · Flight Management System and MCDU
29
e-books by eatpl.in · © 2026 · Do not copy or distribute
The FMGCs protect themselves by resetting. A minor reset lasts two or three seconds and is followed by a resynchronisation; you may see MAP NOT AVAIL and the MCDU may jump to its menu, so you simply reselect your page and re-engage what was lost. Five resets in four minutes latch that computer, and you are in single mode: set both NDs to the same mode and range and press any key on the affected MCDU. Four dual resets in three minutes wipe your data, including the position bias, so you rebuild with a direct to, the destination, weights, cruise level and cost index, and check accuracy. If predictions alone are lost, the scratchpad says FM PREDICTIONS LOST. If both computers latch, you fly raw data, tune on the radio management panels and try a reset. In flight, reset only one FMGC at a time.
Part 6 · Abnormal
Other cases to know MCDU MENU SELECT <FMGC NAV B/UP* <ACARS <AIDS <CFDS 1L 1R 2L 2R 3L 3R 4L 4R 5L 5R 6L 6R CLB EO ACT MODE UTC SPD 270 1220 EO CLR* CI PRED TO FL370 EO LRC <APPR PHASE PHASE> 1L 1R 2L 2R 3L 3R 4L 4R 5L 5R 6L 6R CHECK WEIGHT FMGC GW vs FAC GW differ by more than 7 t check FOB and ZFW FMS right → QRH speeds Engine out (FM) Detected by master lever off or engine shut down, N2 below idle, thrust lever split, or FADEC fault. PERF page appears with EO CLR*; preselected speeds, steps and RTA deleted.
Engine-out SID Failure before the diversion point: the EOSID appears as a TMPY to insert or erase. After it: stay on the SID; the EOSID shows in yellow.
CHECK WEIGHT FMGC and FAC gross weights differ by more than 7 t. Check FOB and ZFW; if the FMS ZFW is right, ignore PFD VLS, F, S, green dot and use the QRH speeds.
Back-up NAV Both FMGCs failed: MCDU NAV B/UP with IRS (GPS). F-PLN on ND and sequencing, but no NAV mode, no managed speed, no autotuning: fly TRK/FPA.
Diversion tools ENABLE ALTN at a LAT REV, SEC F-PLN then ACTIVATE SEC, NEW DEST, CLOSEST AIRPORTS and EQUI-TIME POINT.
Spurious EO, bad predictions Spurious engine out: EO CLR, re-engage modes, re-enter speeds. Bad predictions: check winds and temperatures; do not reset the FMS.
Chapter 9 · Flight Management System and MCDU
30
e-books by eatpl.in · © 2026 · Do not copy or distribute
A few more cases come up in every type rating. When the FMGS detects an engine failure, it calls up the performance page with an EO CLR prompt, switches to engine-out speeds and deletes preselected speeds, steps and time constraints. Do not press EO CLR for a real failure, because you cannot get the engine-out data back. If an engine fails before the diversion point of the departure, the engine-out SID appears as a temporary plan to insert. CHECK WEIGHT means the FMGC and FAC weights differ by more than seven tonnes: check fuel and zero fuel weight, and if the FMS is right, use the QRH speeds instead of the PFD ones. Back-up navigation keeps a flight plan on the ND with the IRS, but no managed modes. For a diversion, use ENABLE ALTN, the secondary flight plan, or NEW DEST.
Summary
Flight management in eight lines Architecture 2 FMGCs (FM + FG), MCDUs, FCU, FACs. Dual normal; independent, single, back-up NAV.
MCDU Amber boxes mandatory, blue modifiable, green active, magenta constraints, yellow TMPY.
Position FM = MIX IRS + bias. GPS first, then DME/DME, VOR/DME, IRS only. HIGH if EPU ≤ RNP.
Flight plan INIT A, INIT B, F-PLN. Every revision is a yellow TMPY until inserted; DIR TO fixes most problems.
Phases TO at SRS + thrust, CLB at ACC ALT, CRZ at CRZ FL, APPR at DECEL or manual, DONE 30 s after landing.
Speeds CI 0 max range, 999 min time. VAPP = VLS + ⅓ HW, +5 to +15 kt. THR RED/ACC min 400 ft.
Pages PERF TAKE OFF: V1, VR, V2 mandatory. PROG: OPT, REC MAX, VDEV, accuracy.
Failures Reset, single latch, dual reset with data loss, dual latch, CHECK WEIGHT > 7 t, EO CLR.
Chapter 9 · Flight Management System and MCDU
31
e-books by eatpl.in · © 2026 · Do not copy or distribute
Let us pull it together. Two FMGCs, each with a management half and a guidance half, normally work in dual mode, and drop to independent, single or back-up navigation when things go wrong. The MCDU speaks in colours: amber boxes must be filled, blue can be changed, green is active, magenta is a constraint, and yellow is a temporary plan. The FM position is the MIX IRS position plus a bias, with GPS as the best update, and accuracy is HIGH when the EPU is inside the RNP. You build the flight on INIT A, INIT B and the flight plan pages, and every revision waits in yellow until you insert it. Know the phase switching points, the cost index, the VAPP formula and the takeoff page, and know how to recover from a reset. That is the flight management system for the type rating.