Find why your flight simulator throttle keeps creeping back and stop axis drift, duplicate bindings, autothrottle overrides or a loose lever.
In general flight simulators, a throttle usually creeps back because its axis is noisy, another controller is sending a second command, autothrottle or an assistance feature has control, or the physical lever cannot hold position. Check the hardware input, remove duplicate bindings, add a small dead zone and disable automatic throttle control.
Is the throttle hardware or the simulator causing it?
Comparing the physical lever, raw axis indicator and cockpit throttle identifies where the unwanted movement begins. Open the simulator’s controls or sensitivity page and watch the throttle input without touching anything.
| What moves? | Most likely cause | What to do |
|---|---|---|
| The physical lever slides towards idle | Insufficient friction, loose tension or cable pull | Adjust the unit’s intended tension control and secure it on a level surface |
| The lever stays still, but the raw input jitters | Sensor noise, poor calibration or an unstable USB connection | Calibrate it, apply a small dead zone and test another direct USB port |
| The raw input is steady, but the cockpit lever moves | Autothrottle, AI assistance or aircraft-specific control logic | Disengage automatic throttle control and test a simple aircraft |
| The cockpit throttle jumps between two positions | Duplicate or conflicting assignments | Remove throttle commands from every controller except the one being tested |
| A thumbstick returns to its centre position | A spring-centred control is assigned as an absolute throttle axis | Use throttle increase/decrease buttons or a non-centring slider |
On a PC, check the axis in the Windows USB game-controller panel as well as inside the simulator. Movement in both places points to the hardware or calibration; movement only inside the simulator points to bindings, automation or an add-on. Our PC joystick calibration and duplicate-axis checklist covers that distinction in more detail.
How do you stop a throttle axis drifting backwards?
- Use a simple test aircraft. Load a basic aircraft without autothrottle and leave it parked. This removes complex aircraft systems from the test.
- Turn off automatic control. Disconnect autothrottle and switch off any AI piloting, assisted throttle, copilot or automatic take-off assistance. Overriding an active autothrottle with the lever may not disconnect it.
- Inspect every connected device. Search the control assignments for “throttle” on the yoke, pedals, joystick, gamepad, keyboard and any virtual controller. A forgotten gamepad axis is a common source of slow movement.
- Keep one analogue assignment. Bind the lever to a throttle axis, not simultaneously to throttle increase, decrease or an engine-specific axis. On a twin-engine aircraft, do not overlap a general throttle axis with separate engine-one and engine-two assignments.
- Calibrate the full travel. Move the lever smoothly from idle to maximum during calibration. Add only enough dead zone to stop visible jitter; a large dead zone hides useful travel and does not repair a worn sensor.
- Check the USB connection. Test a direct port rather than an unpowered hub, and temporarily remove unnecessary controllers. If the raw signal still falls in the operating-system controller panel, the problem is outside the simulator.
- Save a clean control profile. Create a dedicated profile after the throttle remains steady. This prevents an aircraft-specific or imported preset from restoring conflicting commands.
Microsoft Flight Simulator users should assign the lever as an analogue axis and remove competing digital commands; see our MSFS throttle-axis and controller mapping steps. FSX handles controls differently, so use the FSX controller, calibration and virtual-device checks if the problem occurs there.
Why does the throttle creep back only with autopilot on?
Autopilot and autothrottle are separate systems, and it is normally the autothrottle that changes engine power. In aircraft with motorised or animated throttle levers, the cockpit levers may move as the system maintains speed or thrust; that is expected behaviour rather than axis drift.
Aircraft model the system differently. Boeing-style autothrottle commonly moves the virtual levers, while Airbus-style autothrust generally changes commanded thrust with the levers left in their selected detent. Assistance features can also control power without behaving like the aircraft’s real autothrottle.
To take manual control, disconnect autothrottle using the aircraft’s normal control and confirm that its armed mode is no longer active. Match your physical lever approximately to the displayed power before moving it, otherwise the virtual throttle may jump when the simulator receives the first new axis position.
What if the physical throttle lever slides back?
A standard non-motorised USB throttle cannot be pulled backwards by the simulator. If the physical lever itself moves, gravity, weak friction, cable tension or a worn mechanism is responsible; motorised throttle units are the exception.
- Increase the built-in tension or friction adjustment if the manufacturer provides one.
- Mount the quadrant level and prevent its USB cable from tugging on the lever housing.
- Do not lubricate the mechanism or spray cleaner into the sensor unless the device’s approved instructions specifically require it.
- If the lever will not hold position after adjustment, use the warranty or replace the worn component rather than masking the movement with software settings.
Why does it happen in only one aircraft?
A problem confined to one aircraft usually comes from its autothrottle logic, detent calibration or custom control system. High-fidelity aircraft may require idle, climb, maximum continuous thrust and take-off detents to be calibrated inside the aircraft’s own tablet or cockpit configuration panel.
Test the same hardware profile in a basic general-aviation aircraft. If the throttle stays fixed there, leave the global calibration alone and inspect the affected aircraft’s automation, detent settings and engine-specific bindings instead.