Route Correction — Fix a Mistyped Destination

intermediate
📍 Route: KJFK → EGLL (initially mistyped as EGKK)⏱ ~3 minutes📊 5 steps🎓 Flight Plans & Routing

The destination is wrong on the RTE page. Overwriting a field you already filled is a distinct skill from filling it.

What this scenario covers

Correcting an entry on the 737 means typing the new value into the scratchpad and line-selecting it over the old one, then executing. Because the change is staged, you get to see the modified route before it becomes real — and can erase it if it is not what you wanted.

The scenario starts with a mistyped destination in place, so the exercise is the overwrite and the verification, not the original typing.

How it applies in flight ops

Reroutes and destination changes are ordinary events: weather, a diversion, a slot, a tail swap. What makes them safe is that the crew treats a changed field as invalidating everything downstream of it until they have looked.

The cross-check is against the source document — the OFP or the clearance — and never against memory. A well-formed wrong entry is indistinguishable from a right one on the screen.

Start this scenario

Open the SimTuts 737 CDU trainer and select “Route Correction — Fix a Mistyped Destination” from the scenarios list to walk through it step-by-step on the simulated keypad.

Open trainer →

Step-by-step: Route Correction — Fix a Mistyped Destination

  1. Press the RTE page key to open ROUTE.

    Real-world scenario: dispatch sends a corrected OFP, or ATC issues a reroute clearance. You need to overwrite an entry that's already there. The 737 CDU requires CLR-and-retype, not edit-in-place.

  2. Type KJFK and press 1L for ORIGIN.

    Same as a normal route entry. The mistake comes next.

  3. Now type EGKK (London Gatwick) and press 1R for DEST. (We'll fix this in the next step — this is the wrong airport.)

    EGKK is London Gatwick, not Heathrow. A common mistake when copying from an OFP — adjacent codes, similar destinations.

  4. You realise the OFP says EGLL, not EGKK. To fix it: press CLR (or Backspace) until the scratchpad is empty, type EGLL, then press 1R again to overwrite DEST.

    On the 737 CDU there is no edit-in-place. Pressing an LSK with new scratchpad content overwrites whatever was there. This is how every correction works on the box, including ATC reroutes.

  5. Type BAW178 and press 2R for FLT NO to confirm the route is now correct.

    Sanity check — fixing one field doesn't reset the others. The flight number, CO ROUTE, and any other entered data persist.

What to take away

  • Overwrite by line-selecting the new value over the old, then EXEC.
  • The staged modification lets you see the change before committing.
  • Everything downstream of a changed field needs re-checking.
  • Verify against the paperwork, not against what you intended to type.

The rest of Flight Plans & Routing

Background reading

← Back to all scenarios