SUPPLEMENTARY
PROCEDURES
NAVIGATION
AIRPLANE
OPERATIONS
MANUAL
1-02-80
Page
22
Code
02
REVISION 40
AOM-145/1114
ARRIVAL (RNAV 1/P-RNAV AND RNAV 2)
RNAV arrival operation may only be performed down to the FAF, and
shall not be used on Final Approach, i.e. from FAF to RWY or during
Missed Approach.
Active Flight Plan .......................................................... CHECK
Prior to the arrival phase, verify that the correct terminal procedure
has been loaded. Then, compare the charts with the MAP display
and the MCDU. This includes confirmation of the waypoint
sequence, reasonableness of track angles and distances, any
altitude or speed constraints, and, where possible, which waypoints
are fly-by and which are fly-over.
NOTE: If required by procedure, a check will need to be made to
confirm that updating will exclude a particular NAVAID. A
procedure shall not be used in case of doubt regarding the
procedure in the navigation database.
Flight Progress .............................................................. MONITOR
During the procedure and where feasible, monitor navigation
reasonableness by cross-checks with the conventional NAVAIDs
using the primary displays with the MCDU.
NOTE: - When the contingency plan is to revert to a conventional
arrival procedure the flight crew must make the necessary
preparation.
- For GNSS-based RNAV systems, the absence of an integrity
alarm is considered sufficient. If the check fails, a
conventional procedure must be flown.
- Route modifications in the terminal area may take the form of
radar headings or “direct to” clearances and the flight crew
must be capable of reacting in a timely manner. This may
include the insertion of tactical waypoints loaded from the
database. Manual entry or modification by the flight crew of a
loaded procedure, using temporary waypoints or fixes not
provided in the database is not permitted.