4.
How to fly localizer based approaches (e.g., transition from FMS to localizer guidance, proper use of altitude preselector, backcourse, appropriate minimums, etc.).
5.
Appropriate use of MDA or DA(H) for an approach.
4.6. Missed Approach/Alternate Destination
The missed approach phase of flight extends from the decision to execute the missed approach until the missed approach procedure is terminated. The alter-nate destination phase of flight starts when the deci-sion is made to proceed to an alternate destination.
Objectives that shall be understood and demonstr ated :
1.
Selection of flight guidance modes and dis-plays for missed approach (e.g.,selecting FD modes, navigation sources, autothrottles, etc.).
2.
Use of LNAV/VNAV to fly a missed approach (e.g., published missed approach procedure, proper use of altitude preselector, etc.).
3.
Modification of FMS active flight plan to meet revised ATC clearances (e.g., deleting altitude/speed constraints, lateral path, updating active flight plan during radar vectors, holding pattern changes, etc.).
4.
Initialization of the FMS for another approach. This includes:
a.
Selection of approach runway, approach, arrival procedure (per clearance).
b.
Comparison of the electronic arrival/approach/missed approach proce-dure to the printed procedure (e.g., overfly waypoints, left or right turns, discontinuity, altitude constraints, speed restrictions, missed approach hold, etc).
c.
Confirmation of landing data (e.g.
Vspeeds, runway required, etc.).
d.
RAIM checks for GPS approaches
(if applicable).
5. Modification of the FMS active flight plan to divert to alternate destination. This includes:
a.
Use of datalink (e.g.,AFISTM, ACARS, etc.) to obtain ATIS, as applicable.
b.
Selection of approach runway, approach, arrival procedure (per clearance).
c.
Comparison of the electronic arrival/ approach/missed approach procedure to the printed procedure (e.g., overfly waypoints, left or right turns, discontinuity, altitude constraints, speed restrictions, missed approach hold, etc).
d.
Confirmation of landing data (e.g.
Vspeeds, runway required, etc.).
e.
RAIM checks for GPS approaches
(if applicable).
