OPERATOR’S
MANUAL
CMA-9000 FLIGHT MANAGEMENT SYSTEM
Page
A-163
November 19, 2009
WAYPOINT IDENTIFIER [1L, 2L, 3L, 4L, 5L]:
Up to 7 characters (5 characters if Tactical Approach is
configured). Used for entry and/or display of any valid waypoint identifier. Valid entries are: Identifier, Latitude
Longitude, Place/Bearing/Distance, Place/Bearing-Place/ Bearing and Along Track Distance. The active
waypoint identifier is displayed on top of RTE LEGS 1/X page in reverse video (black on white or black on
magenta, or magenta), depending on the installation. The active waypoint cannot be deleted but may be
overwritten. Conditional waypoints cannot be manually entered. They appear as a result of procedure selection
via the DEPARTURES and/or ARRIVALS pages.
If CARP is configured and CRP01/C is entered manually, the waypoints of the CARP procedure (TP, SD, CRP,
XTE, and ESC), except IP, are immediately inserted in the LEGS page and the CARP PLAN 1/3 page is
displayed. If an identifier followed by /C is entered, the waypoints of the CARP procedure (TP, SD, CRP, XTE,
and ESC), except IP, are immediately inserted in the LEGS page and the CARP PLAN 1/3 page is displayed
with the waypoint identifier as PI. IP is only shown in the LEGS pages once it is defined in the CARP PLAN 1/3
page. The CARP procedure waypoints (IP, TP, SD, CRP, XTE, and ESC) are an indivisible group, with no
possibility of removal of a single waypoint or insertion of a waypoint in between. Pressing the LSK of any CARP
procedure waypoint when the scratchpad is empty brings “CRP01” to the scratchpad.
WAYPOINT PROCEDURE [1L, 2L, 3L, 4L, 5L]:
Slash symbol legends indicate a special procedure is
associated with a waypoint: "/
H
" for holding pattern procedure at waypoint, "/
O
" for overfly waypoint, "/
S
" for
search waypoint, “/C” for CARP procedures, "/T" for tactical direct-to, “/A” for tactical approach runway threshold
waypoints. Procedures are cancelled by entering “/” into the scratchpad and pressing the appropriate LSK.
Entering /C over any CARP procedure waypoint displays the CARP PLAN 1/3 page. Entering /C over any other
existing waypoint in the flight plan is not allowed. Entering / over any CARP procedure waypoint removes the
CARP procedure and CRP01 waypoint from the flight plan. From the point of view of the following operations,
the CARP procedure waypoints are an indivisible group and are treated as one waypoint (e.g. the operation on
any waypoint in the procedure produces the same effect as if the procedure was one waypoint): “DELETE”,
close-up of a down path waypoint, insertion of an off-route waypoint. If a CARP procedure is being flown and
some of its points are sequenced, then a direct-to operation deletes the CARP procedure from the flight plan.
If Tactical Approach is present in the flight plan, the following 3 methods can be used to delete the tactical
approach from the flight plan:
•
Entering a forward slash / in the scratchpad and inserting this at the LSK location next to the tactical
approach runway threshold waypoint (e.g. MAP waypoint) in the flight plan (provided none of the tactical
approach procedure related waypoints is currently an active waypoint)
•
Closing out a route. This will completely remove all 3 tactical approach waypoints.
•
Selecting a new destination.
NOTE: That the last item above will not generate any scratchpad message indicating that an approach already
exists in the flight plan. The rationale for this that the crew would be well aware of their intent to enter a
new destination and as such would be no different in philosophy than them selecting a destination to a
new civil destination (e.g. any approach existing in the flight plan would automatically be deleted).
SPEED CONSTRAINTS (or RESTRICTIONS) [1R, 2R, 3R, 4R, 5R]:
Display of mandatory speed in knots
(coming from the Navigation Database or pilot-entered) at the waypoint identified on the same line. Speed
constraints require an altitude constraint at same waypoint. Speed constraints may be manually entered,
modified and deleted (1 to 999 Knots).
The speed/altitude constraints extracted from the navigation database are displayed in small font.
The field to scratchpad transfer of speed constraint is rejected.
This page is printed under user's responsibility
and must not be retained for reference