Learn why autothrottle won’t engage in a flight simulator and check mode logic, throttle detents, axis conflicts, bindings and aircraft limits.
Autothrottle usually will not engage because the aircraft does not support it, the system is only armed rather than active, a required thrust or speed mode is missing, or a throttle-axis conflict is cancelling it. In general flight simulators, follow that aircraft’s checklist first, then eliminate noisy axes, duplicate bindings and assistance conflicts.
What usually prevents autothrottle from engaging?
An autothrottle that will not engage is usually unsupported, unpowered, armed without an active mode, or being cancelled by a controller input. The flight-mode annunciator, rather than the position of the button, tells you what the system is actually doing.
| What you see | Likely cause | What to check |
|---|---|---|
| No A/T or A/THR indication | The aircraft lacks autothrottle, system power or required configuration | Aircraft documentation, electrical power, avionics and setup |
ARM appears but thrust does not change | The system is waiting for an active thrust or speed mode | Take-off mode, selected speed, vertical mode and flight phase |
| A/THR is active but Airbus levers remain still | This is normally correct Airbus-style behaviour | Flight-mode annunciator and commanded thrust, not lever animation |
| It engages and immediately drops out | Axis jitter, manual throttle movement or a repeated disconnect command | Controller calibration, dead zones and duplicate bindings |
| It remains active but misses the selected speed | This is a speed-control problem rather than an engagement failure | Thrust limits, drag, mode selection and aircraft configuration |
Many light aircraft have an autopilot but no automatic throttle control. A G1000-equipped panel, for example, does not by itself mean that the simulated aircraft has autothrottle.
How do I make autothrottle engage?
Work through the aircraft logic first and the simulator controls second; changing bindings cannot make an unsupported or incorrectly configured system operate.
- Confirm that the aircraft has autothrottle. Look for an A/T, A/THR or automatic throttle control procedure in its checklist. Some fighters, business aircraft and add-ons use specialised systems with limited operating modes rather than airliner-style autothrottle.
- Complete the required aircraft setup. Establish electrical and avionics power, finish any necessary flight-management initialisation and select a valid speed or thrust mode. Some modes also depend on the flight director, but this varies by aircraft.
- Arm and activate the correct mode. On Boeing-style systems, moving the A/T arm switch to
ARMonly makes the system available; a mode such as SPEED, N1, THR REF, VNAV or FLCH must command it. Names and permitted combinations vary between aircraft. - Put Airbus-style thrust levers in the correct detent. For a normal take-off, FLX/MCT or TOGA initiates take-off thrust, followed by CL at the thrust-reduction point. Poorly calibrated detents are a common reason an A320 simulation never reaches the expected state; use these A320 detent and autothrust fault checks when that aircraft is involved.
- Read the flight-mode annunciator. Look for an active thrust or speed mode, not merely an illuminated switch. If only
ARMappears, the system is ready but has not been given a valid command. - Stabilise the physical throttle axes. Move all engine levers to the position expected by the aircraft, calibrate any detents and add a small dead zone if the input flickers. Split throttle levers assigned differently can leave one engine outside the required range.
- Remove competing commands. Clear duplicate throttle axes and check every joystick, throttle quadrant, gamepad and switch panel for an A/T disconnect assignment. Disable AI flying or throttle assistance while testing because either can overwrite the aircraft’s automation.
- Compare with a standard aircraft and control profile. If autothrottle works there, the simulator-wide controls are probably sound and the problem lies in the original aircraft’s procedure, configuration or systems modelling.
Fighter systems should not be treated like airliner A/T. In MSFS, the F/A-18’s aircraft-specific engagement and binding checks cover its airspeed and approach-mode behaviour.
What is the difference between armed and active autothrottle?
Armed means autothrottle is available to engage when its conditions are met; active means it is commanding engine thrust now. An armed indication with no active thrust mode is therefore not a fault by itself.
On a conventional airliner, the virtual thrust levers may move once the servo is active, although ordinary USB throttle hardware cannot physically follow them. Airbus-style autothrust normally changes commanded thrust while the cockpit levers remain fixed in a detent, so stationary levers do not prove that A/THR has failed.
Does autopilot need to be on for autothrottle to work?
No, most airliner autothrottles can operate while the pilot flies manually. The systems often share flight-director or flight-management modes, but engaging the autopilot is not a universal prerequisite.
If neither autopilot nor autothrottle will engage in Microsoft Flight Simulator, check their shared electrical, controller and flight-condition dependencies using our broader automation-engagement troubleshooting.
Why does autothrottle engage and then disconnect?
Immediate disconnection usually means the simulator detected manual throttle input, a disconnect command or a condition prohibited by that aircraft. Noisy axes are especially deceptive: the lever may look stationary while its input value changes by a small amount every frame.
- Increase the throttle-axis dead zone slightly and watch the input indicator for flicker.
- Remove duplicate A/T disconnect, throttle increase/decrease and secondary axis assignments.
- Check whether a maintained hardware switch is repeatedly sending a disconnect command.
- Confirm that the expected flight phase, flap configuration and thrust-lever detent are valid.
- Expect autothrottle to disconnect during aircraft-specific actions such as selecting idle or reverse after landing.
If an active thrust mode remains displayed but the aircraft merely accelerates or slows away from the target, the system has not disconnected. Continue with our checks for an engaged autothrottle that will not hold speed.