
OPERATOR’S
MANUAL
CMA-9000 FLIGHT MANAGEMENT SYSTEM
Page
5-31
November 19, 2009
The display reverts to the page where the duplicated identifier was entered, with the selected identifier in the
data field.
When the operator enters in the flight plan (active or inactive) a waypoint identifier which is not unique, then the
"SELECT WPT" page is displayed if any of the two entry modalities was used:
1. Via the FMS keypad;
2. Via the FMS line select key from any page except the "RTE x LEGS" page(s) or the "PROGRESS" page(s)
or the "RTE x" page(s).
The operator selected waypoint via the "SELECT WPT" page is inserted in the flight plan followed by a
discontinuity.
When the operator enters a unique waypoint identifier in the flight plan (active or inactive) via the FMS keypad
or via the FMS line select key from any page except the RTE x LEGS page(s) or the "PROGRESS" page(s) or
the "RTE x" page(s), the waypoint is inserted in the flight plan followed by a discontinuity.
When the operator inserts a waypoint copied using the FMS line select key on the "RTE x LEGS" page or the
"PROGRESS" page or the "RTE x" page in the flight plan (active or inactive), a close up to that particular
waypoint will be done (if the waypoint is inserted before its current position in the flight plan) or the waypoint will
be inserted in the flight plan followed by a discontinuity (if the waypoint is inserted after its current position in the
flight plan).
If the operator inserts in the active route (inactive route) a waypoint copied from any inactive route (active route)
page then the behavior will be the same as when entering an identifier using the FMS keypad.
NOTE: The flight plan can contain waypoints with the same identifier but with different coordinates (a frequent
case being user waypoints named by the operator with an identifier already existing in the navigation
database).
The custom database (usually built using a navigation database) should not contain duplicate waypoints
compared with the navigation database.
If duplicate waypoints exist then the custom database occurrence will not be shown on the SELECT
WPT page.
This page is printed under user's responsibility
and must not be retained for reference