Reading the minima block on a satellite approach without picking the wrong line

Doigt suivant une ligne sur une carte d'approche, texte volontairement flou

On a satellite approach chart, four minima lines sometimes coexist in the same box, and the crew will only apply one. The choice is not a captain’s preference: it is imposed by the service level annunciated before the final approach fix, by the navigation database actually loaded, and by what the operator’s documentation authorizes that day. What remains is the mechanism behind each line, and the selection error that the table’s layout encourages.

Four lines, four contracts that are not interchangeable

Each minima line is a distinct contract. The block reads like a ladder: LPV at the top, LNAV/VNAV, sometimes LP, then LNAV, and often at the foot of the block the circling minima, which belong to a different exercise altogether. The vertical reading suggests a continuous gradation, from most favorable to most penalizing. That is true for altitudes, false for the nature of the operation.

Changing lines is not raising an altitude by a few dozen feet — it is changing contract, and often changing dimension. Performance-based navigation specifications separate two-dimensional operations, where the system delivers only lateral guidance and the crew manages a floor, from three-dimensional operations, where a vertical path belongs to the procedure design and the aircraft descends to a decision altitude.

LNAV and LP are two-dimensional; LNAV/VNAV and LPV are three-dimensional. This boundary runs horizontally across the block and is invisible: nothing in the chart’s typography signals that dropping one line can shift the approach from a decision-altitude regime to a floor regime.

What each line requires on board and what it provides in return
Line Dimension Lateral guidance Vertical, in the procedural sense Low reference Determining requirement
LNAV Two-dimensional Linear, constant width None Minimum descent altitude Approved receiver, database-derived procedure
LNAV/VNAV Three-dimensional Linear, constant width Barometric path, or provided by satellite augmentation Decision altitude Certified vertical function, temperature limits respected
LP Two-dimensional Angular, converging None Minimum descent altitude Satellite augmentation, intact final segment data block
LPV Three-dimensional Angular, converging Satellite geometric path Decision altitude Service available and level actually annunciated

Each line in the minima block represents a different type of approach with different rules. Some give you a floor (minimum descent altitude) where you must have visual references by that altitude, while others give you a decision altitude where the procedure is designed to reach that point safely even if you go around. Mixing them up can be dangerous.

On an Airbus A320 at Paris Charles de Gaulle (LFPG) runway 26L, the LPV minima might be 200 feet with 800 meters visibility, while the LNAV minima is 600 feet with 1,200 meters visibility. If the system downgrades from LPV to LNAV during the approach, the crew must immediately switch to the higher altitude and wider visibility requirements, or go around.

Linear or angular: geometry decides your scan

Lateral guidance behaves differently between line types. On an LNAV line, the final segment is protected by a lateral performance requirement expressed as a distance: full-scale deflection is usually on the order of three tenths of a nautical mile on either side of the axis, and this width remains constant down to the threshold. At two miles as at half a mile, the same displayed deviation represents the same lateral distance: the indicator does not tighten, and it says nothing more at the very moment alignment matters most. Fine tracking of the axis then falls back on the numeric deviation displayed in tenths of a mile and on heading discipline, since the deviation bar no longer says anything useful in the final mile.

Angular guidance works differently. On an LP or LPV line, lateral guidance is angular, referenced to a virtual point in the extension of the runway centerline. Its full-scale half-width at the threshold is typically on the order of a hundred meters, comparable to that of a localizer beam. Sensitivity therefore increases continuously, the same physical deviation producing a growing indication: the deviation bar becomes a precision instrument, and full-scale deflection near the minimum is grounds for a go-around.

Linear lateral protection versus angular lateral protection, plan viewPlan view of the final segment, final approach fix on the left, threshold on the right. The linear corridor, shown as a solid line, keeps the same half-width from the final fix all the way to the threshold. The angular corridor, shown as a dashed line, starts at the same width at the final fix, then converges steadily, so that its half-width at the threshold is only a small fraction of that of the linear corridor.linear: constant widthangular: convergingabout a hundred meters at the thresholdat the threshold: unchangedfinal fixdirection of flightthreshold
At the final fix the two protections are equal; at the threshold, one has narrowed and the other has not. The linear corridor keeps the same half-width from start to finish: the deviation bar gains no extra precision where alignment matters most. The angular corridor converges toward a point in the extension of the axis, which makes a late full-scale deflection far more significant.

This geometry is not computed by the avionics from the chart: it is described by a final segment data block, protected by a cyclic redundancy check and validated when the procedure is selected. Hence three hard consequences: an LP or LPV line is never built by hand, can no longer be modified once the final approach is sequenced, and disappears if the database is out of date. An expired database does not degrade the guidance — it removes the line. When the chart publishes the final approach path identifier, comparing it to the one the system displays is the only cross-check actually available to verify that the loaded block is indeed that of the briefed procedure, and not that of a like-named procedure serving another runway or issued from an earlier revision.

Floor or decision altitude: two distinct exercises

Two-dimensional lines publish a minimum descent altitude. It is a floor, not a decision point: obstacle clearance is only guaranteed provided it is not crossed without the required visual references. Three-dimensional lines publish a decision altitude, and the design already builds in the sink inherent to a go-around initiated at the minimum.

Continuous descent final approach has erased the difference in profile, not the difference in status. Flying a two-dimensional line in continuous descent requires converting the floor into a decision point through a documented addition: the value used is not the raw minimum descent altitude, but that altitude increased by an increment set by the operator.

  • Comparing raw figures is misleading: one line is used as printed, the other is not, and the useful gap often exceeds the printed gap.
  • Visibility requirements often decide whether the approach is worth attempting, not just the altitude.
Three possible low references on the same continuous descent profileSide view of the final segment. A continuous descent profile leaves the final approach fix and joins the threshold. It successively crosses three horizontal references: the increased floor, the highest and farthest from the threshold, then the published floor, then the decision altitude of a three-dimensional line, the lowest and closest to the threshold. Beyond the published floor, the profile is drawn dashed: the path remains displayed but no longer has procedural status.heightincreased floorpublished floordecision, three-dimensional lineadvisory pathfinal fixincreasedfloordecisionthreshold
On a two-dimensional line, the decision is made higher up and much farther from the threshold. The same continuous descent profile crosses three distinct references, and only the increased floor can be used as is. Beyond the published floor, the path remains displayed with no status: that is the dashed portion.

Two LPV lines also do not share the same decision height from one airfield to another, and the difference does not come from the avionics. The lowest, of the same order as those of a Category I precision approach, are published only where the obstacle environment, the approach lighting, and the runway infrastructure meet more demanding criteria. A high LPV does not therefore signal a degraded service but an airfield that does not permit better: hoping for a low minimum simply because the aircraft is LPV-capable is a preparation error, not a flying one.

The trap. An advisory vertical path displays exactly like a procedural path: same diamond, same deviation bar, same feeling of stability. Yet it is protected neither by the procedure design nor bound to stop at the minimum: it continues toward the threshold while the applicable line, for its part, is a floor. The classic chain of events: brief a three-dimensional line, suffer a silent degradation, keep vertical guidance that looks normal, descend below the floor without any alert triggering.

The annunciated level overrides the briefed line

Service levels are dynamic. The receiver does not merely compute a position: it continuously estimates a horizontal and vertical protection level and compares it against the alert limits of the targeted service level. If the estimated vertical protection exceeds the vertical alert limit, the vertical service is not offered, whatever the apparent quality of the position. Constellation geometry, ionospheric activity, and augmentation availability make this result vary from hour to hour at the same airfield.

A pilot points at a flight display showing a graph with LP, LNAV, and LNAV/VNAV approach lines.
Identify the correct minima block line to avoid approach errors.
Continuous comparison between estimated vertical protection and the alert limitA graph over time, with no values marked on the axes. A curve represents the vertical protection that the receiver continuously estimates; a horizontal line represents the vertical alert limit of the targeted service level. As long as the curve stays below the horizontal line, procedural vertical guidance is offered and the annunciation is nominal. In a highlighted central window, the curve crosses the horizontal line: the vertical is no longer offered and the annunciation degrades, then drops back below the limit and the service is restored.estimated vertical protectionvertical alert limitvertical not offerednominal annunciationdegraded annunciationrestored annunciationtime
The service level is not a characteristic of the aircraft: it is recalculated continuously. As long as the estimated vertical protection stays below the alert limit, procedural vertical guidance is offered. The crossing, caused by constellation geometry, ionospheric conditions, or augmentation coverage, removes the three-dimensional line without degrading the lateral guidance at all: the applicable line changes while the flying, for its part, shows nothing. The axes deliberately carry no values; only the crossing matters.

The level actually obtained is annunciated before the final approach fix. It is this annunciation, and nothing else, that designates the applicable line: not the filed flight plan, not the briefing, not the capability recorded in the aircraft flight manual.

Correspondence between the annunciated service level and the applicable line
Receiver annunciation Applicable line Vertical status Low reference What traps you
LNAV LNAV None Increased floor Floor treated as a decision altitude
LNAV with advisory suffix LNAV Advisory, outside the procedure Increased floor Normal-looking path
LNAV/VNAV LNAV/VNAV Procedural, temperature-sensitive if barometric Decision altitude Temperature to check beforehand
LP LP None, angular lateral Increased floor Quality lateral, no vertical
LP with advisory suffix LP Advisory, outside the procedure Increased floor Easily confused with LPV
LPV LPV Geometric, procedural Decision altitude In-flight degradation

The most frequent confusion is not between LNAV and LPV, which do not resemble each other in flying, but between LP and LPV: same angular lateral guidance, one letter apart, two neighboring lines. An LP line exists only if it provides a gain over LNAV, where the obstacle environment forbids a published vertical path but permits a narrowed lateral corridor. It is not a degraded LPV: it is an approach with no vertical guidance, with a floor.

The right reflex. Verbalize the annunciated level before sequencing the final approach fix, in this order: what the receiver displays, then the low reference retained and its value. The annunciation is the only piece of information in the loop that is current, since the briefing was done in cruise. Stating the annunciation rather than the hoped-for line makes the degradation detectable by design.

The hidden clauses: temperature, database, availability

Temperature matters for some approaches. An LNAV/VNAV line built on a barometric vertical path carries a temperature limitation published on the chart. The mechanism is that of any barometric altimetry: in cold air, the altimeter reads higher than true height, so following a path built on indicated altitudes places the aircraft below the nominal profile. Below the published minimum temperature, final segment obstacle clearance is no longer guaranteed. The upper limit, where it exists, relates to gradient rather than to clearance.

An LPV line escapes this mechanism on the path itself, which is geometric and indifferent to temperature, but not on the decision altitude, which is read on a barometric altimeter: the relationship between the path and the displayed altitude shifts with the temperature deviation. Cold-weather correction policy must therefore specify which altitudes are corrected on which line, since carrying a habit formed on a barometric path over to a satellite line is a documented source of error.

Equipment matters too. Satellite augmentation capability is recorded in the aircraft flight manual; a minimum equipment list deferral can remove it for the day and drop two lines from the block at once. Service availability, for its part, is checked before departure. Finally, the missed approach segment also relies on satellite navigation, with a wider performance requirement than that of the final segment: losing the augmentation that gave LPV does not compromise the go-around, losing the satellite position does.

The second trap. A degradation occurring after the final approach fix has been sequenced cannot be recovered by a mental change of line. Switching from a decision altitude to an increased floor in the middle of the final descent requires recomputing a low reference, rebriefing it, and changing the descent-arrest technique, at the exact moment the workload forbids it. The question is therefore not “which line to apply,” but “up to what point in the profile a change of line remains acceptable.”

Briefing two lines and one trigger

Briefing must be robust. A briefing that annunciates only one line is incomplete: it assumes as solved something that will only be resolved on final. The robust form has three elements: the expected line and its low reference, the fallback line and its low reference, and the trigger that moves from one to the other. The third element is almost always missing. It is not an intuition, but a point in the profile tied to an observation: read the annunciated level before the final approach fix, then state the consequence — expected line, fallback line, or go-around. The matrix below prescribes nothing: it lists what the documentation must have settled in advance.

What the documentation must have settled, depending on when the degradation occurs
When the degradation occurs What concretely changes Question resolved on the ground
Before the final approach fix The low reference and the descent-arrest technique At what point in the profile the annunciated level must be checked
After the final approach fix is sequenced The nature of the operation, in the middle of the final descent Whether a change of line is permitted, or a go-around is required
Loss of vertical guidance alone The displayed path may persist without procedural status How to tell a procedural path from an advisory path
Loss of satellite position The final segment and the missed approach are both affected Which go-around, which backup means of navigation

The complementary reflex. Write both low references on the briefing aid, one below the other, with their nature made explicit: decision altitude for one, increased floor for the other. Two figures side by side remove the mental arithmetic at the worst possible moment and make the gap between the hoped-for line and the line actually obtained visible at a glance.

What your documentation still needs to settle

Three gray areas remain, which no article can close. First, the increment applied to the floor in continuous descent: its value varies from one operations manual to another, and it is that figure, not the one on the chart, that the crew uses. Then the cold-weather correction policy, line by line, where the path and the decision altitude do not obey the same mechanism. Finally, the conduct required in the event of a late degradation, the one point where improvisation is costly.

A documentary variable adds to this: the block’s presentation depends on the chart provider. The order of the lines, the presence of an LP line, the way the temperature limitation is flagged are not standardized everywhere, and switching between two sets of charts justifies rereading the legend as a new instruction. For anyone preparing a type rating, the most worthwhile exercise is to take three charts with different blocks and to state, for each, the expected line, the fallback line, the two low references, and the trigger. Concrete cases are discussed on the FL330 forums, and performance-based navigation preparation modules are on the training side.

This article sets out design and reading mechanisms; it replaces no regulatory source. The applicable text, the operator’s approved documentation, the aircraft flight manual, and the charts in effect prevail at all times over what is written here.

Questions fréquentes

Can LPV minima be applied if the avionics only annunciate LNAV before the final?

No. The service level actually annunciated designates the applicable line, and an LNAV annunciation refers to the increased LNAV floor per the operator’s policy. The capability recorded in the aircraft flight manual authorizes the line; it does not guarantee it. A degraded annunciation before the final approach fix therefore requires rebriefing the low reference, or abandoning the approach.

What is the practical difference between LP and LPV?

Both provide angular lateral guidance converging toward the threshold, comparable to a localizer. LPV adds a geometric vertical path that belongs to the procedure, hence a decision altitude; LP has no procedural vertical guidance and ends at a floor. An LP line is published only where the obstacle environment forbids a vertical path but permits a narrowed lateral corridor.

Does an advisory vertical path authorize descending to the decision altitude of the line above?

No, under no circumstances. An advisory path is computed by the receiver to help with stabilization, without being protected by the procedure design or required to stop at the minimum. The applicable line remains that of the annunciated level, with its floor and the increment set by the operator. It is precisely because the display is identical to that of a procedural path that this trap works so well.

Why does a temperature limitation appear on the LNAV/VNAV line and not on LPV?

Because the vertical path of an LNAV/VNAV is most often built on barometric altitudes. In cold air, the altimeter reads higher than true height, so following this path places the aircraft below the nominal profile and eats into the obstacle clearance margin. The path of an LPV is geometric, and therefore insensitive to temperature; its decision altitude, however, remains barometric, which falls under the operator’s correction policy.

What does an outdated navigation database change on these minima lines?

LP and LPV procedures rely on a final segment data block protected by an integrity check and loaded from the database. If it is out of date, or if the check fails, the procedure is no longer selectable at the expected level: the line disappears instead of degrading progressively. The operational consequence is a fallback to a lower line, or even the impossibility of flying the satellite approach.

Should the approach be discontinued if the service level degrades after the final approach fix?

The answer belongs to the operations manual, which must have settled this case in advance. The mechanism to know is that a change of line during the final descent requires recomputing a low reference, rebriefing it, and changing the descent-arrest technique, at the exact moment the workload forbids it. In the absence of an explicit rule, a go-around remains the only course of action that requires no calculation.

Commentaires

Leave a Reply

Découvrez l’écosystème FL330

FL330, c’est toute l’aviation professionnelle — explorez nos autres espaces.