Fix add-on aircraft brakes not working by checking brake-axis bindings, duplicate controls, hydraulic power, anti-skid and EFB settings.
Brakes on an add-on aircraft usually fail because the toe-brake axes are unassigned, inverted or duplicated, or because the aircraft’s custom systems require hydraulic pressure, electrical power or calibration in its electronic flight bag (EFB). Test a default aircraft first: this separates a simulator or controller problem from add-on-specific brake logic.
How do I find why the add-on aircraft brakes are not working?
A controlled comparison with a default aircraft will show whether the fault follows the controller or the add-on.
- Test a default aircraft. Load a powered, ready-to-fly default aircraft on a long runway and taxi slowly. Use the same controller profile and test both an assigned brake button and the toe-brake pedals. If neither works, troubleshoot the simulator or controller rather than the add-on.
- Check the correct brake commands. Analogue pedals should normally use separate left and right brake axes. A keyboard key or joystick button should use the command that applies both service brakes. Do not assign a parking-brake toggle to the toe pedals.
- Remove duplicate bindings. Search every connected yoke, joystick, throttle, gamepad and pedal set for assignments containing “brake”. Delete unintended brake buttons and axes. A mistake we see constantly is a factory controller profile that assigns brakes to an unrelated lever or button; our guide to finding hidden brake assignments triggered by other flight controls covers that fault in detail.
- Watch the axis response. In the simulator’s calibration display, the brake input should be released at rest and increase smoothly as the pedal is pressed. Reverse the axis if it behaves backwards, and add only enough dead zone to remove residual input. FSX users can follow these FSX brake-axis and duplicate-binding checks, which also catch pedals that report maximum braking at rest.
- Try a powered aircraft state. If the brakes work after loading a runway-ready state but not from cold and dark, the controls are reaching the aircraft. The missing part is probably hydraulic pressure, an accumulator, electrical brake control or the correct normal or alternate braking configuration.
- Inspect aircraft-specific options. Check the included manual and EFB for pedal calibration, realistic failures, brake wear and special control modes. Temporarily disable failures and reset any custom brake calibration before testing again.
What does each brake symptom mean?
The failure pattern usually identifies the broken layer before you change any more settings.
| Symptom | Likely cause | Next check |
|---|---|---|
| Brake button works, but pedals do not | Missing, inverted or uncalibrated axes | Check separate left and right brake-axis assignments |
| Pedals work in a default aircraft only | Add-on systems, custom calibration or compatibility fault | Test a powered state and inspect the aircraft’s EFB |
| Only one wheel brakes | One axis is missing or a simulated brake has failed | Compare the left and right input indicators |
| Pressing a pedal releases the brake | Reversed axis | Enable the simulator’s reverse-axis option for that pedal |
| Pedals animate but the aircraft does not slow | No brake-system pressure, custom logic or brake failure | Check hydraulic indications, failures and alternate braking |
| Aircraft veers sharply under braking | Unequal pedal range or differential braking | Recalibrate both axes and compare their full travel |
Why do add-on aircraft need hydraulic power to brake?
Detailed add-ons can ignore generic brake pressure unless their simulated hydraulic, pneumatic or electrical system is available.
Transport aircraft may model normal and alternate braking, brake accumulators, anti-skid control and parking-brake pressure. Starting cold and dark without the required pumps or electrical buses can therefore produce moving cockpit pedals but little or no braking. Anti-skid being off does not universally remove the brakes, though; the result depends on the real aircraft’s design and how deeply the add-on models it.
Not every aircraft uses conventional hydraulic toe brakes. Some vintage and military types combine a hand-operated brake lever with rudder position, while other aircraft use pneumatic braking or have no wheel brakes on a particular undercarriage configuration. In those cases, assigning standard left and right toe brakes may be the wrong control method rather than a software fault.
What if the add-on still has weak or no braking?
Brakes that respond but do not stop the aircraft quickly are not necessarily broken.
First judge them during a slow taxi. At landing speed, aircraft mass, runway condition, brake temperature and weight on the wheels all affect stopping distance. Ground spoilers increase wheel loading, while reverse thrust supplies separate deceleration; neither replaces correctly functioning wheel brakes. Autobrake also requires aircraft-specific arming and touchdown conditions, so failure to activate does not prove the manual brakes are faulty.
If there is still no braking, create a temporary controller profile containing only the essential flight axes and left and right brakes. Disconnect or disable spare controllers and external mapping tools, then retest the add-on in a powered state with failures off. This rules out hidden inputs without destroying a working control profile.
Finally, confirm that the aircraft was made for the exact simulator generation and platform being used. An aircraft converted from an older simulator may load visually while its custom gauges or brake logic fail. If a default aircraft brakes normally but a clean installation of the add-on does not, the remaining cause is an aircraft compatibility problem or defect; reinstall the add-on package rather than the entire simulator.