Fix a Microsoft Flight Simulator controller or throttle not working on Xbox by checking compatibility, profiles, axis bindings and input conflicts.
On Xbox, a Microsoft Flight Simulator controller or throttle fails because the console does not support that peripheral, the device was connected after the sim launched, the wrong per-device control profile is active, or another binding is overriding it. Confirm Xbox compatibility, restart fully, load a default profile, then test one axis at a time.
Is the controller or throttle compatible with Xbox?
A standard Xbox controller should work, but a USB throttle, joystick or yoke must explicitly support Xbox. Being compatible with Windows or having a USB plug is not enough because the console cannot install the Windows drivers used by PC-only flight controls.
Some peripherals must connect through a supported base or hub rather than directly to the console. Check the manufacturer's stated Xbox support and required connection method; our explanation of which flight controls Xbox can recognise covers this distinction in more detail.
If Microsoft Flight Simulator is being streamed rather than installed locally on Xbox Series X|S, test with a normal gamepad first. Cloud sessions can expose fewer peripheral types than a locally installed copy.
How do you fix controller detection on Xbox?
A full quit followed by a clean default-profile test resolves most detection and binding failures.
- Check the controller outside the simulator. Confirm that it can operate the Xbox dashboard. If it cannot, reconnect or pair it, replace or recharge its batteries, and test a different USB data cable where applicable.
- Quit Microsoft Flight Simulator completely. Highlight its tile, open the Xbox menu for the game and select Quit. Do not merely return to the dashboard or resume a suspended session.
- Disconnect unnecessary peripherals. Leave only the Xbox controller or one supported flight-control device connected. This removes duplicate inputs from the test.
- Reconnect before launching. Attach the throttle or controller directly to the console where possible, then start the simulator. Avoid an unpowered USB hub while diagnosing the fault.
- Select the correct device tab. Open the simulator's Controls or Controls Options screen and select the controller, throttle or joystick itself. Each device has its own bindings; changing the gamepad profile does not configure a separate throttle.
- Load a default profile. Restore the affected peripheral's default preset or create a clean profile. Do not delete Xbox cloud-saved data merely to reset one device.
- Test a simple aircraft. Use a basic single-engine aircraft on a runway with assistance, autopilot and automatic throttle functions disabled. If the controls work there, the original aircraft or its selected profile is the likely cause.
MSFS 2020 and MSFS 2024 arrange their control menus differently, but the diagnosis is the same. For the newer simulator, follow our step-by-step Xbox controller configuration checks, including dead zones and devices connected after launch.
Why is the throttle detected but not moving?
If the throttle appears in the controls menu and its input is detected, the fault is normally an incorrect axis assignment, an empty profile or a conflicting binding.
- Use an axis command for a lever. A physical throttle should be assigned to a continuous throttle axis, not only to throttle-increase and throttle-decrease commands intended for buttons.
- Choose the correct engine assignment. A general throttle axis can control all engines, while numbered throttle axes affect individual engines. On a twin-engine aircraft, assigning only the first engine leaves the second unchanged.
- Check direction and range. If the cockpit lever moves backwards or reaches only part of its travel, correct the axis inversion and sensitivity range. Excessive dead zone can make a working lever appear unresponsive.
- Remove duplicate throttle bindings. A gamepad button, another lever or a noisy axis may continually override the intended input. Unplug the second device or clear its conflicting assignment.
- Disable automatic control temporarily. Autothrottle, AI piloting and some assistance settings can command the aircraft independently of the hardware. Airliner throttle detents can also make lever movement look different from a simple proportional axis.
Use the control screen's input-detection or search-by-input function where available, and change the filter from assigned controls to all controls if the throttle command is hidden. Compare gamepad behaviour with the expected default Xbox control layout before remapping every button.
How can you identify whether the fault is hardware or a profile?
The point at which the input disappears tells you where the problem lies.
| What happens | Likely cause | Next check |
|---|---|---|
| Controller cannot operate the Xbox dashboard | Pairing, battery, cable or hardware fault | Reconnect it and test another cable or controller |
| Throttle never appears in the simulator | Unsupported Xbox hardware, wrong connection method or launch-time detection failure | Confirm Xbox compatibility and relaunch with it connected |
| Device appears, but no input is detected | Device firmware, connection or hardware fault | Connect directly and test its buttons and axes individually |
| Input is detected, but the aircraft does not react | Wrong command, empty profile or duplicate binding | Load defaults and map one axis only |
| Controls work in one aircraft but not another | Aircraft-specific profile or cockpit automation | Compare the active profile and disable automatic systems |
A mistake we see constantly is assuming one saved profile covers every connected peripheral. It does not: controller, joystick and throttle assignments are managed separately, as explained in our guide to how MSFS 2024 stores profiles for individual devices.