Fix FS2004 autopilot problems by checking modes, trim, NAV/GPS source, ILS setup, controller mappings and add-on panel faults.
FS2004’s autopilot usually appears broken because only the master switch is on, the wrong lateral or vertical mode is selected, or NAV is reading the wrong source. Stabilise and trim the aircraft, engage the master, select a mode such as HDG or ALT, then verify its target and radio/GPS source.
How do I fix the FS2004 autopilot?
The fastest way to fix an FS2004 autopilot is to establish a simple, stable test rather than troubleshooting it during an approach.
- Return to normal flight: leave pause or slew mode, use the normal simulation rate and establish a safe altitude and moderate airspeed.
- Stabilise and trim: fly approximately straight and level, then trim away heavy control pressure. An autopilot may struggle, oscillate or run out of trim authority if engaged while the aircraft is badly out of balance.
- Check electrical power: switch on the battery, avionics and any aircraft-specific autopilot or flight-control power. Custom panels may model additional switches that the default aircraft do not.
- Engage the correct controls: switch on the autopilot master, then choose one lateral mode such as HDG and one vertical mode such as ALT or VS. Confirm that the expected mode is shown on the panel or annunciator.
- Set the targets: move the heading bug to the required heading and set the desired altitude or vertical speed. Selecting a mode without setting its target is a mistake we see constantly.
- Check for unwanted commands: centre the joystick or yoke, release the trim control and make sure no button is repeatedly sending an autopilot-disconnect command.
- Test a default aircraft: try the stock Boeing 737-400 with its original panel. If basic HDG and ALT modes work there, the simulator itself is functioning and the fault belongs to the other aircraft or panel.
| Symptom | Most likely cause | What to check |
|---|---|---|
| Autopilot will not remain engaged | Disconnect assignment, controller input, trim or custom protection logic | Buttons, axes, power and stable flight conditions |
| Master is on but the aircraft does not turn | No lateral mode selected | Engage HDG or NAV and set the heading bug or navigation source |
| NAV follows the wrong course | Wrong NAV/GPS source or inactive route leg | NAV/GPS selector, NAV1 tuning and active GPS leg |
| Altitude mode will not climb or descend | Incorrect altitude, VS, trim or power setting | Selected altitude, vertical mode, throttle and trim |
| Aircraft porpoises or oscillates | Excessive speed, poor trim, high simulation rate or add-on flight dynamics | Normal rate, stable speed and correct aircraft installation |
What does the FS2004 autopilot master actually do?
The autopilot master gives the system control authority, but it does not guarantee that the aircraft will follow a heading, altitude or flight plan. The default Z command toggles the master; the required guidance modes must still be selected.
- HDG turns towards the heading bug.
- NAV tracks the selected VOR, localiser or GPS source.
- ALT controls altitude according to the panel’s selected-altitude logic.
- VS commands a selected climb or descent rate where fitted.
- APP arms localiser and glideslope capture for a suitable ILS.
A flight director is not the autopilot. Command bars may show the required pitch and bank while leaving you to fly them manually. Likewise, an autopilot is not necessarily an autothrottle: many FS2004 aircraft still require manual power adjustments. If the keyboard commands do not respond as expected, compare the assignments with our reference for FS2004 autopilot and flight-control keys.
Why does NAV mode not follow the GPS flight plan?
NAV mode follows whichever navigation source FS2004 has selected, so it can track a VOR instead of the GPS route even when the route is visible on the map.
For GPS tracking, load or activate the flight plan, confirm that the required leg is active, move the panel’s NAV/GPS selector to GPS and engage NAV mode. Position the aircraft so it can intercept the active course without an extreme turn. Our explanation of coupling the FS2004 GPS to the autopilot covers inactive legs and source-selection errors in detail.
For VOR navigation, set the selector to NAV, tune the correct frequency and set the required course. Add-on aircraft with an FMC or custom navigation gauge may not use the default GPS/NAV logic, so follow that panel’s own mode sequence.
Why will APP mode not capture the ILS?
APP mode will capture only when the ILS is tuned correctly and the aircraft approaches the localiser and glideslope with sensible geometry.
- Tune NAV1: enter the runway’s correct ILS frequency and verify the station identification where possible.
- Select NAV: move the GPS/NAV selector away from GPS and back to the radio-navigation source.
- Set the front course: enter the runway course on the course or OBS control where the panel provides one.
- Intercept correctly: approach the localiser at a modest angle and from below the glideslope. Joining from above is a common reason for no glideslope capture.
- Arm APP: arm approach mode before reaching the localiser and watch the annunciations to distinguish armed modes from captured modes.
The full setup is covered in our FS2004 ILS capture troubleshooting procedure. APP mode does not make every approach an autoland; many FS2004 aircraft still require manual flare, touchdown and rollout.
Why does the autopilot disconnect immediately?
An immediate disconnect usually points to a repeated command, active control input, electrical interruption or aircraft-specific protection logic rather than a navigation error.
- Check whether
Zor an autopilot-disconnect command is assigned to more than one controller. - Temporarily unplug extra controllers or increase the dead zone on a noisy pitch or roll axis.
- Release electric-trim switches and make sure no key or button is stuck.
- Reduce speed, recover from any stall or steep attitude, stabilise the aircraft and try again.
- Verify that the battery, avionics and relevant panel switches remain on.
Some custom gauges disconnect when they detect manual control pressure or an unsafe condition; the default autopilot may instead fight the input. For persistent drop-outs, use our broader checklist for autopilot disconnects and controller conflicts.
How can I tell if an add-on panel is faulty?
If the autopilot works in a default FS2004 aircraft but not in one add-on, the add-on’s panel, gauges, configuration or operating procedure is at fault.
Check whether the aircraft actually includes an autopilot and whether it uses custom engagement requirements. A blank display, missing buttons or controls that never respond can indicate an absent or incompatible gauge. Reinstall the aircraft from its original archive while preserving the supplied folder structure, and do not overwrite default gauges casually.
If the fault affects every default aircraft, restore the control assignments to their defaults and retest with controllers disconnected. That separates a global input or configuration problem from an aircraft-specific failure without disturbing scenery, saved flights or unrelated add-ons.