Learn how to use FS2004 autopilot for an ILS landing, capture the localiser and glideslope, fix common errors and disconnect safely.
In FS2004, the autopilot can fly a coupled ILS approach by capturing the localiser and glideslope, but the stock aircraft cannot complete a true automatic landing. You must tune and intercept the ILS correctly, manage speed, then disconnect the autopilot and handle the flare, touchdown and runway rollout manually.
What can the FS2004 autopilot do during landing?
FS2004's standard autopilot is an approach aid, not a complete autoland system. Its exact capabilities depend on the aircraft's panel and gauges, but the stock airliners and suitably equipped general-aviation aircraft can normally track an ILS localiser and descend on its glideslope.
| Function | What to expect in FS2004 |
|---|---|
| Heading and altitude hold | Available when the aircraft's panel includes those modes. |
| GPS route tracking | Lateral guidance only on most stock panels; it does not provide an automatic landing. |
| ILS localiser and glideslope | Normally captured through APP or APR mode. |
| Automatic speed control | Only available when the aircraft has a working autothrottle; otherwise you control the throttles. |
| Flare, touchdown and rollout | Not modelled as a complete autoland function in the stock aircraft. |
Some sophisticated add-on aircraft model automatic flare, throttle retard and rollout. In those aircraft, use the add-on's own manual because its arming sequence and limitations may differ substantially from the standard FS2004 autopilot. Our explanation of how autopilot and true autoland differ covers the wider distinction.
How do I fly an ILS approach with FS2004 autopilot?
To fly an autopilot-assisted landing in FS2004, couple the aircraft to a valid ILS and supervise every mode change. Pressing the approach button alone will not select a runway, tune the radio or position the aircraft for capture.
- Choose an ILS-equipped runway. Obtain its ILS frequency and inbound course from FS2004's own airport information, map or GPS. FS2004 uses an old navigation database, so a modern chart may show a changed frequency or course.
- Tune the ILS into NAV1. Set the published front course on the course selector or OBS where the panel provides one. Confirm that the receiver is responding to the correct localiser.
- Select NAV rather than GPS. If the panel has a
NAV/GPSswitch, move it toNAVbefore localiser capture. Leaving it in GPS mode is one of the most common reasons approach hold fails. See our guide to the FS2004 GPS and NAV/GPS switch for route-tracking details. - Establish a sensible intercept. Use heading and altitude hold to approach the localiser at roughly a 20- to 30-degree intercept angle. Be level and below the glideslope; trying to capture it from above is unreliable and procedurally wrong.
- Configure and control the speed. Extend flaps and landing gear according to the aircraft's normal procedure. The autopilot controls attitude, not necessarily airspeed, so use the throttles or a fitted autothrottle to maintain a stable approach speed.
- Arm approach mode. Select
APPorAPRas the localiser indication begins moving towards the centre. Verify localiser capture, followed by glideslope capture. Altitude hold should release when the glideslope is captured; do not reselect it during the descent. - Monitor and disconnect. Watch the mode indications, needles, speed and descent path. Disconnect before the flare, reduce power as appropriate, raise the nose gently and complete the touchdown and rollout manually.
Why won't approach hold capture the ILS?
Approach mode usually fails because the navigation source, frequency or intercept geometry is wrong. Check these causes before blaming the autopilot:
- GPS is still selected: change the panel's source switch to NAV for an ILS approach.
- The ILS is tuned in NAV2: most standard FS2004 autopilots couple to NAV1.
- The runway has no ILS: approach mode cannot create vertical guidance for a visual, VOR or localiser-only approach.
- You are above the glideslope: descend and intercept again from below rather than chasing it down.
- The intercept is too steep or too late: establish farther out with a shallow intercept angle.
- The frequency comes from newer data: use the frequency stored in FS2004 or in scenery designed for your installed airport.
- The aircraft uses custom gauges: follow its documented procedure; an add-on may require extra arming steps.
If the localiser or glideslope is not captured and stable, disconnect, fly away from the approach path and try again. Do not let the aircraft continue towards the runway while troubleshooting panel modes.
When should I disconnect the autopilot?
Disconnect before the flare and at or above any minimum autopilot-use height specified for the aircraft. FS2004 has no single correct disconnect altitude because panels, aircraft and add-ons have different limitations.
For the stock aircraft, disconnecting on a stable short final between roughly 500 and 200 feet above ground gives you time to settle into manual control. If the aircraft becomes unstable, the runway is not visible at the applicable minimum, or the guidance behaves unexpectedly, go around instead. Our manual landing technique guide explains the flare, touchdown and rollout that the standard FS2004 autopilot cannot perform.