How do I fly an ILS approach in an Airbus A320 simulator?

To fly an Airbus A320 ILS approach, load and verify the runway ILS in the MCDU, intercept the localiser from below the glideslope, press APPR, confirm LOC* and G/S* on the FMA, configure for landing, then decide at minimum and land manually or continue a supported autoland.

The sequence applies broadly to Airbus A320 simulations in Microsoft Flight Simulator, X-Plane and Prepar3D, but exact MCDU pages, mode logic and autoland depth depend on the aircraft model. If the terminology is unfamiliar, start with our explanation of localiser, glideslope and ILS fundamentals.

Airbus A320 ILS approach step by step

1. Collect the approach data. Confirm the runway, ILS identifier, frequency, inbound course, decision altitude or height, and missed-approach instructions. A correct frequency alone is not enough: verify the identifier because scenery and navigation databases can disagree.
2. Load the arrival in the MCDU. On the flight-plan arrival page, select the correct ILS runway, then the appropriate STAR, transition or vectors option. Review every waypoint, altitude and speed constraint. Do not automatically delete a vector discontinuity; it may mark the point where heading instructions are expected. For the preceding flight phases, use our complete A320 setup and flight workflow.
3. Verify the ILS receiver. Most detailed A320 models auto-tune the ILS after the approach is loaded. Check the RAD NAV page and confirm the identifier, frequency and course. Manually enter the ILS only if auto-tuning has failed or the simulation requires it. Press the LS buttons to show localiser and glideslope scales on the PFDs; LS displays the guidance but does not arm approach mode.
4. Complete the PERF APPR page. Enter the landing QNH, temperature, wind and appropriate minima, then check the calculated VAPP and landing configuration. The approach phase normally activates near the DECEL point. If radar vectors or a shortcut bypass it, activate the approach phase manually when ready to slow; activating it too early can command an unwanted reduction towards approach speed.
5. Set up a sensible intercept. Approach the localiser from the correct side, preferably on a heading no more than about 30 degrees from the final course. Be level at the cleared altitude and below the glideslope. Trying to capture from above is one of the most common causes of a failed or unstable A320 ILS approach.
6. Arm the correct mode. Engage AP1 if using the autopilot. If cleared only to intercept the localiser, press LOC first. Once cleared for the full ILS, press APPR, which arms localiser and glideslope capture. Keep the cleared altitude selected until glideslope capture; after capture, set the published missed-approach altitude according to the procedure.
7. Monitor the FMA. The flight mode annunciator at the top of the PFD is the authority, not the APPR button light or moving diamonds. Confirm LOC* followed by LOC, then G/S* followed by G/S. If those modes do not appear, the aircraft has not captured the ILS.
8. Configure for landing. A typical sequence uses initial flap before or during localiser capture, followed by gear down and further flap around glideslope capture. Select Flaps 3 or FULL as planned, arm the spoilers, set the required autobrake and complete the landing checklist. Aim to be on speed, on path and fully configured by 1,000 ft above the runway.
9. Land or go around at minimum. At the displayed decision altitude or height, continue only if the required visual reference is available. Otherwise, set TOGA and fly the missed approach. For a manual landing, disconnect the autopilot at a stable point permitted by the simulated aircraft, make a small flare near 30 ft and move the thrust levers to idle at the RETARD call.

Microsoft Flight Simulator 2024 users can also follow our sim-specific procedure selection and ILS capture guidance, particularly when the loaded approach or radio data does not match expectations.

What should the A320 FMA show during an ILS?

A correctly armed and captured ILS produces a clear sequence of flight-mode indications.

When should I press APPR in the A320?

Press APPR when cleared for the ILS, established on a suitable intercept and below the glideslope. APPR arms both localiser and glideslope guidance; it does not guarantee capture or correct a poor intercept.

If instructed to capture the localiser while maintaining altitude, use LOC first. Press APPR when cleared for glideslope interception. Avoid forcing the aircraft down in vertical-speed mode to chase a glideslope from above; level off, obtain another intercept and capture it normally.

Why will the A320 not capture the ILS?

An A320 usually misses ILS capture because the wrong approach is loaded, the receiver is not tuned correctly, APPR is not armed, or the aircraft reaches the glideslope from above.

• No localiser or glideslope scales: press LS, verify the ILS frequency and confirm that the receiver can detect the station.
• Diamonds move but no LOC* appears: check APPR or LOC is armed and reduce an excessive intercept angle.
• Localiser captures but G/S does not: the aircraft may be above the glideslope or APPR may not be armed. Re-intercept from below rather than diving after it.
• The FMA shows FINAL APP: a managed non-precision approach was probably selected instead of the runway’s ILS procedure.
• The aircraft tracks an offset or wrong beam: verify the ILS identifier, inbound course and runway. A navigation-database and scenery mismatch can place the electronic guidance somewhere other than the displayed runway.
• Managed speed remains too high: check whether the MCDU approach phase has activated and whether an altitude or speed constraint is still controlling the profile.

Do I need AP2 for an A320 ILS approach?

AP2 is not required for a normal coupled ILS followed by a manual landing; one autopilot is sufficient. Dual autopilots are used for autoland, provided the aircraft model, runway ILS and simulated system status support it.

For autoland, engage both autopilots as permitted by the model and verify an appropriate capability indication such as CAT 3 DUAL, followed later by LAND. Some simplified A320 simulations do not model dual-channel landing or rollout correctly. Pressing AP2 cannot repair an incorrect frequency, poor intercept or failed glideslope capture.

Can I hand-fly the A320 ILS?

Yes. Complete the same MCDU, receiver and LS setup, then fly the flight-director commands or centre the raw localiser and glideslope indications with small control inputs. Autothrust may remain engaged if desired.

If practising a true raw-data ILS, switch off the flight directors so their commands do not conflict with the indications you intend to follow. Keep corrections small, monitor VAPP and go around if the approach becomes unstable or either guidance signal behaves unexpectedly.