Why Didn't My Glideslope Capture?

Few things are more frustrating than setting up an ILS approach, seeing the localizer capture perfectly, and then watching the aircraft fly straight through the glideslope.

If this has happened to you, you're not alone.

Glideslope capture failures are one of the most common problems encountered by new airline pilots in flight simulators. The good news is that the cause is usually simple and easy to fix.

This guide covers the most common reasons a glideslope fails to capture and how to prevent them.

First: What Should Happen?

During a normal ILS approach:

1. The aircraft intercepts the localizer.
2. The localizer captures.
3. The aircraft approaches the glideslope from below.
4. The glideslope captures.
5. The aircraft begins descending automatically.

If any of those conditions are not met, the glideslope may never capture.

Cause #1: You Were Above the Glideslope

This is by far the most common reason.

ILS systems are designed to be intercepted from below.

If the aircraft is above the glide path:

• The localizer may capture.
• The glideslope may never capture.
• The aircraft may continue flying level.

For example:

• Published intercept altitude: 2,300 ft
• Aircraft altitude: 3,500 ft

In this situation the aircraft is already above the glide path.

The solution is simple:

Always arrive below the glideslope and allow it to descend onto the aircraft.

Cause #2: APPR Mode Was Never Armed

In both Airbus and Boeing aircraft, the approach mode must be armed before the glideslope can capture.

Common symptoms:

• Localizer visible.
• Glideslope visible.
• Aircraft ignores the glideslope.

Always verify:

• APPR is selected.
• Approach mode is armed.
• FMA indications are correct.

If the aircraft is not expecting to capture the glideslope, it won't.

Cause #3: You Armed APPR Too Late

Another common mistake is waiting until the last moment to arm the approach.

If the aircraft is already crossing the localizer or glideslope when APPR is selected, capture may not occur correctly.

A good habit is to arm APPR before intercepting the final approach course.

Cause #4: Wrong Runway or Approach Loaded

Sometimes the aircraft is trying to fly a different approach than the one you expect.

Examples:

• Wrong runway selected.
• Wrong transition selected.
• Approach not activated.
• FMC or MCDU mismatch.

Always verify:

• Runway number.
• ILS frequency.
• Final approach course.
• Approach chart.

Small setup errors can completely prevent glideslope capture.

Cause #5: Incorrect ILS Frequency

Most modern aircraft tune ILS frequencies automatically.

However, automatic tuning is not foolproof.

If the wrong frequency is tuned:

• The localizer may behave unexpectedly.
• The glideslope may not be available.
• The approach may fail entirely.

When troubleshooting, compare the tuned frequency against the approach chart.

Cause #6: Intercepting Too Close to the Runway

The aircraft needs time to capture and stabilize.

If vectors place you too close to the runway:

• The localizer may capture late.
• The glideslope may not have enough distance to capture.
• The approach may become unstable.

This often happens when pilots shortcut arrivals aggressively.

Cause #7: Flying an RNAV Instead of an ILS

Many airports publish multiple approaches to the same runway.

Examples:

• ILS RWY 25
• RNAV RWY 25
• RNP RWY 25

Loading the RNAV approach by mistake means there is no glideslope to capture.

Always confirm the approach type in the FMC or MCDU.

Cause #8: Focusing on the PFD Instead of the FMA

New pilots often stare at the localizer and glideslope needles.

Experienced pilots monitor the Flight Mode Annunciator.

The FMA tells you:

• What is armed.
• What is active.
• What the autopilot intends to do.

If the glideslope isn't armed on the FMA, it won't magically capture later.

The FMA is usually the fastest way to diagnose the problem.

Airbus Example

In an Airbus A320, after pressing APPR you would typically see:

LOC (blue)
G/S (blue)

Blue means armed.

When captured:

LOC (green)
G/S (green)

Green means active.

If G/S never appears in blue, the aircraft is not prepared to capture it.

Boeing Example

In a Boeing 737, after selecting APP mode, the FMA should indicate that localizer and glideslope capture are armed.

If APP mode was never selected or the aircraft is above the glide path, capture may never occur.

Again, the FMA is your primary source of truth.

Quick Troubleshooting Checklist

If the glideslope doesn't capture, ask yourself:

• Am I below the glideslope?
• Did I arm APPR mode?
• Did I arm it early enough?
• Is the correct runway selected?
• Is the correct ILS frequency tuned?
• Am I flying an actual ILS approach?
• What does the FMA show?

In most cases, the answer is found within seconds.

Final Thoughts

Most glideslope capture problems are not aircraft problems.

They're setup problems.

If you remember only one rule, remember this:

Intercept the glideslope from below.

That single habit eliminates the majority of failed ILS approaches and will make your arrivals significantly more reliable in both Airbus and Boeing aircraft.