Learn to fly the iniBuilds A320neo in MSFS 2024, from MCDU setup and thrust detents to managed descent, ILS landing and common fixes.
To fly the iniBuilds A320neo in Microsoft Flight Simulator 2024, load fuel and payload, initialise the MCDU, set the FCU altitude, start both engines, taxi with the calculated flap setting, take off in FLX/MCT or TOGA, move the thrust levers to CLB, then manage the descent and configure early for landing.
Which A320neo should you select?
The iniBuilds-built aircraft is the more systems-focused A320neo commonly identified as the A320neo V2. Its EFB, MCDU, electrical system and Airbus throttle detents are functional parts of the flight, so procedures written for the older stock A320neo may not match.
If you are unsure which model you have loaded, our comparison of the iniBuilds A320neo and FlyByWire A32NX explains the distinguishing features and platform differences.
What should you configure before the first flight?
Correct control assignments matter more in this aircraft than aggressive sensitivity changes. In particular, the physical throttle position must agree with the Airbus detents shown in the cockpit.
- Assign each sidestick, rudder, brake and throttle axis only once; duplicate gamepad, joystick and keyboard bindings cause many unexplained inputs.
- Calibrate the throttle so IDLE, CL, FLX/MCT and TOGA register reliably. Do not leave the levers between detents.
- Assign reverse thrust separately if your hardware supports it, and check that the levers return cleanly to idle.
- Disable AI piloting and take-off or landing assistance if those features move the controls against you.
- With a controller, watch the animated thrust levers and PFD annunciations because there is no physical detent to feel.
How do you fly the iniBuilds A320neo from gate to gate?
- Load fuel and payload. Use the EFB or simulator loading tools before calculating performance. Record the zero-fuel weight, centre of gravity and block fuel, and avoid changing the load after entering take-off data.
- Power and align the aircraft. Switch on the batteries, connect external power or start the APU, and turn the three ADIRS selectors to NAV. For every overhead-panel action, use our full electrical, APU and engine-start sequence.
- Programme the MCDU. Enter the origin and destination, flight number, cost index and cruise level on INIT A. Check every departure, airway, arrival and runway on the F-PLN page. Remove only discontinuities that should genuinely connect; a vectors discontinuity may be intentional. Enter ZFW/ZFWCG and block fuel on INIT B before engine start, then complete PERF TO with the runway, flap/trim setting, V1, VR, V2 and a valid FLEX temperature if one is available.
- Prepare the FCU and start the engines. Set the initial cleared altitude rather than automatically selecting cruise altitude, check the barometric setting and switch on both flight directors. With the beacon and fuel pumps on, APU available and APU bleed supplying air, set the engine mode selector to IGN/START. Start engine 2 and then engine 1, waiting for each to stabilise before continuing. Return the selector to NORM afterward.
- Configure for taxi. Set the calculated flaps, take-off trim, arm the spoilers and select MAX autobrake. Run the take-off configuration test and resolve any ECAM warning before moving. Steer with the nosewheel or rudder controls, not the sidestick, and avoid riding the brakes.
- Take off. Hold the brakes, stabilise the engines around an intermediate thrust setting, release the brakes and move both levers positively into FLX/MCT when valid FLEX data has been entered, or TOGA otherwise. Confirm the expected thrust and guidance modes on the Flight Mode Annunciator. At positive climb select gear up.
- Climb in managed modes. When
LVR CLBflashes, move the levers back to the CL detent. Retract flaps as the PFD speed cues permit. Engage the autopilot only after the aircraft is stable and following the intended flight-director commands. - Prepare the descent early. Select the arrival, runway and approach before reaching the top of descent. Complete PERF APPR with the destination pressure, temperature, wind and decision height or minimum descent altitude. Set a lower cleared altitude and push the altitude knob at the calculated descent point for managed descent; pull it only when you intentionally want open descent.
- Configure and land. For an ILS, verify the tuned frequency and identifier, display LS information and arm APPR while intercepting from below the glideslope. Extend flaps on schedule, lower the gear and select the planned landing flap setting. If hand-flying, disconnect the autopilot once stable but leave autothrust active. Flare gently, move the thrust levers to idle at the RETARD call, then use reverse thrust, autobrake and manual braking as required. Our detailed A320 ILS and flare procedure covers the final approach in greater depth.
How do managed and selected Airbus modes work?
Push an FCU knob for managed guidance and pull it for a selected value. Mouse interaction zones vary with the cockpit interaction setting, so always confirm the result on the Flight Mode Annunciator at the top of the PFD.
| FCU control | Push for managed mode | Pull for selected mode |
|---|---|---|
| Speed | FMGS target speed | Pilot-selected speed |
| Heading | NAV follows the programmed route when capture conditions are met | HDG or TRK follows the value in the FCU window |
| Altitude | Managed climb or descent using the vertical profile | Open climb or open descent directly towards the selected altitude |
A common mistake is watching the knob rather than the FMA. The FMA is the authoritative indication of what the aircraft is actually doing; our practical explanation of airliner autopilot and Airbus FCU logic shows how to read each mode change.
Why won't the iniBuilds A320neo follow the flight plan?
The usual causes are an unresolved route discontinuity, selected heading mode, a missed waypoint or an incomplete MCDU route. The magenta line alone does not prove that NAV is active.
| Symptom | Likely cause | Fix |
|---|---|---|
| Aircraft flies straight after take-off | HDG is selected or NAV did not arm | Intercept the route, use an appropriate direct-to if needed, then push the heading knob and confirm NAV on the FMA. |
| Aircraft turns away at a waypoint | Discontinuity, incorrect leg or wrong departure | Inspect the F-PLN page and correct the route rather than repeatedly forcing NAV. |
| Autopilot will not engage | Aircraft is unstable or the sidestick is not centred | Stabilise manually, release control pressure and remove duplicate or noisy axis bindings. |
| Autothrust does not control climb speed | Thrust levers are outside the CL detent | Place both levers in CL and recalibrate the throttle if the detent does not register consistently. |
| An engine will not start | No pneumatic air, fuel pumps off or thrust lever not idle | Confirm APU AVAIL, APU bleed on, fuel pumps on, engine mode at IGN/START and both levers at idle. |
| ILS does not capture | Wrong approach, intercept from above or APPR not armed | Verify the ILS identifier, intercept below the glideslope at a sensible angle and confirm LOC and G/S modes on the FMA. |
Can you start the A320neo on the runway?
Yes. A runway start bypasses most cold-and-dark work and is useful for practising take-offs, circuits and landings. Before advancing the thrust, still verify the FCU altitude, barometric setting, flaps, trim, armed spoilers, MAX autobrake, flight directors and take-off configuration.
A runway start does not guarantee that the MCDU contains a usable route. If you intend to use managed navigation, inspect the F-PLN and PERF pages before departure rather than discovering missing data after lift-off.