CDU Pages Tour

beginner
๐Ÿ“ Route: EFHK โ†’ ESSAโฑ ~3 minutes๐Ÿ“Š 5 steps๐ŸŽ“ Foundations

A tour of the 737 CDU with nothing to type: where each page lives, so that later scenarios can say "go to LEGS" and mean something.

What this scenario covers

The Boeing CDU is organised around a handful of hard keys โ€” INIT REF, RTE, LEGS, DEP/ARR, PERF INIT, PROG, HOLD, N1 LIMIT and MENU โ€” each of which opens a page or a family of pages. Unlike a modern touchscreen, there is no discovery: you either know the key or you do not.

This scenario visits the major pages in sequence. IDENT confirms the database and model, RTE holds the route, PERF INIT the weights and performance, LEGS the waypoint-by-waypoint detail, and MENU is the way out to the other systems that share the box.

How it applies in flight ops

Boeing's layout reflects the order of work: INIT REF and RTE at the gate, LEGS and PROG in the air, DEP/ARR at both ends. Crews build the muscle memory early in type training and it survives fleet changes within the family.

Knowing where things are is also error-defence. When something on the display looks wrong, the fast question is "which page owns this number?" โ€” and on the 737 the answer is nearly always a single page.

Start this scenario

Open the SimTuts 737 CDU trainer and select โ€œCDU Pages Tourโ€ from the scenarios list to walk through it step-by-step on the simulated keypad.

Open trainer โ†’

Step-by-step: CDU Pages Tour

  1. You start on IDENT. Navigate to RTE to see where the flight plan lives.

    RTE (Route) is where you enter origin, destination, and the route between them. After IDENT, this is the first page every flight visits. Companies that use saved company routes type the route code here; otherwise you build the route on LEGS.

  2. Go to the PERF INIT page. PERF INIT holds the performance setup.

    PERF INIT (Performance Initialisation) is where you enter cruise altitude, cost index, zero fuel weight, and fuel reserves. The FMC needs all of this before it can compute trip fuel and predictions. Required before takeoff.

  3. Go to the LEGS page. LEGS shows each waypoint of the route with predictions.

    LEGS is the in-flight version of the flight plan โ€” every waypoint with altitude and speed constraints, and predicted ETA / fuel at each one. ATC reroutes are entered here. This is the page you look at most after departure.

  4. Open the MENU page. MENU is the FMC system index.

    MENU is the FMC system page โ€” it lists every subsystem the CDU can talk to (FMC, ACARS, MAINTENANCE). On the ground you use it for the FMC self-test. In flight you rarely need it, but knowing where it lives means you can return to a known state if you get lost in nested pages.

  5. Return to the IDENT page to complete the tour.

    The CDU has more pages than these five โ€” DEP/ARR, HOLD, N1 LIMIT, FIX, PROG โ€” but you can fly a complete flight using just the five you have just toured. Master these first; the others are extensions.

What to take away

  • Each major CDU function has its own hard key โ€” there is no menu tree.
  • IDENT verifies the navigation database; check its validity dates.
  • RTE and PERF INIT are gate work; LEGS and PROG are in-flight work.
  • Learn the layout first and every later scenario gets faster.

The rest of Foundations

Background reading

โ† Back to all scenarios