Vertical Navigation (VNAV) Path Computation and Descent Planning

Vertical Navigation, universally abbreviated VNAV, is the flight management system (FMS) capability that constructs and monitors a continuous vertical flight path from cruise altitude down to a runway threshold or missed approach point. While lateral navigation (LNAV) keeps the aircraft on the correct track, VNAV answers the equally critical question: how fast should we descend, and when should we start? For Airline Transport Pilot (ATP) candidates, a deep understanding of VNAV is not merely an exam requirement — it is a professional necessity. Modern transport-category crews rely on VNAV every day, and misunderstanding how the system computes its path is a well-documented factor in controlled-flight-into-terrain (CFIT) and unstabilized approach incidents.

This article builds the concept from first principles: how the FMS constructs the vertical path, the difference between path types, how constraints are honored, and the practical discipline required when automation diverges from expectation.

How VNAV Path Computation Works

The FMS constructs a vertical profile by working backward from a fixed reference point — typically the runway threshold crossing height or, on a procedure with a published vertical angle, the final approach fix (FAF) crossing altitude. Starting from that anchor, the FMS traces the required path back toward the aircraft's current position using a computed flight-path angle (FPA), which for most airline approaches is 3.00° (matching the ILS glideslope) unless the procedure specifies otherwise. Steeper angles such as 3.5° or even higher are used at airports with terrain or obstacle constraints (e.g., London City or Kathmandu), and the FMS uses the charted angle when it is loaded from the navigation database.

Along the arrival route, the navigation database contains altitude constraints at each waypoint. These constraints are coded as:

AT constraints — the aircraft must cross exactly at the specified altitude (e.g., "cross FLUKY at 10,000 ft").
AT or ABOVE constraints — the aircraft must be at or above the altitude (common on departure and in mountainous terrain segments).
AT or BELOW constraints — the aircraft must be at or below the altitude (common at speed/noise abatement fixes).
WINDOW (BETWEEN) constraints — the aircraft must cross within a defined altitude band (e.g., "between 8,000 and 10,000 ft").

The FMS evaluates every constraint along the arrival and approach path and selects the most restrictive combination that allows a smooth, continuous path. Where a single straight-line descent angle cannot satisfy all constraints simultaneously, the system inserts level segments between steeper legs, creating a stepped profile. This is why the FMS vertical profile on the navigation display sometimes shows a staircase shape rather than a single straight line from top of descent (TOD) to touchdown.

Top of Descent Calculation

The Top of Descent (TOD) is the waypoint — or point in space — where the computed descent must begin in order to arrive at the first downstream altitude constraint on path. The FMS calculates TOD based on:

Current cruise altitude and the first target altitude constraint
The computed or selected descent flight-path angle (often 3° in the terminal area, but the FMS typically uses a shallower angle — around 2.5° to 3° — in the en-route and STAR phases, translating to a rule-of-thumb descent rate of roughly 3 times groundspeed in hundreds of feet per minute at typical airspeeds)
Wind forecast data entered or uplinked (tailwinds flatten the path and push TOD closer; headwinds steepen it and pull TOD farther out)
Aircraft performance data (deceleration segments required for speed constraints, step-downs for terrain)

A commonly tested rule of thumb: multiply the altitude to lose (in thousands of feet) by 3 to get the approximate distance in nautical miles needed to descend at a 3° angle. For example, descending from FL350 to sea level requires roughly 35 × 3 = 105 NM. This mental math lets crews cross-check whether the FMS TOD is reasonable or whether a programming error may have shifted it incorrectly.

VNAV Path Types: PTH, SPD, and ALT

Most Boeing and Airbus FMS designs display the current VNAV sub-mode, and these modes are central to the ATP exam:

VNAV PTH (Path) — The FMS is actively tracking the computed geometric descent path. The autopilot adjusts pitch to maintain the path, and thrust is managed to control speed within limits. This is the normal, expected mode during a STAR or approach. If the aircraft gets above the path (common with an early clearance to a lower altitude), the FMS may command an increased descent rate to recapture.
VNAV SPD (Speed) — The FMS has transitioned from path-following to speed control, typically because the computed path is too steep or too shallow to follow while staying within structural or buffet limits, or because the aircraft is above idle thrust and cannot descend steeply enough without accelerating. VNAV SPD commonly occurs when ATC vectors the aircraft well above the computed path: the system essentially says "I cannot follow a path this steep, so I will target descent speed instead." Pilots must recognize VNAV SPD as a signal that the aircraft is not on the computed path and intervention may be required.
VNAV ALT (Altitude) — The FMS is holding a constraint altitude. This can be expected behavior (honoring an AT constraint) or an unintended capture of a lower altitude if the crew selected an incorrect MCP altitude. Understanding why the aircraft levels off is critical; an unexpected VNAV ALT annunciation demands immediate crew verification of the MCP altitude setting versus the clearance.

Energy Management and Deceleration Planning

A transport-category aircraft carries enormous kinetic and potential energy. VNAV must account for the fact that slowing down and descending happen simultaneously and neither can be instantaneous. The FMS inserts computed deceleration points into the vertical profile. At these points, the thrust levers may advance slightly to maintain the flight-path angle while the aircraft slows, or the path may include a brief shallowing to allow deceleration. Crews must monitor these segments carefully — a common error is accepting a high-energy state at the deceleration point without action, then arriving at the FAF fast, high, or both.

When ATC issues a "direct to" shortcut that eliminates miles along the STAR, the FMS must recompute the vertical profile over fewer miles. This often results in an impossible path — the aircraft cannot lose the required altitude in the remaining distance at any acceptable flight-path angle. The FMS will either display an error message, revert to VNAV SPD, or show the path broken. Crews should immediately request a lower altitude, plan for a visual approach, or request vectors that restore adequate descent distance.

Why VNAV Discipline Matters for Safety

CFIT accidents and unstabilized approaches have repeatedly been traced to crew over-reliance on VNAV without monitoring its outputs. Key discipline points include:

The FMS is only as good as its inputs. An incorrectly entered runway, wrong transition, or missed constraint entry will corrupt the entire vertical profile silently. Crews must verify the VNAV path against published procedure altitudes at each waypoint.
ATC clearances must be entered promptly and correctly. Accepting an oral clearance without updating the FMS means the automation is flying a different profile than ATC expects.
"Dive and drive" versus VNAV approach. On LNAV/VNAV approaches, the aircraft follows a computed geometric path similar to an ILS. On LNAV-only (step-down) approaches, there is no geometric path — the crew must manually descend to each step-down altitude. Confusing these two approach types has led to controlled flight below minimum descent altitudes.

Key Numbers and Rules

3° flight-path angle — standard precision and RNAV/RNP approach angle; FMS default for terminal geometry
3 × altitude (thousands) = distance (NM) — rule of thumb for TOD planning at 3° descent
~300 ft/NM — the altitude loss per nautical mile at a 3° FPA (useful for quick mental math)
Stabilized approach gate — 1,000 ft AGL in IMC, 500 ft AGL in VMC; if not configured and on profile by these gates, a go-around is required per most airline SOPs and FAA guidance
VNAV SPD annunciation — aircraft is NOT on the computed geometric path; pilot action or awareness required
Required Navigation Performance (RNP) — VNAV used with RNP AR approaches can achieve curved paths to tight tolerances (e.g., 0.1 NM); requires specific aircraft and crew authorization

Common Test Traps

Assuming VNAV SPD means the aircraft is on the vertical path — it does not. VNAV SPD means the FMS has abandoned path-following in favor of speed management; the aircraft is almost certainly above the desired path.
Confusing LNAV/VNAV with ILS precision — LNAV/VNAV minima are higher than ILS Cat I minima because the geometric path relies on barometric altimetry (baro-VNAV), which is temperature-compensated but not as precise as a glide signal. At cold temperatures, baro-VNAV paths become increasingly unreliable and temperature corrections may be required per the approach plate notes.
Ignoring the TOD marker — passing the TOD in level flight without a descent clearance is common; if cruise altitude is not abandoned at TOD, the aircraft will arrive at constraints high and potentially in an unrecoverable energy state.
Overlooking "AT or ABOVE" constraints on the STAR — the FMS will not descend below a coded AT-or-ABOVE altitude even if ATC has verbally cleared a lower altitude that hasn't been entered into the system.
Temperature effect on baro-VNAV — in temperatures significantly below ISA, the aircraft will fly below the indicated (barometric) altitude. LNAV/VNAV approaches at cold airports require temperature compensation, and some approaches are not authorized below a published minimum temperature. Failure to apply corrections has resulted in CFIT events.

VNAV is a powerful tool that, when understood deeply and monitored diligently, reduces workload and dramatically improves profile precision. The ATP-level pilot treats it as a sophisticated flight-planning assistant — verifying its outputs, cross-checking every constraint altitude against the published procedure, and always knowing what mode the automation is in and why. Automation that is trusted without understanding is arguably more dangerous than no automation at all.