Fix autopilot altitude oscillation by checking trim, speed, vertical modes, control bindings and turbulence with a practical recovery sequence.
Autopilot altitude oscillation in flight simulators usually means the aircraft is poorly trimmed, too slow, receiving conflicting control inputs, or using an unsuitable vertical mode. Stabilise speed and pitch before engagement, confirm the active mode, remove duplicate axis bindings, and reduce aggressive vertical-speed commands. Disconnect immediately if the swings grow rather than settle.
This basic fault pattern applies across Microsoft Flight Simulator, FSX, Prepar3D, X-Plane and most other general-purpose simulators. A few feet of movement in turbulence is normal; repeated climbs and descents, especially growing ones, are not.
What causes autopilot altitude hunting?
The usual cause is a mismatch between what the autopilot is commanding and what the aircraft can achieve.
- Incorrect vertical mode: The selected altitude may be armed while vertical speed, pitch or airspeed mode remains active. Read the flight mode annunciator rather than assuming a button press activated the intended mode.
- Insufficient speed or power: Altitude hold controls pitch, not engine power, unless a correctly configured autothrottle is also active. If speed decays, the autopilot raises the nose to hold altitude until the aircraft approaches a stall, drops, accelerates and repeats the cycle.
- Excessive vertical speed: A steep climb command can consume the available airspeed and cause an overshoot when altitude capture begins. The autopilot then pitches down sharply, creating another overshoot.
- Poor trim: Engaging while holding heavy control pressure gives the servos a large correction to make. Basic autopilots may have limited authority, while systems with automatic trim can still oscillate if a physical trim axis keeps overwriting their commands.
- Conflicting controls: Joystick jitter, duplicate pitch or trim assignments, keyboard commands and assistance features can fight the autopilot. Some aircraft disconnect; others continue chasing the unwanted input.
- Unstable simulation conditions: Strong turbulence, icing, an unsuitable centre of gravity, very low or uneven frame rates, and accelerated simulation rates can expose or amplify weak autopilot control.
An incorrect barometric setting can make the aircraft hold the wrong indicated altitude, but it does not normally produce rhythmic altitude hunting.
Which vertical mode should you use?
Use altitude hold for level flight, vertical speed for a controlled rate, and FLC or IAS mode when protecting airspeed matters more than maintaining a fixed climb rate.
| Mode | What it controls | When to use it |
|---|---|---|
ALT | Pitch to maintain a captured altitude | After levelling or when the system has captured the selected altitude |
VS | Pitch for a selected climb or descent rate | When sufficient power and airspeed are available for a modest, predictable rate |
FLC or IAS | Pitch to maintain selected airspeed | For climbs where power sets performance and speed protection is the priority |
VNAV | A computed vertical profile | Only after route constraints and aircraft-specific guidance have been configured correctly |
Only one pitch mode is normally active at a time, although altitude capture may be armed while VS, FLC or VNAV is active. Some panels capture the present altitude when ALT is pressed; others arm capture of the preselected altitude. MSFS 2024 users can compare these behaviours in our practical explanation of ALT, VS, FLC and VNAV operation.
How do you stop altitude oscillation?
The fastest fix is to disconnect, stabilise the aircraft manually and re-engage the autopilot under conditions it can hold without a large correction.
- Disconnect the autopilot. If the aircraft is close to a stall or the oscillations are increasing, recover normal speed and attitude before troubleshooting the panel.
- Establish steady flight. Hand-fly near the required altitude with stable airspeed, suitable power and a sensible configuration. Retract drag devices when appropriate.
- Trim out control pressure. The aircraft should remain close to its attitude when the controls are released. If trim immediately moves back or behaves erratically, use our trim-axis conflict diagnostic before trying the autopilot again.
- Select one suitable vertical mode. For level flight, capture altitude from a stable condition. During a climb, reduce an aggressive VS command or choose FLC/IAS mode and set adequate climb power.
- Check the annunciation. Confirm the mode shown as active, not merely armed. If the display still shows VS, pitch or FLC, the aircraft has not entered altitude hold.
- Release the flight controls. Avoid resting pressure on the yoke or stick. Increase small dead zones where necessary and remove duplicate pitch, trim and autopilot assignments. The MSFS keyboard and control-command reference helps identify assignments that may have been added unintentionally.
- Test under simple conditions. Return simulation rate to normal, use calm weather and disable icing for the test. If the oscillation disappears, restore each condition separately to identify the trigger.
Is some altitude movement normal?
Small, bounded corrections are normal in turbulence because the autopilot must respond to changing lift. A repeating pitch cycle that grows, produces large airspeed changes or varies by tens or hundreds of feet indicates a fault rather than ordinary correction.
Watch airspeed as closely as altitude. If every climb coincides with falling speed and every descent with acceleration, the aircraft has an energy problem: reduce the commanded climb rate, add appropriate power or use an airspeed-based climb mode.
What if only one aircraft oscillates?
If the problem affects only one aircraft, its autopilot tuning, flight model, loading or an add-on conflict is the likely cause.
Repeat the same flight with a stock aircraft, normal simulation rate, calm weather and no external control utilities. If the stock aircraft holds altitude, check the affected aircraft's weight and centre of gravity, remove conflicting modifications and verify that you are following its specific autopilot logic. Do not keep the autopilot engaged while the oscillation worsens; hand-fly until the underlying cause is resolved.