Fix FS2004 altitude hold that will not engage, captures the wrong altitude, overshoots, disconnects or oscillates, with control and add-on checks.
Altitude hold in FS2004 usually fails because the autopilot master is off, the aircraft remains in vertical-speed or approach mode, the selected altitude was not captured, or joystick or trim input is overriding the autopilot. Stabilise and trim the aircraft first, engage the correct vertical mode, then check control conflicts or an add-on panel fault.
How do I engage altitude hold correctly in FS2004?
In Microsoft Flight Simulator 2004, altitude hold must be used with the autopilot master and the panel's intended altitude-capture logic. Switching on the flight director alone only displays guidance; it does not fly the aircraft.
FS2004 panels generally use one of two methods. A simple hold-now system captures the aircraft's present altitude when ALT is pressed. A preselect system treats the altitude window as a target, uses vertical-speed or pitch mode to climb or descend, and then captures that target. Merely turning the altitude selector does not necessarily activate anything. Our explanation of altitude capture, altitude hold and vertical modes covers the underlying autopilot behaviour.
- Establish a stable flight condition. Use normal cruise speed, return simulation rate to 1x and avoid testing in strong turbulence.
- Trim the aircraft. It should fly close to the intended attitude without heavy control pressure before the autopilot is engaged.
- Engage the autopilot master. Confirm the panel annunciator shows that the autopilot, rather than only the flight director, is active.
- Select the vertical mode. For a hold-now system, press
ALTupon reaching the desired altitude. For a preselect system, set the target and command a sensible climb or descent through vertical-speed or pitch mode. - Verify capture. Watch the annunciator and vertical speed as the aircraft reaches the target. Manage power and airspeed yourself unless that aircraft has an active autothrottle.
Do not keep moving the yoke or manually chasing elevator trim after engagement. Some FS2004 aircraft tolerate control input, while others override or disconnect the autopilot.
Why does it hold the current altitude instead of the selected altitude?
The altitude selector may be a preselection display rather than a direct climb command. On panels using hold-now logic, pressing ALT captures the altitude being flown at that moment, regardless of the number previously set in the window.
To reach another level, disengage altitude hold, select a climb or descent mode, set a moderate vertical speed and then arm or re-engage altitude capture as the panel requires. Some add-on aircraft change altitude while ALT remains engaged; others require a fresh mode selection, so their supplied panel instructions take precedence over stock FS2004 behaviour.
| Symptom | Likely reason | What to do |
|---|---|---|
ALT will not remain active | Autopilot master is off, electrical power is unavailable or a control repeatedly sends a disconnect command | Check the master annunciator, avionics power and control assignments |
Aircraft holds the altitude where ALT was pressed | The panel uses hold-now logic | Climb or descend first, or use the panel's preselect and vertical-speed sequence |
| Aircraft passes through the selected altitude | Capture was never armed, the climb rate is excessive or a custom gauge failed | Reduce vertical speed, reselect the mode and test the same procedure in a stock aircraft |
| Altitude changes after ILS capture | Approach mode has captured the glideslope | This descent is intentional; glideslope guidance replaces altitude hold |
| Altitude is steady but disagrees with ATC | The altimeter pressure setting is wrong | Set the correct barometric pressure; the hold mode itself may be working normally |
Why does altitude hold disconnect or oscillate?
Repeated disconnections and pitch oscillations normally indicate unwanted control input, an unsuitable flight condition or an aircraft configuration problem rather than the altitude selector itself.
- Duplicate assignments: Check FS2004's control assignments for autopilot disconnect, altitude hold, elevator trim and pitch controls. If FSUIPC is installed, avoid assigning the same switch or axis in both places.
- Noisy hardware: A spiking pitch axis, trim wheel or button can fight the autopilot. Increase the appropriate null zone, recalibrate the controller and temporarily unplug suspect hardware.
- Manual trim input: Trim the aeroplane before engagement, then let the autopilot command pitch. Continuous manual trimming can produce a cycle of climbing and descending.
- Insufficient airspeed or power: An autopilot cannot maintain altitude after the aircraft reaches a stall, pitch or trim limit. Reduce the commanded vertical speed and establish a safe speed.
- Time acceleration: High simulation rates can make older FS2004 autopilot and gauge logic unstable. Diagnose the problem at 1x.
- Loading or flight-model errors: An extreme centre of gravity or poorly configured add-on can leave insufficient pitch authority.
If the controller also behaves incorrectly outside the autopilot, work through these joystick detection, calibration and assignment checks. Menu wording varies between simulator generations, but the duplicate-binding and axis-noise checks also apply to FS2004.
How can I tell whether an FS2004 add-on is at fault?
A clean test with an unmodified stock aircraft separates a simulator-wide control problem from an add-on-specific autopilot fault.
- Start a new flight rather than loading a saved situation, and choose a stock aircraft with its original panel.
- Use clear weather and 1x simulation rate, then stabilise at a safe altitude and normal cruise speed.
- Operate the panel with the mouse instead of keyboard shortcuts or controller buttons. Engage the master, then test altitude hold.
- Compare the result. If the stock aircraft works, the add-on's panel, gauges, configuration or installation is responsible. If it also fails, inspect assignments, hardware inputs, failures and simulator configuration.
For an add-on fault, confirm that the aircraft is the FS2004 version and that all supplied gauges and modules are installed. Restore its original panel.cfg if panels or gauges have been mixed between aircraft. The [autopilot] section of aircraft.cfg must also make an autopilot available, but copying an entire section from an unrelated aircraft can create worse pitch and bank behaviour.
If altitude hold fails in every stock aircraft, disable controller inputs temporarily and repeat the mouse-only test. As a final diagnostic, back up FS2004's configuration before allowing the simulator to generate a fresh one; this resets customised settings, so it should follow the simpler control and aircraft checks rather than replace them.