What are the best Airbus A320 add-ons for Prepar3D?

Recommendation checked 26 October 2026: for Prepar3D v4.5 or v5, Flight Sim Labs A320-X is the high-fidelity choice; Aerosoft A320/A321 Professional is better for everyday airline flying; François Doré’s FD-FMC package is the best freeware starting point. Credible supported choices exist for v4.5 and v5, but not v6.

Best Prepar3D A320 add-ons compared

The deciding factors are your exact Prepar3D release, the systems depth you want and whether you need an aircraft with formal developer support.

FSLabs A320 P3D: which package do you need?

Buy the base Flight Sim Labs A320-X package for the classic A320 in Prepar3D v4.5 or v5. It supplies the A320-214 with CFM56 engines and the A320-232 with IAE V2500 engines. The A319-X and A321-X products are optional expansions, not substitutes for the required A320-X base package.

Use the installer and licence intended for your P3D generation. The old P3D v3 build is 32-bit, while the v4.5 and v5 builds are 64-bit; those binaries are not interchangeable. A P3D v5 installation must not be copied into v6.

Why is the FSLabs A320-X more realistic?

The difference is in the interaction between systems rather than the number of clickable switches. Its FMGS models Airbus lateral and vertical modes, predictions, constraints and mode reversions closely enough that monitoring the flight-mode annunciator becomes part of flying the aircraft.

ECAM indications are driven by the underlying electrical buses, pumps, valves, bleed-air sources and flight-control state. A fault can therefore affect several connected systems and produce the associated ECAM actions, rather than merely displaying a scripted warning.

Do not buy it for P3D v6, quick sightseeing flights or minimal cockpit preparation. It is also the wrong choice if you do not want to learn Airbus FMGS conventions, managed versus selected guidance and ECAM handling.

Aerosoft A320 P3D: Professional versus Airbus X and Extended

Aerosoft A320/A321 Professional is the correct Aerosoft package for 64-bit Prepar3D v4.5 and v5. It includes both A320 and A321 airframes with CFM and IAE engine choices; it does not require Airbus X, Airbus X Extended or another base product.

The similarly named older releases belong to different simulator generations:

• Airbus X is an original 32-bit FSX product, not a P3D v4, v5 or v6 aircraft.
• Airbus X Extended belongs to the FSX and first-generation 32-bit Prepar3D v1 era. It is not the Professional edition.
• Aerosoft A320/A321 without “Professional” was the later 32-bit line for P3D v2/v3 and FSX. It does not support P3D v4-v6.
• A320/A321 Professional is the 64-bit product for P3D v4.5/v5. It does not support P3D v6.

A mistake we see constantly is treating “Professional” as a patch for Airbus X Extended. It is a separate aircraft generation with different installers and 64-bit components. Our comparison of Aerosoft’s legacy and Professional Airbus generations explains the distinction in more detail.

How realistic is Aerosoft A320/A321 Professional?

It handles the work used on a normal airline sector: MCDU flight-plan entry, departures and arrivals, altitude and speed constraints, managed climb and descent, selected modes, ECAM monitoring, autoland and structured cockpit preparation. That makes it a practical everyday P3D A320.

Its limit is abnormal depth. Not every component, circuit breaker, secondary system or cascading failure is simulated to the level found in FSLabs. Choose Aerosoft when normal gate-to-gate operation matters more than engineering-level failures and edge cases.

What is the best free A320 for Prepar3D?

The strongest freeware starting point is the package titled “FSX Airbus A320-200 with FD-FMC and VC”. It combines the Project Airbus A320 model with François Doré’s FD-FMC integration, a virtual cockpit and support for route procedures. It is a complete archive and does not need a separate A320 installation.

This is still an FSX package, not a supported native P3D aircraft. Its XML-based elements have a reasonable chance of working in P3D v4 or v5, but any compiled gauge must be checked separately. Search the exact package title in our freeware aircraft and add-ons library.

The second legacy archive, Airbus A320-200 Update by Michael Pook, is not a complete aircraft. It updates the panel, configuration and handling of the Project Airbus A320-200 and therefore requires that base aircraft first. It is useful for default-style flying, but it does not provide an Airbus FMGS or realistic systems simulation.

Does any Airbus A320 support Prepar3D v6?

There is no credible, formally supported Prepar3D v6 A320 among the FSLabs, Aerosoft or legacy freeware packages covered here. FSLabs A320-X and Aerosoft A320/A321 Professional stop at P3D v5, while the freeware aircraft were created for FSX.

A model displaying in v6 does not establish compatibility. Native DLL gauges, sound modules, effects, installers and simulator API calls can fail even when the exterior and XML gauges appear to work. Never assume that P3D v5 support also means P3D v6 support.

How do I install a legacy FSX A320 in P3D v4, v5 or v6?

A legacy A320 should be staged and tested component by component rather than installed directly over an existing aircraft.

1. Read the archive documentation. Establish whether it is a complete aircraft, an update, a repaint or a panel package. Install its named base aircraft first if one is required.
2. Extract it outside Prepar3D. Check the contents before allowing an old automatic installer to write into the simulator. Do not point an FSX installer at P3D merely because the folder can be selected.
3. Use a version-specific add-on folder. Where practical, create the package under Documents\Prepar3D v4 Add-ons, Documents\Prepar3D v5 Add-ons or Documents\Prepar3D v6 Add-ons. Our guide to managing P3D add-on.xml packages and external folders covers the safer method.
4. Inspect the model and panel. P3D v4-v6 need an FSX-native or later model. An old FS2004-format .mdl may leave the aircraft invisible. Check every compiled panel gauge before copying it.
5. Keep matched files together. Do not mix the panel, aircraft.cfg and .air files from unrelated A320 releases. That commonly causes unstable pitch, incorrect speeds and autopilot oscillation.
6. Test the unmodified aircraft first. Load a default airport, clear weather and the package’s original livery before adding repaints, sound sets or replacement panels. A detailed Prepar3D aircraft installation checklist can help isolate folder and configuration errors.

What changes between P3D v4, v5 and v6?

• P3D v4: This is 64-bit. FSX-native models and XML gauges may work, but 32-bit .gau files and DLL gauges cannot load.
• P3D v5: This is also 64-bit, but its rendering and simulator interfaces differ from v4. A v4 aircraft may show broken effects, dark materials or failed native modules unless v5 is explicitly supported.
• P3D v6: A v5-compatible binary is not automatically usable. Native modules and gauges need an explicit v6 build or confirmation from their developer.

How can I identify an incompatible 32-bit gauge?

Open panel.cfg and inspect the gauge entries under the window and virtual-cockpit sections. The name before the exclamation mark identifies the gauge container. Locate the corresponding item in the aircraft’s panel folder or Prepar3D’s gauge folders.

• XML gauges are normally stored as XML files inside a folder or cabinet archive. They are generally more portable, although they can still depend on missing fonts, scripts or modules.
• Legacy .gau files are compiled FS-era gauges and should be treated as incompatible with 64-bit P3D unless the documentation explicitly says otherwise.
• DLL gauges may be 32-bit or 64-bit; the extension alone does not tell you. If the documentation lists only FSX or P3D v1-v3, do not load the DLL in v4-v6.
• Load errors may appear as a failed-module or bad-image message. Copying the same binary into another Gauges or Modules folder will not convert it to 64-bit.

Why are the A320 displays blank or the simulator crashing?

After confirming electrical power and display brightness, blank PFD, ND or MCDU screens usually indicate a missing or incompatible gauge. A crash while selecting the aircraft points more strongly to a binary module, sound gauge or panel component that cannot load in that P3D version.

• All displays remain black: restore the package’s original panel, verify battery or external power and then remove unsupported gauges one at a time.
• Aircraft crashes on selection: temporarily remove third-party DLL and .gau components. If the basic model then loads, the panel or module is the fault.
• Exterior is invisible: check that the package uses an FSX-native model and that its model.cfg points to an existing .mdl file.
• Textures or cockpit surfaces are black: suspect an unsupported material, shader or v4-era effect when testing in v5 or v6.
• Autopilot pitches or oscillates: reinstall the matching aircraft.cfg, .air file and panel instead of combining updates from different authors.
• SIDs or STARs are absent: verify the FMC’s own procedure files and AIRAC method. Installing a navigation cycle for a different A320 product will not update FD-FMC.

Once the base aircraft works, add one livery or modification at a time. That keeps a missing texture separate from a gauge failure and makes the faulty component much easier to identify.