Approach guidance types
Two approaches to the same runway can demand different navigation sources and vertical guidance. Brief the procedure you actually selected, not just the runway.
Approach type
Confirm airport, runway, procedure name and chart validity. Check that the approach selected in the FMS has the same name and transition.
Identify lateral guidance
An ILS uses a localizer; an RNAV approach uses the applicable FMS navigation guidance. Check the selected source and expected lateral FMA.
Identify vertical guidance
An ILS may provide a glideslope; an RNAV procedure may provide an FMS glidepath. Other approaches may lack published vertical guidance.
Read the minimums
Use the chart and the correct line of minima for the procedure and conditions. Minimums are the approach decision reference; ALTSEL is a separate target for the missed approach. FSS says to set the missed-approach altitude in ALTSEL after GP or GS capture.
Brief the missed approach
Brief the track and altitude before final.
Review the initial track, altitude and procedure before reaching the final segment.
PFD and FMA
Before final, confirm that the selected navigation source, FMA modes and guidance deviations match the charted procedure.
The FSS approach table gives configuration examples, including specific minimums treatment. These are simulator instructions with build and procedure applicability; do not substitute them blindly for a current chart.
For a CAT I ILS, the FSS approach-types page [157] specifies BARO minimums and disconnecting the autopilot by 200 ft AGL. The separate limitations page [10] lists a general minimum autopilot-use height of 50 ft without stating the height reference there. Use the CAT I instruction for that approach.
For non-precision approaches, the FSS limitations page lists the MDA as the minimum autopilot-use height. Check the published minimum and the applicable simulator procedure before the approach. FSS limitations [10].
For a VOR approach, FSS describes flying the FMS approach with magenta needles and arming APP. It also calls for the VOR frequency and course to be set in cyan preview as a backup. This backup instruction applies to the VOR approach described by FSS; check the chart and selected procedure.
For its LNAV and VOR examples, the FSS approach table lists MDA plus 50 ft. For its localizer example, it says to round the published MDA up to a whole 100 ft. These entries are specific to the documented simulator workflow; check the applicable chart, approach type and installed version before setting minimums. FSS approach types [157].