Why is ILS not working in Microsoft Flight Simulator?
ILS usually fails in Microsoft Flight Simulator 2020 or 2024 because the wrong runway or frequency is selected, the receiver is still in GPS mode rather than VLOC/LOC, or the aircraft tries to capture the glideslope from above. Confirm the approach, tune NAV1, select the localiser source and arm APP/APR.
In most general-aviation aircraft, that means using the active NAV1 frequency and selecting VLOC. Airliners may use a dedicated ILS receiver, an FMS radio-navigation page or automatic tuning, but the same checks apply: correct frequency, correct source, viable intercept and the proper autopilot mode.
What should you check when ILS is not working?
- Confirm that the runway has an ILS. An RNAV, RNP, visual or localiser-only approach is not a full ILS. A localiser-only procedure provides lateral guidance but no glideslope, while an airport may equip only one runway direction.
- Verify the runway, frequency and inbound course. Tune the frequency belonging to the exact runway direction, not the opposite end. Runway renumbering, outdated approach information and add-on airport data can create mismatches. Set the published inbound course where the aircraft requires it, but remember that turning the course knob does not tune the receiver.
- Put the frequency in the active receiver. A frequency left in the standby window will not drive the instruments. NAV1 is normally the safest choice in light aircraft because some autopilots cannot follow NAV2. In an airliner, check the dedicated ILS or radio-navigation page and verify that automatic tuning has selected the expected runway.
- Select LOC or VLOC instead of GPS. Loading an approach creates a route, but it does not guarantee that the cockpit has changed from GPS guidance to the localiser. On Garmin-style avionics, check the CDI source. Traditional panels must display the NAV receiver connected to the autopilot.
- Intercept from below at a shallow angle. Establish on the published intercept altitude, preferably with a localiser intercept angle of roughly 30 degrees or less. Capture the localiser first and approach the glideslope from below; descending steeply onto it from above is unreliable and unsafe.
- Arm APP or APR before crossing the beam. The cockpit annunciation should show LOC and GS armed, followed by captured indications as each mode engages. A lit button alone is not proof of capture. Exact labels and annunciation colours vary between aircraft.
What does each ILS failure symptom mean?
| Symptom | Most likely causes | What to do |
|---|---|---|
| No localiser or glideslope indication | Wrong frequency, frequency in standby, GPS source selected, receiver unpowered, out of range or no ILS on that runway | Check the approach type, active NAV receiver, electrical power and CDI source |
| Localiser works but glideslope does not | Localiser-only approach, aircraft above the beam, or LOC mode selected instead of APP/APR | Confirm it is a full ILS, remain below the glideslope and arm approach mode |
| Needles move but autopilot ignores them | Autopilot is following GPS or heading mode, APP is not armed, or the wrong receiver drives the autopilot | Match the autopilot navigation source to the displayed ILS receiver and check mode annunciations |
| Glideslope marker moves down the scale | The aircraft is above the glideslope | Do not dive after it; go around or reposition for a lower, stabilised intercept |
| Aircraft turns away from the runway | Wrong runway frequency, back-side localiser reception, incorrect approach selection or conflicting airport data | Recheck the runway identifier, inbound course and installed airport packages |
| APP mode cancels or will not arm | Aircraft-specific mode requirements, conflicting key bindings or an avionics fault | Use the cockpit control, verify the flight director and source, then test without duplicate controller assignments |
Why does the localiser work but not the glideslope?
A working localiser with no vertical guidance usually means the approach is LOC-only, APP mode has not been armed, or the aircraft has intercepted from above. The glideslope is designed to be captured from below after the localiser is established.
If the glideslope diamond is already below the aircraft symbol, maintain safe altitude and reposition rather than forcing a steep descent. Also check that the approach name explicitly includes ILS; loading a runway transition or an RNAV procedure to the same runway does not create an ILS glideslope.
Does loading an ILS approach tune it automatically?
Automatic ILS tuning depends on the aircraft and its avionics implementation, so loading or activating the procedure is not enough by itself. Some airliners and glass cockpits can tune and switch sources automatically, while others require manual frequency entry and a deliberate GPS-to-VLOC change.
Always verify the active frequency, Morse identifier where the aircraft supports it, selected navigation source and armed modes. If Garmin knobs, FMS fields or CDI controls are unresponsive, use our avionics control and navigation-source troubleshooting steps before changing the approach setup.
Is ILS setup different in MSFS 2020 and 2024?
The underlying ILS technique is the same in Microsoft Flight Simulator 2020 and 2024; the larger difference is the aircraft's avionics and systems depth. A default light aircraft, an Airbus-style airliner and a complex add-on may tune and arm the same approach in different ways.
For the complete intercept sequence, follow our MSFS 2024 ILS capture procedure. The MSFS 2020 localiser and glideslope walkthrough explains the equivalent technique in the earlier simulator.
What if ILS fails at only one airport?
An ILS that fails at one airport but works elsewhere usually points to runway data, scenery or a package conflict rather than incorrect cockpit technique. Test the same approach in a standard aircraft, then temporarily remove or disable airport scenery and navigation-data modifications that affect that location.
Runway renumbering can leave an add-on airport visually showing one designation while the simulator's navigation database expects another. Compare the selected approach, runway direction and frequency inside the avionics rather than relying only on signs painted in the scenery.
If VOR and ILS receivers both fail across several aircraft and airports, the problem is broader than one approach. Our NAV-radio reception checklist covers receiver power, range, source selection and package conflicts. If only one complex add-on aircraft fails, use its specific ILS procedure and test a default aircraft before treating the airport as broken.