What is the Airbus A320 ICAO code in flight simulators?

The ICAO aircraft type designator for the original-engine Airbus A320, often called the A320ceo, is A320. The A320neo uses A20N. In real-world aviation and flight simulators, these codes identify the aircraft in flight plans, online ATC, traffic injection and model matching; they do not select the cockpit or configure its avionics.

Which Airbus A320 ICAO code should I enter?

For an A320 with CFM56 or IAE V2500 engines, enter A320; for an A320neo with LEAP-1A or PW1100G engines, enter A20N.

The aircraft's engines and model determine the code, not its livery or airline branding. Our comparison of A320-family variants covers the related A319, A321 and neo designators.

Where do flight simulators use the A320 type code?

The ICAO code is an identification field used by several simulator and ATC systems.

• Flight plans: It tells ATC and planning software which basic aircraft type is being flown.
• Online ATC: Pilot clients can transmit the code so controllers and other pilots receive the correct aircraft type.
• Model matching: Traffic software uses the type code, often alongside airline and livery data, to choose a visible AI model.
• Aircraft metadata: Depending on the simulator and add-on, the code can appear in package configuration, traffic data or ATC labels.
• Performance profiles: Planning tools may use the designator as an initial filter, although an exact add-on profile is still needed for reliable weights, fuel and performance.

If a form asks only for the aircraft type, enter A320 or A20N. A complete ICAO Item 9 entry may appear as A20N/M, with M indicating the wake-turbulence category. Do not paste that full string into a box that accepts only the four-character type designator.

Is A32NX or 32N the ICAO code?

Neither A32NX nor 32N is the ICAO type designator for an A320neo; the correct code is A20N.

A32NX is a simulator project and package name. The aircraft represented by the MSFS A32NX package listing is an A320neo, so its flight-plan type should be A20N. Package names are not automatically valid aviation codes.

320 and 32N are IATA equipment codes used in airline schedules and booking systems. They are easily confused with ICAO designators, but an ICAO aircraft-type field requires A320 or A20N.

Why does the wrong code cause model-matching problems?

An incorrect code can make traffic software display the wrong A320 version, substitute a generic aircraft or fail to show a model at all.

Filing A320 for a neo may produce an original-engine A320 on other users' screens. Conversely, a model matcher without an installed A20N model may deliberately fall back to A320; that fallback does not mean A320 is the correct neo designator.

How do I fix an A320 or A20N mismatch?

1. Identify the simulated variant. Check the aircraft selector and add-on description. CFM56 or V2500 engines indicate A320; LEAP-1A or PW1100G engines indicate A20N.
2. Correct the flight-plan field. Replace package names, IATA codes or guessed abbreviations with the official four-character ICAO designator.
3. Refresh the connected system. Refile or reload the flight plan, traffic injector or pilot client. Some software caches the aircraft type until the session or traffic is refreshed.
4. Check local model rules. If the filed code is correct but the displayed aircraft is not, the missing or misconfigured model-matching rule is the problem.
5. Select the precise performance profile separately. The ICAO code distinguishes the broad type; it does not define the exact engine, cabin layout, operating weight or add-on flight model.

You normally do not enter A320 or A20N into the MCDU to configure the aeroplane. The simulated airframe and performance database come from the loaded aircraft package; our practical A320 cockpit workflow for Microsoft Flight Simulator explains that separate setup process.