737 MAX Flight Crew Operations Manual
Normal Procedures -
Amplified Procedures
MN-FLT-OH-201
NP.21.80
• Check if GPS is installed (FMC - POS INIT page 2/3) and check
GPS update ON (FMC - NAV Options page 2/2);
• Approach is not allowed with “UNABLE REQUIRED NAV
PERF” displayed on FMC;
• Correct Approach RNP value of 0.3 must be checked on Progress
Page 4/4 before commencing the approach;
• Procedure should be performed in LNAV. RNAV (GNSS) only
procedures should be flown in VNAV mode;
• BARO V-NAV procedures must be flown in VNAV mode.
Otherwise MDA related to “LNAV only” applies;
• Altitude restrictions are set on the MCP considering IAF, FAF and
DA. They are released after its compliance is assured and about
2NM prior to the waypoint;
• After FAF and at least 300ft below the missed approach altitude,
set the existing Go Around altitude restriction on the missed
approach altitude on the MCP;
• When V/S is used, altitude restrictions must be released step by
step on the MCP. After its compliance is assured, set the next
restriction on the MCP (about 2NM before the next waypoint);
• Altitudes restrictions should be checked, and must remain as “AT
OR ABOVE” after the IAF if they are like this on the FMC
database, to comply with the FMC Glide Path and prevent
unwanted level offs;
• Center map with VSD is the standard display configuration for the
Pilot Monitoring during the approach. The Pilot flying display
must be in the Expanded MAP Mode;
• GPS or BARO V-NAV course may differ from those of ILS/VOR
approach for the same runway.
• As pilot’s discretion, consider to edit in the FMC the flap 1
maneuvering speed on the Initial Approach Fix or plan to be with
that configuration 15NM prior to the runway on the procedure
profile, whichever is closer, as well as with flaps 15 speed on the
FAF;
• If the speeds are not edited in FMC, the system logic may assume
higher speeds upon Initial Approach Fix and this amount of energy
must be worked upon during the approach.
March 1, 2021