Fly a Fenix A320 ILS approach in MSFS: MCDU setup, ILS tuning, LOC/GS capture, FMA checks, landing configuration and common fixes.
To fly an ILS approach in the Fenix A320 for Microsoft Flight Simulator, load the ILS runway in the MCDU, complete PERF APPR, display and identify the ILS, intercept the localiser from below the glideslope, then press APPR. Confirm LOC and G/S capture on the FMA, configure for landing, and disconnect or autoland as planned.
Fenix A320 ILS approach procedure
The aircraft must be correctly programmed, positioned and configured before APPR mode can capture the ILS.
- Select the ILS approach. On the destination ARRIVAL page, choose the correct ILS runway, STAR and transition. Review the F-PLN page for an unexpected discontinuity, duplicate waypoint or incorrect runway. Do not remove a MANUAL/vector segment unless you are replacing it with a valid clearance or routing.
- Complete PERF APPR. Enter the destination QNH, temperature, wind, transition altitude and published minima. Confirm VAPP rather than accepting an unsuitable default; our guide to calculating Fenix landing weight and VAPP explains where that figure comes from. Allow the approach phase to activate at the deceleration point, or activate it manually when beginning the approach.
- Verify the ILS. The FMGS normally auto-tunes the ILS associated with the selected approach. Check the RAD NAV page and compare the identifier, frequency and front course with the approach data. Press the
LSpushbutton on the EFIS panel to show the localiser and glideslope scales on the PFD. The LS button displays the guidance; it does not tune the radio. - Set up the intercept. Use NAV or selected heading to approach the localiser at a shallow angle, ideally no more than about 30 degrees. Be level below the glideslope, with AP1 and A/THR engaged if flying a coupled approach. Begin slowing and select the first stage of flap as required.
- Arm approach mode. Once cleared for the ILS and positioned for capture, press
APPRon the FCU. Look for blueLOCandG/Sarmed indications on the Flight Mode Annunciator. Activating the MCDU approach phase is not the same as pressing APPR; this confusion causes many failed captures. - Confirm capture on the FMA. The localiser normally changes through
LOC*to greenLOC, followed byG/S*and greenG/S. The autopilot should then follow both beams. Do not assume centred diamonds mean the autopilot has captured them—the FMA is the authority. - Configure for landing. Select gear and flap progressively so that the aircraft reaches Flaps 3 or FULL, VAPP and the landing configuration before the stabilisation gate. Arm the spoilers, select the planned autobrake setting and confirm that the ECAM LAND memo has no outstanding blue items.
- Finish the approach. For a normal hand-flown landing, disconnect the autopilot at a comfortable height while retaining stable ILS guidance. Reduce thrust and flare according to the normal A320 technique; the complete A320 touchdown and rollout sequence covers the remaining steps.
What should the FMA show during an ILS?
A correctly coupled ILS changes from armed blue modes to captured green modes as the aircraft reaches each beam.
| FMA indication | Meaning | Required response |
|---|---|---|
LOC and G/S in blue | Both modes are armed | Maintain the intercept and remain below the glideslope |
LOC* | Localiser capture is in progress | Monitor the turn onto the runway centreline |
LOC in green | Localiser is being tracked | Check alignment and continue configuring |
G/S* | Glideslope capture is in progress | Confirm the aircraft begins the expected descent |
G/S in green | Glideslope is being tracked | Monitor vertical path, speed and stabilisation |
After glideslope capture, set the missed-approach altitude when appropriate. Setting it too early can create confusion if the aircraft is still level at an assigned approach altitude.
Why will the Fenix A320 not capture the ILS?
Most failed captures come from incorrect tuning, approaching above the glideslope or arming the wrong FCU mode.
- No ILS diamonds or identifier: press LS, confirm the selected procedure is an ILS rather than RNAV or LOC-only, and check the frequency. You may also be outside reception range.
- Diamonds are visible but nothing captures: check that APPR is armed on the FMA, not merely the MCDU approach phase. Confirm that an autopilot is engaged if you expect the aircraft to fly the approach automatically.
- LOC captures but G/S does not: the aircraft is commonly above the glideslope. Descend and reposition for another intercept rather than diving after it. A LOC-only procedure has no glideslope to capture.
- The aircraft follows the wrong runway: verify the ILS identifier, especially at airports with parallel approaches. Reselect the correct approach or tune its ILS manually if automatic tuning is wrong.
- The world-map plan and MCDU disagree: selecting an approach in the MSFS planner does not remove the need to verify it in the Fenix MCDU. A runway change also requires the ARRIVAL and PERF APPR pages to be checked again.
- The procedure or frequency is missing: the Fenix database, airport scenery and planning data may represent different AIRAC cycles. Follow our instructions for updating the Fenix AIRAC data, then remove any conflicting airport scenery if the mismatch remains.
Do I need both autopilots for the ILS?
One autopilot is sufficient for a coupled ILS followed by a manual landing; both autopilots are required for a dual-channel autoland.
For autoland, engage the second autopilot when the approach mode and aircraft state permit it, then verify the required capability and subsequent LAND, FLARE and ROLLOUT indications. Do not continue solely because both AP buttons are illuminated. MSFS 2024 users can follow our dual-autopilot CAT III workflow for the additional checks.
If the aircraft is not on the correct beam, not fully configured or not stable by about 1,000 feet above the airport in instrument conditions, go around and set up again. APPR mode cannot rescue a poor intercept or an incorrect ILS selection.