MSFS 2024 throttle not working, jumping or reversed? Fix detection, axis bindings, profile conflicts and calibration on PC, Xbox and PS5.
A Microsoft Flight Simulator 2024 throttle usually stops working because the wrong device profile is active, its lever is bound as buttons instead of an analogue axis, another controller has a conflicting assignment, or the axis is reversed. Select the throttle, bind one axis, clear duplicates, save the profile, and test a default aircraft.
MSFS 2024 throttle not working: fix it step by step
Work through detection, binding, conflicts and aircraft calibration in that order; changing sensitivity first often hides the real fault.
- Confirm that the hardware is detected. Open MSFS Controls and check that the throttle appears as a separate device. On PC, run
joy.cpland move the lever: the corresponding axis indicator should move smoothly. If it is absent or stationary there, reconnect the throttle directly, check its power and USB connection, and update its firmware where supported. Resolve that problem before editing bindings; our controller-detection and USB troubleshooting covers the full hardware stage. - Select the throttle device itself. MSFS stores assignments against individual devices. A mistake we see constantly is editing the yoke, joystick or gamepad profile while the separate throttle quadrant is selected elsewhere in the device list.
- Find and bind the analogue input. Use the input-search function while moving the lever, then assign that input to a throttle-axis command. Do not use Increase Throttle, Decrease Throttle or fixed-percentage commands for a physical analogue lever; those commands suit keys and gamepad buttons. See our guide to choosing axis and button-based throttle commands if the available bindings are unclear.
- Choose combined or per-engine control. Use the combined or all-engines axis when one lever should control every engine. With separate levers, use the numbered throttle axes. Do not assign the combined axis and numbered engine axes to the same lever.
- Remove conflicting assignments. Search every connected gamepad, joystick, quadrant and virtual controller for throttle commands. Clear duplicate axes and any button that repeatedly commands idle, full power or reverse thrust.
- Check direction and range. Move the lever from idle to full power while watching the response indicator. Enable Reverse Axis only when the indicator moves backwards. Begin with a nearly linear curve and a small dead zone; an extreme curve cannot repair an incorrect binding.
- Save and activate the preset. Confirm that the edited preset remains selected for the throttle device. Check it again after changing aircraft because MSFS can use another saved or aircraft-specific profile.
- Test a default runway-start aircraft. The engine will already be running, removing cold-and-dark configuration from the test. If the throttle works there, the original aircraft probably needs detent calibration, a different engine assignment or an aircraft-specific control setting.
Which throttle axis should I bind?
The correct command depends on the number of physical levers and whether the hardware has a usable reverse-thrust range. Binding names can vary slightly by device preset and localisation.
| Hardware arrangement | Binding to use | Common mistake |
|---|---|---|
| One lever for every engine | Combined or all-engines throttle axis | Also assigning numbered engine axes |
| One lever per engine | Throttle 1, Throttle 2 and further numbered axes as required | Binding both levers to the same engine |
| Ordinary idle-to-full lever | The 0–100% throttle-axis variant, when offered | Using an axis designed to include reverse travel |
| Lever with a reverse range or detents | The supported reverse-inclusive axis, or a separate reverser command and aircraft calibration | Assuming every aircraft interprets reverse travel identically |
Reverse and detent handling is not universal. Some aircraft use a separate reverse command; detent-based airliners may require idle, climb, flex and take-off positions to be calibrated in the aircraft's tablet or electronic flight bag after the basic MSFS axis works.
I’m on PS5: can I use a throttle with MSFS 2024?
Yes, but the throttle must be supported on PlayStation 5 and recognised by the PS5 version of Microsoft Flight Simulator 2024. MSFS 2024 has been available on PS5 and PS5 Pro since 8 December 2025; Microsoft Flight Simulator 2020 was never released on PlayStation.
Peripheral support is model- and platform-specific. Check that the exact throttle or HOTAS is listed as compatible with the PS5 version, then confirm that it appears as its own device in MSFS Controls. A PC-only or Xbox-only USB throttle does not become PS5-compatible simply because its plug fits, and an adapter cannot supply missing game support.
joy.cpl is a Windows utility and is PC-only. On PS5, use the in-game device list and input-response indicator instead. Select the throttle's own device tile, create or select its own MSFS profile, bind its analogue lever to the appropriate axis, and remove any duplicate throttle commands from the DualSense profile.
PS5 and Xbox console troubleshooting path
If a supported console throttle is connected but not working, use this shorter console-specific sequence.
- Reconnect and power the peripheral. Fully close MSFS, disconnect the throttle, reconnect it securely, switch on any required external power or console mode, and then restart the game.
- Update its firmware where supported. Use the manufacturer's supported update method; some console peripherals require a computer for firmware maintenance.
- Confirm platform compatibility and recognition. For PS5, the exact model must support the PlayStation version. For Xbox Series X|S, it must support Xbox. In either case, it must also appear in the MSFS Controls device list. If it does not appear, profile changes cannot fix the problem.
- Select its own MSFS profile. Do not edit only the console gamepad preset. Open the throttle device, activate or create a profile, and bind the physical lever there.
- Remove duplicate gamepad assignments. Clear throttle axes and increase/decrease commands from the gamepad when they fight the external lever. Retain only the controls you intentionally use.
- Test a default aircraft. Start on a runway with a simple default aircraft. Success there confirms that the console, game and basic throttle profile can communicate.
Why does the throttle move in Controls but not in the cockpit?
If the input meter moves but the cockpit lever does not, MSFS is receiving the hardware signal but is not applying the intended active-aircraft binding.
- Confirm that the assignment was saved on the throttle device rather than the yoke, stick or gamepad.
- Make sure the profile you edited is still active for the aircraft being tested.
- Remove simultaneous combined and per-engine assignments.
- Disconnect unused controllers temporarily; gamepad buttons, triggers and virtual devices commonly provide a second throttle command.
- Disable autothrottle and AI piloting assistance for the runway test, then restore the features you normally use after manual control works.
If the cockpit lever follows the hardware and then snaps elsewhere, look for a second controller command, active automation or aircraft-specific throttle logic. If it never moves, the active binding or profile remains the likely cause.
Why does the cockpit throttle move but engine power stay at idle?
A moving cockpit lever with no increase in engine power usually points to aircraft state, the wrong engine axis or aircraft-specific calibration rather than failed hardware.
- In a cold-and-dark aircraft, confirm that the engine is running and that fuel shut-off, mixture or condition controls are in the required positions.
- Check that the lever was not assigned to propeller pitch, mixture or another engine control.
- On a multi-engine aircraft, verify that each numbered throttle axis operates the intended engine.
- For a detent-based aircraft, calibrate the lever inside that aircraft after establishing a working MSFS axis.
If a default runway-start aircraft responds normally but one add-on does not, leave the global profile and sensitivity alone. Concentrate on that aircraft's calibration, engine state and throttle implementation.
Why is my MSFS 2024 throttle jumping, reversed or missing travel?
The response indicator reveals whether throttle jumping comes from the raw signal or from a conflicting in-game command.
| Symptom | Likely cause | What to change |
|---|---|---|
| Lever moves smoothly but backwards | Axis direction is inverted | Toggle Reverse Axis once; do not invert it in both device software and MSFS |
| Throttle jumps straight between idle and full | The lever is bound as buttons rather than an axis | Clear the button commands and bind the detected analogue axis |
| Raw input meter spikes or flickers | Connection, firmware, calibration or hardware noise | Reconnect directly, update firmware where supported and test the raw input again |
| Raw meter is smooth but the cockpit lever jumps | Duplicate binding, autothrottle or assistance | Clear the second command and disable automation for the diagnostic test |
| Idle or full power cannot be reached | Wrong axis variant or incomplete calibration | Verify the raw range, choose the correct 0–100% or reverse-inclusive axis, then make small endpoint adjustments |
A small dead zone can suppress minor endpoint flutter, but it should not be used to conceal spikes throughout the lever's travel. Our axis sensitivity, dead-zone and range guidance explains how to correct the response after the binding itself is sound.
When should I rebuild the throttle profile?
Create a clean profile when several devices control the same throttle, deleted assignments return, an imported preset contains unknown bindings, or different aircraft keep selecting incompatible presets.
Start with only one combined throttle axis and no reverse, detent or engine-specific commands. Test that basic profile before adding controls one at a time. If the existing setup is badly tangled, follow our process for clearing duplicate and ghost bindings before rebuilding a preset.
Still not working?
Use one final isolation test to determine whether the fault is in the hardware signal, the MSFS profile or the aircraft.
- Test the raw input where the platform permits. On PC, open
joy.cpland verify that the axis moves smoothly from end to end. On PS5 and Xbox, confirm that the device appears in MSFS and watch its in-game response indicator. - Disconnect every other non-essential input device. Remove extra sticks, quadrants, gamepads and virtual controllers. On a console, retain the system controller only if it is needed for menus and clear its throttle assignments.
- Create a clean throttle-only preset. Bind one physical lever to one combined throttle axis. Leave reverse, detents, sensitivity changes and additional engine axes out of this first test.
- Test a default runway-start aircraft. Move the lever through its full range and compare the input indicator, cockpit lever and engine response.
- Interpret the result. No raw movement indicates hardware, connection, firmware or platform compatibility trouble. Smooth raw movement but no cockpit response points to the profile or binding. A default aircraft that works when the original aircraft does not points to aircraft state or calibration.
- Collect precise support details. Record the platform, simulator update, aircraft and start state; the controller make and model, connection and firmware; the active profile name and exact throttle binding; whether Reverse Axis is enabled; and what happens in the raw meter, Controls response indicator, cockpit lever and engine power display. Also state whether the clean preset and default aircraft worked.