Why is FS2004 autopilot not working, and how do I fix it?

In Microsoft Flight Simulator 2004 (FS9), an autopilot that will not engage or steer usually lacks electrical power, has no active guidance mode, is reading the wrong NAV/GPS source, or is being cancelled by a control assignment. Test HDG and ALT in the stock Boeing 737-400, then isolate navigation, input and add-on faults.

How do I fix the FS2004 autopilot?

The fastest repair is to test one function at a time in stable flight, rather than diagnosing the whole system during an approach.

1. Return to normal flight: leave pause and slew modes, select the normal simulation rate and climb to a safe altitude clear of terrain.
2. Use a default aircraft: load the stock Boeing 737-400 with its original panel. This separates an FS2004-wide problem from an add-on fault.
3. Check electrical power: make sure the battery, generators, avionics and any aircraft-specific flight-control power are on. A blank autopilot display usually indicates power or gauge trouble.
4. Stabilise and trim: establish moderate airspeed and approximately straight-and-level flight. Trim away heavy control pressure before engaging the system.
5. Set obvious targets: place the heading bug about 10 degrees away from the present heading and set the altitude selector as close as possible to the present altitude.
6. Engage the system once: use the panel’s autopilot master or the default Z key, then select HDG and ALT. Confirm that the corresponding panel lights or annunciations remain visible.
7. Check the response: the aircraft should turn towards the heading bug and hold altitude. If that works, add NAV, VS or APP one at a time until the failure returns.

If you searched non funziona, не включает or no working, use the same diagnostic split: no light or annunciation points to power, assignment or gauge trouble; a light that remains on while the aircraft flies incorrectly points to the selected mode, target or navigation source.

What am I doing wrong if the autopilot is on now but it’s not working?

An illuminated autopilot master does not tell FS2004 which heading, altitude or course to follow; at least one appropriate guidance mode and a valid target are still required.

• HDG turns towards the heading bug, not the COURSE selector.
• NAV tracks the selected radio or GPS navigation source.
• ALT holds or captures altitude according to the panel’s logic. Changing the altitude window alone may not start a climb or descent.
• VS commands a selected vertical speed where fitted, but the pilot must monitor power and airspeed.
• APP arms localiser and glideslope capture for a correctly configured ILS.
• FD displays flight-director commands but does not fly the aircraft unless the autopilot is also engaged.
• A/T controls thrust or speed where available; it is separate from the autopilot master.

The default Z command is a toggle, not a dedicated on command. Pressing it when the autopilot is already engaged switches it off again. A mistake we see constantly is repeatedly pressing Z because the aircraft has not yet begun to turn, when the real omission is HDG or NAV mode.

How do I set and test a flight course in the FS2004 737-400?

A simple heading-and-altitude test in the stock 737-400 confirms that the basic autopilot works before you introduce a VOR, GPS route or ILS.

1. Fly level: stabilise the 737-400 at a safe altitude and trim it.
2. Set the heading bug: move it slightly left or right of the present heading.
3. Set altitude: place the selected altitude near the aircraft’s present altitude.
4. Engage AP, HDG and ALT: release control pressure and watch for a smooth turn followed by heading and altitude capture.
5. Change one target: move the heading bug again. A second correct turn confirms that HDG control is working.

In this context, heading and course are not interchangeable. The heading bug commands HDG mode; the COURSE or OBS control sets a VOR radial or an ILS front course. Turning the COURSE selector while HDG mode is active will not make the aircraft turn.

For a climb or descent, set the new altitude and use an appropriate vertical mode such as VS where the panel provides it. Select a sensible rate and adjust the throttle to protect airspeed; an FS2004 autopilot is not automatically an autothrottle.

It’s not turning back on: why does the autopilot disconnect immediately?

An autopilot that switches off at once is usually receiving another toggle or disconnect command, losing electrical power, or reacting to trim, controller input or aircraft-specific protection logic.

• Press the master command once and wait for the annunciation. A stuck key or button can send repeated on-off commands too quickly to notice.
• Check for duplicate autopilot-master or disconnect assignments across the keyboard, joystick, yoke and throttle quadrant.
• Release electric-trim switches and confirm that no trim button is held down.
• Temporarily disconnect extra controllers. A noisy axis may fight the default autopilot, while some custom systems disconnect when they detect manual input.
• Recover from stalls, extreme attitudes and excessive speed before trying again.
• Verify that electrical and avionics power remain available after engine or generator changes.

Our guide to checking FS2004 keyboard and joystick assignments explains how to find conflicting controls. If the system works with controllers unplugged, reconnect them individually and calibrate the device that brings the problem back.

Why does NAV or APP mode not follow the course?

NAV and APP modes can remain armed without capturing anything when FS2004 is using the wrong source, the radio is not tuned correctly or the aircraft is poorly positioned for interception.

Why does NAV mode not follow the GPS flight plan?

FS2004 NAV mode follows the source selected by the panel’s NAV/GPS switch, not simply the route displayed in the GPS window.

• For GPS tracking: load the flight plan, confirm that the intended leg is active, select GPS on the NAV/GPS switch and then engage NAV. Approach the active course at a reasonable intercept angle.
• For VOR tracking: select NAV, tune the correct station in the active NAV1 frequency and set the required course. Confirm that the signal is being received before expecting capture.

An add-on aircraft with an FMC or custom navigation gauge may bypass the default NAV/GPS logic. In that case, use the aircraft’s own lateral-navigation engagement sequence rather than assuming the stock 737 procedure applies.

Why will APP mode not capture the ILS?

APP captures an ILS only when NAV1 is tuned to the correct localiser, the radio source is selected and the aircraft intercepts the localiser and glideslope with suitable geometry.

1. Tune NAV1: enter the runway’s ILS frequency in the active radio position and verify the station identification where possible.
2. Select NAV: move the NAV/GPS selector away from GPS and onto the radio-navigation source.
3. Set the front course: use the published runway course on the COURSE or OBS selector where the panel provides one.
4. Intercept from below: approach the localiser at a modest angle while below the glideslope. Joining from above is a common reason for no vertical capture.
5. Arm APP: watch the annunciations to distinguish an armed mode from one that has actually captured.

Use our detailed FS2004 ILS capture checks when the localiser or glideslope still refuses to engage. APP mode does not guarantee a complete automatic landing: speed, flaps, gear and stabilisation remain the pilot’s responsibility, and many aircraft require a manual flare and rollout. Our explanation of what the FS2004 autopilot can and cannot do during landing covers that sequence and its limitations.

How can I tell whether an add-on panel is faulty?

If HDG and ALT work in the stock Boeing 737-400 but fail in only one downloaded aircraft, FS2004’s core autopilot is working and the fault lies with that aircraft, its panel or its operating procedure.

• A blank display or invisible buttons suggests a missing or incompatible gauge.
• Buttons that animate but never change a mode may indicate an incomplete custom-gauge installation.
• An aircraft may require extra hydraulic, electrical, flight-director or autopilot switches that the default 737 does not model.
• Missing .gau files, .cab gauge archives or supporting modules can leave only part of a panel functional.

Reinstall the aircraft from its original archive and preserve the supplied aircraft, panel and gauge folder structure. Do not overwrite default gauges casually. For blank or unresponsive custom controls, follow our FS2004 add-on gauge installation and dependency checks.

If every default aircraft fails the same stock 737 HDG-and-ALT test, return to electrical power and control assignments. That global result does not point to scenery, a flight plan or one downloaded aircraft, so reinstalling unrelated add-ons will not fix it.