See which MSFS 2024 aircraft work with the Winwing MCDU, why stock Airbuses differ, and how to verify the correct SimAppPro profile.
In Microsoft Flight Simulator 2024, the Winwing MCDU’s clearly established aircraft pairing is the FlyByWire A32NX on Windows PC through SimAppPro. Do not assume the stock A320neo, A320neo V2, A380X or another Airbus add-on will work: each needs an explicit profile for that exact aircraft in the installed SimAppPro release.
MSFS 2024 Winwing MCDU compatibility
| Aircraft | Compatibility guidance |
|---|---|
| FlyByWire A32NX | Supported pairing. Use the dedicated A32NX integration through SimAppPro rather than generic keyboard assignments. |
| Default A320neo or A320neo V2 | Not automatically compatible through the A32NX profile. These aircraft use different systems and data interfaces; use them only if your SimAppPro release lists the exact model. |
| FlyByWire A380X | Do not infer hardware compatibility from its FlyByWire origin. It requires its own Winwing profile; A32NX support does not cover it. |
| Fenix or other iniBuilds Airbus aircraft | Profile-dependent. Match the exact developer, aircraft family, variant and MSFS version shown by SimAppPro. |
| Boeing and non-Airbus aircraft | Not suitable for normal aircraft-specific integration. Their CDU layouts, functions and simulator interfaces differ from an Airbus MCDU. |
The important distinction is between Windows recognising the USB device and SimAppPro supporting the loaded aircraft. A lit screen or working buttons only confirms part of the connection; it does not establish full two-way MCDU integration.
How do I check whether an aircraft is supported?
- Update the software and firmware. Install a SimAppPro release intended for MSFS 2024 and update the MCDU firmware when the software offers a matching update.
- Load the exact aircraft. Wait until the cockpit and avionics have initialised; testing from the main menu cannot confirm aircraft integration.
- Check the aircraft profile. The developer and model must match exactly. An A32NX profile is not a substitute for an A320neo V2, Fenix A320 or A380X profile.
- Test both directions. Confirm that the hardware displays the aircraft’s MCDU pages and that key presses change the in-sim unit. One-way operation usually indicates an incomplete or incorrect profile.
For the confirmed aircraft, our A32NX Winwing MCDU connection procedure covers the aircraft-specific setup. If SimAppPro does not detect the unit at all, start with the broader Winwing control and SimAppPro configuration steps.
Does the Winwing MCDU work with the FlyByWire A380X?
The A380X should be treated as unsupported unless the installed SimAppPro release explicitly provides an A380X profile. Its built-in remote MCDU capability is separate from Winwing hardware integration, even though both the A32NX and A380X use FlyByWire systems.
If the objective is an external A380X CDU rather than this particular physical unit, the FlyByWire browser-based remote MCDU setup is the more dependable option.
Why does the MCDU light up but not control the aircraft?
The usual causes are the wrong aircraft profile, a SimAppPro build without support for that aircraft, outdated firmware, or selection of an MSFS 2020 profile for MSFS 2024. Another common mistake is mapping the keys as generic keyboard controls: that may produce button presses but will not provide the live display, scratchpad or aircraft-specific page logic.
Close duplicate bridge or mapping utilities while troubleshooting, reconnect the device, restart SimAppPro and load the aircraft again. If the exact aircraft is absent from SimAppPro’s supported list, remapping buttons will not create full compatibility.
Can the Winwing MCDU be used on Xbox or PlayStation?
No full Winwing MCDU integration should be expected on Xbox Series X|S or PlayStation 5. The aircraft bridge depends on SimAppPro running on Windows, so this MSFS 2024 compatibility applies to the PC version.