Learn how to use FSX autopilot on final, capture the ILS, avoid glideslope errors and understand why default aircraft do not fully autoland.
In FSX and FSX: Steam Edition, intercept the runway ILS from below, tune NAV1, set the inbound course, select NAV rather than GPS, and arm APP/APR. The autopilot can capture the localiser and glideslope, but most default aircraft do not flare, retard thrust or steer after touchdown; disconnect and land manually.
Can the default FSX aircraft perform a full autoland?
The standard FSX airliners provide ILS approach tracking, not a dependable full autoland. Approach mode can keep the aircraft on the localiser and glideslope, but it does not make the entire landing automatic.
| Function | Default FSX APP/APR mode | True autoland system |
|---|---|---|
| Localiser capture | Yes | Yes |
| Glideslope capture | Yes | Yes |
| Automatic flare | No dependable flare | Yes, when modelled and correctly armed |
| Automatic thrust retard | Generally no | May be included |
| Runway rollout guidance | No reliable centreline tracking | May be included |
An illuminated APP button only confirms that approach mode has been selected or armed. It does not prove the aircraft can flare or roll out. An ILS marked CAT II or CAT III also does not give a stock FSX aircraft autoland capability.
How do I set up FSX autopilot for final approach?
A reliable coupled approach begins before the aircraft reaches the localiser. For a broader explanation of the instruments and capture sequence, use our complete FSX ILS procedure from NAV1 setup to landing.
- Choose an ILS-equipped runway. Not every runway, or both ends of a runway, has an ILS. Check the frequency and inbound course using the FSX map, GPS or airport information.
- Tune NAV1. Enter the ILS frequency into NAV1 and make it active rather than leaving it in standby. Set the published inbound course on the course selector. Use the identification audio where the panel supports it.
- Select NAV instead of GPS. On aircraft with a GPS/NAV selector, move it to NAV. Leaving it in GPS is one of the most common reasons APP mode fails to capture the ILS.
- Establish a sensible intercept. Use heading mode to approach the localiser at roughly 20–30 degrees. Be level below the glideslope and far enough from the runway to capture both beams without aggressive corrections.
- Arm APP or APR. Keep the autopilot engaged and select the panel’s approach mode before crossing the localiser. If the timing is unclear, see our guidance on arming approach mode at the correct point.
- Confirm localiser capture. The aircraft should turn onto the runway centreline as the horizontal deviation closes. Check the needles and mode annunciation where available; the button light alone is not enough.
- Confirm glideslope capture. The vertical mode should capture as the glideslope descends towards the centre. Altitude hold should release and the aircraft should begin descending. Do not reselect ALT after capture.
- Configure for landing. Extend the gear and flaps on schedule, set the correct approach speed and monitor pitch, power and descent rate. APP mode does not control airspeed; autothrottle must be armed separately where fitted.
- Disconnect before the flare. Once visual and stable, disconnect the autopilot with enough height to settle into manual flight. Reduce thrust, flare and control the rollout yourself.
Make configuration changes early. Selecting large flap increments or lowering the gear close to the runway can upset a marginal capture, especially when the aircraft is fast or approaching from a steep angle.
Why won’t APP mode capture the localiser or glideslope?
Most FSX approach-mode failures come from incorrect navigation selection or poor interception geometry rather than a broken autopilot.
- GPS is still selected: switch the GPS/NAV selector to NAV for an ILS approach.
- The frequency is wrong or in standby: verify the scenery’s ILS frequency and ensure it is active in NAV1, not NAV2.
- The runway has no ILS: a visual, GPS or localiser-only approach cannot provide a normal glideslope capture.
- The aircraft is above the glideslope: FSX autopilots capture most reliably from below. Reposition rather than forcing a steep descent from above.
- The intercept is too steep or too close: use a shallow intercept with enough distance for the autopilot to settle.
- The navigation data does not match: older FSX scenery may use a different frequency from a newer real-world chart. Check the frequency shown inside FSX.
- The add-on uses custom logic: complex aircraft may require both navigation radios, specific autopilot channels or panel-specific arming steps.
If the localiser works but the aircraft remains level or passes through the vertical beam, follow our focused glideslope-capture troubleshooting checklist.
When should I disconnect the autopilot on final?
With a default FSX aircraft, disconnect while visual and high enough to stabilise the aircraft manually before the flare. For practice, 500–1,000 feet above ground gives a comfortable transition, but that is a technique rather than a universal minimum.
If simulating a published procedure, follow its decision altitude and the aircraft’s minimum autopilot-use height. At decision altitude, continue only with the required visual reference; otherwise go around. Expect a small trim or control-pressure change when disconnecting, and remember that an armed autothrottle may remain active until separately disengaged.
What is required for a genuine FSX autoland?
A genuine autoland requires an aircraft, panel or gauge package that explicitly models flare and usually rollout. Advanced implementations may also require multiple autopilot channels, both NAV receivers, autothrottle and specific mode indications such as FLARE or ROLLOUT.
Follow that aircraft’s documentation exactly because the arming sequence is not standard across FSX add-ons. For aircraft designed to accept panel modifications, our CAT II/III autoland gauge package with flare and rollout functions is an option; check its installation and compatibility notes before changing any panel files.