FMC/CDU Programming
B787 & B777X
Easy guide to basic functions
and hints on EFB
Rev 1.0 - ENG
08/18/23
Marco Ramondino
Simulation only - not for real flight
This guide is intended for simulation only and covers only the basic functions of the FMC/CDU of the
Boeing B787 and B777X. Therefore, only the menus and functions essential for flying will be illustrated
and some more in-depth topics will not be covered.
For those familiar with the FMC of other Boeing aircraft, many of the pages/menus as well as the
operating principle will be very similar.
Depending on the simulators and aircraft developers, not all functions may fully correspond to those
described below and some may not be operational, as well as the naming and layout of some buttons
may change. The indications described here and the general functioning remain valid in principle even in
the event of discrepancies on the various simulators.
This guide is not a substitute for comprehensive checklists and procedures, which you should always
review.
For the system to function, it is necessary to enter the data relating to a flight plan, which can be
generated using special software (such as Simtoolkitpro or Volanta) or web services
(eg flightplandatabase).
You can download also the FMC/CDU guide of:
the other Boeing series at this link;
the Airbus MCDU at this link;
the FMC UNS-1 at this link.
Content index
Introduction
Overview
4
Preflight flow
7
INIT REF
8
Simulation only - not for real flight
Preflight pages
IDENT
9
Performances initialization (PERF INIT)
13
Position initialization (POS INIT)
10
Thrust settings (THRUST LIM)
14
Route (RTE)
11
Takeoff settings (TAKEOFF REF)
15
Departure/Arrival (DEP/ARR)
12
Operational pages
LEGS and discontinuity
16
Radio settings (NAV RADIO)
25
LNAV
18
FIX
27
VNAV
21
Holding (HOLD)
28
Landing settings (APPR REF)
24
EFB (Electronic Flight Bag) - cenni
34
FMC error messages
36
Consultation pages
Alternate airport (ALTERNATE)
29
Route data (RTE DATA)
30
Navigation data (NAV DATA)
31
Flight progress (PROG)
32
Appendix
Synthetic preflight
33
INTRODUCTION
Simulation only - not for real flight
FMC/CDU overview
(or MCDU= multi-function control display unit)
On the B787 & 777X, the FMC/CDU is integrated into the MFD (multi function display, or
lower display unit) in the center of the pedestal, flanked by two physical alphanumeric
keypads that also include lower display control keys.
The graphics and operating philosophy recall those of the FMCs of the other Boeing series,
with the difference that the selection keys (LSK) and the function keys in this case are virtual
(therefore reproduced on the display).
FMC DISPLAY (CDU)
Displays pages, input fields and
their respective data
SCRATCHPAD
It shows the data we type
MFD(lower display unit) CONTROL KEYS
They manage the functions of the entire central
display (CDU-Onboard systems, Navigation
display, etc.)
LINE SELECT KEYS (LSK)
They select the corresponding fields to enter data
or activate options
ALPHANUMERIC KEYPAD
Used to enter the data to be entered.
The PREV and NEXT PAGE keys are used to
navigate between pages (in menus that contain
more than one page), while the EXEC key makes
some settings and changes operational
The letters “E,N,S,W” appear framed because in
some functions they represent the corresponding
cardinal points
MENU/PAGES FUNCTION KEYS
They allow access to menus/pages
The EXEC, PREV and NEXT PAGE keys repeat
the same physical keys on the keypad
Just as the FMC/CDU is reproduced on both sides (one for Cpt and one for F/O), the main display is also split
into two equal parts. Each side can independently display certain functions, so for example one half can play
the FMC and the other the systems page. These functions are controlled by the keys at the top of each
physical keyboard
CDU overview
INTRODUCTION
Some
pages
contain
subpages,
indicated by the number at the top left
of the display.
Use the PREV & NEXT keys to
navigate through them
Simulation only - not for real flight
ENTER activates scratchpad data entry
EXEC allows the system to acquire the
entered data (repeats the same key shown on
the display)
L
R
1
1
2
2
3
3
4
4
5
5
6
6
The line selection keys (LSK) are ideally
numbered from 1 to 6 and are subdivided
into the left (L) and right (R) column, they
will later be called 1R, 2R, etc. and 1R,
2R etc.
The fields that can be filled in or modified
are indicated by boxes with a gray
background (so-called "open").
When the field adjacent to a selection key
is not selectable or cannot be filled in
(because it is empty or because it is filled
in automatically by the system), the
corresponding LSK will be shown empty
and highlighted in blue
INTRODUCTION
When the aircraft systems are powered up,
the CDUs are shown by default on the
lower display, with the initial page IDENT.
CDU overview
To enter data, type it into the scratchpad using
the alphanumeric keyboard.
The fields in which they will be entered will be
highlighted in magenta
Simulation only - not for real flight
During the
lower right
step and
completion
preflight cycle, a prompt in the
(LSK 6R) takes you to the next
a status bar indicates the
of the sequence (not on all
simulators/developers)
Otherwise:
- if the CDU are not
displayed, press the
appropriate
key
(above the numeric
keypad) to activate
it;
- if the CDU is displayed but not the IDENT
page, click Line Select Key (LSK) 6L to
display the INDEX page where you can
select the IDENT page (lsk 1L in the menu
that will appear)
The IDENT page does not contain any item to enter
(indicated by open boxes) but only provides some
information, the most important of which is the
navigation database, ACTIVE for the range of dates
indicated (AIRAC cycles).
If the navigation database is not updated, this is
indicated by a message. This does not affect the
ability to fly, but some inconsistencies with the flight
plan may occur (e.g. waypoints may not match or
SID and STAR may vary) as procedures change
Illumination of the EXEC button, accompanied
by an acoustic signal, indicates that it is
necessary to press the EXEC button for the
system to acquire the entered data
In the lower part, any system messages are
displayed, in a special window which is
shown if necessary and which can be
canceled using the CLR MSG key
INTRODUCTION
Simulation only - not for real flight
Standard flow of the preflight menu
During programming, some menus and submenus have a defined sequence. As we have seen, during the preflight a prompt in the lower right indicates
the progress towards the completion of the sequence. Selecting the prompt key displays the next page in the loop. If a page is skipped, a prompt on the
TAKEOFF page takes you back to the page with the missing data.
Entering the current position is sometimes optional as the IRS has continuous access to the GPS position on some simulators (so it is not always
necessary to enter a current position during the IRS alignment as on most FMCs).
The minimum route data is the origin and destination airports and a route.
Performance data requires input of aircraft weight, fuel reserves, cost index and cruising altitude.
Takeoff data requires flap setting and center of gravity (CG).
The main preflight cycle takes place according to the following flow. After this sequence, it will always be possible to access the pages using the menu
keys.
IDENT
POS INIT
RTE
POS REF
RTE 1
etc
DEPAR
TURE
PERF
INIT
THRUST
LIMIT
TAKEOFF
REF
TAKEOFF
Pg2 etc
Sometimes extra pages are needed. These
pages have no prompts and interrupt the usual
sequence. When the route includes SID and
STAR, these can be entered using the DEP
ARR (departure/arrival) key
DEP
ARR
DEP
Rwy, sid
ARR
Rwy, star
Remember that...
on some pages, data entry will be followed by the
illumination of the EXEC button, accompanied by an
audible signal: this indicates that it is necessary to press
the EXEC button for the system to acquire the data.
INTRODUCTION
Simulation only - not for real flight
INIT REF MENU
From the INIT REF button, the INIT/REF INDEX* page opens, which contains:
on the left
a menu with options for navigating to all other pages;
1. Identification (IDENT) The IDENT
page is used to verify basic aircraft
data and currency of the navigation
database
2. Position (POS) The POS INIT
page is used for IRS initialization
3. Performance (PERF) The PERF
INIT page is used for initialization of
data required for VNAV operations
and performance predictions
4. TAKEOFF The TAKEOFF REF
page is used to enter takeoff
reference data and V-speeds
5. APPROACH The APPROACH REF
page is used for entry of the approach
VREF speed
on the right
a series of functions concerning the flight plan
1
6
2
7
3
8
4
9
5
10
11
6. NAV DATA The REF NAV DATA
page is used for data on waypoints,
navaids, airports, and runways. NAV
DATA pages are accessible only from
this page
7. FLIGHT PLANS The FLIGHT
PLANS page allows selection of User
stored flight plans**
8. LOAD ATC RTE The LOAD ATC
ROUTE prompt loads the any active
default FSX Planner Generated
Route**
9. LOAD PNL The STORED PANELS
page allows selection of any user
stored panel states**
10. SAVE PNL The SAVE PNL
prompt saves the current panel state
for retrieval in the LOAD PNL page**
11.
SAVE
FPL
The
SAVE
FLIGHTPLAN prompt saves any
currently Loaded Flightplan**
**
These
features
are
implemented on all simulators
* the contents of this menu may change depending on the simulators/developers
not
PREFLIGHT
IDENT page
Simulation only - not for real flight
As we saw in the introduction, IDENT is the first page that will appear at the beginning of the sequence. You do not need to fill in
any of the entries in it and it only contains information on:
Time and date
Aircraft type
Navigation Database
in use
(AIRAC cycle)
Operating
system
number and version
(it may also contain a part
marked with "U", which
indicates the update)
Max engine power
allowed in the
performance
database
AIRAC cycle validity
From this page select
POS INIT
to start the flight
planning sequence
Until the required preliminary entries are incomplete,
the wording “PRE-FLT” is displayed on the right side
of the dotted line
If the AIRAC cycle has expired, this
message indicates it.
As mentioned in the introduction, this does
not affect the ability to fly, but may cause
some inconsistencies with the flight plan
(e.g. waypoints may not match or SID and
STAR vary) as some waypoint naming and
procedures are continuously updated
Pages that require input appear below the dotted line
as a prompt
When the preflight items are complete, “FMC
PREFLIGHT COMPLETE” is displayed on the dotted
line against a green background
PREFLIGHT
Simulation only - not for real flight
POS INIT page
Entering the position of the aircraft (and geographical coordinates): on this page, the system indicates the current position
of the aircraft and asks us to enter only the code of the airport where we are currently located.
ICAO CODE
of the airport
GATE
(optional)
Type the ICAO code of the airport into the
scratchpad and enter it in the appropriate field
with the LSK 2L key.
The gate can also be entered in the same way
The position currently shown is the real one, since in this
type of aircraft the inertial platforms (IRS) constantly
detect it from the GPS. It should therefore not be
necessary to tell the system what your current exact
location is
If the IRS does not align automatically, it is possible
to do it manually by copying the GPS POS
geographical position (click on the 4R selection key)
and pasting it in the SET INERTIAL POS field (click
on the 5R selection key)
After filling out this page, select the ROUTE prompt (LSK 6R) to go
to the next step
PREFLIGHT
Simulation only - not for real flight
ROUTE page – ROUTE INIZIALIZATION and ENTRY
Once the previous step has been completed, we will be taken to the
ACT RTE 1 page, which requires the insertion of:
Origin Airport
(ICAO)
Takeoff
runway
Destination
Airport
By the NEXT PAGE key you pass to the
following pages, where there are the
waypoints and the airways of the flight plan
AIRWAYS
(VIA) identified in the
flight plan by letters
and numbers
WAYPOINTS
(TO)
identified in the
flight plan by only letters
(except landing runway)
Flight number
(optional)
Click on ACTIVATE
The EXEC button will
light.
Click on EXEC
We can also access this page using the RTE key
Use the PREV and NEXT
PAGE keys to navigate in
the sub-pages of the flight
plan
After entering or modifying the fields, always press
the ACTIVATE (6R) item and then EXEC to let the
system acquire the data
To obtain waypoints and airways of a route it is necessary to generate a flight plan
PREFLIGHT
DEP/ARR page - DEPARTURE (and ARRIVAL) SETTINGS
Simulation only - not for real flight
With the DEP ARR key we enter the settings page for the departure and arrival airports.
On this page we will have on the left the options for the departure airport (1L) and on the right for the arrival one (2R).
DEPARTURE
ARRIVAL
On this page we can select the runway and a standard
instrument departure (SID).
If the departure rwy has already been entered, it will
already be shown.
From this page, which works exactly like the previous
one, we can select the landing options. This step can
be performed (or modified) even during the flight.
On the right side there are the runways available for
take-off and on the left side the SIDs relating to the
selected runway
On the right side we find a list of approaches (with
relative runways)* and on the left a list of approach
procedures (STAR) available for the selected runway
Always press EXEC after selection
In some simulators, once the RTE page has been completed
and the route has been activated, an entry appears in the 6R
field which leads directly to the DEPARTURE page
* Selecting an ILS approach
automatically tunes the NAV
radios and the COURSE.
Selecting a back course
approach
(B/CRS)
automatically tunes the ILS
and displays the front
course
If arrival transitions are listed, you can choose one (not
mandatory)
PREFLIGHT
Simulation only - not for real flight
PERFORMANCE INITIALIZATION page
On the performance initialization page, you need to enter some aircraft parameters so that the system can correctly
calculate speed, altitude, time and fuel consumption.
To access the page, press the INIT REF key.
If the PERF INIT page is not
This page can also be accessed from
displayed directly from INIT REF,
select the PERF item
the previous step, by pressing INDEX
at the bottom left (6L) and selecting
PERF from the list
GROSS WEIGHT (plane+pax+cargo+fuel). It is entered
automatically by the system and is calculated after
entering the Zero Fuel Weight.
Manual entry is not permitted
AMOUNT OF FUEL EXPECTED for the flight
CRUISE ALTITUDE *
Indicated on the flight plan or by ATC
ZERO FUEL WEIGHT: Weight of the aircraft +
passengers + cargo excluding fuel (sometimes it is
entered automatically by clicking on the button,
otherwise it can be found in the EFB on the FUEL,
WEIGHT & BALANCE page)
COST INDEX **
it is an (arbitrary) value ranging from 0 to
2000 and indicates how cheap we want
the flight to be: the lower it is, the
cheaper the flight will be
FUEL RESERVE
(total onboard - estimated consumption)
CRUISE CENTER OF GRAVITY
Displays the default value of 28.0% in
small print. Valid values are 6.0 to 39.5. It
is entered automatically
* The
cruising altitude can be entered by the pilot or by the
uplink. Usually the field is already filled in when this page is
opened, and in this case it can be changed.
Valid values are in the format XXX, XXXX, XXXXX, or
FLXXX.
Cruising altitude is also displayed on the CLB and CRZ
pages
**The C.I. affects some aircraft performance, such as speed
or rate of climb (which, however, can always be changed
during flight as we will see later)
Once this step is complete, select THRUST LIMIT to go to
the engine performance setting page
STEP SIZE
Displays the ascent rate increment used
to plan the optimal ascent profile. It is
entered automatically (valid manual
entries range from 0 to 9000 in 1000 foot
increments).
For non-zero values, performance
predictions are based on optimal step
climbs; for a value of zero, performance
predictions are based on a constant CRZ
ALT
PREFLIGHT
THRUST SETTINGS FOR TAKE OFF & CLIMB
Simulation only - not for real flight
By the THRUST LIMIT item (6R), which will automatically appear once the previous step has been completed, we go to the engine
performance settings page, in which we can choose the thrust profile for take-off (on the left of the display) and climb (on the right)
and a possible derate, always for both phases.
Assumed Temperature (SEL) and Air Temperature (OAT)
Entering an assumed temperature (SEL) higher than the OAT reduces takeoff thrust. Valid values range from 0
to 99°C.
The entered values replace those previously displayed.
Therefore, by setting a "fictitious" temperature higher than the real one already indicated, the derate is forced.
If TO 1 or TO 2 is selected and an assumed temperature is entered, the thrust is further reduced. If the entry
results in a thrust reduction of more than 25%, the value entered is reset to a value which results in a
maximum reduction of 25%
Take-off thrust (TO)
TO Select the maximum rated takeoff thrust
limit
TO 1 Select the fixed TO1 derate
percentage (-10%) for the takeoff thrust
limit
TO 2 Select the fixed TO2 derate
percentage (-20%) for the takeoff thrust
limit
The word SEL will appear next to the
selected take-off option
!
On some simulators, once this step has been
completed, the wording "FMC PREFLIGHT
COMPLETE" may already appear, but it is instead
necessary to continue to the next page
(TAKEOFF)
Climb thrust (CLB)
CLB Select maximum rated climb thrust
(CLB) limit
CLB 1 Select a percentage derated
uphill thrust limit.
CLB 2 Select a further derated hill-push
limit.
CLB steeper rate of climb
CLB-1 intermediate rate
CLB-2 lower rate
(CLB is selected by default)
The wording ARM will appear next to the
option selected for the climb, since being a
subsequent phase it will be activated once
take-off has taken place
Once this page is completed, we
select TAKEOFF
PREFLIGHT
Simulation only - not for real flight
TAKEOFF REFERENCE page
On the THRUST LIM page, selecting the TAKEOFF prompt (6R) opens the TAKEOFF REF page, where we can set the takeoff flaps,
acceleration and thrust-reduction height, as well as enter the reference speeds (v- ref).
This page can also be accessed from the INIT REF menu.
Value of flaps for take-off.
Valid values are:
5, 15 or 20 for the B787-8 and 777X;
5, 10, 15, 17, 18 or 20 for 787-9 & 10.
The value can be entered manually or via
uplink from EFB (not always implemented)
Reference speed (V-Ref)
They are entered automatically by the system. If
the fields are empty, just press the selection
keys corresponding to V1, VR, V2 (the speeds
calculated by the system will be copied).
The values can be changed manually and in this
case they are displayed in large characters and
replace the speeds calculated by the system
Acceleration altitude (optional).
Displays the altitude above the airport
(corrected for temperature and barometric
setting) at which acceleration to retract flaps
will begin.
The default value is 1500 Ft AGL and can be
changed
TRIM and Center of Gravity (CG)
The CG value is entered automatically by the
system by pressing the corresponding selection
key (4R).
After entering the CG, the FMC calculates the
elevator trim setting for takeoff and displays the
setting value to the right of the CG item (trim
display is in 0.25 unit intervals)
Thrust reduction altitude (optional).
Displays the armed climb thrust value and the
altitude above the airport (corrected for
temperature and barometric setting) where the
reduction from takeoff thrust to climb thrust will
begin.
The default value is 800 Ft AGL and can be
changed
Valid values are between 400 and 9999 Ft
!
Before completing the preflight it is
advisable to check for the absence of
discontinuities (see next page)
Pos shift is the distance between the runway
threshold and the point where the A/T will be
engaged for take-off (optional)
Now the preflight is completed and on some simulators
the wording “FMC PREFLIGHT COMPLETE” may
appear
Once this page is complete,
press EXEC
for the settings to take effect
LEGS and discontinuity check
The LEGS page can be
accessed from the dedicated
key
Once the initial programming has been completed, it is
necessary to check on the LEGS page that the route has been
entered correctly and there are no discontinuities, which will
otherwise have to be corrected. If you have not entered the
entire route in the previous steps, you can do it again in this
phase.
On the LEGS page we find:
Distance to waypoint
Waypoints
and their
orientation
The first wpt of the
list (page 1/x only) is
always highlighted in
magenta because it
is the one we are
directed to
Discontinuity
Any discontinuities
are indicated by
the empty wpt box
and the wording
ROUTE
DISCONTINUITY
below it:
this indicates that
that wpt is not
connected with the
next one.
For the correction
of this problem
see the following
paragraph
Simulation only - not for real flight
Speed /
altitude for the
respective wpt
Below the
transition level
altitude is
expressed in Ft,
above in FL
Speed / altitude
restrictions
Next to the speed or
altitude we could find
the letters A (above)
or B (below), which
respectively indicate
below or above the
value to which they
refer.
In the example
opposite it is
therefore expected to
fly above 5000 ft on
wpts UPEND and
BERKS
By selcting the PLAN mode from EFIS, the
STEPS item will be activated: using the
STEP command, you will pass from each
waypoint to the next one.
In this way it will be possible to scroll the
route in succession and check for any
discontinuities in order to be able to correct
them
On the navigation display we will see a
screen similar to this one
LEGS - DISCONTINUITY CORRECTION
In the LEGS page we can view the entire route, scrolling through each single waypoint using the STEP command at the bottom right
(or the entire pages using the NEXT & PREV PAGE keys) and perform a series of operations that we will see later.
If in the previous steps we have entered only a departure and an arrival or if we have skipped a few wpts, the flight management
system still does not know how to connect the route, generating a discontinuity that we can correct from this page.
When one waypoint is not connected to
the next, the route remains open and
there will therefore be a break.
This can happen because an intermediate wpt is
missing or a wrong wpt has been entered.
This discontinuity point will be reported
with
the
wording
"THEN"
and
represented by the empty field with white
boxes. The words "DISCONTINUITY" or
"ROUTE DISCONTINUITY" will also
appear under the breakpoint
The easiest way to remove the
discontinuity is to copy the first waypoint
after the discontinuity by selecting it with
the LSK next to it (the wpt name will be
displayed in the scratchpad) and paste it
on the empty field, selecting the
corresponding LSK
In the example, CCR (3L) has been selected and
pasted into the discontinuity field with empty boxes (2L)
During operations on waypoints
(even following pages), the page
header will change to "MOD"
(modification)
with
a
white
background and will return to "ACT"
(active) after selecting EXEC
2
1
As we can see, the discontinuity has
been eliminated and the route is now
closed
!
Press the EXEC key to
activate the correction
The one described here is a simplified technique, suitable for
simulation only. In real flights, there are thorough checks and
procedures for correcting such errors.
Simulation only - not for real flight
Failure to press EXEC will only result in the
modification being displayed on the navigation
display and a preview of the corrected route, but
not its actual execution.
LEGS – ROUTE MODIFICATIONS (LNAV)
On the LEGS page you can make changes to your route by adding waypoints
more points on which to better define the vertical profile in the VNAV page, which we will see later):
Non per volo reale
Simulation only - not for real flight
(e.g. to have
For this procedure the EFIS can be set in MAP
mode, in order to have an overview of the whole
route on the ND
ADD WPT
Waypoints can be added anywhere along the route. The added waypoints are always followed by a discontinuity, which must be corrected as we saw in the
previous paragraph.
To add a wpt:
1 type the name of the waypoint in the
2 Identify the position where you want to insert
it and select the adjacent LSK, as if we
scratchpad (in the example EBONY)
(starting situation)
wanted to superimpose the new wpt on the
one already present (in the example on
ELLEN): the new wpt is inserted in the
selected line and the wpt that was in that
position slide forward to the new entry.
Press EXEC key
4
3
(this would be the new sequence)
The inserted waypoint is connected to the
waypoint above it, but is discontinuous with the
next one, so we eliminate the discontinuity
! EXEC
to activate the changes
Once the discontinuity is eliminated, the wpt
will be added to the route in the position we
have chosen (all subsequent wpts will scroll
forward by one position).
With ERASE you can undo your changes at
any time
LEGS – ROUTE MODIFICATIONS (LNAV)
Non per volo reale
Simulation only - not for real flight
On the LEGS page waypoints can also be deleted (e.g. if they were entered by mistake):
For this procedure the EFIS can be set in MAP
mode, in order to have an overview of the whole
route on the ND
DELETE WPT
The procedure for deleting a wpt is very simple:
3
The system will immediately report a
discontinuity, which will have to be eliminated
!
Press EXEC key to activate modifications
1
Press the DELETE key on the keyboard (the word
"DELETE" will appear in the scrcatchpad and the
system waits to know which wpt we want to delete)
2
Select the wpt you want to delete using the LSKs (in the
example we want to eliminate TOCOS, so we press the
LSK 2L)
Press EXEC
Once the discontinuity has been removed, the new route
will be displayed (in the example, TOCOS has been
eliminated and it will go directly from EASON to ELLEN).
Subsequent wpts will all move down one position
LEGS – ROUTE MODIFICATIONS (LNAV)
Non per volo reale
During the cruise it may be necessary skip one or more wpts of the sequence and go directly to
the next one (e.g. for ATC directions or to avoid areas of turbulence, but also to save time/fuel). Even this important
operation, which is called Direct-To, can be performed from the LEGS page:
Simulation only - not for real flight
DIRECT-TO
It is possible to go from the current
position to any subsequent waypoint,
skipping one or more along the route
B
A
3
2
1
To direct-to a subsequent wpt:
A- select the wpt we want to go to (it will
be copied to the scratchpad);
B- paste the selected wpt in place of what
would have been the next waypoint to
reach
Once the modification is activated, we will
be directed to the new wpt (which will now
be highlighted in magenta)
Now we will see as the next waypoint
the one we moved, highlighted again in
white (since the modification has not
yet been activated)
!
Click EXEC to activate changes
For example: from our position on the route, the next waypoint is EASON (in magenta since it is the one we are heading towards),
and the next one would be TOCOS, but we want to skip this last one and go directly to EBINY.
Then we select EBINY and paste it in place of EASON
Then EXEC
In this case there will be no discontinuity, since the wpts are already connected to each other in the same operation
In the steps described in this page and for adding
and deleting wpts, a new route will be drawn on
the navigation display and will be previewed (in
white) and will replace the current one (magenta)
only after pressing EXEC
VNAV – ALTITUDE AND SPEED CHANGES (CLB)
On the VNAV pages, during the flight you can change the planned cruising altitude and the
altitude and/or speed restrictions for the various phases of the flight. The three VNAV pages are
CLB (climb), CRZ (cruise) and DES (descent). Normally the VNAV page that is opened when the
key is pressed is the one corresponding to the current flight phase, but you can always move
between the pages with the PREV & NEXT keys.
Non per volo reale
Simulation only - not for real flight
CLIMB
Use the PREV and NEXT PAGE buttons to scroll
through the VNAV pages (CLB, CRZ, DES)
The Climb Page (CLB) is the first of three pages (1/3) displayed in the VNAV menu. When the
FMC switches to cruise mode (2/3), the climb page data is cleared
You can also remove the speed limit by pressing
the DEL key (to insert the DELETE command into
the scratchpad) and selecting the SPD RESTR
field to remove the speed limit altogether
You can edit:
- the cruising altitude by entering a new one
(e.g. 40000 to set FL400) and inserting it in the
CRZ ALT field (1L)
- the speed limit by entering a new one in field
4L (e.g. 240/10000 to order the system to fly at
240 Kt below 10000 Ft)
You can also change the altitude and
transition level (TRANS ALT or LVL)
by typing a new value in FT (e.g.
8000) and entering it in the 3R field
!
Press EXEC key
to activate changes
VNAV – ALTITUDE AND SPEED CHANGES (CRZ)
The CRZ (cruise) page is dedicated to the settings for the cruise phase. It is very similar to the CLB
page, but differs from it in some items. Displays VNAV related data and is used to monitor and
change altitude and cruising speed.
CRUISE
The cruise phase begins once the ascent is complete. While cruising, the main FMC
pages are CRZ (shown by default) and PROGRESS (accessible from prompt)
CRZ ALT (Cruising Altitude)
Displays the cruising altitude entered on the
PERF INIT page and can be changed.
Valid values for editing are: XXX, XXXX,
XXXXX (in Ft) or FLXXX. Altitude is displayed
in Ft or FL depending on the transition
altitude.
Changing the altitude on the MCP and
pressing the altitude selector enters the MCP
altitude as the active cruising altitude, without
creating a change in the CDU
ECON SPD (Economic Speed) or SEL
SPD (Select Speed)
Displays target speed set in (Kt or Ma)
and can be changed.
ECON SPD is displayed when the speed
is set by the FMC according to the ECON
parameters
Entering a speed manually will change the
header to SEL SPD.
Speed changes can be selected manually
or automatically with selection of other
VNAV modes. Cruising ascents, cruising
descents and step climb can also be
performed from this page.
When using VNAV in ECON mode, the
parameters are based on the ECON SPD
setting, which depends on the cost index
set in the preflight. When a selected
speed is entered, the parameters will no
longer refer to the ECON SPD
!
Press EXEC to activate changes
The title of the page indicates the active cruise (ACT) or
being modified (MOD). The title usually contains ECON for
economy cruising. Depending on the selected speeds, the
title can change to:
ECON CRZ: speed based on cost index;
ECON CRZ CLB or CRZ DES: cruising uphill or downhill with
ECON selected;
MCP SPD CRZ: MCP cruising speed selected
The PROGRESS pages display flight progress data and
are divided into:
RTE DATA, which displays progress data for each
waypoint;
REF NAV DATA, which displays data about waypoints,
navigation aids, airports or runways;
FIX INFO, which displays waypoint data. Page data can
be transferred to other pages to create new waypoints
and fixes
ETA/FUEL
Displays estimated arrival time and calculated
fuel remaining at destination (calculations are
based on optimal climbs and cruising
altitudes).
The line header displays ETA/FUEL W/MOD
when a modification is pending.
OPT/MAX/RECMD suggests flight level
(optimal, maximum and recommended)
Simulation only - not for real flight
VNAV – ALTITUDE AND SPEED CHANGES (DES)
The descent page is used to monitor and manage the descent profile. The descent speeds (shown in the
page title) can be ECON (economical) and SEL (selected manually). The default VNAV descent mode is
ECON and controls the rate of descent in economy mode until a slower rate is reached. When using the
SPD INTERVENTION function on the MCP or when the speed is changed on the FMC a descent is
performed at the selected speed instead.
DESCENT
The page title displays the active (ACT) or modified (MOD)
descent. Usually, the title shows ECON for the economic
descent. Fixed speed descent change the title to:
ECON : speed based on cost index;
MCP SPD: speed selected via speed intervention on the
MCP;
XXXKT or MXXX: fixed rate of descent (in Kt or Ma), due to:
- activation of a selected speed (SEL SPD);
- speed transition;
- speed limit associated with an altitude constraint;
- speed constraints of a waypoint
E/D AT (End of Descent at)
Displays the altitude and the End of Descent
waypoint (the wpt in the descent phase with
the lowest altitude constraint).
The field is blank if no E/D point exists
ECON SPD (Economic Speed) or SEL SPD
(selected)
Indicates the descent speed (in Ft and Ma)
and the value can be changed.
The line header can indicate:
ECON SPD if speed is based on cost index;
SEL SPD if the speed is entered manually or
has been temporarily changed by the system
due to a speed constraint during the
transition (one wpt constraint, speed
restriction or spedd transition).
The speed commanded by the FMC is
indicated in magenta. Initially, Mach is
magenta and Ft white. Below the transition
altitude Ft it turns magenta and Ma white
SPD RESTR (Speed Limit)
Displays the maximum speed that can be
reached below a certain altitude (in the
example 240 Kt below 8000 Ft).
This limit can be forced by entering new
values
!
Press EXEC to activate changes
By the FORECAST prompt you access the page for
entering the descent winds (shown in the flight plan).
These data will be used by the FMC to calculate any
deviation from the route or speed adjustments.
The items to enter are:
Flight Level (decreasing). Valid entry is XXX (FL only)
Wind direction (degrees) and speed (at respective
altitudes). Valid entry is XXX/XX
AT
Displays the next speed/altitude constraint
for the indicated waypoint (in the example on
BERKS we will have to fly at 190 Kt above
5000 Ft).
The field is blank when there is no constraint
Flight Path Angle (FPA), Vertical Bearing (V/
B), Vertical Speed (V/S)
-FPA displays the aircraft's current flight path
angle
-V/B displays the calculated vertical bearing
needed to reach the altitude of the waypoint
we are heading to
-V/S displays the vertical speed required to
reach the altitude of the waypoint we are
heading to
Simulation only - not for real flight
APPROACH REF
Non per volo reale
Before the descent it is necessary to set the system by entering the reference speeds and the
value of the falps for landing, via the APPROACH REF page.
This page is accessed by
selecting the INIT REF key
during descent
Gross weight
Estimated aircraft gross weight at
landing, calculated by FMC.
Only change the value if you expect a
different weight based on fuel
consumption
Runway length
Displays the length in feet and
meters of the selected rwy
ILS information
Displays ILS frequency* and landing
runway orientation
Simulation only - not for real flight
On some simulators, the
INIT REF key may open
this menu. To go to the
APPROACH REF page,
choose
APPROACH
(5L)
FLAPS VREF
Displays the calculated reference speed
for flap extension at 20°, 25° and 30°.
VREFs are automatically calculated and
displayed upon opening the Approach
Ref page.
- Copy one of the suggested items
according to the extension of the flaps
that will be used, by pressing the
corresponding LSK and
- enter it in the FLAP SPEED field (4R) to
set the approach speed.
It is also possible to manually type in a valid
setting for flaps and speed (eg 30/143) and enter it
in the FLAPS SPEED field or calculate more
accurate speeds with the EFB and import them
(see EFB appendix)
* If the runway is equipped with ILS
Wind correction
Displays the wind correction to apply to
the approach speed.
The default is 5 Kt and valid values for
manual entry range from 0 to 20 Kt
NAV RADIO page – FUNCTIONS
Non per volo reale
NAV RAD is a fundamental page especially for navigation aids. This page displays the tuning of VOR,
ILS-GLS and ADF radios and allows you to change frequencies.
Simulation only - not for real flight
The page is accessed using the
NAV RAD key
!
Manual entry of frequencies prevents automatic tuning (autotuning)
of the FMS: if NAV frequencies have been entered manually, they
must be removed to allow autotuning to resume normal operation.
Frequencies
The FMC automatically sets VOR and
DME
for
route
operations
and
procedures. For automatic tuning to be
active, no data must be entered in any
field.
Entering a frequency manually tunes a
VOR and prevents autotuning.
Tuning status
The tuning status is displayed next to the
left and right VOR frequencies. The
identifier and frequencies are shown in
green, while the tuning status in white.
The tuning status items are:
- A (autotuning): the FMC selects a
navaid for the best orientation;
- M (manual): The frequency has been
set manually.
As mentioned, deleting a manually tuned
frequency returns the system to
autotuning.
If a frequency has been entered
manually, to reactivate the automatic
tuning function simply delete the fields
containing the frequencies entered
manually (DEL and LSK key of the
frequency to be deleted)
You can save a frequency for later entry by
typing it into the scratchpad and selecting the
PRESELECT fields (left or right) or copy a
frequency to the scratchpad by selecting VOR L
or VOR R or one of the PRESELECT fields with
the scratchpad empty
Valid entries for manual entry:
- VOR or DME identifiers (e.g. ABC)
- VOR or DME frequencies (e.g. 110.5 or
110.50)
NAV RADIO page – ILS
Non per volo reale
The NAV RAD page is essential especially for autoland, as it contains settings for tuning the ILS
and runway header.
!
Simulation only - not for real flight
Manual entry of the wrong ILS frequencies and COURSE prevents alignment to
the runway. To enable autotuning of the FMS it is necessary to remove any
manual entries. Otherwise the system will not be able to autoland.
ILS
ILS tuning
ILS receivers operate in FMC-managed automatic
or manual tuning modes.
If you do not enter any data, the FMC
automatically tunes the ILS frequency/route
according to the approach selected in the flight
plan. *
CRS (course)
This field is blank in autotune mode.
The position of the aircraft on the route determines
the ILS-GLS mode of operation.
The operating mode items are:
- PARK: the ILS or GLS is not tuned or cannot be
used;
- XXX.XX/YYY PARK: the ILS is tuned to the
selected approach but is not used;
A indicates FMC autotune for approach;
M indicates ILS or GLS is manually tuned.
With a VOR approach selected,
sequencing an IAF/FAF causes the FMC
to automatically tune the VOR frequency.
When the approach has a runway
waypoint, the FMC selects the inbound
route.
The valid entry consists of three digits,
indicating the runway orientation.
Data can be entered manually when
dashes are displayed.
RADIAL Displays the radial from the left
and right VOR stations to the aircraft
For manual entry it is necessary to enter:
- ILS frequency and front course (e.g. 111.55/250
for runway locator EDDF 25C), or
- front course only, if attendance is already entered
(/250)
* The runway must be equipped
with ILS
FIX page
The FIX page allows you to set references on the navigation display.
The most commonly used one allows you to "draw" reference circles with a given radius around a fix
(such as around an airport to help us approach).
On the navigation display we will see our three
references in the form of dashed circles around the
indicated point, with the radius that we have set
Enter in this line the
ICAO code of the
airport
(possibly
followed by the runway
if we want more detail)
or of the wpt of interest
(in the example we
have
entered
the
KORD airport, runway
22L)
Insert in the following 3
lines the radius around
which we want to draw
the circle (as in our
example 5, 10 and 15
Mn) in this way:
/5
/10
/15
To erase a fix, simply select the "ERASE FIX" (6L)
item and then the fix to erase.
Further fixes can be inserted by moving to the
following pages with the PREV & NEXT PAGE
keys
This function is widely used to get an idea, for example,
of where the extension of the flaps or the landing gear
will begin or to remind us of an area with the presence
of constraints or with particular characteristics
Simulation only - not for real flight
HOLD page
The HOLD page, accessible from the appropriate key, is used to insert a holding circuit.
HOLD AT
Displays the boxes to insert the entry fix in
the holding pattern (e.g. a wpt of the route
or defined by the pilot or an FAF already in
the flight plan)
PPOS (HOLD AT Present Position)
Create a holding pattern from your current
location
Simulation only - not for real flight
The page displays the actual or default data on the holding pattern. Entries can be
edited or deleted.
When waiting for the next LNAV event, active commands are displayed in magenta.
When one or more hold patterns are present, the first one will be displayed when the
page is opened, while the other patterns can be recalled from the NEXT HOLD
prompt.
Holding FIX
View the entry fix into the holding
INBD CRS/DIR (Inbound Route/Direction)
Displays course entry and direction of turn.
Valid values are XXX (course in), XXX/X (course in/heading), /
X, or X (heading)
FIX ETA Displays the time the aircraft will pass the next
pending fix
LEG TIME
Displays the waiting time (1.0 MIN by default).
Displays dashes when an entry is entered on the LEG DIST
line.
Valid entry is X, X.X, or .X
LEG DIST (Stage distance)
Allows input of distance between legs for hold.
The entry displays dashes on the LEG TIME line.
Valid entry is X, XX, X.X, or XX.X, where X is any integer
Active holding pattern and exit
course are displayed on the ND in
magenta, changes in white until
activated
BEST SPEED Displays the best speed to hold for the aircraft
gross weight, altitude and flap setting
NEXT HOLD
Displays a new holding pattern
EXIT HOLD
Activate the exit from the holding pattern: the
aircraft will exit the holding pattern once it
reaches the pre-set exit point. Once the output
has been activated, the EXIT ARM item will be
displayed
ERASE Erase all changes
!
Following the execution of the exit hold, only the remaining part of
the holding returns to the correction views. Exiting the holding
pattern before crossing the holding fix (fly-by) may occur if the
course to the next waypoint is not closely aligned with the held
return course
ALTERNATE page
The ALTN (alternate) page displays four airports per page in order of time or distance for choosing
an alternate airport. The page can be accessed via the dedicated key, or from the ALTN (LSK 5R)
prompt on the RTE page.
This page is for view only
The ALTN page is view only and contains a list that helps the pilot find a
suitable alternative airport for landing. To enter any alternate airport, refer
to the procedure for entering the arrival (DEP ARR page)
Alternative airports
ICAO code for alternate airports
- in ETA (Estimated Time of Arrival)
order when airborne e
- in order of distance when on the
ground
FUEL
Displays fuel on estimated arrival at
alternate airport, calculated based on
course, altitude and speed
ETA
at the
Shows the arrival time
alternative airport.
ETA is calculated based on course,
altitude and speed
Simulation only - not for real flight
ROUTE page
Simulation only - not for real flight
The RTE (Route Data) page displays data for each waypoint on the ACT RTE X LEGS page. This
page is accessed via the RTE DATA (LSK 6R) prompt on the LEGS page and is only available for the
active route.
This page is for view only
ETA
Displays the estimated time for
the waypoint
WAYPOINTS
Displays the waypoint identifier
FUEL
Displays the fuel remaining
calculated by the FMC at the
waypoint
The ETA and calculated fuel remaining at the
waypoint are displayed for each wpt.
The ETA and estimated fuel calculations assume a
direct flight through the route discontinuities
NAV DATA page
The NAV DATA page displays data about waypoints, navaids, airports and runways.
This page can be accessed from the NAV DATA (LSK 1R) item in the INIT/REF page menu.
This page is for view only
By inserting in field 1L any waypoint, navaid or airport from
the navigation database, the system will indicate:
The frequency of the
identifier when it is a
navaid
Its geographical coordinates
The elevation if it is
an airport
Simulation only - not for real flight
PROGRESS page
The PROG (progress) page shows flight progress data.
DGT (Distance To GO)
Distance to the respective
wpts and to the destination
This page is for view only
ETA (Estimated Time of Arrival)
Estimated time of arrival at
waypoints or destination
The POS REPORT item (LSK 6R) displays the
position report page, where we find:
TO
The first waypoint on which you
are
going
(displayed
in
magenta)
NEXT
The next waypoint (displayed in
white)
DEST
Shows the destination airport
SEL SPD (selected speed)
The speed mode set on the
FMC is displayed in magenta (it
is the same as the performance
page, unless changed by the
MCP or a limit).
The speed modes are:
-ECON SPD: economic speed
-MCP SPD: Speed entered on
the MCP in the IAS/MACH
indicator
-SEL SPD: selected speed
entered manually in the FMC
WIND
Show current wind (direction /
speed)
Simulation only - not for real flight
POS (position)
Displays the name of the
last waypoint or the
latitude/longitude used to
report the position
ATA
Actual time of arrival on the
last wpt
ETA
Estimated time for the next
wpt
FUEL
Estimated fuel remaining at
next waypoint or destination
To T/C (o T/D)
displays ETA and DTG at Top
Of Climb or Top Of Descent
FUEL QTY
Total amount of fuel
Using the PREV & NEXT PAGE keys it is also possible
to scroll through the PROGRESS sub-pages, which
contain further information, including:
information on wind components (beam, tail and
headwind), course corrections (XTK), static air
temperature, true speed, fuel used
EST (estimated)
Next waypoint we will
reach (active)
NEXT
Waypoint following the
active one
TEMP
Outside air temperature
(OAT)
ALT
Overflight altitude
the last waypoint
of
POS FUEL
Remaining fuel at the
position wpt (POS)
calculated by FMC
Synthetic preflight
0
1
AIRAC cycle
verification
(optional)
2
Airport and gate
settings, check IRS
alignment
4
a
Take-off runway &
sid setting
Origin & destination,
waypoints (TO) &
airways (VIA)
5
Weight, fuel, cost
index, flight level,
etc.
b
3
DEP/ARR - arrival
rwy & star (optional
in preflight)
6
Thrust & derate
settings
(for take off and
climb)
Flaps, elev. trim,
speed ref, rwy
conditions settings.
Route verification
(recommended)
SET FLAPS
SET TRIM
Simulation only - not for real flight
7
EFB – Electronic Flight Bag
The EFB is a tablet-like device conceived in a similar way to the FMC which, in addition to containing various tools (aeronautical and airport charts,
navigation aids, logbook, request for ground services, etc*), allows you to enter some information (in particular take-off settings) more precisely and then
transmit them to the FMC/CDU. Like the FMC/CDU, it has selection keys (LSK) on both sides, which are used to enter menus or select corresponding items.
So let's see how to use the EFB to insert the data for the takeoff reference page (TAKEOFF REF) in the FMC, in particular more accurate v-speeds.
1
Since we have already entered a route, the
INITIALIZE FLIGHT item is available at the bottom
right. As on the CDU, we select the LSK 8R to
enter this page.
The system will load the ORIGIN and
DESTINATION airports already entered in the route
page in the FMC
The PERFORMANCE item will then become
available. Then click on the corresponding
button to open the page
2
The Performance-Takeoff page will be
displayed. Since we have initialized the
EFB, some information (airport, runway,
flap setting, wind, CG, etc.) has been
pre-populated with the data entered in
the FMC.
We will have to import only the take-off
weight data from the FMC, so click on
COPY FMC DATA
Now you need to enter information about
runway conditions and thrust level
Simulation only - not for real flight
3
Once this information has been
entered, the CALC item will become
available.
By selecting it, the EFB will then
provide more accurate V-Speeds than
those already available on the Takeoff
Ref page
* Features included or implemented as well as the
arrangement of the items may change depending on
the simulators.
EFB – Electronic Flight Bag
4
5
The newly calculated v-speeds will be shown in a summary
tab
We therefore confirm that we want to
transmit them to the FMC by ticking the
relative item, then click on COMPLETE to
start the transfer
The performance application
calculates
accurate
performance data for takeoff
and landing.
The calculations are based on
the
combination
of
data
preloaded on the system and
data entered manually.
Preloaded data includes:
- airport characteristics (e.g.
altitude, data on the runway
and on any obstacles);
- aircraft data (engine type,
rating, flaps configuration).
Data entered manually by the
pilot includes:
- current track conditions (e.g.
dry or wet, etc.)
current
environmental
conditions
(e.g.
outside
temperature, wind speed);
- specific configuration of the
aircraft (for example position of
the flaps);
- NOTAM data (that may affect
performance).
We just have to transfer them to the FMC by selecting the
SEND OUTPUT item (8L)
An audible signal will confirm the operation and
the new data will be entered and displayed in
the FMC/CDU
Simulation only - not for real flight
FMC messages
System messages are displayed in the message window on the CDU and can be alerts or warnings.
The alert messages are generally also accompanied by the “FMC MESSAGE” warning message on the EICAS.
Use the CLEAR key and/or correct the condition to remove the message.
Below is a list of possible messages.
FMC Alerting Messages
CHECK ALT TGT
With VNAV active, the aircraft is between the MCP and FMC altitudes. VNAV maintains level flight.
CYCLE IRS OFF - NAV
With the aircraft on the ground any IRS has detected a condition that requires cycling inertial power off and back to
NAV.
DESCENT PATH DELETED
VNAV is active and all waypoint with altitude constraints defining the descent profile are deleted.
Note: This message displays before execution of the modification which deletes the descent path.
DISCONTINUITY
LNAV is active and the aircraft has passed the last waypoint prior to a route discontinuity (except on a manually
terminated leg, such as a VECTORS legs).
DRAG REQUIRED
VNAV is active and additional drag is required or Autothrottle is off and less thrust is required to maintain the VNAV
descent path.
END OF ROUTE
LNAV active and end of active route overflown.
ENTER IRS POSITION
The flight crew-entered present position did not pass one of the IRS comparison checks, or the IRS is ready to
change to navigate mode and has not received a present position entry. Use the CLEAR key to remove this
message.
FUEL DISAGREE or FUEL QTY ERROR
Totaliser Fuel Quantity and FMC calculated Fuel Quantity disagree by a significant amount.
INSUFFICIENT FUEL
Estimated fuel at destination less than entered RESERVES value.
IRS MOTION
An IRS has detected motion while in ALIGN.
FMC Alerting Messages
IRS NAV ONLY
The FMC has been without radio or GPS updating for a predetermined period of time.
IRS POS/ORIGIN DISAGREE
Valid inertial position differs from active origin airport.
LIMIT ALT FLNNN
VNAV engaged and cruise altitude greater than VNAV limit altitude.
NAV DATA OUT OF DATE
The clock calendar date is after the active navigation database valid calendar cycle.
NAV INVALID - TUNE XXXX
RNAV or VOR approach procedures must have a specific navaid tuned or a valid signal is not being received.
NO ACTIVE ROUTE
LNAV is selected and no route is activated.
PERF/VNAV UNAVAILABLE
VNAV selected and either gross weight, cost index or cruise altitude are not entered.
PURGE UPDATES - POS 2
Multiple navaids rejected by the FMC due to a position error.
RESET MCP ALT
2 minutes prior to the top of descent point with VNAV active and MCP not set to an altitude below cruise altitude.
RESYNC FAIL - SINGLE FMC
Resynchronisation attempt failed and one FMC is shutdown.
RESYNCING OTHER FMC
offside FMC has just powered up or failed comparison data check and is being resynchronised to onside FMC.
RW/ILS CRS ERROR
LOC mode armed and the selected ILS course is incorrect for the active route runway.
FMC Alerting Messages
RW/ILS FREQ ERROR
Selected ILS frequency does not match frequency for runway in active route.
SET CLOCK TO UTC TIME
the UTC time from the GPS disagrees with the captains clock by more than 12 seconds.
SINGLE FMC OPERATION
One FMC is not operational.
THRUST REQUIRED
VNAV active, Autothrottle disconnected, and additional thrust required to track VNAV descent path and maintain
speed.
UNABLE NEXT ALT
VNAV active and climb not sufficient to comply with waypoint altitude constraint.
VERIFY POSITION
The difference between the FMC position and other position data exceeds a comparison threshold. The possible
conflicts are:
- the left FMC position differs from the right FMC position;
- the radio position differs from the FMC position;
- the GPS position differs from the FMC position.
VERIFY RNP - POS REF 2
The default RNP (requested navigation performances) has changed due to a change in flight phase and the flight
crew entered RNP value exceeds the new default RNP value.
VIA OFFSET INVALID
Flight conditions invalidate the modification with a divert to an alternate airport via OFFSET.
FMC Advisory Messages
Those messages which are caused by an entry error must be cleared before the entry can
continue.
ARR N/A FOR RUNWAY
The runway/approach selected is not compatible with arrival selected.
CRS REVERSAL AT FA FIX
A conflict exists between the default final approach (FA) waypoint (result of a runway or VFR approach selection) and
the flight plan before it.
DELETE
DEL key pushed.
HOLD AT XXXX
A waypoint not contained in the active route is entered into the HOLD AT box on the RTE LEGS page, after selection
of the HOLD function key. Selection of HOLD AT XXXX into a RTE LEGS page waypoint line makes a holding fix at
the XXXX waypoint.
INVALID DELETE
Deletion of selected data is not allowed.
INVALID ENTRY
Entry format or range is incorrect for the selected field or the entered airway or TO waypoint does not coincide with
the navigation database.
INVALID TUNE REQUEST
Attempt to remotely tune a VOR is not valid.
MANUALLY TUNED
Attempt to remotely tune a VOR that is manually tuned.
MAX ALT FL-XXX
The altitude entry on any CDU page is above the performance calculated maximum attitude.
NOT IN DATABASE
Data is not in the route or the navigation database.
FMC Advisory Messages
NOT ON INTERCEPT HEADING
LNAV selected and the airplane is outside active capture criteria and the present heading will not intercept the active
leg.
ROUTE FULL
The route is filled to the allowable capacity.
RUNWAY N/A FOR SID
Selected runway not compatible with SID.
RW/ILS FREQ ERROR
The selected ILS frequency does not match frequency for runway in active route.
STANDBY ONE
The FMC temporarily prevents further CDU inputs.
UNABLE CRZ ALT
Performance predicts a zero cruise time at the entered cruise altitude.
XXXXX
Altitude set in the MCP window when VNAV is engaged, the CLB or CRZ page is displayed, and the altitude is
above, within 4000 feet below, and not equal to the CRZ ALT.