Hi all, I have posted on this topic some time ago, but could not find the thread in a recent search.

The issue I am facing is this. I use the Thrustmaster Hotas Warthog throttle and joystick. When I spawn any of the Fenix airbuses onto a runway, the digital displays come online, and then after about a minute an orange 'speed brake' sign appears on the upper ecam, and I cannot clear it.

When I look at the wings, the speedbrakes are not deployed, and that is confirmed by looking at the facilities on the lower ecam. The speedbrake arm is in the off position, and if I engage it (or the axis that I also have for the speedbrakes) they work as one would expect.

If I 'continue' to fly and ignore the speed brake warning message, I then get a message saying F/CTL SPD BRK DISAGREE.

I thought I might have some double bindings, particularly on my numeric keypad which I use for chaseplane views, and sure enough I did. So, I cleared all of those, but the issue persists.

I am running out of ideas as to what to do next to fix the issue, and would welcome any thoughts and/or suggestions.

Cheers.

Copilot "dixit":

============================================================

On an Airbus, “F/CTL SPD BRK DISAGREE” means the aircraft’s flight control computers detect a mismatch between the commanded speedbrake position and the actual position of the spoilers.

In plain terms: 🛫 The system thinks the speedbrakes should be in one position, but the sensors show something different.

💡 What typically triggers it

• Your hardware throttle/joystick is sending a small speedbrake input even though the lever in the cockpit is down.

• Double bindings (keyboard, controller, or add‑ons) sending conflicting spoiler commands.

• A noisy or uncalibrated axis on your hardware (very common with older or sensitive potentiometers).

• A virtual “ghost input” from a controller that MSFS still sees even if you think it’s disabled.

🛠 Why it appears in Fenix specifically

The Fenix Airbus simulates the real Airbus logic very closely. If the aircraft senses even a tiny spoiler deflection while the lever is down, it raises:

• SPD BRK (amber) on the ECAM

• Then F/CTL SPD BRK DISAGREE if the mismatch persists

This matches the real aircraft behaviour.

✔ How to fix it in MSFS (especially with Thrustmaster Warthog)

Since your open tab mentions the Warthog, here’s what usually solves it:

1. Check your spoiler axis

• Move your spoiler axis fully up/down once after loading the aircraft.

• Recalibrate it in MSFS or in the Thrustmaster control panel.

• Add a dead zone of 5–10% at the bottom of the axis to eliminate micro‑inputs.

2. Remove ALL duplicate spoiler bindings

Check every connected device, including:

• Joystick

• Throttle

• Rudder pedals

• Xbox controller

• Keyboard (especially NumPad keys, as you suspected)

MSFS often auto‑assigns spoiler commands to multiple devices.

3. Check for “virtual” inputs

Even if you don’t use them:

• Disable spoiler bindings on any unused controllers

• Unplug devices you don’t need for the flight

4. Verify in Fenix EFB → Controls

The Fenix EFB shows raw input values. If the spoiler axis is not exactly at 0.00 when stowed, the aircraft will complain.

Have you calibrated the axis you use for the spoilers withing the Fenix FMS?

Many thanks jcomm and sniper31 for your responses - very helpful and I now think I have cracked the problem. It would appear that it was the sensitivities that needed adjusting on the X axis. Now all seems to be working as I would expect. Thanks again and happy flying.

6 hours ago, SquadronLeader said:

Many thanks jcomm and sniper31 for your responses - very helpful and I now think I have cracked the problem. It would appear that it was the sensitivities that needed adjusting on the X axis. Now all seems to be working as I would expect. Thanks again and happy flying.

Glad to hear you got it sorted. Happy flying 😊