How do I install the Fenix A320 in MSFS?

To install the Fenix A320 in Microsoft Flight Simulator, use its own installer or desktop app instead of copying files into Community yourself. Sign in with your purchase account, point the installer to the MSFS packages folder if asked, finish setup, then launch MSFS and confirm the aircraft appears in the Airbus list.

Why is the Fenix A320 installation different?

The Fenix A320 is installed with its own desktop app, not as a simple drag-and-drop aircraft package.

That matters because the installer handles more than one file set. It has to place the aircraft in the correct MSFS packages location and install the external components the add-on uses. If you only need the standard process for freeware and simpler aircraft, our guide to installing add-on aircraft in MSFS covers the normal Community-folder workflow.

How to install the Fenix A320 in MSFS

The cleanest method is to let the official installer do the whole job from start to finish.

1. Close MSFS first. The initial install and major updates are less likely to leave locked or half-written files behind.
2. Download the official Fenix installer or app. Use the account area tied to your purchase. Do not try to install the aircraft from a copied zip or from a random extracted folder.
3. Sign in with the correct account. If the app cannot validate the purchase, it may not deploy the aircraft package properly.
4. Select the right MSFS packages path if asked. Choose the folder that contains both Community and Official. Do not point it at the MSFS shortcut, the launcher executable, or a broad Steam or Xbox app folder.
5. Install all components. Let the app place both the in-sim package and any companion files it needs. Do not move the aircraft folder by hand afterwards.
6. Start the Fenix app if it is not already running. The aircraft depends on its desktop side as well as the in-sim package.
7. Open MSFS and check the aircraft list. Look under Airbus entries and clear any filters that might hide third-party aircraft.

Do you need to use the Community folder manually?

Usually no. The Fenix installer should place the aircraft where it belongs, so manual copying is more likely to break the install than fix it.

A mistake we see often is users unzipping files into Community after the installer has already done its work. That can create duplicate or partial folders, which then leads to missing aircraft, failed updates or a broken model in the menu.

Why is the Fenix A320 not showing in MSFS?

In most cases, the installer was pointed at the wrong packages path or the installation was blocked before it finished.

• Wrong target folder: the valid path is the MSFS packages location that contains Community and Official.
• Account mismatch: you signed into the installer with a different account from the one that owns the aircraft.
• Security or permissions problem: Windows Defender, antivirus or folder permissions stopped some files from being written.
• Leftover older files: a partial older install can interfere with a fresh one.
• Aircraft filters in the menu: the aircraft selector can hide third-party aircraft if filters are active.

If the package looks installed but the aircraft still does not appear, use our detailed fix for add-on aircraft that are missing from Microsoft Flight Simulator after installation.

Can you install the Fenix A320 on Xbox?

No. The Fenix A320 is a PC add-on because it relies on software outside the console environment, so its installer does not work the way Xbox Marketplace aircraft do.

How do you install Fenix A320 liveries?

Install liveries only after the base aircraft loads correctly in MSFS.

Most Fenix liveries are separate packages, and the same folder-path mistakes apply. If you need the generic method, our MSFS livery installation guide shows the usual package structure and the common reasons a repaint does not appear.