Learn to fly the A320neo V2 in MSFS 2020, from cold start and MCDU setup to managed climb, approach, landing and common fixes.
To fly the Airbus A320neo V2 in Microsoft Flight Simulator 2020, prepare the aircraft and EFB, initialise the MCDU, start the engines, use managed speed and navigation after take-off, configure progressively for approach, then land with a small nose-up attitude and use reverse thrust and braking.
Which A320neo is the V2 in MSFS 2020?
The V2 is the iniBuilds-developed Airbus listed separately from the original default A320neo in the aircraft selector. Its cockpit systems, EFB and handling workflow differ from the older aircraft, so check that the selected name includes A320neo V2.
If it is missing, install or update its package through the simulator's content system. Our guide to installing the iniBuilds A320 in MSFS 2020 covers the aircraft selection and installation checks.
Before flying, remove duplicate throttle bindings and disable any piloting assistance that tries to control the aircraft. Hardware throttle users should also calibrate the idle, climb, flex and TOGA detents in the EFB; an incorrectly calibrated climb detent is one of the most common reasons autothrust appears broken.
How do I complete a full A320neo V2 flight?
A reliable A320neo V2 flight follows the normal Airbus flow: power and alignment, MCDU preparation, engine start, take-off, managed climb, descent, approach and shutdown.
Establish electrical power. Set the parking brake, switch BAT 1 and BAT 2 on so their OFF lights extinguish, and connect external power if it is available. Switch the three ADIRS selectors to NAV early because alignment may take time, depending on the realism setting.
Set fuel, payload and ground equipment. Use the EFB to load the aircraft, confirm the centre of gravity and manage doors, chocks or ground services where those functions are available. Do this before entering final performance data because changing the load can alter the take-off figures. Our A320neo V2 EFB walkthrough explains the tablet pages and loading workflow.
Program the MCDU. Enter the departure and destination, cruise level, cost index, departure runway, SID, arrival, STAR and approach. Add zero-fuel weight, centre of gravity, block fuel, take-off flap setting, trim and V1, VR and V2 data as required.
Review the flight-plan page from top to bottom. Remove a discontinuity only when the legs on either side should connect; do not automatically delete a MANUAL or vector leg expected in the real procedure. For the complete page sequence, use our guide to setting up the A320neo MCDU.
Prepare for engine start. Close the doors, turn the fuel pumps on and start the APU. Once APU AVAIL appears, select APU bleed and disconnect external power if appropriate. Switch the beacon on before starting or pushing back.
Start the engines. Set the engine mode selector to IGN/START, turn engine 2 master on and wait until the engine stabilises. Start engine 1 in the same way, return the mode selector to NORM, switch APU bleed off and shut down the APU when it is no longer required.
Configure for taxi. Select the calculated take-off flap setting, normally Flaps 1 for a routine departure, and set the pitch trim shown in the take-off data. Arm the ground spoilers, select MAX autobrake, check the flight controls and press the TO CONFIG test button. Release the parking brake only after confirming that the route and taxi clearance are understood.
Take off. Line up, switch the landing lights on and set the transponder or TCAS to its operating mode. Hold the brakes, stabilise both engines near 50 percent N1, release the brakes and move the thrust levers into the calculated FLX/MCT detent or TOGA.
Check the Flight Mode Annunciator at the top of the Primary Flight Display. It should show MAN FLX or MAN TOGA. At VR, rotate smoothly at about 3 degrees per second towards roughly 15 degrees nose-up, then select gear up after establishing a positive climb.
Climb in managed mode. At thrust-reduction altitude, move the levers back to the
CLdetent. Retract each flap stage when the relevant speed marker permits, rather than retracting everything immediately. Engage AP1 once the aircraft is safely climbing and confirm that NAV and the expected vertical mode appear on the FMA.Begin the descent. Before the top of descent, check the arrival, approach, constraints and landing data. Set the cleared lower altitude on the FCU and push the altitude control for managed descent. Pulling it commands an open descent instead, which disregards programmed altitude constraints.
Configure for approach. Allow the approach phase to activate near the deceleration point, or activate it manually when being vectored and genuinely ready to slow. Select Flaps 1 below the permitted speed, then Flaps 2, gear down and Flaps 3 or FULL as speed decreases. Never chase the flap schedule by extending above the displayed limit.
For an ILS, confirm that the correct approach is inserted, display the landing system information and select APPR while established on a sensible intercept below the glideslope. AP1 can fly a coupled approach; selecting AP2 does not guarantee an autoland unless the runway, signal and aircraft indications support it.
Land and decelerate. Disconnect the autopilot when comfortable, keep the flight directors and autothrust as required, and follow the target speed. Near 30 feet, make a small flare by increasing pitch only a few degrees. Move both thrust levers to idle at the RETARD call, touch down on the main wheels and lower the nose gently.
Confirm spoiler deployment, apply reverse thrust and let the selected autobrake work. Reduce reverse as the aircraft slows, then brake manually for the runway exit. Retract the flaps and disarm the spoilers only after leaving the runway.
Shut down at the stand. Set the parking brake or use chocks, start the APU or connect external power, and turn both engine masters off. Switch off the beacon, fuel pumps and unnecessary lights. Turn the ADIRS selectors and batteries off last if the aircraft is being fully secured.
What do push and pull mean on the Airbus autopilot?
Push selects managed guidance; pull selects a pilot-selected value. Managed speed, heading and altitude modes follow MCDU targets and route constraints, while selected modes follow the number shown in the FCU window.
- Push the heading knob to request NAV mode and follow the programmed lateral route.
- Pull the heading knob to fly a heading selected on the FCU.
- Push the altitude knob for a managed climb or descent that observes valid constraints.
- Pull the altitude knob for open climb or open descent towards the selected altitude.
- Push the speed knob to use the MCDU's managed speed target.
- Pull the speed knob to command a selected speed.
The FMA, not the knob position or route line, is the final authority on what the aircraft is doing. Our detailed Airbus autopilot and FCU guide explains these modes and the indications to expect.
Why will the A320neo V2 not follow the flight plan?
The A320neo V2 usually fails to follow a route because NAV has not captured, the flight plan contains a discontinuity, or the aircraft is not positioned to intercept the active leg.
If the FMA shows HDG rather than NAV, select a heading that intercepts the magenta route at a shallow angle and then push the heading control. Check the MCDU for an incorrect active leg, a route gap or a missed departure selection. Importing a plan from the MSFS World Map does not remove the need to verify every leg in the aircraft.
Common A320neo V2 problems and fixes
| Problem | Likely cause | Fix |
|---|---|---|
| Autothrust does not control speed | Thrust levers are outside the CL detent or calibrated incorrectly | Move both levers to CL and recalibrate every detent in the EFB |
| Take-off configuration warning | Flaps, spoilers, pitch trim, brakes or performance data are not set | Correct the item shown and repeat the TO CONFIG test |
| Autopilot disconnects without warning | Control input, a noisy axis or duplicate bindings are overriding it | Centre the controls, increase dead zones if needed and remove conflicts |
| Aircraft will not descend at top of descent | No lower altitude is selected, or the wrong vertical mode is active | Set the cleared altitude, push for managed descent and verify the FMA |
| Displays remain dark | No electrical source, incomplete alignment or dimmed display controls | Check batteries, external or APU power, ADIRS selectors and brightness knobs |
Can I fly the V2 without a cold-and-dark start?
Yes. Select a runway departure or another ready-to-fly state in MSFS 2020, then verify the MCDU route, take-off performance, flap setting, trim and thrust detents before moving. This skips the electrical and engine-start work but does not guarantee that imported route or performance data are complete.
For a first flight, we recommend a short route in clear weather with an ILS at the destination. Learn the thrust detents, FMA and managed modes before adding live weather, failures or a complex arrival.