What is the best A320 add-on for X-Plane 11 and 12?

For most pilots, the best A320 add-on for X-Plane 11 and 12 is the ToLiss A320neo, provided the edition you buy explicitly supports your simulator version. It offers the strongest balance of Airbus systems, dependable autoflight, useful situation saving and simulator performance. Choose FlightFactor A320 Ultimate when you specifically need an A320ceo.

Which X-Plane A320 add-on should you choose?

Choose ToLiss for the best all-round A320neo; choose FlightFactor when accurately representing an A320ceo is a firm requirement.

Why is the ToLiss A320neo the best overall choice?

ToLiss leads because it combines systems depth with predictable Airbus behaviour during the phases where weaker simulations often fail.

Its strengths include MCDU preparation, altitude and speed constraints, managed descent, autothrust, flight-envelope protections and transitions between managed and selected guidance. It also copes well with route changes, interrupted flights and approach-mode changes, where correct Flight Mode Annunciator behaviour matters far more than exterior detail.

Situation-saving and aircraft-state controls make it practical for repeating an approach or practising an abnormal procedure without flying the entire sector again. It is not a certified training device, but it is well suited to realistic procedural flying.

ToLiss generally places a lighter load on an X-Plane installation than FlightFactor, though scenery, weather, AI traffic, display resolution and other plugins can overturn that advantage. If the default aircraft already struggles at a detailed airport, there may be too little performance headroom for any systems-heavy A320.

When is FlightFactor A320 Ultimate the better choice?

FlightFactor is the better purchase when an A320ceo is non-negotiable and you are prepared to maintain a clean, correctly matched installation.

It rewards proper MCDU preparation, close attention to the Flight Mode Annunciator and disciplined use of managed and selected guidance. Its older engine generation is the deciding advantage when following ceo-specific operating material, recreating an airline fleet or modelling a period before that operator adopted the neo.

Do not choose it merely because “Ultimate” sounds more advanced, and do not compare these aircraft from cockpit screenshots alone. The meaningful differences appear when changing a departure, inserting an arrival, intercepting a vertical path or moving the thrust levers through the Airbus detents.

Does the A320neo versus A320ceo difference matter?

Yes—the variant matters whenever you use airline-specific procedures, performance figures or historical fleet information.

• A320neo: ToLiss models the new-engine generation, with the associated engine behaviour, indications and performance profile.
• A320ceo: FlightFactor represents the older current-engine-option generation.
• Performance planning: Fuel burn, weights, engine indications and performance entries cannot be treated as interchangeable between variants.
• Liveries: Painting a neo in a ceo operator’s colours does not change its engines, systems or performance into those of a ceo.
• Tutorials: The broad Airbus cockpit philosophy transfers, but engine-start timing, thrust settings, ECAM indications and some operating details may not match another variant.

What should you check before buying an A320 for X-Plane?

Confirm the exact aircraft variant, simulator build, operating-system support and licence coverage before comparing liveries or visual extras.

• Simulator compatibility: The package must explicitly support X-Plane 11 or X-Plane 12 as appropriate. An aircraft appearing in the selector does not prove that its custom systems and plugins are compatible.
• Update entitlement: Check whether one purchase covers both simulator generations or whether a separate update is required. Do not assume an X-Plane 11 licence includes the X-Plane 12 package.
• Systems depth: Look beyond the exterior model to the MCDU, FCU logic, Flight Mode Annunciator, ECAM, electrical and pneumatic systems, flight protections and failures. Our breakdown of the A320’s FCU, MCDU, displays and ECAM explains the cockpit functions a serious add-on should reproduce.
• Hardware support: Airbus-style throttle quadrants need reliable detent calibration. Home cockpit equipment may also depend on aircraft-specific commands rather than X-Plane’s standard assignments.
• Performance headroom: Judge the aircraft against the scenery, weather and traffic used on a normal flight. Custom avionics add CPU load, while detailed cockpit and exterior textures can expose limited graphics memory.
• Training features: Situation saving, panel-state controls, failure options and clear documentation matter when practising approaches, abnormal procedures or cold-and-dark operation.

Will an X-Plane 12 A320 work in X-Plane 11?

No, not unless the developer explicitly supplies an X-Plane 11-compatible build. The reverse is also true: loading an older aircraft in X-Plane 12 does not guarantee compatible custom plugins, graphics, systems or flight-model behaviour.

Copying an installed aircraft between simulator folders is particularly risky. Obtain the package intended for the target simulator and follow its supplied update or installation process.

How do you install and configure an A320 add-on correctly?

A clean installation, working aircraft plugins and accurate throttle calibration prevent most faults wrongly blamed on the A320 itself.

1. Use the correct package: Download the build supplied for your simulator and licence. Do not copy an old X-Plane 11 installation into X-Plane 12 or merge an update over a heavily modified aircraft folder.
2. Extract the complete aircraft: Follow the supplied installer when one is provided. Otherwise, place the extracted folder beneath X-Plane 11/Aircraft/ or X-Plane 12/Aircraft/. Do not run it from the compressed archive or leave it inside unnecessary nested folders. Our folder and extraction guidance for X-Plane 11 and 12 covers these common mistakes.
3. Keep bundled plugins in place: Aircraft-specific plugins normally remain inside the aircraft package. Do not move them to X-Plane’s global plugins folder unless the manual expressly requires it.
4. Authorise and test the base aircraft: Complete any required activation, then reload the aircraft or restart X-Plane when instructed. Test without third-party sound packs, scripts, cockpit modifications or extra liveries before adding them one at a time.
5. Create a dedicated control profile: Remove duplicate throttle, reverse, speedbrake, tiller and brake assignments. Two devices commanding the same axis commonly cause flickering or uncommanded movement.
6. Calibrate the thrust detents: Calibrate the axes in X-Plane and then use the aircraft’s own controls to define IDLE, CL, FLX/MCT and TOGA where supported. Check axis reversal and watch the virtual levers for jumping. Our multi-engine throttle setup instructions cover duplicate bindings and calibration in more detail.
7. Keep navigation data consistent: Match the aircraft’s AIRAC cycle with the source used to create the route. Different cycles can produce missing waypoints, renamed procedures and runway data that no longer agree.

What do common A320 faults usually mean?

Each symptom has a different first check, so reinstalling the entire aircraft should not be the automatic response.

Is there a good freeware A320 for X-Plane 11 or 12?

Freeware A320 files can be useful for casual flying, visual models and AI traffic, but we do not rank any freeware aircraft in our library alongside ToLiss or FlightFactor for complete MCDU, autoflight and systems simulation.

Check whether a download is actually pilotable before installing it. The older XPFW A320 package intended for AI traffic, for example, illustrates why an A320 model should not be mistaken for a study-level aircraft with a working virtual cockpit. Older packages also need explicit compatibility confirmation before use in X-Plane 11 or 12.