Aerosoft CRJ throttle will not stay at idle in MSFS? Fix duplicate axes, reverse detents, jitter, assistance inputs and EFB calibration.
The Aerosoft CRJ will not stay at idle in Microsoft Flight Simulator when another device or assistance feature keeps sending throttle input, the idle region is too narrow, or reverse is mapped twice. Remove duplicate bindings, choose one reverse-thrust method, define a stable idle band, and recalibrate both levers in the CRJ tablet.
Does the Aerosoft CRJ have autothrottle?
No, the Aerosoft CRJ does not have autothrottle, so normal aircraft automation should not advance or retard its thrust levers. The autopilot controls pitch and roll; when a speed mode is used, it changes pitch rather than commanding the throttles.
The FADEC manages engine response to the thrust-lever position, but it does not select that position for you. If the cockpit levers move after you place them at idle, Microsoft Flight Simulator is receiving another control input or interpreting the axis incorrectly.
Match the CRJ throttle symptom to its likely cause
The way the throttle misbehaves usually identifies which setting to inspect first.
| What you see | Likely cause | First check |
|---|---|---|
| The levers advance again after being moved with the mouse | A physical axis is continuously overriding the mouse | Duplicate axes and connected controllers |
| Both levers jump together | A combined axis, assistance feature or global throttle command | Throttle Axis and assisted-control assignments |
| Only one lever moves | That engine's axis, calibration or hardware sensor | Throttle 1 Axis or Throttle 2 Axis |
| The lever flickers around idle | Axis jitter crossing a narrow idle boundary | Idle calibration range and raw controller input |
| The lever jumps straight into reverse | Reverse is mapped through both axis travel and a button | Full-range axis and reverse command assignments |
| There is no movement at all | The wrong profile or control is active, or the input is not reaching MSFS | The input indicator in the controls screen |
How to make the Aerosoft CRJ stay at idle
The reliable fix is to leave one control path for each thrust lever and calibrate that exact arrangement inside the CRJ.
- Secure the aircraft. Apply the parking brake and, where available, use chocks. An incorrect forward or reverse command can move the aircraft while you test.
- Inspect every connected device. Open the MSFS controls settings and check the active profile for each throttle, joystick, yoke, gamepad, keyboard and other controller. Filter for assigned controls and search for throttle, reverse, decrease and cut commands.
- Remove duplicate axes. With one physical lever controlling both engines, use a combined throttle axis only. With a twin-lever quadrant, use separate engine-one and engine-two axes and remove the combined
Throttle Axis. Variants marked0 to 100%are different from full-range assignments, so do not leave both active. - Choose one reverse method. Use either analogue travel below idle or a separate reverse command. Do not combine a full-range reverse axis with another button or switch that also toggles reverse.
- Disable automatic inputs temporarily. Turn off AI piloting and throttle-related assistance while diagnosing the fault. Also check for a gamepad trigger, VR controller or latching hardware switch sending repeated commands.
- Stabilise the idle position. Watch the axis input while the physical lever rests at idle. If the value moves slightly, create a modest idle band in the CRJ calibration. A conventional centre dead zone may not help when idle is at the end of the axis.
- Calibrate both levers in the CRJ EFB. Open the aircraft's throttle-calibration page and record the requested reverse, idle and forward positions for each engine. Labels differ between CRJ releases, but any upper and lower idle boundaries should contain the lever's settled value without overlapping the reverse region.
- Test one engine at a time. Move the first lever forward and return it to idle, then repeat with the second. Test reverse only through the method selected for that profile.
For the underlying MSFS 2020 sensitivity, reversal and duplicate-binding checks, follow our detailed throttle-axis calibration procedure.
Which throttle-axis and reverse arrangement should I use?
Choose the arrangement that matches what the hardware actually sends below its idle position.
| Hardware behaviour | Recommended arrangement | Avoid |
|---|---|---|
| The analogue axis stops at idle | A forward-only or 0 to 100% axis with reverse on a separate command | A full-range axis that places idle part-way through the lever travel |
| The analogue axis continues below idle | A full-range axis with reverse and idle regions calibrated in the CRJ | An additional reverse toggle generated by the same movement |
| The aft detent activates a button | A forward-only axis plus a reverse command suited to that button's momentary or latching behaviour | Treating the button detent as analogue reverse travel |
| A twin-lever quadrant controls both engines | Separate engine-one and engine-two axes calibrated individually | A combined axis assigned in parallel |
How do I turn off a throttle detent in MSFS 2024?
There is no universal throttle-detent switch in MSFS 2024 because a detent can come from the physical quadrant, a control binding or the aircraft's own calibration.
- Physical detent: software cannot remove the mechanical notch, but you can leave its button unassigned or prevent that part of the analogue range from selecting reverse.
- Reverse button or switch: clear its reverse, throttle-decrease or toggle assignment from the active controller profile.
- CRJ calibration boundary: recalibrate the idle and reverse regions in the EFB. Do not remove the idle band simply to disable reverse.
If you want forward thrust only, select the appropriate forward-only axis, clear every reverse assignment and recalibrate the CRJ around the physical idle position.
Why does the throttle jump or show no movement in MSFS 2024?
In MSFS 2024, throttle jumping or no movement usually means the wrong per-device profile is active, a default assignment conflicts with the intended axis, or the axis direction and range do not match the aircraft calibration.
Do not assume a profile prepared for MSFS 2020 has transferred correctly. Select every recognised controller, confirm which profile is active and watch the on-screen input indicator while moving the lever. Our MSFS 2024 controller-profile diagnosis covers incorrect axes, conflicting assignments and reversal in more detail.
The installed Aerosoft CRJ build must also be intended for the simulator version being used. Check the CRJ's MSFS 2024 compatibility considerations before treating behaviour from an unsupported or mismatched installation as a calibration fault.
What if the CRJ throttle has no movement?
No cockpit movement means the selected hardware input is not reaching the aircraft through the expected axis assignment.
- If the controls screen shows no input, check the active device profile and whether the controller is recognised by the system.
- If the input indicator moves but the cockpit lever does not, inspect the axis name and repeat the CRJ EFB calibration.
- If the lever moves in the wrong direction, reverse the axis once; do not use reversal to conceal a duplicate binding.
- If the cockpit lever moves but engine thrust does not respond, the controller is reaching the aircraft. Check the engine, fuel and lever operating state rather than adding more sensitivity or dead zone.
How can I tell whether the problem is the throttle hardware?
Remove or temporarily unassign the intended hardware axis, then place the virtual CRJ levers at idle with the mouse. If they stay there, the cause is the controller profile, calibration or physical sensor rather than the CRJ's throttle logic.
Reconnect one device at a time. A fault affecting only one lever points towards that engine's axis or sensor; both levers moving together usually indicates a combined axis, assistance setting or global command.
On PC, inspect the controller's raw input through the operating system or its configuration utility. Small fluctuations can be contained by a sensible idle band. Large jumps across a significant part of the range suggest a worn or dirty sensor, and an oversized dead zone will only hide the fault while making thrust control less precise.
What if the throttle command will not go away?
A throttle state that remains after the control is released usually comes from a latched toggle or a switch sending repeated commands. If the fault is described as no se quita, meaning it will not clear, inspect reverse-toggle, throttle-decrease, cut and set-throttle bindings on every connected device.
A hardware detent that stays electrically active normally needs a hold-style command, while a momentary button may require different behaviour. Match the assignment to the switch rather than stacking several reverse commands until one appears to work.
Can the CRJ still fly or roll at idle thrust?
Yes; idle is the minimum commanded forward thrust, not zero thrust and not a braking command. A CRJ can continue flying in a descent at idle, and a lightly loaded aircraft may roll or accelerate slowly while taxiing with both levers correctly positioned.
Use wheel brakes to control taxi speed and the parking brake when stationary. Do not use reverse as the normal way to hold the aircraft. Also avoid judging calibration from one expected N1 value, because engine idle varies with conditions and aircraft state; watch the lever position and confirm a smooth thrust response around idle instead.
What if calibration and binding changes do not fix it?
If the levers still move with all external axes removed and assistance disabled, check the aircraft installation. An outdated package or duplicate CRJ installation can leave aircraft code and tablet calibration components out of step.
Update through the channel from which the aircraft was installed, make sure only one intended CRJ package is active, and then repeat the throttle calibration. Our Aerosoft CRJ update and duplicate-installation checks explain how to rule this out without deleting unrelated controller profiles.
Search clarification: an IdleOn Keep Away contract is unrelated to Aerosoft, the CRJ or Microsoft Flight Simulator. Idle on this page refers only to an aircraft engine's minimum thrust setting.