Learn how to fly an ILS approach in a flight simulator: set the radios, capture localiser and glideslope, troubleshoot errors and complete the landing.
To fly an ILS approach in a flight simulator, tune and identify the runway’s ILS, set the published inbound course, and intercept the localiser from below the glideslope. If using autopilot, arm approach mode, confirm localiser and glideslope capture, then disconnect to land manually or continue only with a supported autoland system.
For Aviation & Real-World Flying practice, this method applies across desktop simulators, but cockpit labels and automation differ. The flight-mode annunciator, not an illuminated approach button, tells you what the autopilot is actually doing.
What must be set before intercepting the ILS?
Before intercepting, you need the correct runway, ILS frequency and identifier, front course, intercept altitude, minimums and missed-approach instructions. If the panel is unfamiliar, check which receiver, display and navigation-source settings an ILS needs.
- Runway and approach: Confirm that the selected procedure is a full ILS, not a localiser-only or RNAV approach to the same runway.
- Frequency and identifier: Tune the active navigation receiver and verify the displayed or audible Morse identifier. Some simulator aircraft auto-tune through the flight-management system, but the frequency still needs checking.
- Front course: Set the published inbound course where the aircraft provides a course selector. Do not use the reciprocal course unless you are deliberately flying an authorised back-course procedure.
- Intercept altitude: Use the published altitude that places the aircraft below the glideslope. Capturing a false or excessively steep glideslope from above can produce an unsafe descent.
- Navigation source: On panels that switch between GPS and radio navigation, select
VLOC,LOCor the equivalent radio source before capture. - Minimums: Set the charted decision altitude or decision height and the correct pressure setting. Brief the missed approach before descending.
Use approach information that matches the simulator’s navigation database and scenery. Our guide to finding matching simulator ILS chart data explains where the runway frequency, course, fixes and intercept altitude come from. Old scenery paired with newer navigation data can produce renamed runways, changed frequencies or small course discrepancies.
How do you fly the ILS step by step?
A reliable simulator ILS is flown by establishing a stable intercept, capturing the localiser first and allowing the glideslope to come down to the aircraft.
- Load or brief the procedure. Select the ILS runway and an appropriate transition, or prepare to receive vectors. Loading an approach into the flight-management system does not guarantee that every aircraft will tune the radio automatically.
- Tune, identify and set the course. Place the ILS frequency in the active receiver, confirm its identifier and set the published front course. Check that the correct receiver is driving the primary flight display or HSI.
- Fly towards the localiser. Approach the final course at the charted altitude. An intercept angle of about 20–30 degrees is easy for most pilots and autopilots to manage; a sharp crossing angle can cause overshoot or prevent capture.
- Slow and configure. Reduce speed and begin extending flaps according to the aircraft procedure. Do not arrive at the localiser fast, high and clean, then expect approach mode to repair the profile.
- Capture the localiser. Arm
LOC,APP,APRorAPPR, depending on the aircraft. Watch the flight-mode annunciator change from armed to captured. When hand flying, make small corrections towards the needle rather than chasing every movement. - Intercept the glideslope from below. Hold the published altitude while the glideslope pointer moves towards the centre. At capture, verify that the vertical mode changes to
G/Sor its equivalent and that the aircraft begins a sensible descent. Never dive to catch the beam from above. - Complete the landing configuration. Extend the landing gear, select final flap, stabilise the speed and complete the landing checks. Set the missed-approach altitude at the stage required by the aircraft procedure, commonly after glideslope capture.
- Make the decision at minimums. If the required runway references are visible and the approach is stable, continue and land. Otherwise initiate the missed approach immediately. Disconnect the autopilot by its required minimum height unless the aircraft and simulator model support a properly configured autoland.
Simulator controls differ enough that platform-specific instructions can help with the final setup. In Microsoft Flight Simulator 2024, follow the MSFS 2024 procedure-selection and mode sequence for its navigation and autopilot workflow.
Why will the localiser or glideslope not capture?
An ILS usually fails to capture because the wrong navigation source is selected, approach mode is not armed, the intercept is too steep or the aircraft reaches the glideslope from above.
| Symptom | Likely cause | What to check |
|---|---|---|
| No localiser indication | Wrong frequency, receiver still in standby, GPS source selected or aircraft out of usable range | Verify the frequency and identifier, swap it to active, select the radio source and confirm the runway actually has an ILS. |
| Needle moves but autopilot does not capture | LOC or approach mode is not armed, another lateral mode remains active or the intercept angle is excessive | Read the flight-mode annunciator, arm the correct mode and establish a shallower intercept. |
| Localiser captures but glideslope stays armed | Aircraft is above the beam, full approach mode was not armed or the procedure is localiser-only | Do not force a steep descent. Reposition for another intercept from below and verify the approach type. FSX users can work through these FSX glideslope capture checks. |
| Aircraft turns away from the runway | Wrong runway, reciprocal course, back-course selection or incorrect receiver | Recheck the runway identifier, front course, navigation source and active frequency. |
| ILS needles disagree with the magenta route | The flight-plan path and radio beam are separate guidance sources | Confirm that the loaded approach matches the tuned ILS and monitor the radio guidance after selecting the approach source. |
| Published frequency gives no signal | Scenery and navigation data represent different airport revisions | Use runway and ILS data consistent with the installed scenery and aircraft database. |
A mistake we see constantly is treating a lit APP button as confirmation of capture. It may mean only that the mode is armed. Look for captured localiser and glideslope modes on the flight-mode annunciator and confirm that the aircraft is tracking towards the runway at a plausible descent rate.
Can every simulator aircraft perform an autoland?
No—an aircraft can fly a coupled ILS without being capable of automatically flaring, touching down and controlling the rollout.
- Hand-flown ILS: Use the localiser and glideslope indications as raw guidance, then land manually.
- Coupled ILS: Let the autopilot track the approach, then disconnect by the aircraft’s specified minimum height and complete the landing manually.
- Autoland: Continue only when the aircraft model explicitly supports it and all required autopilot channels, approach modes, radio-altimeter functions and landing configuration are correct.
Pressing approach mode does not by itself create an autoland, and a runway offering low-visibility ILS capability does not guarantee that the selected simulator aircraft can use it. For real-world flying, aircraft manuals, valid official charts, instructor guidance and operator procedures take precedence over simulator technique.