Why is my aircraft not capturing or following the ILS glideslope in Microsoft Flight Simulator X (FSX)?
If your aircraft will not capture or follow the ILS glideslope in FSX, the usual cause is setup rather than a simulator bug: wrong ILS frequency, incorrect inbound course, trying to intercept from above, being too fast, or leaving the GPS/NAV source or autopilot mode in the wrong state. Aircraft and scenery limitations can also be involved.
What usually stops glideslope capture in FSX?
An ILS has two parts: the localiser for lateral guidance and the glideslope for vertical guidance. It is quite common in FSX to capture the localiser but miss the glideslope because the conditions for vertical capture are more strict.
In plain terms, FSX usually expects you to be established on the localiser, below the glideslope, at a sensible intercept altitude, with the correct navigation source selected. If one of those pieces is off, the aircraft may fly straight through, level off, or pitch up and down without locking on properly.
Why is the glideslope not capturing even though the localiser works?
| Common cause | What you will see | What to do |
|---|---|---|
| Wrong ILS frequency | Localiser or glideslope stays dead or behaves oddly | Check the exact ILS frequency for the runway in the FSX map, GPS or approach chart |
| Wrong inbound course set | Autopilot captures poorly or wanders after intercept | Set the published runway front-course on the OBS/course selector |
| Intercepting from above | Glideslope needle comes alive but never captures | Descend to the published intercept altitude before the final approach fix |
| GPS still selected instead of NAV | Aircraft follows GPS route but ignores the ILS | Switch the CDI/nav source from GPS to NAV before intercept |
| APR mode armed too late | You fly through the beam without capture | Arm approach mode before localiser and glideslope intercept |
| Too fast or badly configured | Overshoots localiser or porpoises on glideslope | Slow down, use approach flap and stabilise early |
| Non-precision or localiser-only runway | No glideslope indication exists | Confirm the runway actually has a glideslope in FSX |
| Aircraft autopilot limitations | One aircraft works, another does not | Check whether that aircraft supports full coupled ILS approaches properly |
Check the ILS setup first
This is the part most often missed. A runway may have a localiser on one end but not the other, or the frequency may be different from what you expected. In FSX, stock airports and add-on airports can also differ.
- Confirm the runway has an ILS. Do not assume every paved runway does. Some are localiser-only, and many runways have no precision guidance at all.
- Tune the correct NAV radio. Most aircraft use NAV1 for the primary ILS, though some can use NAV2 depending on the setup.
- Set the inbound course. Many FSX aircraft will still show guidance without it, but proper autopilot tracking is usually better when the correct front-course is set.
- Switch from GPS to NAV if your aircraft has a GPS/CDI selector. If you stay in GPS mode, the autopilot may keep tracking the flight plan instead of the ILS.
- Arm approach mode early. We usually recommend doing it once you are cleared and established for intercept, not after you are already crossing the beam.
Intercept altitude matters more than most people think
The glideslope is normally captured from below, not from above. If you are high, FSX will often let the needle slide downward through the centre without the autopilot pitching down to chase it. That is correct behaviour.
As a rule, be at or below the published glideslope intercept altitude before the final approach fix. If you are unsure, level off earlier, get established on the localiser, then wait for the glideslope to come down to you.
If you try to dive for it late, the aircraft may never capture cleanly. Even if it does, the approach will usually be unstable.
Aircraft speed and configuration can prevent a stable capture
FSX autopilots are not all equally refined. A fast jet or a heavy airliner left clean and fast until the last moment can overshoot the localiser or struggle to settle on the glide path. Small GA aircraft can also bobble if the power setting is poor.
We recommend stabilising before intercept:
- Approach speed set and under control
- First stage of flap or normal approach configuration selected as appropriate
- Power trimmed so the aircraft is not accelerating
- Localiser intercepted on a modest angle rather than a sharp cut-in
If the aircraft is already fighting speed and trim, the autopilot has much less chance of making a tidy capture.
Autopilot mode mistakes that cause ILS problems in FSX
Mode confusion is a classic FSX trap, especially in add-on aircraft with custom avionics. One wrong mode can make it look as though the simulator has broken the approach.
Common mode errors
- NAV mode left on instead of APR: localiser may capture, but vertical guidance does not.
- APR armed after passing the intercept point: the glideslope is already behind you.
- Altitude hold still commanding level flight: some aircraft handle this fine, others will not capture cleanly until approach mode takes priority.
- Back-course mode selected by mistake: tracking can become erratic or reversed.
- GPS source still active: autopilot ignores the radio beam.
In stock FSX aircraft, approach mode is usually enough if the radios and source selection are correct. In some complex add-ons, the exact arming sequence matters more.
Could the runway or scenery be the problem?
Yes, sometimes. If you are using add-on scenery, older AFCAD-style airport files, or modified navigation data, the ILS at that airport may not match what you expect. A runway renumbering, displaced threshold change or duplicated airport file can all create odd behaviour.
Typical clues are these:
- One airport has the issue, but others work normally
- The glideslope appears offset or too steep
- The localiser works, but the vertical beam seems absent
- A stock aircraft and an add-on aircraft both fail at the same runway
If that happens, test the same approach at a default FSX airport with a known-good ILS. If it works there, the problem is probably airport data or scenery rather than your flying technique.
How to fix an ILS glideslope that will not capture in FSX
- Verify the runway has a real ILS and not just a localiser or non-precision approach.
- Tune NAV1 to the exact ILS frequency shown in FSX for that runway.
- Set the inbound course on the OBS/course selector.
- Switch the CDI/source from GPS to NAV if your panel supports both.
- Intercept the localiser at a shallow angle, ideally already slowed and configured.
- Level at the correct intercept altitude so you are below the glideslope, not above it.
- Arm APR mode before the glideslope reaches centre.
- Monitor the needles. If the glideslope starts moving down and the aircraft does not react, disengage, reset the setup and fly another intercept rather than forcing it.
- Test another aircraft or airport if the problem repeats. That quickly tells you whether the issue is aircraft-specific or airport-specific.
Does FSX itself have ILS quirks?
It does. FSX ILS logic is generally workable, but it is not perfect. Some stock autopilots are basic, some add-on aircraft override default behaviour, and scenery conflicts can upset radio navigation. That said, most glideslope problems come from intercepting high, staying in GPS mode, or arming the wrong autopilot mode.
If you want to practise, use a default aircraft and a default airport first. Once that is working consistently, move back to your preferred aircraft or add-on scenery and narrow down what changed.
If the glideslope still will not follow
When everything appears correct and the aircraft still refuses to track, strip the situation back:
- Use clear weather with little or no wind
- Choose a default FSX aircraft
- Pick a major default airport with a well-known ILS runway
- Start on vectors or on downwind so you can build a stable intercept
If it works in that simple setup, FSX is fine and the fault lies with the original aircraft, scenery, panel logic or procedure. If it still fails, revisit the radio frequency, course, source selector and intercept altitude. In our experience, one of those four is almost always the culprit.