On the same RNP approach chart, the LPV line and the LNAV/VNAV line do not announce two different heights by chance: they rest on two different ways of building a vertical path, guaranteed by two distinct systems that fail for unrelated reasons. Choosing one or the other engages the onboard database, the installation’s approval, the day’s temperature, and the altimeter setting available on arrival.
Two lines on the same chart, two physics of the vertical path
The lateral track is shared, and that is what misleads: same constellation, same waypoints, same runway. The divergence begins at the final segment.
On the LNAV/VNAV line, the vertical path is computed by the flight management system, which continuously compares the current barometric altitude to the one the path requires at the remaining distance. The path is therefore a locus of pressure altitudes: it coincides with the published angle only in standard atmosphere.
On the LPV line, the final segment is not reconstructed from waypoints: it comes from a data block sealed by a cyclic redundancy check — threshold point, course, path angle, crossing height, alert limits. The receiver verifies this seal, reconstructs the path, then compares it to its geometric height corrected by satellite-based augmentation. No pressure enters this comparison.
The failure modes are therefore separate, and treating the two lines as two tiers of a single function is a fundamental error. The barometric path degrades through altimetry: an incorrect setting, a remote source, out-of-range temperature, a faulty static port. The geometric path degrades through the signal: satellite geometry, the ionosphere, masking, jamming, insufficient integrity. Losing one does not make the other available.
The LPV and LNAV/VNAV lines use different systems to guide the plane vertically. One relies on air pressure, the other on satellites. If one fails, the other won’t take over.
On a Boeing 737 flying an LPV approach to a 200-foot decision height, the plane uses satellite corrections to stay on the right path. If the satellite signal is lost, the plane can’t automatically switch to the LNAV/VNAV path, which uses barometric data. The pilot must then decide whether to continue or go around.
What satellite-based augmentation actually adds to the signal
Augmentation is often summarized as a more precise position. That is true, and secondary. The service broadcasts two products of a different nature: corrections — an ionospheric model on a grid, clock and orbit corrections satellite by satellite — and integrity information, that is, bounds on the error remaining after correction.
It is this second product that opens the door to a vertical minimum: it allows the receiver to compute in flight an upper bound on its own position error, the horizontal and vertical protection levels. Not precision estimates, but bounds with a demonstrated probability of exceedance.
The procedure carries alert limits: the value beyond which a position error is no longer tolerable for the intended operation. They amount to tens of meters for LPV minima, with the vertical limit in practice being the one that governs availability. Availability rests entirely on a continuous comparison: protection below the alert, the function is present; above it, it disappears, and the receiver must announce this within seconds.
That is exactly what an LNAV line lacks. The receiver’s autonomous integrity monitoring, without augmentation, bounds the horizontal error through measurement redundancy but does not bound the vertical error to the required level. The absence of a vertical minimum is therefore not editorial caution: it reflects what the electronics can actually guarantee. Augmentation also changes the scale of the displayed lateral deviation, linear on the LNAV line and converging angular on the LPV line: the same displayed deviation therefore does not represent the same distance from the target depending on the line flown, and it tightens as the threshold is approached. Hence two piloting consequences: stabilization criteria are read in displayed deviation and never in distance, and a correction that was adequate at the start of the segment becomes late by the end.
The barometric path and its dependence on the day’s atmosphere
The mechanism is well known; its effect on a continuous path less so. Below standard atmosphere temperature, isobaric surfaces move closer to the ground: an indicated altitude corresponds to a lower true altitude, and the gap widens with height above the altimeter setting source. A path defined as a sequence of pressure altitudes therefore becomes, in severe cold, shallower than the published angle: the aircraft faithfully follows its indicated path and passes lower than intended over obstacles. In great heat, it steepens instead.
Hence two constraints printed on the chart, to be read as design elements. The temperature range within which the LNAV/VNAV line is usable protects the final segment’s obstacle clearance margin: it is not negotiable on the pretext that the path is being flown cleanly. Next comes the requirement for a local altimeter setting: a distant pressure source shifts the entire pressure-altitude locus that serves as the path, and many procedures for this reason prohibit the barometric decision height when only a remote setting is available — in which case only the LNAV line remains, or the LPV line if the aircraft serves it.
Some installations compensate for outside air temperature in the computed path. The function exists only if it is approved, and its use is only assured if the operator’s documentation authorizes it: two aircraft from the same fleet can differ without the chart saying so.
The right reflex. Before deciding whether the temperature limit concerns you, name the source of the vertical path your installation will use for the line in question. Geometric guidance approved to serve the LNAV/VNAV line does not describe the same path as a barometric computation: the restriction published for the latter does not apply to the former. The question is not which line, but which source.
What each line requires of the aircraft and the database
Three conditions must be met simultaneously: equipment of the appropriate class, an installation approved for the operation, and a database carrying the necessary coding. The third is the one most often forgotten because it is invisible from the flight deck: the LPV line exists for the receiver only if the final segment data block is present in the loaded cycle, with a valid seal. A chart publishing LPV minima proves nothing about the onboard database.
| Element | LNAV | LNAV/VNAV, barometric path | LPV |
|---|---|---|---|
| Origin of the vertical path | None: two-dimensional operation | Barometric altitude computed by the flight management system | Geometric height corrected by satellite-based augmentation |
| Integrity ensured by | Receiver autonomous integrity monitoring, horizontal only | Lateral as with LNAV, vertical via certified altimetry | Protection levels compared to alert limits, lateral and vertical |
| Temperature sensitivity | Indirect but general: step-down and minimum altitudes are pressure altitudes, and therefore subject to a low-temperature correction | Direct on the path, hence a published range | None on the path; the decision remains barometric |
| Nature of the minimum | Minimum descent altitude | Decision height | Decision height |
| Minimum floor | On the order of 250 ft height, published values often being higher depending on the obstacle clearance altitude | Same order of magnitude, with a decision height instead of a minimum descent altitude | Goes down to 200 ft decision height where procedure design and the environment allow |
| Database | Final segment points | Final segment points and vertical coding | Sealed final segment data block, essential |
| Approval | Receiver approved for the approach | Approved receiver and barometric vertical function | Augmented receiver of the required class, approved installation |
| Loss during the approach | Loss of lateral guidance: go-around | Loss of the vertical function: continuation toward the LNAV minimum descent altitude only if its value and its missed approach point have been briefed and not yet passed | Downgrade or locked alert depending on the installation |
This table can also be read the other way around: when a pillar is missing, the question is not by how much the minimum is raised, but whether a usable line remains.
When the function is lost during the approach
The approach mode activates at a defined distance before the final approach fix, provided the protection levels are then below the alert limits. Degradation occurring before this gate is almost comfortable: the mode does not engage, and the announcement comes early. The difficult case arises afterward.

Behavior then depends on the installation, which must be known by heart for one’s own aircraft: some downgrade the function with an announcement and let the vertical bar disappear, others lock the mode and alert, forcing a go-around. In both cases, the pilot flying loses a path being followed at the moment their workload is highest.
Continuing on the LNAV line is not automatic: its minimum is higher, its missed approach point is elsewhere, and depending on the moment of the loss, the aircraft may already be below that minimum or past that point. Hence the value of briefing both lines with their own values: a fallback is only useful if its numbers are in mind when it becomes necessary.
The trap. The advisory vertical path shown by many installations on a procedure publishing only LNAV minima is not vertical guidance in the sense of minima. It is built between the final approach fix and a threshold crossing height, ignoring the minimum altitudes of intermediate step-downs: following it without monitoring them can put the aircraft below a step-down altitude. And it does not turn a minimum descent altitude into a decision height: descending below that minimum because a bar is displayed confuses a piloting aid with an approved operation.
The right reflex. At the briefing, state the fallback before the lowest minimum: which line, which value, which missed approach point, under what condition continuing remains possible. Not « we have LPV », but « if vertical guidance is lost, we continue to such a value down to such a point, otherwise go-around ».
The briefing matrix: the conditions that make a line available
The availability of an LPV line is prepared on the ground and cannot be deduced from the state of the constellation. Augmentation is a service: it is the subject of notices to navigators, it has prediction tools by aerodrome and time slot, and its margin narrows at the edges of the service area as well as during periods of ionospheric activity. Its message also arrives from geostationary satellites seen at low elevation at high latitudes: terrain, a nearby obstacle, or a prolonged pitch attitude can mask it even while the navigation satellites are healthy.
| Condition to check | When it holds | When it does not hold |
|---|---|---|
| Final segment data block present in the loaded cycle, and installation approved for this line | LPV line achievable | LPV unavailable, regardless of everything else |
| Augmentation availability forecast for the aerodrome and the time slot | LPV line achievable | Prepare the barometric line or a conventional aid |
| Barometric vertical function approved on board | Decision height for the LNAV/VNAV line | LNAV alone, with its minimum descent altitude |
| Forecast temperature within the published range, or approved and authorized compensation | Decision height for the LNAV/VNAV line | LNAV alone |
| No satellite interference reported over the area | All three lines remain on the table | No line on the chart: conventional aid, another aerodrome, fuel planned accordingly |
The first two conditions are checked once per fleet and per database cycle, the following ones for the day’s flight. The last one cannot be recovered by switching lines.
The trap. The three lines on the same chart share an antenna and a constellation. Jamming does not degrade LPV to LNAV: it removes the entire procedure, lateral line included. Planning an LNAV fallback in the face of a notice signaling satellite interference is planning a fallback that does not exist. The alternative is a conventional aid, another airfield, and the fuel to get there.
What remains to be checked in one’s own documentation
Three points deserve to be found in black and white, because they vary from one operator and one aircraft to another.
- The minima lines for which the installation is approved, and — a separate question — the source of vertical guidance it offers for the LNAV/VNAV line. The answer governs the applicability of the published temperature range.
- The operator’s policy on low-temperature correction of the minimum when the path being flown is geometric: the path does not need correcting, but the published value is still read on the barometric altimeter, and this asymmetry is not handled the same way everywhere.
- The installation’s behavior on loss of the vertical function, described in plain terms, and what the procedure then requires.
For anyone preparing a qualification, the shift is clear: the expectation is no longer to know how to fly an approach without vertical guidance in a continuous descent, but to know how to state what guidance is being used, why, and what to do when it is lost. The distinction between a two-dimensional and a three-dimensional approach operation is not mere vocabulary: it determines the decision technique, the stabilization criteria, and the go-around. This is exactly what an examiner targets by failing the augmentation mid-way through the final segment, and what FL330 training courses dedicated to performance-based navigation.
A gray area remains, better named than suffered. Many charts publish several lines without stating which vertical source serves which. Coverage of final segment data blocks varies by provider and cycle, with no warning beyond the line simply not appearing on selection. And low-temperature correction of the minimum on a geometric path is decided at the State and operator level, not the chart’s. These three points are settled in onboard documentation; comparing them across fleets is what exchanges between professionals.
This article describes mechanisms; it sets no minima. In case of discrepancy, the applicable regulations, the charts and notices in force, and the operator’s approved documentation take precedence over what is written here.
Questions fréquentes
Is an approach with LPV minima a precision approach?
No: it is classified as an approach with vertical guidance, in other words a three-dimensional approach operation, not as a precision approach. The resemblance to a localizer alignment comes from the angular scale of the lateral deviation, not from an equivalent regulatory status. A concrete consequence: there is no protected critical area on the ground, and the operational credit is exactly what the chart publishes, not that of an ILS.
Why does the chart carry a temperature range on the LNAV/VNAV line but not on the LPV line?
Because the barometric path is a locus of pressure altitudes: it only retains the published angle in standard atmosphere. In severe cold it becomes geometrically shallower, which erodes the final segment’s obstacle clearance margin, hence a temperature range that is part of the procedure’s design. The path serving the LPV minima is geometric and does not depend on pressure: this limitation does not concern it.
Can the LNAV/VNAV line be served with vertical guidance derived from satellite-based augmentation?
Yes, when the equipment and installation are approved for it. The path flown is then geometric, and the temperature range published for barometric vertical guidance does not describe this path. It is still necessary to know with certainty which source the installation uses and to have operator documentation stating it: this is a matter of approval, not of settings.
What to do if LPV guidance is lost after the final approach fix?
Behavior depends on the installation: an announced downgrade with a return to a linear scale, or a locked alert forcing a go-around. Continuing on the LNAV line is only possible if its minimum descent altitude and missed approach point have been briefed, and the aircraft is neither below that minimum nor past that point. In doubt, the go-around is the only defensible option.
Does the advisory vertical path displayed on an LNAV procedure allow descent to a decision height?
No, it does not change the nature of the minimum: a minimum descent altitude remains a minimum descent altitude, below which one does not descend without the required visual references and without being in a position to land. This path is moreover built between the final approach fix and a threshold crossing height, without taking into account the minimum altitudes of intermediate step-downs, which remain the crew’s responsibility to monitor.
What should be checked in flight preparation before relying on the LPV line?
Four things: that the final segment data block is present in the loaded database cycle, that the installation is approved in writing for this line, that augmentation availability is forecast for the intended aerodrome and time slot, and that no satellite interference is reported over the area. A fallback solution that does not depend on the same signal is also needed, since jamming removes every line on the chart, not just the lowest one.

Leave a Reply
You must be logged in to post a comment.