Calibrate PMDG throttles in MSFS correctly: map each engine axis, set endpoints, stop lever jitter, fix autothrottle conflicts and set reverse.
Calibrate PMDG throttles in Microsoft Flight Simulator by first calibrating the hardware in its driver, then assigning each lever to the correct numbered throttle axis in a dedicated controller profile. Use a linear response, verify idle and full-forward endpoints with autothrottle off, and remove duplicate bindings before configuring reverse thrust separately.
PMDG throttle calibration, step by step
The reliable order is hardware calibration, MSFS axis assignment, endpoint checking and then PMDG-specific tuning.
- Calibrate the physical quadrant. Use the manufacturer's utility or documented calibration method. If none is provided on PC, use the Windows controller calibration facility where supported. Move every lever through its complete usable range and confirm that the raw input reaches both stops without flickering.
- Create a dedicated control profile. Copy your normal throttle profile, name the copy for the PMDG aircraft and select it whenever you load that aircraft. Our detailed MSFS axis and endpoint procedure covers the simulator's sensitivity graph and input testing.
- Remove competing assignments. Search the controls by input and move each throttle lever. Delete throttle-axis bindings from gamepads, joysticks or other quadrants that should not control the aircraft. A mistake we see constantly is a combined throttle axis remaining active alongside the individual engine axes.
- Assign each engine correctly. With a twin-lever quadrant, bind the left lever to the engine 1 throttle axis and the right lever to engine 2. Use the equivalent numbered axes for aircraft with more engines. A single physical lever can use the combined throttle axis instead.
- Choose the appropriate axis range. For a lever whose analogue travel ends at idle, use the forward-only axis, commonly labelled
Throttle 1 Axis (0 to 100%)and its numbered equivalents. Use a full-range axis only when the hardware has an analogue reverse region and the PMDG model recognises it. Do not bind both versions. - Start with a linear response. Keep the sensitivity curve straight and use little or no dead zone. Add only enough dead zone to suppress genuine electrical jitter; a large value reduces useful lever travel.
- Check direction and endpoints. With autothrottle disengaged, move each lever from idle to full forward while watching the virtual thrust levers. Enable the axis-reversal option if they move backwards. If either endpoint is missed, correct the hardware calibration first and then make a small endpoint adjustment in MSFS.
Microsoft Flight Simulator 2020 and 2024 present their control settings differently, and some action labels vary, but the rule is unchanged: each physical lever must feed one intended axis through one input route.
Which throttle axis should I bind?
Use separate numbered throttle axes when the hardware has one lever per engine; use a combined axis only for a genuinely shared lever.
| Hardware layout | Recommended mapping | Avoid |
|---|---|---|
| One lever for all engines | Combined forward throttle axis | Also binding individual engine axes |
| One lever per engine | Numbered throttle axes | Mapping both levers to the same engine |
| Analogue reverse travel | Full-range numbered axes, if supported by the aircraft | A second forward-only binding on the same levers |
| Button or switch below idle | Forward-only axes plus separate reverse commands | Treating the button as an analogue reverse zone |
If the engines do not respond independently, follow our explanation of mapping physical levers to the correct numbered engine axes. This is especially useful when a quadrant exposes several similarly named inputs.
Why do PMDG throttles jump with autothrottle on?
A mismatch between non-motorised hardware and PMDG's moving virtual thrust levers is normal while autothrottle is controlling the aircraft.
Do the calibration check with autothrottle off. When it is engaged, do not chase the cockpit levers with your physical quadrant. Before disconnecting autothrottle, bring the hardware close to the commanded thrust position where practical; this reduces a sudden power change when manual input takes over.
Small axis fluctuations can also be interpreted as manual input. Add a minimal dead zone, and check the PMDG aircraft options for a throttle-noise or manual autothrottle-override setting if that model provides one. On the PMDG 737, a clean axis is particularly important around the autothrottle's HOLD logic.
Why will the throttles not reach idle or stay matched?
Endpoint errors, duplicate bindings and mismatched raw lever calibration cause most PMDG throttle problems.
| Symptom | Likely cause | Fix |
|---|---|---|
| Virtual lever moves backwards | Axis direction is reversed | Toggle the simulator's reverse-axis option for that input |
| Both engines move from one lever | Combined and numbered axes are active together | Keep only the intended mapping |
| Reverse will not engage | Forward lever is not reaching a stable idle value | Recalibrate the endpoint and add a very small idle dead zone if required |
| Engine levers do not match | Different raw ranges or incorrect engine numbering | Recalibrate both levers and verify each numbered assignment |
| Thrust changes without touching the quadrant | Axis noise, another controller or piloting assistance | Search by input, remove duplicates and disable assistance that controls power |
| Throttle snaps when autothrottle changes state | Physical and virtual lever positions differ | Match the hardware position before returning to manual control |
How should reverse thrust be configured?
Configure reverse thrust only after both forward levers reach a reliable idle position.
A quadrant with button-operated reverse detents needs different bindings from one with a true analogue reverse range. Do not force a button-only detent into the sensitivity curve or sacrifice forward-axis travel to create an artificial reverse zone. Our PMDG reverse-thrust setup instructions explain the appropriate method for each hardware type and how to avoid duplicate engine commands.
Should I calibrate PMDG throttles through FSUIPC?
Use FSUIPC only when you need custom reverse zones, per-engine processing or filtering that the native MSFS controls cannot provide.
On PC, either route the axis through FSUIPC or bind it directly in MSFS—not both. Two active input paths cause jumping, delayed response and throttles that refuse to remain at idle. If FSUIPC is your chosen route, use our guide to record idle, maximum and reverse zones in FSUIPC, then remove the corresponding MSFS axis assignments.