Fix PMDG 737 throttles not responding by removing binding conflicts, mapping both engines, calibrating travel and checking autothrottle overrides.
PMDG 737 throttles usually stop responding because the hardware axes are unassigned, duplicated, reversed or fighting the autothrottle. First test the virtual levers with autothrottle disengaged, then remove duplicate bindings, assign each engine correctly, calibrate the full travel and check PMDG’s throttle-override and reverse-thrust settings.
In Microsoft Flight Simulator and earlier PMDG platforms, the symptom matters. A lever that never moves has a different cause from one that jumps back, controls both engines or works only while the autothrottle is off.
What does the throttle behaviour tell you?
| Symptom | Likely cause | First action |
|---|---|---|
| Neither cockpit lever moves | Missing axis assignment, wrong control profile or undetected hardware | Check the input indicator and assign a throttle axis |
| Both cockpit levers follow one physical lever | Combined throttle axis is assigned | Use separate Engine 1 and Engine 2 axes for a dual quadrant |
| Only one lever responds | One engine axis is missing, duplicated or assigned to the wrong lever | Check each axis separately |
| Levers jump, twitch or return | Duplicate bindings, noisy hardware or autothrottle override | Remove conflicts and inspect the input trace for jitter |
| Forward travel enters reverse | Reversed axis or incorrect full-range reverse assignment | Remove reverse bindings and test forward travel alone |
| Levers move but thrust does not rise | Aircraft state, reversers, engine failure or fuel control issue | Check engine indications and aircraft configuration |
How do you fix unresponsive PMDG 737 throttle axes?
- Test without autothrottle. Park the aircraft, move the A/T ARM switch off and disconnect the autothrottle. Try dragging each virtual throttle lever with the mouse. If the cockpit levers move by mouse but not from the quadrant, the PMDG model is responding and the fault is in the hardware assignment or calibration.
- Confirm that the simulator sees the axis. Open the controller settings, select the throttle device and move each lever. The input indicator should travel smoothly from one end to the other. No movement points to the device connection, driver, USB port or hardware configuration rather than the aircraft.
- Remove every duplicate throttle binding. Search all connected controllers for throttle, Engine 1, Engine 2, reverse thrust and throttle-decrease commands. A mistake we see constantly is a quadrant mapped correctly while a joystick slider, gamepad trigger or second profile still controls the same function. If an external control utility handles the axes, remove their simulator assignments so only one control layer sends commands.
- Choose combined or separate axes—not both. With one physical lever, assign the combined
THROTTLE AXIS. With two levers, assignTHROTTLE 1 AXISandTHROTTLE 2 AXIS, then clear the combined axis. Our dual-engine throttle mapping procedure covers the correct left-and-right arrangement. - Calibrate the complete forward range. Start with a linear response, confirm that physical idle reaches virtual idle and that maximum travel reaches full forward thrust. Add only enough dead zone to suppress genuine jitter. Large dead zones and restricted sensitivity curves can prevent the PMDG 737 from reaching idle or full travel. PMDG generations expose calibration differently, so use the relevant aircraft or simulator controls described in our PMDG throttle calibration walkthrough.
- Test reverse thrust separately. Temporarily delete all reverse-axis and reverse-button assignments. If forward thrust then works normally, rebuild the reverse setup using either a forward-only axis with separate reverse commands or a properly calibrated full-range axis. Do not combine both methods. See the PMDG reverse-thrust configuration options for the appropriate choice.
- Check the PMDG autothrottle override behaviour. PMDG products may provide an option controlling when physical throttle movement overrides the autothrottle; its location and wording vary between product generations. A noisy axis can repeatedly override or disconnect automation, while a non-motorised quadrant may remain physically out of position when the virtual levers move. If the problem occurs only with A/T engaged, use our explanation of PMDG autothrottle disconnects and hardware conflicts.
- Reload with the correct control profile. Save the controller changes, verify that the intended aircraft-specific profile is active and reload the PMDG 737 if the old input state persists. Simulator updates or newly connected devices can cause a different profile to be selected without changing the visible hardware.
Why does only one PMDG 737 throttle work?
One working lever almost always means the other engine axis is missing or mapped incorrectly. Move each physical lever while watching the controller input display, then confirm that the left lever operates Engine 1 and the right lever operates Engine 2.
If both inputs register but one cockpit lever remains still, clear that engine’s assignment and bind it again. Also check for a second controller holding the same engine at idle. Reverse the axis direction only when the virtual lever moves opposite to the physical one; reversing an unresponsive axis will not fix a missing assignment.
Why do the throttles stop responding when autothrottle is on?
The PMDG 737 autothrottle and a stationary hardware quadrant can issue competing demands. Most consumer throttle units are not motorised, so they do not physically follow the moving cockpit levers. PMDG’s override setting decides when movement of the hardware takes control back from the automation.
Do not treat THR HLD on the flight-mode annunciator as proof of a fault. It is a normal Boeing autothrottle mode in specific phases of flight. Diagnose manual throttle response with A/T disengaged first; once that works, investigate mode logic, override settings and axis noise.
Why do the levers move but the engines produce no thrust?
If the virtual levers move through their full range, the axis binding is working. Check that both engines are running at stable idle, the fuel control levers are in the required position, the reversers are fully stowed and no simulated failure is active.
Watch the N1 indications. If N1 rises but the aircraft does not move, the throttle is not the problem; check the parking brake, toe-brake axes, wheel chocks, pushback state and pause mode. If the levers advance but N1 remains at idle, load a known PMDG panel state and retest before rebuilding the controller profile.