APPROACH PROGRAMMING AND PROTECTED FINAL-SEGMENT DATA
Selecting an approach brings coded path definitions, course/gradient information and missed-approach structure into the flight plan. Some displayed altitudes are predictions or procedure references rather than editable waypoint constraints. The supplied Thales standard also protects particular final-approach fields. Inspect the selected approach and revision page before trying to overwrite a final-segment value that does not behave like an enroute restriction. [66, PDF pp. 205-207,248-268,404-410] [70, Available Options: FLS configuration and approach equipment applicability]
1. Identify the complete approach. Match runway, procedure identifier, transition/VIA and applicable chart. Confirm whether the installation and intended guidance use ILS, another radio approach, FINAL APP or a supported FLS arrangement. Fenix's FLS option establishes equipment availability, not an operational approval for every RNP procedure or proof that an older FINAL APP keystroke sequence applies unchanged. [66, PDF pp. 205-207,248-268,404-410] [70, Available Options: FLS configuration and approach equipment applicability]
2. Inspect the final sequence. Review the intermediate segment, final approach fix, destination runway or missed-approach point and coded missed approach. Check course, gradient and altitude references against the chart. A radio approach's glideslope-intercept reference differs from an editable altitude constraint. The source's final-approach rules explain why a blank ALT CSTR field may coexist with a meaningful altitude displayed in F-PLN. [66, PDF pp. 205-207,248-268,404-410] [70, Available Options: FLS configuration and approach equipment applicability]
3. Investigate protected or absent entries. The cited standard restricts constraint handling at the destination/MAP and within certain precision-approach final segments. Deleting an associated fix or altitude can also remove gradient/crossing information. Do not dismantle the final segment to make it accept an arbitrary number. First establish whether the request belongs in a procedure selection, a valid revision or the aircraft's present selected-guidance plan. [66, PDF pp. 205-207,248-268,404-410] [70, Available Options: FLS configuration and approach equipment applicability]
4. Keep programmed data separate from approach arming. An approach in F-PLN does not itself prove that LOC, G/S, FINAL APP or FLS guidance is armed or captured. Likewise, PERF approach-phase activation is not the FCU APPR selection. Verify the actual equipment, clearance and FMA sequence in the corresponding operational chapter. No unverified FLS-specific binding or universal button recipe is implied here. [66, PDF pp. 205-207,248-268,404-410] [70, Available Options: FLS configuration and approach equipment applicability]
5. Validate after a revision. Reinspect the final approach and missed-approach connection, relevant radio selection, minima and landing configuration. If the intended guidance cannot be supported by the available coded procedure/equipment, retain an understood alternative and resolve the mismatch. A successful route insertion establishes that the FMS accepted the coding, not that every operational requirement for the intended approach is met. [66, PDF pp. 205-207,248-268,404-410] [70, Available Options: FLS configuration and approach equipment applicability]