Download and install the free iniBuilds A320neo V2 in MSFS 2020, find it in Content Manager, and fix common missing-aircraft problems.
In Microsoft Flight Simulator 2020, download the iniBuilds A320neo V2 from the in-simulator Marketplace, where it is a free official aircraft. Claim it, download the package, then restart the simulator if it does not appear. Do not use iniManager or copy this official version into the Community folder.
Where do I download the iniBuilds A320neo V2?
The official iniBuilds A320neo V2 for MSFS 2020 is distributed through the simulator's Marketplace. It was introduced with Sim Update 15, so update the simulator before looking for it.
Search the Marketplace for A320neo and identify the aircraft whose name includes V2 and whose developer is iniBuilds. If your account has already claimed it, the package may appear in Content Manager rather than showing another acquisition button.
How do I install the iniBuilds A320 in MSFS 2020?
A fully updated simulator and a signed-in simulator account are the only prerequisites.
- Update MSFS 2020: Allow your platform client and the simulator's installation manager to complete any pending updates.
- Open the Marketplace: Start MSFS 2020, enter the in-simulator Marketplace and search for A320neo.
- Claim the V2 aircraft: Open the iniBuilds product page and select the free claim or purchase option. Button wording can differ depending on whether the account already owns it.
- Download the package: Select the download or install option and leave the simulator running until it reports completion.
- Check Content Manager: From the main menu, open Profile and then Content Manager. Search for A320neo and confirm that the V2 package is marked as installed. Our guide to Content Manager filters and installation statuses explains what each state means.
- Select the correct aircraft: Restart MSFS 2020, open the World Map and choose the A320neo entry marked V2 from the aircraft selector.
The procedure is the same on PC and Xbox. Xbox users must use the Marketplace route because consoles do not support manual Community-folder installation.
Which A320 should I select after installation?
Select the aircraft whose name contains A320neo V2; the older default A320neo can remain installed alongside it.
| Aircraft | Developer | Installation source |
|---|---|---|
| Original A320neo | Asobo | Base simulator content |
| A320neo V2 | iniBuilds | Free in-simulator Marketplace package |
The two aircraft use different systems and package structures. Liveries or modifications made for the original A320neo may not work with the iniBuilds V2 unless their description explicitly names that model.
Why does the iniBuilds A320 not appear?
A missing A320neo V2 usually means the package is owned but not downloaded, the simulator needs updating, or an aircraft-selection filter is hiding it.
- Search Content Manager: Remove its filters, search for A320neo and install any package shown as owned but not installed.
- Check online functionality: The Marketplace requires the simulator's online services to be enabled and the account to be signed in.
- Restart MSFS: Aircraft lists do not always refresh immediately after a large package finishes installing.
- Clear aircraft filters: In the World Map aircraft selector, remove favourites, manufacturer or aircraft-type filters that could hide the V2 entry.
- Test without conflicting add-ons: On PC, temporarily remove older A320 modifications and incompatible liveries from the Community folder. A package designed for the original A320neo can interfere with the V2.
- Reinstall through Content Manager: If the package is listed as installed but remains unavailable, uninstall and download it again from Content Manager rather than deleting files from the Official content folders.
Can I install the iniBuilds A320 manually?
No manual installation is required for the official iniBuilds A320neo V2. It is managed as Marketplace content, so an archive copied into the Community folder or an iniManager installation is not the correct package.
Only independently distributed aircraft use the Community-folder method. For those packages, follow our manual add-on aircraft installation procedure and verify that the extracted package has the correct folder structure.