PROG: NAVIGATION AND PREDICTION CROSSCHECKS
Review the cruise reference and available progress information against the preparation completed so far. Some predictions depend on inputs that may not yet be present. Distinguish a missing prerequisite from a value that contradicts the plan before attempting to correct the display. [26, PDF p. 124]
A selected PROG reference provides bearing and distance for monitoring without changing the active route. Use it deliberately when a fix or runway reference helps assess position, and compare it with the wider navigation picture. Selecting a monitoring reference and directing the aircraft to it are separate actions. [26, PDF p. 124]
Continue to PERF after the progress review. DIFRIPPS is useful because it brings the relevant entries back into view, including after an import. With experience the review becomes quicker; retain the readback and consistency checks that make the sequence worthwhile.
IN PRACTICE: PROG: a useful check on the preparation
Before you begin: Route, cruise reference and mass/fuel inputs have been entered. Keep the OFP available so the page can be checked against an independent plan.
1. Review the cruise reference
Action. Press PROG and compare CRZ with the intended FL280 for the exercise. Inspect OPT and REC MAX when available, treating an unexpected result as a reason to revisit the aircraft, mass and planning inputs.
Check. The planned cruise reference is intentional and compatible with the information the aircraft is providing. The page is being read, not simply visited. [26, PDF p. 124]
2. Check navigation information
Action. Review the available GPS-primary/navigation-accuracy information. If it is inconsistent with completed alignment and the aircraft position, investigate the position/navigation pages before taxi.
Check. The information supports the navigation state you intend to use. A plausible route drawing has not replaced a position/accuracy check. [26, PDF p. 124] [26, PDF pp. 492-495] [26, PDF pp. 486-491]
3. Add a monitoring reference
Action. Enter EGLL as the BRG/DIST reference for the exercise, or use the appropriate actual reference. Read the resulting direction and distance as a direct reference measurement, not the remaining route distance.
Check. The bearing/distance reference is meaningful. The active flight plan and next active waypoint have not been changed by this monitoring entry. [26, PDF p. 124]
4. Account for an empty prediction
Action. If an expected value is absent, first check that its route, cruise and mass inputs are complete. Confirm which flight phase/page you are reviewing before treating a blank as a system failure.
Check. Missing inputs and an unexplained computation problem are distinguished. You have not supplied a convincing-looking number just to fill the space. [26, PDF p. 124] [26, PDF p. 123]
5. Recognise the current build’s limitation
Action. If NO-COMPUTATION persists despite coherent inputs, record the conditions and consult the current Fenix issue information. Some V3 prediction cases were reported in the 24–25 October 2026 staff update.
Check. A known-issue check supports diagnosis, but does not automatically excuse every missing prediction or justify changing correct mass and route data. [42]
Complete when: Cruise/navigation information is credible, a monitoring reference is understood, and any missing prediction has been investigated without inventing data.