SUPPLEMENTARY
PROCEDURES
NAVIGATION
AIRPLANE
OPERATIONS
MANUAL
1-02-80
Page
20
Code
02
REVISION 40
AOM-145/1114
DEPARTURE (RNAV 1/P-RNAV / RNAV 2)
NAV Database (both pilots) .......................................... VERIFY
CURRENCY
Airplane Position Entry.................................................. CHECK
Desired Path (PNF)....................................................... VERIFY
Airplane Position relative to the Path............................ CHECK
Flight Plan ..................................................................... CHECK
Compare the navigation charts with the MAP display and the
MCDU.
NOTE: - A procedure shall not be used if doubt exists as to the
validity of the procedure in the navigation database;
- The creation of new waypoints by manual entry into the
RNAV system by the flight crew is not permitted;
- Route modifications in the terminal area may take form of
radar headings or direct to clearances.
Airplane Minimum Configuration................................... VERIFY
AVAILABILITY
Also, where applicable, verify if the correct airport and runway data
have been loaded.
NOTE: Where GNSS is used, the signal must be acquired before the
takeoff roll commences and GNSS position may be used
instead of runway update.
Flight Progress .............................................................. MONITOR
During the procedure and where feasible, monitor navigation
reasonableness by cross-check with conventional NAVAIDs using
the primary displays with the MCDU.
NOTE: When automatic update for departure is not available, the
procedure should be flown by conventional navigation means.
If a procedure is designed to be started conventionally, then
the latest point of transition to the RNAV structure will be
marked on the charts. If a Pilot elects to start a RNAV
procedure using conventional methods, there may not be any
indication on the charts of the transition point to the RNAV
structure.