How do you use autopilot in a propeller aircraft?

To use autopilot in a propeller aircraft, first establish stable, trimmed flight, set the heading or navigation source, choose an appropriate lateral and vertical mode, engage the system, and confirm the active-mode annunciations. Keep managing power, propeller, mixture, rudder and engine limits unless the aircraft documentation explicitly says automation controls them.

In our Aviation & Real-World Flying coverage, the aircraft flight manual, pilot's operating handbook and autopilot supplement always take precedence. Propeller aircraft range from basic trainers with roll-only wing levellers to turboprops with integrated flight directors, yaw damping and automatic power functions. Our explanation of autopilot axes, feedback loops and flight-director modes covers the principles shared by these systems.

What should you check before using the autopilot?

There is no universal engagement sequence, so identify what the installed system can control and where it may legally be used.

• Controlled axes: a one-axis autopilot normally controls roll only; a two-axis unit controls pitch and roll. Do not expect altitude control from a roll-only system.
• Trim system: determine whether pitch trim is automatic, prompted or entirely manual. Trimming against an engaged servo can create large control forces or trigger a disconnect.
• Operating limits: check minimum engagement and disconnect heights, maximum speeds and restrictions involving icing, turbulence, approaches or equipment failures.
• Disconnect method: know the normal disconnect control, warning indication and published response to unwanted trim or servo operation before departure.
• Initial modes: some systems engage in basic roll and pitch modes; others couple to modes already selected on the flight director. Never assume what pressing the AP button will command.

Most light propeller-aircraft take-offs are hand-flown. Engage only after reaching the height permitted by the aircraft documentation and establishing a safe attitude, airspeed and climb; an autopilot should not be used to rescue an unstable departure.

How do you engage a propeller-aircraft autopilot?

The safe generic method is to stabilise and trim the aircraft, configure the guidance, engage the autopilot and verify what actually became active.

1. Complete the system checks. Confirm the required electrical and avionics power, successful self-test and absence of autopilot, trim or flight-control warnings.
2. Hand-fly into a stable condition. Establish a sensible attitude, airspeed and bank angle. Set the intended climb or cruise power and allow the aircraft to settle.
3. Trim the aircraft. Remove sustained control pressure before engagement. A badly out-of-trim aeroplane may cause an immediate disconnect, a trim warning or an abrupt pitch change.
4. Set the references. Position the heading bug, course pointer, selected altitude, target vertical speed or airspeed as required. Confirm that the navigation source is GPS, VOR or localiser as intended.
5. Select the guidance modes. Choose HDG, NAV or another lateral mode and ALT, VS, IAS/FLC or pitch mode if the system controls pitch. Follow the installed system's order of selection and engagement.
6. Engage and verify. Look for the AP indication and read the active and armed modes on the annunciator. A lit flight director, selected altitude or illuminated push-button does not by itself prove that the servos are controlling the aircraft.
7. Watch the first response. Keep your hands ready and confirm the aircraft turns, pitches or levels in the expected direction without losing airspeed. Disconnect immediately if the response is not understood.

Which autopilot mode should you use?

Choose the mode according to the variable you need controlled, then confirm it on the mode annunciator.

An armed mode is waiting for capture; it is not yet controlling the aircraft. For example, HDG may remain active while NAV is armed, and a vertical-speed climb may remain active until altitude capture occurs. Labels and annunciator colours differ between installations, so read the displayed status rather than relying on button lights.

How do NAV, GPS and GPSS differ?

NAV is a tracking mode, while GPS, VOR and localiser are navigation sources that can feed guidance to it.

A mistake we see constantly is selecting NAV while the course indicator is still receiving VOR or localiser data instead of the intended GPS route. GPSS is a more capable form of GPS roll steering on compatible equipment, but it may be selected differently from ordinary NAV. See our guide to choosing the correct NAV mode and navigation source for the practical distinction.

Does setting an altitude make the aircraft climb?

No; selecting an altitude usually sets a target, not the method used to reach it.

You must normally apply suitable power and select VS, IAS/FLC or pitch mode. Some systems arm altitude capture automatically, while others require a separate action and older units may have no altitude preselect at all. Pressing ALT during a climb often holds the aircraft's present altitude rather than taking it to the number in the selector.

Our guide to altitude hold, preselection and capture behaviour explains why an aircraft may level at the wrong height or fail to capture.

Does autopilot control the throttle and propeller RPM?

Most piston-aircraft autopilots control flight attitude rather than the engine, leaving power and propeller management to the pilot.

In a fixed-pitch aircraft, that normally means managing throttle, mixture and carburettor heat where fitted. A constant-speed propeller adds a propeller control, and some installations also require manual cowl-flap management. Turboprops have aircraft-specific power, propeller and condition-control procedures.

Automatic power control exists in some sophisticated propeller aircraft, but it must never be assumed. Even with the autopilot flying, the pilot remains responsible for airspeed, fuel selection, engine temperatures, torque or manifold pressure, propeller RPM and all published limits.

Power changes also produce pitch and yaw effects through slipstream, torque and trim changes. Set the intended power, monitor the response and follow the aircraft's trim procedure. Do not manually trim against the servos unless the installed-system instructions call for it.

Why can a propeller aircraft stall on autopilot?

A propeller aircraft can stall on autopilot because the system may keep increasing pitch to satisfy an altitude or vertical-speed command while airspeed decays.

VS mode is a common trap. If the selected climb rate exceeds the aircraft's performance at its weight, altitude or temperature, the autopilot raises the nose to preserve that rate. The same danger exists in ALT mode after a large power reduction, engine problem, downdraught or performance loss: the system may pitch up while trying to hold altitude.

IAS or FLC mode is usually the better choice for a sustained climb when available because pitch is used to protect the selected airspeed. It cannot create performance, however. With insufficient power, the climb rate will reduce and the aircraft may level or descend.

Without an airspeed-based mode, select a conservative vertical speed and monitor airspeed continuously. If stall indications appear or control is uncertain, disconnect, take manual control and follow the aircraft's published recovery procedure.

What must you monitor while autopilot is engaged?

Monitor the aircraft's flight path, mode status, airspeed, power, trim and navigation for the entire time the autopilot is engaged.

• Verify every active and armed mode after pressing a button or changing a selection.
• Confirm that turns and pitch changes occur in the expected direction.
• Watch airspeed during every climb, descent and power change.
• Check that the heading bug, course, navigation source and active route leg match the intended clearance or plan.
• Observe altitude capture rather than assuming that a selected value guarantees level-off.
• Investigate repeated trim prompts, unusual control pressure, oscillation or unexpected servo noise.
• Continue normal fuel, mixture, propeller and engine monitoring.
• Maintain outside awareness; autopilot does not provide traffic, terrain or weather avoidance unless separate approved systems do so.

Automation reduces control workload, not command responsibility. Programming an avionics unit while the aircraft quietly loses speed or tracks the wrong source defeats the reason for using the autopilot.

When should you disconnect the autopilot?

Disconnect whenever the aircraft behaves unexpectedly, approaches an operating limit or reaches a phase in which manual control is required.

Reasons include an unexplained turn or pitch change, stall or overspeed warning, unstable approach, excessive turbulence, prohibited icing conditions, trim malfunction, unreliable navigation guidance or reaching the published minimum-use height. Many propeller aircraft can fly a coupled approach but still require the pilot to control power and land manually.

For a normal disconnect, hold the controls, use the designated disconnect control, confirm the aural or visual warning and stabilise attitude, power and trim. Be prepared for control force when the servo releases. Do not fight an engaged servo for an extended period.

For suspected runaway trim or a servo fault, use the aircraft's emergency checklist. Switches, circuit breakers and isolation methods vary too much for a universal shutdown sequence to be safe.

Does autopilot work the same way in a flight simulator?

Flight simulators use the same basic modes, but engagement logic and fidelity vary by aircraft model, avionics package, assistance settings and controller configuration.

In Microsoft Flight Simulator 2020 and 2024, X-Plane and Prepar3D, the most useful first step is to practise in trimmed, straight-and-level flight. Add HDG, ALT and NAV one at a time rather than programming everything while the virtual aircraft is already unstable.

• Autopilot will not engage: check electrical and avionics power, simulated failures, trim position, the system's self-test and duplicate AP-disconnect or trim bindings.
• Aircraft turns the wrong way: inspect the heading bug, course pointer, CDI source and active lateral mode. A joystick axis sending unwanted roll input may also disconnect or oppose the system.
• NAV ignores the flight plan: confirm that the intended GPS leg is active, the navigation source is set correctly and NAV has captured rather than merely armed. Our guide to making simulator autopilot follow the active flight-plan leg covers that workflow.
• Aircraft will not climb to the selected altitude: setting the altitude alone is insufficient. Apply power, select a climb mode and verify altitude capture is armed.
• Aircraft pitches or banks repeatedly: stabilise and trim manually, then check controller noise, hardware trim wheels, assistance features and competing keyboard or controller bindings.

If the simulated aircraft departs from the intended path, disconnect first, regain stable manual flight and diagnose the mode or input conflict afterwards. Resetting buttons at random while the autopilot remains engaged usually makes the original fault harder to identify.