How do I fly an ILS approach in MSFS 2024?
To fly an ILS approach in Microsoft Flight Simulator 2024, select the correct runway procedure, verify its ILS frequency and identifier, set the inbound course, choose the radio navigation source, intercept the localiser at a shallow angle from below the glideslope, then arm APP/APR and monitor both captures to minimums.
How do I use approach mode in MSFS 2024?
APP, APR or APPR arms the autopilot to capture the ILS localiser and glideslope; it does not tune the ILS or correct a poor intercept for you. MSFS 2024 has no universal ILS panel, so button labels, radio management and mode indications vary between aircraft.
- Select the actual ILS procedure. Choose an approach named
ILS RWYfollowed by the runway number in the pre-flight planner or onboard FMS. Merely selecting a landing runway does not load its ILS, and some runways have no ILS at all. - Verify the approach in the aircraft. Confirm that the intended runway, transition and final approach legs appear in the onboard flight plan. A plan created outside the cockpit may not configure every aircraft's radios or approach logic automatically.
- Tune and identify the ILS. Check the published frequency against the active navigation receiver, normally
NAV1in a general-aviation aircraft. If it is in standby, swap it to active. Where supported, confirm the displayed identifier or listen to its Morse identifier; seeing a frequency is not proof that the correct localiser is tuned. - Set or verify the front course. Use the published magnetic inbound course. Older HSI and CDI installations may require it to be set manually, while managed airliners and modern glass cockpits often insert it automatically. We still verify it.
- Brief the intercept and minimums. Note the final approach course, glideslope intercept altitude, decision altitude or height, missed-approach instructions and landing configuration. Set the missed-approach altitude when the aircraft's normal procedure calls for it.
- Select the correct navigation source. In many Garmin-equipped aircraft, change the CDI from
GPStoVLOC,NAV1or the equivalent radio source. Some avionics switch automatically when an ILS approach is active, but do not rely on that. Airliners use aircraft-specific radio and display logic, so verify that ILS indications are shown rather than looking for a Garmin-style CDI switch. - Intercept from sensible geometry. Approach the final course at roughly 20–30 degrees, level at the published intercept altitude and from below the glideslope. If the glideslope pointer is above centre and moving down towards it, the aircraft is normally below the path and positioned for capture.
- Stabilise before capture. Reduce speed, establish the required flap setting and avoid arriving at the localiser while still descending rapidly. Extend the intercept if MSFS ATC turns you towards final too high, too close or at a near-right angle.
- Arm approach mode. Press
APP/APRwhile established on the intercept and before crossing the localiser. The existing heading or navigation mode should remain active until the localiser captures. - Confirm both captures on the mode annunciator. The normal sequence is localiser armed, localiser captured, glideslope armed and glideslope captured. The exact labels may be
LOC,GS,G/Sor aircraft-specific equivalents. - Manage the descent and speed. Once the glideslope captures, the autopilot should pitch down to follow it. A basic autopilot does not control the throttle, so adjust power, gear and flap while monitoring speed, vertical rate and beam tracking.
- Continue visually or go around. At the applicable minimums, land only with the required runway references in sight and a stable aircraft. Otherwise execute the missed approach. Glideslope capture alone does not mean the aircraft can flare or land automatically.
What should the approach-mode annunciations show?
A correctly armed approach should progress from lateral and vertical modes being armed to LOC and GS becoming active. The flight-mode annunciator is more reliable than the light on the approach button.
| Stage | Expected indication | Meaning |
|---|---|---|
| Before localiser capture | Heading or navigation mode active; LOC armed | The autopilot is waiting for the localiser beam. |
| Localiser capture | LOC active; GS armed now or shortly afterwards | The autopilot is steering onto the runway centreline. |
| Glideslope capture | LOC and GS active | The autopilot is controlling lateral track and descent. |
| After an unexpected reversion | HDG, VS, ALT or another mode replaces LOC/GS | The ILS is no longer controlling that axis; intervene or go around. |
Colours and intermediate capture symbols differ by avionics package. A lit APP button means the mode was selected, not necessarily that either beam has been captured.
Quick ILS check before turning final
- Approach: the correct ILS and runway are active
- Radio: frequency active and identifier confirmed
- Course: front course set or verified
- Source:
VLOC/NAV/ILS, not unintendedGPS/FMS - Position: shallow localiser intercept and below the glideslope
- Aircraft: speed and configuration under control
- Modes:
LOCandGSarmed, then positively captured - Plan: minimums and missed approach understood
What is the difference between ILS, localiser and RNAV?
An ILS uses a radio localiser for lateral guidance and a glideslope for vertical guidance, while localiser-only and RNAV approaches require different sources or descent methods.
| Approach | Guidance source | Vertical guidance |
|---|---|---|
| ILS | VLOC, NAV or aircraft-specific ILS receiver | Radio glideslope |
| LOC or localiser-only | Localiser receiver | None; descend using the published altitudes and minimum descent altitude |
| GPS/RNAV | GPS or FMS | Only when the procedure and avionics provide a supported vertical path |
The same APP/APR button may be used for both ILS and some RNAV approaches, but the selected source is different. Do not switch to VLOC for an RNAV final; our GPS/RNAV approach setup and source-selection guide covers that workflow separately.
Why is my ILS not capturing in MSFS 2024?
An ILS usually fails to capture because the wrong source, receiver, frequency, altitude or intercept geometry has been selected. The mistake we see most often is a general-aviation aircraft remaining in GPS mode while the pilot expects it to follow the radio beam.
| Symptom | Likely cause | Fix |
|---|---|---|
| No localiser or glideslope indication | Wrong frequency, frequency still in standby, wrong receiver, or the runway has no ILS | Verify the named approach, active frequency and receiver. Many basic autopilots couple only to NAV1. |
| Needles appear, but the autopilot follows the magenta line | The CDI remains on GPS/FMS, or approach mode is not armed | Select the radio source where required and check the flight-mode annunciator. |
| The aircraft flies through the localiser | Approach mode was armed too late, or the intercept is too fast or steep | Reintercept from farther out at a shallow angle and controlled speed. |
| Localiser captures, but glideslope does not | The aircraft is above the path, only LOC mode is active, or the procedure is localiser-only | Confirm GS is armed and that this is a true ILS. If high, go around or reposition to intercept from below. |
| The aircraft turns away from final | Wrong runway, reciprocal course, back-course signal or parallel-runway ILS | Check the approach name, identifier, frequency and front course before trying again. |
| The needles oscillate and the autopilot weaves | Excessive speed, a late intercept, turbulence or large corrections | Slow down, stabilise earlier and use a longer intercept. Gusts move the aircraft around the beam even when the radio is working. |
| MSFS ATC leaves the aircraft high or close | The vector does not provide usable intercept geometry | Extend the leg, descend to the published intercept altitude and rejoin rather than forcing capture from above. |
| The beam is absent or visibly offset from the runway | Airport scenery and navigation data may conflict, particularly with an add-on airport | Verify the procedure data and test without conflicting airport scenery. Do not continue an approach whose guidance is clearly displaced. |
If the autopilot commands an unsafe turn or descent, disconnect it, stabilise the aircraft and either rebuild the intercept or go around. Repeatedly pressing APP does not repair an incorrect radio or source selection.
Can I fly and land the ILS without autopilot?
Yes, an ILS in MSFS 2024 can be hand-flown from intercept to minimums; the autopilot is optional. Centre the localiser with small bank corrections, follow the glideslope with restrained pitch changes, and use power to keep the aircraft on its target speed.
Avoid chasing every needle movement. Trim the aircraft, maintain a steady instrument scan and correct developing trends rather than waiting for full-scale deflection. Once visual, transition to the runway and apply the appropriate wind correction; our crosswind landing technique guide explains the final alignment, touchdown and rollout.
Does APP mode perform an automatic ILS landing?
No, approach mode normally flies only the localiser and glideslope; it does not guarantee an automatic flare, touchdown or rollout. For an ILS landing in MSFS 2024, assume the final landing is manual unless that specific aircraft explicitly supports and has been configured for autoland.
Autoland-capable airliners use aircraft-specific requirements such as suitable autopilot channels, radio configuration and confirmed landing, flare and rollout modes. If the annunciator never shows the expected autoland status, disconnect at the appropriate point and land manually or go around rather than assuming glideslope capture is enough.