How do I fly an ILS approach in X-Plane?

To fly an ILS approach in X-Plane 11 or 12, load or brief the correct runway procedure, tune and identify its localiser frequency, set the published inbound course, select VLOC/NAV, intercept the localiser from below the glideslope, arm APP/APR mode, then monitor both captures and land or go around at minimums.

Prepare the ILS before the final approach

Use an approach chart or X-Plane's navigation data to confirm the runway, localiser frequency, identifier, inbound course, glideslope intercept altitude, minimums and missed-approach procedure. Set the local pressure and relevant decision altitude before workload increases.

Make sure the frequency belongs to the intended runway, not its reciprocal or a parallel runway. Our guide to selecting and verifying the correct ILS frequency covers identifiers, courses and common runway-selection mistakes.

How do I fly the ILS step by step?

1. Load or brief the approach. Loading an ILS in a GPS or FMS provides routing to the final approach, but it does not by itself prove that the correct NAV receiver and guidance source are selected.
2. Tune and identify the localiser. Put the published frequency in the active NAV1 position unless the aircraft procedure specifies another receiver. Confirm the Morse identifier through the audio panel or the displayed identifier where supported.
3. Set the inbound course. Enter the published front course on the course selector. Although some instruments derive localiser direction independently, the correct course is needed for an intelligible HSI display and proper aircraft-specific operation.
4. Select VLOC or NAV guidance. The CDI or PFD must be taking lateral guidance from the NAV radio for the ILS final. A magenta GPS course can guide you towards the approach, but it is not the localiser signal.
5. Intercept at a sensible angle. Join the localiser from the correct side, normally at about 20–30 degrees, and be established at the published intercept altitude. The aircraft must be below the glideslope; capturing it from above is unreliable and may produce an unstable descent.
6. Configure and stabilise. Reduce speed, extend flap and gear as required, and complete the landing checklist early enough to avoid large configuration changes after glideslope capture.
7. Arm APP or APR mode. With the autopilot engaged, arm approach mode as the localiser becomes active. Check the flight-mode annunciator rather than relying on an illuminated button: LOC and GS should first arm, then show as captured. Our explanation of what autopilot APR mode actually controls explains these mode changes in detail.
8. Monitor the descent. Localiser capture normally occurs first. When the glideslope centres from above, the autopilot should leave altitude hold and begin descending. APP mode usually controls pitch and roll, not throttle, so manage airspeed and power unless the aircraft has an active autothrottle system.
9. Decide at minimums. Continue only with the required runway environment in sight and a stable approach. Otherwise, apply go-around power and fly the published missed approach. Disconnect the autopilot and land manually unless the aircraft and approach are specifically configured and approved for autoland.

Should I use GPS or VLOC for an ILS in X-Plane?

Use GPS guidance for the arrival and initial approach if desired, but use VLOC/NAV for the conventional ILS localiser and glideslope. The changeover must occur before final capture; leaving the CDI in GPS mode is one of the mistakes we see most often.

Automatic source switching and frequency tuning vary by aircraft, so verify the indication rather than assuming the avionics handled it. For the stock-style glass cockpit workflow, see our practical X-Plane 12 G1000 instructions. We also explain when to change from GPS to NAV for an ILS.

Why will the localiser or glideslope not capture?

Most failed captures come from an incorrect radio source, bad intercept geometry or approaching the glideslope from above. Check these items in order:

• The correct runway's ILS frequency is active rather than sitting in standby.
• The identifier matches the intended localiser.
• The CDI or PFD source says VLOC, LOC or NAV rather than GPS.
• The aircraft is approaching the front course, not the reciprocal or back course.
• The intercept angle is shallow enough for the autopilot to capture.
• The aircraft is below the glideslope at the published intercept altitude.
• APP/APR is armed and the flight-mode annunciator shows LOC and GS armed.
• The avionics, NAV receiver and relevant electrical systems are powered.
• The chart and X-Plane navigation data agree; changed runway identifiers or mismatched scenery can otherwise point you at the wrong facility.

If the glideslope never appears, confirm that the procedure is a full ILS rather than a localiser-only approach. A back-course localiser normally provides no usable glideslope.

Does APP mode land the aircraft automatically?

APP mode does not automatically mean autoland. In most X-Plane aircraft it captures and tracks the localiser and glideslope, leaving the pilot to control speed, monitor the approach, disconnect the autopilot and land.

Autoland is available only in suitably modelled aircraft and requires an aircraft-specific setup, often involving multiple autopilot channels, valid radio-altimeter data and the correct landing configuration. Do not assume that seeing LOC and GS means the aeroplane will flare or control the rollout.

You can also hand-fly the entire ILS: select VLOC, centre the localiser with small heading corrections, then use pitch and power to keep the glideslope centred while maintaining approach speed. The radio setup, intercept restrictions and decision at minimums remain the same.