Speed & Altitude Constraints (VERT REV)

Premiumintermediate
📍 Route: EGLL → DVR → LFPG⏱ ~4 minutes📊 5 steps🎓 Enroute Operations

ATC wants you at an altitude by a waypoint. The vertical revision page is where that promise gets written into the flight plan.

What this scenario covers

A vertical revision is opened by right-selecting a waypoint on the F-PLN page. It carries the vertical data for that point: altitude constraints, speed constraints, and the wind and step information the FMGS uses to build its profile.

Entering a crossing altitude there does more than annotate the display. The FMGS re-plans the vertical path so that the profile actually meets the constraint, which is what makes managed descent able to fly it.

How it applies in flight ops

Crossing restrictions are the currency of arrival management — "cross ABCDE at or below FL100 at 250 knots" is a normal instruction into any busy terminal area. Typing it into the box means the aeroplane will plan for it rather than the crew flying it by hand and hoping.

It is also a trap worth respecting. A constraint the aircraft cannot make is shown as unable, and crews are expected to notice and tell ATC rather than discover it at the fix. The FMGS will tell you; it will not negotiate for you.

Fly this one with Premium

Everything about this scenario is on this page, steps included — reading it costs nothing and always will. What Premium adds is doing it: the MCDU validates every entry as you make it, tells you when an entry was accepted but wrong, and saves your progress across devices.

Step-by-step: Speed & Altitude Constraints (VERT REV)

  1. Enter a route. Type EGLL/LFPG into the scratchpad and press 1R.

    This seeds a route with a discontinuity between EGLL and LFPG — we will close it with a waypoint, then put a constraint on that waypoint.

  2. Press F-PLN to open the flight plan.

    Constraints are entered per waypoint on the flight plan, so we work from the F-PLN page.

  3. Close the gap so there is a waypoint to constrain. Type DVR into the scratchpad and press 2L (the discontinuity line).

    DVR (Dover VOR) is now an enroute waypoint between EGLL and LFPG — exactly the kind of point you would cross at a charted altitude.

  4. Open the vertical revision for DVR. Press 2R — the RIGHT line key next to DVR.

    On the real A320, a LEFT line-select opens LAT REV (lateral — routing); a RIGHT line-select opens VERT REV (vertical — speed and altitude). This is the page where crossing constraints live.

  5. Enter a crossing altitude. Type FL100 into the scratchpad and press 1R (ALT CSTR).

    ALT CSTR FL100 tells the FMGS to cross DVR at 10,000 ft. It now feeds the descent/climb profile and the predictions. A constraint shown in magenta is one the FMGS predicts it will meet; an amber one would warn it expects to miss it — which you fix by managing the energy state (speed/speedbrake), not by retyping the altitude.

What to take away

  • Right-select a waypoint on F-PLN to open its vertical revision.
  • Altitude and speed constraints entered there reshape the computed descent path.
  • Managed descent flies constraints; it cannot fly the ones you never entered.
  • If the profile says unable, that is a call to ATC, not a number to overwrite.

The rest of Enroute Operations

Background reading

← Back to all scenarios