Aircraft support · MSFS 2024 · Free
Headwind A330neo in FlightFabric: experimental controls and live data
FlightFabric’s support for the Headwind A330neo is limited: 8 voice commands, 2 presets and 14 controls, plus 21 live cockpit values, with the app’s own labels quoted below. It is not on the homepage’s supported list yet. Expect gaps, and check every result in the cockpit.
- 1Aircraft covered
- 8Voice commands
- 2Presets
- 14Cockpit controls
- 21Live cockpit values
Aircraft covered
Load this aircraft in MSFS 2024 and FlightFabric switches to its cockpit layout and control set by itself. There is nothing to configure in the app.
- Headwind A330-900neo
Vendor: Headwind Simulations. Other Airbus A330-900neo products from other developers are not covered by this page.
What you need
- FlightFabric 0.10.2 on the Windows PC that runs Microsoft Flight Simulator 2024, with the aircraft installed. MSFS and the aircraft are separate products; FlightFabric is free and needs no account.
- Voice control is optional and runs offline in the desktop app; the voice-control guide covers microphone and push-to-talk setup in five steps.
Try saying
Hold push-to-talk, say one of these, and release. Numbers are spoken as digits, so 270 is “two seven zero”. Each phrase below is accepted by FlightFabric 0.10.2 for the Headwind A330neo.
Every command
The full list, grouped by cockpit system. Every control here is also available from the Aircraft page and its control library, so you can tap it on a tablet instead of saying it. Setting a target such as a heading does not engage the autopilot; the aircraft’s current mode decides how it uses the target.
Flight controls
| Control | Say | Value |
|---|---|---|
| Landing gearStandard simulator control. | “gear value”or 1 other phrasing | up · down |
| Flaps one detentStandard simulator control. | “flaps value one”or 1 other phrasing | increase · decrease |
Exterior lights
| Control | Say | Value |
|---|---|---|
| Landing lights | “landing lights value”or 9 other phrasings | On / off |
| Taxi lightsNose taxi light only; runway turnoff lights are controlled separately. | “taxi lights value”or 9 other phrasings | On / off |
| Runway turnoff lights | “runway turnoff lights value”or 19 other phrasings | On / off |
| Strobe lights | “strobe lights value”or 7 other phrasings | off · auto · on |
Presets
A preset works through several switches in order and reports each step, the way a pilot monitoring runs a flow. It stops, rather than retrying, when the aircraft does not confirm a step.
Presets
| Control | Say | Value |
|---|---|---|
| Cockpit lighting14 dimmers · panel and flood lighting · flight displays | “set cockpit lighting value”or 2 other phrasings | 0–100 % · step 1 |
| Flight displays8 dimmers · PFD, navigation and engine displays | “set display brightness value”or 6 other phrasings | 0–100 % · step 1 |
Live cockpit data
The Aircraft page shows these 21 values as the aircraft reports them, next to the controls that change them. What you see is the switch position in the cockpit, not what the app last asked for.
Exterior lights 7
- Individual landing 2
- Individual landing 3
- Individual taxi 1
- Individual runway turnoff 2
- Individual runway turnoff 3
- Strobe mode
- Strobe active
Cockpit lighting 14
- Glareshield percent
- Glareshield lcd percent
- Main and pedestal percent
- Overhead percent
- Main flood percent
- Pedestal flood percent
- Captain PFD percent
- Captain ND percent
- Captain weather percent
- First officer PFD percent
- First officer ND percent
- First officer weather percent
- Upper display percent
- Lower display percent
Verification status
All 14 aircraft-specific controls on this page are mapped from standard simulator events. The project has not yet confirmed them one by one in a live simulator session, so the app lists each of them as awaiting verification. That is a statement about the project’s own testing, not a known fault: wherever the aircraft exposes the switch state, the app reads it back before reporting success.
Every control is guarded the same way: FlightFabric sends it once, waits for the aircraft to report the new switch position, and shows a failure instead of retrying. A few momentary controls are confirmed only by the simulator accepting the command. If a control does not respond on your installation, please report it on GitHub with the aircraft version so it can be fixed.