Why are my ailerons stuck or not responding in FSX?

FSX and FSX: Steam Edition ailerons usually stick or stop responding because the aileron axis is missing, duplicated, reversed, badly calibrated, or overridden by autopilot or another device. Test Num Pad 4/6 in a default aircraft with Num Lock off; if the keyboard works, repair the controller assignment rather than the aircraft.

How do I tell whether FSX or the controller is at fault?

A keyboard test in the default Cessna 172 separates an FSX or aircraft problem from a joystick, yoke or gamepad problem.

1. Load a default aircraft. Turn off the autopilot, release any control lock and make sure FSX is neither paused nor in slew mode.
2. Test the standard keys. With Num Lock off, press Num Pad 4 for left aileron, Num Pad 6 for right aileron and Num Pad 5 to centre the controls. FSX keyboard inputs are not spring-loaded, so repeated presses can leave the ailerons deflected until they are centred. Our reference for the standard FSX keyboard commands explains these bindings in more detail.
3. Watch the actual surfaces. Observe the cockpit yoke and both ailerons in an external view. They should move even while parked, although the aircraft will not roll without airflow.
4. Repeat with controllers disconnected. If a surface moves briefly and immediately returns or goes hard over, close FSX, disconnect every controller, restart it and repeat the keyboard test. A live analogue axis was probably overriding the key command.

Top-row number keys are not substitutes for Num Pad 4, 5 and 6. On a compact keyboard without a numeric keypad, assign temporary keys through the controls settings instead.

How do I fix the aileron axis in FSX?

The joystick or yoke must have one analogue assignment to Ailerons Axis, with no competing assignment on another connected device.

1. Open the controls settings. Select the intended joystick or yoke from the device list. Boxed FSX and FSX: Steam Edition use slightly different menu presentation, but both provide separate pages for axes and key or button commands.
2. Confirm controller input is enabled. Check the controller enable setting. FSX also has a controller on/off command commonly bound to Ctrl+K in the default profile, so an accidental toggle can disable every controller axis.
3. Inspect every device. A mistake we see constantly is checking only the main yoke. Select the throttle, pedals, gamepad and any virtual device in turn, then remove unwanted Ailerons Axis assignments.
4. Assign the correct command. Bind the stick or yoke’s left-right movement to Ailerons Axis. Do not bind an analogue axis to the digital Aileron Left and Aileron Right commands.
5. Check the direction. Apply left input and watch the control wheel and surfaces. Use the reverse option only if left input produces right roll command.
6. Adjust sensitivity and null zone. Start with high sensitivity and a small null zone. An excessive null zone makes the control feel dead around the centre, while very low sensitivity can prevent useful travel.
7. Test the raw hardware signal. Close FSX, run joy.cpl in Windows and open the controller’s properties. The axis indicator should travel smoothly to both ends and return to centre. FSX cannot correct an axis that sticks, spikes or fails to reach full travel in Windows.
8. Return to the default aircraft. Verify normal roll control there before testing the original add-on.

If no buttons or axes respond, use our broader controller detection and assignment checklist. For off-centre input, unwanted rolling and duplicate assignments, follow our Windows calibration and axis-conflict procedure.

If a separate control utility manages the axis, remove the equivalent assignment from FSX. One axis should be managed in one place; parallel mappings can fight each other.

Why are the ailerons stuck at full left or right?

Ailerons held at full deflection normally indicate an accumulated keyboard command, a badly centred analogue axis or an unwanted assignment on another device.

• Press Num Pad 5 with Num Lock off. This centres the default aileron and rudder keyboard inputs. If the ailerons stay centred afterwards, repeated keyboard commands caused the problem.
• Watch what happens after centring. If the ailerons centre briefly and then move back, an analogue axis, trim command or autopilot is reapplying the deflection.
• Disconnect devices one at a time. When the ailerons centre after one device is removed, inspect that device’s axis assignments and Windows calibration.
• Check aileron trim. Aircraft that support aileron trim can roll despite a centred yoke. Reset the trim in the cockpit and remove unintended trim-axis or trim-button assignments.
• Inspect the physical controller. If the stick springs to centre but its indicator remains hard over in joy.cpl, the fault is in the hardware, calibration or driver rather than FSX.

What if the ailerons move but the aircraft will not roll?

Visible aileron movement will not roll a stationary aircraft, and autopilot or add-on flight-control systems can oppose manual input in flight.

Test at a safe flying speed with FSX unpaused, slew mode off and the autopilot master disengaged. The flight director alone displays guidance and does not control the default aircraft. If the aircraft rolls under those conditions, the input system is working.

When only one complex add-on is affected, check its gust or control lock, hydraulic pumps, electrical supply, flight-control computers and programmed failures. Clear any active FSX control-surface failure as well. If the default Cessna responds normally, repeatedly remapping the joystick will not repair an aircraft-specific system or animation.

Nothing worked: what should I reset next?

If every check still produces “nothing worked”, reset the control profile before repairing or reinstalling FSX.

Readers arriving through short multilingual searches—German “funktioniert nicht” or “nein es geht nicht”, Portuguese “não funciona” or “nao da”, and an incomplete Polish phrase such as “nie jest…”—should use the same isolation order: default aircraft, keyboard test, disconnected controllers, then a clean control profile.

1. Record custom assignments. Restoring defaults removes personalised axes, buttons and keyboard commands.
2. Use Restore Defaults in the controls settings. Restart FSX and test Num Pad 4, 6 and 5 before adding custom bindings. If the keys were changed, see how to inspect and restore the active FSX keyboard assignments.
3. Rebuild a damaged controls file if necessary. Exit FSX and open the active per-user Controls folder under %APPDATA%\Microsoft\FSX. A side-by-side boxed and Steam installation may instead use an FSX-SE profile folder. Back up Standard.xml, rename the original, then start FSX so it can create fresh default controls.
4. Reconnect only the intended controller. Assign Ailerons Axis once and test it before reconnecting throttles, pedals or gamepads. FSX may automatically assign axes when a device reappears, so inspect each one afterwards.

If clean keyboard controls work but the hardware fails in joy.cpl, repair the hardware or its Windows setup. If neither keyboard input nor fresh controls move the default aircraft, use installation file verification for Steam Edition or the repair option for boxed FSX. Reinstalling first often leaves the same per-user control profile in place and changes nothing.