How do I assign autopilot speed to a button or panel?

Assign two momentary inputs to the simulator’s autopilot selected-speed increase and decrease commands; use an encoder for a hardware panel, not a throttle-style axis. Bind the separate speed mode or autothrottle command only if the aircraft requires it, then test that the cockpit speed window and the aircraft’s response both change.

The principle is the same in Microsoft Flight Simulator, FSX, Prepar3D and X-Plane, although command names and add-on support differ. On consoles, only platform-compatible peripherals appear as assignable devices; a generic USB button box may not be recognised.

Which autopilot speed commands should I assign?

Bind the commands that adjust selected airspeed, not throttle, aircraft pitch or the autopilot master switch.

Search the controls list for terms such as autopilot airspeed, selected speed, airspeed bug, IAS, Mach and speed hold. The labels are not standardised between simulators.

A command containing “set selected speed” may expect a numerical value from a script or hardware interface. An ordinary button cannot provide that value, so increase and decrease commands are usually the reliable choice.

How do I map a button or rotary encoder?

Create a separate device profile for the aircraft or avionics family, then assign and test the two speed-selector directions.

1. Select the correct device. Open the simulator’s control assignments and choose the joystick, button box or panel rather than the keyboard profile.
2. Find the selected-speed commands. Locate explicit increase and decrease actions. Avoid generic toggle commands because their resulting state can be unclear.
3. Assign the inputs. Use one momentary button for increase and another for decrease. For an encoder, map clockwise pulses to increase and anticlockwise pulses to decrease.
4. Add the mode control separately. If wanted, assign another button to the aircraft’s IAS, FLC, SPD or autothrottle function. A mistake we see constantly is assigning only the autopilot master and expecting it to control speed.
5. Remove conflicts. Search by input and by command to find duplicate assignments on the keyboard, throttle, joystick and panel. One physical turn should generate one logical command.
6. Test in the cockpit. Power the avionics, operate the control once and confirm that the selected-speed indication changes in the correct direction. Then engage an appropriate mode in stable flight and check the aircraft’s response.

A rotary encoder should behave as two momentary buttons, not as an absolute axis. If you are building or configuring one, our encoder and switch assignment guide explains pulse inputs, maintained switches and suitable control types.

Why doesn’t the aircraft hold the selected speed?

A moving speed target proves that the binding works, but the aircraft will not obey it unless its active flight modes can control speed.

• General aviation FLC or IAS mode: the autopilot normally changes pitch to maintain airspeed while the pilot sets power. Insufficient power may prevent a climb or produce a descent.
• Altitude or vertical-speed mode without autothrottle: selected speed may be only a reference. Throttle position determines whether the aircraft accelerates or slows down.
• Airliner with autothrottle or autothrust: the thrust system generally manages speed while the autopilot’s vertical mode manages the flight path. Both systems must be in suitable modes.
• Managed avionics: turning the selector may alter a displayed value without changing from managed to selected speed. The aircraft may require a push, pull, intervention or aircraft-specific mode command.

Microsoft Flight Simulator users can see this distinction in our explanation of how altitude and speed modes interact in MSFS 2024. Also check whether the aircraft is displaying IAS or Mach; the same hardware knob may adjust whichever unit the avionics have selected.

Why doesn’t my hardware panel work with an add-on?

If the panel works in a default aircraft but not an add-on, the add-on probably uses custom events, local variables or datarefs instead of the simulator’s generic autopilot commands.

Use the aircraft’s supported control interface or documented events rather than adding more generic bindings. For the common Logitech/Saitek unit, follow our add-on mapping steps for the Multi Panel, including its IAS selector and aircraft-specific integration.

Quick fault checks

• If the knob changes heading, altitude or vertical speed, put the physical panel’s mode selector in the IAS or speed position.
• If values jump by several increments, remove duplicate bindings and disable excessive encoder acceleration or repeated pulses.
• If the cockpit value changes but the panel display does not, input mapping is working; panel-display synchronisation is the separate fault.
• If nothing changes, confirm that the aircraft has electrical and avionics power and that the correct device profile is loaded.
• If a maintained switch repeatedly toggles a mode, replace the toggle assignment with explicit on/off commands or use a momentary button.
• If the selector works but the autopilot will not activate, use our MSFS autopilot engagement checks to identify control conflicts and aircraft-state requirements.

A successful assignment passes two separate tests: the hardware changes the selected-speed value exactly once per input, and the aircraft follows that target when the correct speed, vertical and thrust modes are active.