Airbus A320neo V2 in MSFS 2024 explained: what V2 means, what it simulates, and how it differs from the original A320neo and advanced add-ons.
The Airbus A320neo V2 in Microsoft Flight Simulator 2024 is Microsoft’s newer, more detailed simulation of the A320neo, developed by iniBuilds. “V2” identifies the second simulator package—not a real Airbus model. It offers deeper avionics, systems and cockpit workflows than the original default A320neo.
What does A320neo V2 mean?
V2 means version two of the simulated aircraft package. Airbus does not sell a real aeroplane called the “A320neo V2”. The aircraft remains an Airbus A320neo, with “neo” meaning New Engine Option; the simulation represents the CFM LEAP-powered version.
Microsoft uses the V2 label to distinguish the iniBuilds-built aircraft from the older Asobo A320neo supplied with earlier versions of Microsoft Flight Simulator. If both appear in the aircraft selector, they are separate packages rather than two configurations of one aircraft.
What is different about the A320neo V2?
The V2 is a substantial aircraft rebuild rather than a new exterior model placed over the original systems. Its cockpit supports a more complete Airbus operating workflow, including:
- More detailed electrical, hydraulic, pneumatic, fuel and engine systems.
- A functional MCDU with route, performance and flight-plan pages.
- Airbus managed and selected autopilot modes through the FCU.
- More capable PFD, ND and ECAM displays.
- An electronic flight bag for aircraft settings, loading, performance functions and hardware calibration.
- Cold-and-dark, turnaround and gate-to-gate operation.
That extra detail makes the V2 less forgiving than the legacy aircraft. Our guide to the A320’s FCU, MCDU and cockpit displays explains the controls that cause the most confusion.
Why are there two A320neos in the aircraft menu?
The two entries are separate simulations with different systems, configuration files and cockpit logic.
| Aircraft | Main difference | Best reason to use it |
|---|---|---|
| Original default A320neo | Older Asobo aircraft with simpler systems | Faster familiarisation and compatibility with older tutorials or profiles |
| A320neo V2 | Newer iniBuilds package with deeper Airbus procedures | More realistic built-in gate-to-gate operation |
| Third-party A320 | Separate add-on whose depth and platform support vary | Specific variants, airline procedures or additional system detail |
Settings, liveries and control profiles made for the original A320neo do not necessarily work with V2. Select the entry explicitly labelled V2 when following a V2 checklist or tutorial.
Is the A320neo V2 included with MSFS 2024?
Yes. The A320neo belongs to the standard MSFS 2024 aircraft set, so it is included across the simulator’s editions rather than being restricted to Premium Deluxe or Aviator Edition. Our MSFS 2024 aircraft and edition breakdown shows where it sits in the complete fleet.
If it is missing, first update Microsoft Flight Simulator 2024 and check that the aircraft package is enabled in the simulator’s content library. MSFS 2024 can stream aircraft data, so being entitled to the aeroplane does not always mean every file is stored locally.
What commonly goes wrong when flying the V2?
Most A320neo V2 problems come from applying procedures or controller profiles made for the older default aircraft.
- Throttle detents are misaligned: calibrate the throttle through the V2’s electronic flight bag and remove duplicate axis assignments. Incorrect CL, FLEX/MCT or TOGA positions can prevent autothrust from behaving properly or leave the PFD showing
LVR CLB. - The route is incomplete: loading a World Map flight plan does not necessarily finish the Airbus setup. Check the MCDU for discontinuities, weights, cruise level, take-off data and incomplete PERF pages.
- Managed and selected modes are confused: Airbus push and pull actions command different modes. Confirm the indication on the flight mode annunciator rather than assuming the autopilot accepted an FCU input.
- The wrong checklist is used: legacy A320neo and third-party A320 instructions may refer to switches, tablet pages or system behaviour that do not match V2.
For a complete power-up rather than an automatic runway start, follow our A320neo V2 cold-and-dark sequence.
Is A320neo V2 the same as FlyByWire or Fenix?
No. FlyByWire and Fenix produce separate A320-family add-ons; neither name is another label for the Microsoft/iniBuilds V2 aircraft. They have their own models, system logic, installation requirements and platform limitations.
The V2 is the sensible choice when you want an included aircraft that works within the standard MSFS 2024 environment on supported platforms. A specialist PC add-on may suit pilots seeking a particular engine variant, airline-specific functions or deeper failure and maintenance simulation. Our comparison of the bundled and add-on A320s sets out those trade-offs without treating “study level” as a single fixed standard.