737 MAX Flight Crew Operations Manual
Supplementary Procedures -
Automatic Flight
SP.4.8
MN-FLT-OH-201
Note:
Do the Go-Around and Missed Approach Procedure if the
UNABLE REQD NAV PERF-RNP, FMC DISAGREE, or any
VERIFY POS alerting message is shown unless suitable visual
reference is established and maintained.
(SB Changes YF631, YF632, YL621, YR619)
WARNING: If an UNABLE REQD NAV PERF-RNP is shown
during the approach, whether the lateral or vertical
RNP are exceeded or not, do the Go-Around and
Missed Approach Procedure unless suitable visual
reference is established and maintained.
Do the following before starting the approach
• verify that the UNABLE REQD NAV PERF-RNP alert is not
displayed
• verify that the approach RNP is equal to or greater than:
YC095, YF703 - YF832, YL806 - YM648, YN109 - YN112, YN701 - YV671
• 0.10 (A/P or F/D)
• set current local altimeter (remote altimeter settings not allowed)
• verify that the wind is within limits published for the approach (if
applicable)
• verify that the reported airport temperature is within published limits
for the approach
• review the maximum IAS for each segment of the approach as
determined by aircraft category and applicable regulatory airspeed
requirements.
Cruise Procedure
Pilot Flying
Pilot Monitoring
When selecting the approach from the
navigation database verify ACT RTE X
LEGS page matches the charted
approach.
If there is an “at or above” altitude
restriction before the FAF, it may be
changed to an “at” altitude restriction
using the same altitude.
Speed modifications are allowed as
long as the maximum published speed
is not exceeded.
March 1, 2021
