Fix speed brakes that won't deploy by checking spoiler bindings, axis conflicts, hydraulics, arming logic and aircraft-specific conditions.
Speed brakes usually fail to deploy in Microsoft Flight Simulator, X-Plane, FSX or Prepar3D because the control is bound incorrectly, a hardware axis is overriding the command, or the aircraft’s spoiler logic is inhibiting movement. Check the lever, bindings and hydraulics, then distinguish manual extension from armed automatic ground-spoiler deployment.
How do I diagnose speed brakes that will not deploy?
Test the cockpit control, simulator assignment and aircraft system separately; this reveals which part is blocking deployment.
- Confirm the aircraft has speed brakes. Some light aircraft have none, while gliders may label them airbrakes. Check for a cockpit lever and use the aircraft’s own checklist or manual rather than assuming every model responds to a generic spoiler command.
- Power the aircraft normally. Start the engines or otherwise establish the required hydraulic and electrical power. A cold-and-dark aircraft may let the cockpit lever move while leaving the spoiler panels stationary.
- Operate the virtual lever. Use the mouse or a known keyboard command, then watch both the cockpit lever and the surfaces in an external view. If this works but the hardware does not, the fault is in the controller profile. If the lever moves but the panels do not, investigate hydraulic pressure, failures and aircraft-specific inhibition.
- Inspect every controller assignment. Search the controls for
spoiler,speed brakeandairbrake. Remove duplicate assignments from throttles, joysticks, gamepads and unused controller profiles. - Disconnect controllers one at a time. A forgotten slider or noisy axis can continuously command the retracted position. Also disable any assistance option or control utility that operates the aircraft automatically.
- Compare another aircraft and profile. If several aircraft have the same fault, the simulator or controller setup is responsible. If only one add-on is affected, its custom systems, required aircraft state or configuration are the more likely causes.
Choosing the correct speed-brake binding
| Control type | What it does | When to use it |
|---|---|---|
| Speed-brake or spoiler axis | Maps the full physical lever travel | Use for a quadrant lever; calibrate both endpoints and reverse it only if the direction is wrong |
| Extend and retract | Commands a definite direction | Best for two buttons, a rocker switch or keyboard keys |
| Toggle spoilers | Changes to the opposite state | Useful with one button, but harder to diagnose because its state can become unclear |
| Arm spoilers | Prepares automatic deployment | Use before landing; it does not normally extend the panels immediately |
For a physical lever, our quadrant axis-assignment and calibration guidance covers reversed travel, overlapping bindings and unstable detents. Microsoft Flight Simulator users should also check the active device profile and follow the process for removing duplicate MSFS controller assignments.
Why does the speed-brake lever move and snap back?
A lever that returns immediately is almost always being overridden by another axis, button or aircraft-control utility.
Move every slider on the connected hardware while watching the simulator’s input indicator. Remove any accidental spoiler assignment, calibrate the intended lever through its full range and add a small dead zone if the retracted detent jitters. Some simulators use a one-direction axis while others use a signed range, so reverse the axis only when its endpoints are genuinely backwards.
If the virtual lever still snaps back after all controllers are unplugged, reload the aircraft without control utilities or automation enabled. A custom add-on may also enforce an interlock or use its own tablet-based hardware configuration.
Why won't armed ground spoilers deploy on landing?
Arming the spoilers does not deploy them; it tells the aircraft to deploy them automatically only when its touchdown conditions are satisfied.
- The speed-brake lever must be in the correct ARMED detent rather than merely near it.
- The virtual thrust levers generally need to reach idle. Poorly calibrated hardware can leave a small amount of thrust commanded even when the physical levers appear fully back.
- The aircraft must detect touchdown through wheel spin-up, weight-on-wheels sensors or another ground-sensing condition, depending on the type.
- Hydraulic power and the relevant aircraft systems must be available, with no active failure preventing deployment.
Do not test an armed lever while parked and expect the panels to rise. Use manual extension for a static test if the aircraft permits it. During landing, inspect the virtual throttle position as well as the spoiler lever; an idle-detent calibration error is a common reason manual speed brakes work but automatic ground spoilers do not.
Aircraft logic also differs. On many Boeing types, the armed detent is for automatic ground-spoiler deployment, while in-flight speed braking requires moving the lever farther towards its flight detent. On an Airbus, the speed-brake lever is separate from the thrust levers, and flight-control protections or flap configuration can limit or retract spoiler panels. Our explanation of A320 quadrant detents and the separate speed-brake control helps when an Airbus hardware setup is involved.
Are spoilers and speed brakes the same control?
They often use the same panels, but the terms describe different functions: speed brakes deploy symmetrically to add drag, ground spoilers dump lift after touchdown, and spoilerons assist roll control.
Simulator control menus commonly call the command Spoilers even when the cockpit lever says SPEED BRAKE. Partial or unequal panel movement is not automatically a fault; aircraft may use only selected panels in flight, mix them with aileron input or restrict their angle. Centre the roll controls before judging whether the speed-brake deployment is genuinely asymmetric.