Meet Airbus A320 family
The original A320 first flew in 1987 and entered service in 1988. Airbus subsequently stretched the design into the A321 and shortened it into the A319 and A318. The family made digital fly-by-wire and sidestick controls familiar to a large part of the airline world.
Family resemblance does not erase the differences between an A319, an A321 and an A320neo. Fuselage length, engines, fuel arrangements and equipment vary. In the simulator, the original bundled A320neo, the later V2 aircraft and independent developers' products also have their own systems and documentation.
In your simulator
Systems, equipment and documentation for each developer’s aircraft.
A320neo v2 (iniBuilds)
Microsoft Flight Simulator
Edition / package Standard
The later bundled A320neo has its own systems guide
The iniBuilds guide explains load-factor-based fly-by-wire control and automatic trim, and separates autopilot, flight-director and autothrust indications. It describes the later A320neo implementation. These details should not be silently assigned to the original Asobo aircraft or to an independent A320 add-on.
Microsoft / aircraft developers · Airbus A320neo V2 Manual ↗Archived simulator manual; installed package revision not observed · PDF pp.3,18 (printed17), visually rendered
A321LR
Microsoft Flight Simulator
Edition / package Standard
Hydraulic architecture appears in the cockpit documentation
The A321 guide explains the relationship between engine-start preparation and the yellow hydraulic system's brake-accumulator supply. That is a concrete systems connection within this implementation, rather than a generic A320-family checklist copied onto a longer aircraft.
Microsoft / aircraft developers · Airbus A321LR ↗Archived simulator manual; installed package revision not observed · PDF p.68; engine-start preparation
A320neo
Microsoft Flight Simulator
Edition / package Standard
Airbus A320neo V2
Microsoft Flight Simulator
Edition / package Standard / free update
The later bundled A320neo has its own systems guide
The iniBuilds guide explains load-factor-based fly-by-wire control and automatic trim, and separates autopilot, flight-director and autothrust indications. It describes the later A320neo implementation. These details should not be silently assigned to the original Asobo aircraft or to an independent A320 add-on.
Microsoft / aircraft developers · Airbus A320neo V2 Manual ↗Archived simulator manual; installed package revision not observed · PDF pp.3,18 (printed17), visually rendered
A319 / A320 / A321 family
Fenix
Hardware integration starts with the shipped definition
Fenix directs hardware users to VAR_NAME entries in the installed Cockpit_Behavior.xml and provides example LVar bindings. The shipped file and applicable aircraft version are the source of the names. Guessing an identifier from a cockpit label is not an equivalent method.
Fenix Simulations · Fenix public external hardware binding guide ↗Fenix A320 family guide, 2026-02-26 · article updated 2026-02-26; XML variable discovery and two examples
A321ceo / A321neo
Flight Sim Labs
A dated simulator-support announcement
Flight Sim Labs's A321ceo v11.0.1.302 announcement, dated 4 June 2025, introduces initial MSFS 2024 support. This is a specific release statement. The current product and update pages remain the reference for later support changes.
Flight Sim Labs · A321ceo v302 MSFS 2024 compatibility ↗document snapshot; exact installed package not observed · A321ceo v11.0.1.302 announcement, 2025-06-04
A dedicated hardware-interface resource
Flight Sim Labs hosts a separate MSFS hardware-interface download area. That is the developer's entry point for the integration material, rather than inferring a supported interface from a generic MSFS variable list.
Flight Sim Labs · MSFS Hardware Interface distribution ↗MSFS hardware-interface listing · Hardware Interface for MSFS download category
A32NX
FlyByWire
A319 / A320neo / A321 family
ToLiss
Systems & details
Direct sidestick position, rudder animation including trim, trim-actuator feedback and hydraulic circuit pressure are distinct signals.
Several familiar AUTOPILOT_ACTIVE and FMA variables are now listed as deprecated; a historical binding list is insufficient for current mappings.
The developer warns that generic PFD values bypass the add-on sensor model. Some autopilot selections are exceptions using standard datarefs.
Direct-law transition logic now uses actual gear-not-uplocked state rather than lever position; cockpit-output datarefs also changed.
Manuals & resources
Read the original documentation from the people who created it. Manuals open on their publisher’s website.
Manual
Airbus A320neo V2 ManualMicrosoft / aircraft developers Microsoft Flight Simulator aircraft manualsMicrosoft / aircraft developers Airbus A321LRMicrosoft / aircraft developers X-Plane aircraft and avionics manualsLaminar ResearchAircraft background
Airbus A320 familyWikipedia contributors · Research background · Wikipedia revision 1374072105 · retrieved 2026-09-12Resource
MSFS 2024 FAQ and edition aircraft inventoryMicrosoft MSFS 2020 FAQ and edition aircraft inventoryMicrosoft Aircraft and Avionics Update 3Microsoft Fenix BFU release and flight-control changesFenix A321ceo v302 MSFS 2024 compatibilityFlight Sim Labs A321neo productFlight Sim Labs MSFS Hardware Interface distributionFlight Sim Labs A320neo change logToLissDeveloper reference
Fenix public external hardware binding guideFenix Simulations A32NX systems APIFlyByWire ToLiss developer explanation of sensor-model datarefsToLiss developer on X-Plane.orgDocumented interfaces
Source-documented identifiers. Documentation does not prove that every add-on populates a value correctly.
L:A32NX_SIDESTICK_POSITION_X
Direct lateral stick.
- Units
- Number
- Access
- read semantics documented; write contract not established
API snapshot 2026-09-10
FlyByWire · Flight Controls ATA27 ↗L:A32NX_SIDESTICK_POSITION_Y
Direct longitudinal stick.
- Units
- Number
- Access
- read semantics documented; write contract not established
API snapshot 2026-09-10
FlyByWire · Flight Controls ATA27 ↗L:A32NX_RUDDER_PEDAL_POSITION
Direct pedal position.
- Units
- Number
- Access
- read semantics documented; write contract not established
API snapshot 2026-09-10
FlyByWire · Flight Controls ATA27 ↗L:A32NX_HYD_TRIM_WHEEL_PERCENT
Trim wheel position.
- Units
- Percent
- Access
- read semantics documented; write contract not established
API snapshot 2026-09-10
FlyByWire · Flight Controls ATA27 ↗L:A32NX_HYD_THS_TRIM_MANUAL_OVERRIDE
Pilot moving or holding trim wheel.
- Units
- Boolean
- Access
- read semantics documented; write contract not established
API snapshot 2026-09-10
FlyByWire · Flight Controls ATA27 ↗L:A32NX_HYD_{loop_name}_SYSTEM_1_SECTION_PRESSURE
Hydraulic circuit section pressure.
- Units
- Psi
- Access
- read semantics documented; write contract not established
API snapshot 2026-09-10
FlyByWire · Flight Controls ATA27 ↗L:A32NX_HYD_RUDDER_TRIM_FEEDBACK_ANGLE
Rudder trim unit feedback.
- Units
- Degree
- Access
- read semantics documented; write contract not established
API snapshot 2026-09-10
FlyByWire · Flight Controls ATA27 ↗Something missing or a source that needs attention?
Suggest a correction ↗
