Glide Slope Intercept Altitude: Why This Number Is on the Chart

A pilot in a cockpit at dusk, monitoring the ILS display as the aircraft descends along a 3.0° glidepath toward a runway.

Every ILS profile publishes an altitude at which the glidepath must be intercepted, and it is rarely explained where this number comes from. It is not a number of convenience: it is where obstacle protection, guaranteed signal volume, and aircraft energy still align. Here’s how it is constructed and what no longer applies above and below it.

A line in space and the level segment that finds it

An ILS glidepath is not information provided by the chart. It is a physical thing radiated from a mast beside the runway. Its straight section passes through the ILS reference point, a point above the threshold at a nominal height of 15 m (50 ft), and rises from there at the published angle – 3.0° by standard design, steeper only where the site requires it, and above a certain angle only under a certain operating authorization. This line exists regardless of whether anyone flies it or not, and no chart change moves it.

The published intercept altitude is the altitude of a level segment that meets this path. In terms of PANS-OPS, the intercept point is the Final Approach Point, the FAP, and on most charts, it coincides with the point used as the Final Approach Fix for the localizer-only approach. Upstream of it is the intermediate segment; downstream is the final segment with a completely different set of protected surfaces.

Since the path is straight, altitude and distance are linked by fixed arithmetic. At 3.0°, one mile of distance is approximately 318 ft – the familiar 300 ft per mile, plus the six percent that explains why the rule of thumb leaves you slightly low.

Glidepath geometry at 3.0° – altitude above the reference point, distance from the threshold, required descent rate
Altitude above the reference point Distance from the threshold Descent rate at 130 kt ground speed Descent rate at 160 kt ground speed
1,500 ft 4.7 NM 690 ft/min 850 ft/min
2,000 ft 6.3 NM 690 ft/min 850 ft/min
2,500 ft 7.9 NM 690 ft/min 850 ft/min
3,000 ft 9.4 NM 690 ft/min 850 ft/min
4,000 ft 12.6 NM – beyond range 690 ft/min 850 ft/min

The descent rate on the path depends only on ground speed, not on where it was joined. And an intercept altitude significantly higher than about 3,000 ft above the threshold shifts the FAP beyond the range over which glidepath coverage is guaranteed. A particular installation may be flight-checked further out, but the designer cannot rely on it – hence a high and comfortable level segment cannot simply be published.

The intercept altitude is the point where the aircraft must meet the glidepath to ensure safety and proper signal reception. Flying too high or too low changes the approach geometry and risks.

On a 3.0° glidepath, an Airbus A320 intercepting at 3,000 ft above the threshold is at 9.4 NM from the runway. If it intercepts at 4,000 ft, it’s at 12.6 NM, beyond the 10 NM guaranteed glide slope coverage, risking false path capture.

Where the number actually comes from

The published number is the result of a short chain. It starts with the obstacle survey. The intermediate segment has its own minimum obstacle clearance – in PANS-OPS terminology, significantly less than the initial segment, in the order of 150 m (492 ft) over the primary area, reducing in the secondary areas. The designer takes the lowest altitude that preserves this clearance above the controlling obstacle. This floor has nothing to do with the ILS.

An airplane on a runway at dusk with light trails and a tall light pole near water.
Landing height is critical for safe runway approach.

Then comes the requirement that the segment be flown level and long enough. Criteria demand a minimum level distance before the FAP – in the order of one and a half miles per PANS-OPS, expressed differently in other design criteria – so that the aircraft is level, on the localizer, slowed, and configured before the path arrives.

The intersection of this level altitude with the nominal path fixes the FAP. The altitude is rounded, and it is rounded up. This is more important than it seems: rounding up keeps the aircraft on or slightly above the published altitude, not below it, so the path is intercepted from above and capture occurs from below.

Finally, the airspace has its say. Sequencing, vectoring altitudes, noise abatement, or flows from a neighboring airport can significantly increase the number beyond what obstacle geometry alone requires. An intercept altitude that appears generous over flat terrain usually has one of these factors behind it.

What the published intercept altitude sets and how each input influences it
Design input Impact on the published altitude Consequence if the crew ignores it
Controlling obstacle plus clearance height Sets a hard lower limit Descending below it before the FAP consumes the buffer
Minimum level distance before the FAP Shifts the point outward, increases the altitude Late configuration; the gate arrives before the aircraft is ready
Guaranteed coverage volume Limits how high and how far the FAP can be Arming beyond coverage; a centered needle that means nothing
Rounding rule (up) Adds a few dozen feet None if respected; it is what enables capture from below
Airspace, sequencing, vectoring altitude, noise Can increase it significantly above the geometric minimum Expecting a lower join than the chart supports

Why capture must occur from below

A ground-based glidepath antenna works with the terrain in front of it: the usable signal is formed by the interference of a direct wave and a ground-reflected wave. This creates not a beam, but a pattern, and above the nominal path, there are other angles at which the 90 Hz and 150 Hz modulation depths are equal again, and the deviation indicator is centered again. The structure depends on the antenna type – zero reference, sideband reference, M-array, capture effect – and the terrain in front of it, so the angles in the table below only indicate where false paths are reported, not certified values. The principle applies regardless: more than one place sets the needle in the middle, and the receiver cannot tell you which.

True path and false paths above – indicative angles for a 3.0° site and the descent rate each requires at 140 kt
Path Approximate angle Direction of deviation Required descent rate What the flight mode indicator shows
True glidepath 3.0° Normal approximately 740 ft/min Glidepath capture
First false path approximately twice the nominal angle Reversed – commands fly up when high approximately 1,500 ft/min Glidepath capture, identical
Second false path approximately three times the nominal angle Normal approximately 2,250 ft/min Glidepath capture, identical

There is a second, less discussed boundary. The signal is only guaranteed within a defined volume: generally a sector of about eight degrees on either side of the path, from approximately 0.45 to 1.75 times the nominal angle, up to about ten miles. Beyond that, nothing is guaranteed – not that the needle is off-scale, not that it is visibly wrong. A centered glidepath needle at fourteen miles is proof of nothing.

The trap. The terrain awareness and warning system cannot be relied upon to detect a false lobe capture. The below-glideslope alert mode looks at deviation below the beam; an aircraft descending at 1,500 ft/min on a false path at twice the nominal angle is above the true path, so this mode remains silent. The first automatic warning is likely an excessive descent rate or excessive terrain closure rate – by then you are low, fast, and short of the runway.

Arriving above the published altitude

High arrivals result from a descent clearance that never came, or an approach flown too fast to lose the altitude. Above the intercept altitude at the FAP, the aircraft is above the path, and the flight management system captures the first thing that centers – the true path if it reaches it, a false lobe if the aircraft is high and close enough that one crosses it. The display is identical in both cases, and so is the reading of a centered needle.

Even without a false path getting in the way, capture from above is not the maneuver for which the aircraft is certified. Many operating manuals restrict or prohibit it: the mode is not designed for a chase, and configuration must be completed within a shrinking distance. Recovery is not arm and wait, but flying a defined vertical speed to return to the path, with a running height-versus-distance check.

Arriving below the published altitude

The mirror error is quieter and more frequent. Level below the published altitude, the aircraft does not miss the intercept – it intercepts later and closer, consuming the intermediate segment’s obstacle clearance to get there.

That is the real consequence. The published altitude is the number against which the controlling obstacle was evaluated. Below it, the survey does not say the aircraft is unsafe; it says nothing at all – which is far less reassuring. The final approach protection is built around the nominal path and begins at the FAP; before this point, the aircraft is still in the intermediate segment, where the published altitude is the only one evaluated.

The operational consequence is this: intercepting the path one or two miles closer eliminates the level distance the criteria placed there. The configuration, deceleration, and checklist must adapt to what remains, and the gate does not move.

Three ways to reach the Final Approach Point and the defense that works
Arrival state What is lost Display that won’t save you The check that will
Above The capture geometry for which the flight management system is certified; immunity to false lobes; deceleration distance A centered needle and a capture indication Altitude versus distance at the point; descent rate versus ground speed
Below, leveled Nothing — The same cross-check, as a trap for a gross altimeter setting error
Below Intermediate segment clearance; level distance before the point A normal-looking capture, later and closer Intermediate segment minima flown as minima, not targets

Intercepting the localizer is not intercepting the glidepath

The two events are habitually mentioned as one – « established » – but the localizer is guaranteed much further out: in the order of twenty-five miles within about ten degrees of the course, less in the wider sectors, versus about ten for the glidepath. Therefore, an aircraft can be laterally well established, on a valid and stable localizer, long before vertical guidance means anything. Arming the glidepath there is not an error; reading a centered vertical needle as information is.

The altitudes can also differ: where the procedure includes a stepdown between the two, the localizer intercept altitude or the published level segment is above the glidepath intercept altitude – although on many charts, the two are the same number. The correct picture is a staircase – intercept the localizer at the assigned altitude, descend to the published segment altitudes when the procedure and clearance allow, level off at the intercept altitude, let the path arrive. The mode annunciations are the crew’s proof that it happens in the right order.

The reflex that works. In the briefing, state the intercept altitude and the point crossing altitude as two separate numbers and call out the second aloud upon passing the point. If it does not match the chart within a few hundred feet, the aircraft is not on the path described in the chart – regardless of what the needle says. Disconnect, reset, or go around.

« Cleared for the approach » – what it clears and does not clear

Here, the intercept altitude shifts from a design number to a clearance issue. An approach clearance authorizes the aircraft to fly the published procedure. Under radar vectors, it does not by itself clear the aircraft to leave the last assigned altitude before it is established on a published segment – and this altitude comes from a minimum vectoring altitude not printed on the approach chart.

The phraseology helps less than it should because it varies: some states expect an explicit altitude with every approach clearance, some rely on « report established, » some issue the localizer descent separately. This variation is found in the states’ AIPs and cannot be resolved from memory at 210 knots. The ambiguity is a persistent thread in professional discussion, including in the FL330 operating forum, and the outcome never changes: no altitude, not established – ask.

The trap. « Cleared for the approach » is not a clearance to descend to profile altitudes under vectors. Until the aircraft is established on a published segment, the last assigned altitude remains in effect. Early descent to the intercept altitude is an altitude deviation that, from the cockpit, looks exactly like flying the chart.

Temperature and pressure: the beam does not move, the altimeter does

The glidepath is a physical angle; the intercept altitude is a barometric value. Anything that separates the indicated altitude from the true altitude separates the aircraft from the geometry the designer intended.

In cold air, the aircraft is lower than the altimeter indicates. Leveling off at the published altitude then places it below the intended profile in true altitude: the path is intercepted later and closer, and the intermediate segment’s clearance is reduced by exactly the temperature error. Hence the cold temperature corrections to the intermediate and level-segment altitudes – and to the crossing altitude used for the cross-check, or the corrected level-off will appear wrong against an uncorrected number.

Corrections end at the glidepath: the beam is the beam, and following it provides the correct geometric profile regardless of temperature. A corrected altitude must also be reported to ATC, whose separation assumptions are based on the uncorrected number. An incorrect pressure setting produces the same error without the excuse of physics – and the cross-check catches both, so it is worth doing when everything appears normal.

From intercept to gate: what the number brings

The intercept altitude is ultimately a distance reserve: it buys the miles needed to turn a clean, fast, level aircraft into a configured one, on speed and on path, before the stabilization gate. This gate is an operator number, not a regulatory constant. The widely adopted set – stabilized at 1,000 ft above aerodrome elevation in instrument conditions and 500 ft in visual conditions, on the correct flight path, in the landing configuration, at target speed with thrust set, within the operator’s descent rate limits – comes from the industry’s work to reduce approach and landing accidents. Read the number that applies to your operation.

The arithmetic behind this gate is not negotiable. From a typical intercept, the aircraft has a few miles – a minute or two at approach speeds – to slow and configure. Finding the path high, fast, or late does not shift the gate; it shortens the available distance to fix the problem. Here lies the tension with continuous descent operations: a lower intercept allows a cleaner join, but the obstacle floor and level distance are fixed, so the designer publishes the lowest number that both allow.

The reflex that works. In the briefing, state the intercept altitude together with its reason, not as a mere restriction. Knowing whether it is due to the obstacle floor, the airspace floor, or a distant FAP changes what you do if the descent clearance is delayed. This reasoning runs through the procedure design material used in FL330 training.

What the number really protects

The intercept altitude is not the altitude at which descent is permitted. It is where four guarantees still hold together: the obstacle survey covers the aircraft, the signal is within the volume in which it is guaranteed, capture occurs from below and therefore on the true path, and enough distance remains to stabilize. Arriving above it forfeits the signal volume and capture from below; arriving below it forfeits the obstacle survey; both reduce the remaining distance to stabilize. None of these failures is annunciated on the instruments – that is why the height-versus-distance check at the point, spoken aloud every time, is the most valuable thirty seconds of the approach.

Commentaires

Leave a Reply

Découvrez l’écosystème FL330

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