How do I fly the iniBuilds A321 in MSFS 2024?

To fly the iniBuilds A321 in MSFS 2024, load or enter a route in the MCDU, complete the INIT and PERF data, start the engines, set take-off configuration, use FLEX or TOGA thrust, then manage climb, descent and approach through the FCU while checking the PFD flight-mode annunciator.

The procedure is broadly the same on every Microsoft Flight Simulator 2024 platform where the aircraft is available, although mouse, controller and cockpit-interaction inputs differ. If you are unsure which model your edition provides, see our breakdown of the included iniBuilds A321 variants and access requirements.

What is the easiest way to learn the iniBuilds A321?

Start from a parking stand with the aircraft powered, or use a runway-ready state for the first flight. Pick a short route in clear weather, disable AI piloting and assisted landing, and avoid online ATC until you can control the thrust detents and read the flight-mode annunciator.

A runway start skips the electrical, inertial-reference and engine-start work, but it does not teach you why the aeroplane sometimes refuses to follow a route. Once take-off, FCU operation and landing feel comfortable, repeat the flight from cold and dark.

How do I set up and fly the A321 from cold and dark?

1. Check the controls. Confirm that pitch, roll, rudder, brakes, nose-wheel steering, spoilers and throttle axes move in the correct direction. Remove duplicate bindings and calibrate the Airbus throttle detents if the aircraft's tablet offers that facility. An incorrect CL detent is one of the main reasons autothrust appears broken.
2. Load fuel and payload. Use the aircraft's tablet or loading system where available, then allow the load to finish before entering performance data. Do not change the MSFS fuel sliders halfway through the setup because the MCDU figures may no longer match the aircraft.
3. Establish electrical power. Switch on the batteries and connect external power, or start the APU. Set the three inertial-reference selectors to NAV and allow alignment to complete. Confirm that the aircraft position is valid before expecting NAV mode to work.
4. Create or import the route. Enter the origin, destination, runways, departure, airway legs, arrival and approach in the MCDU. A route created outside the cockpit still needs checking; our guide to building and transferring an MSFS flight plan explains the simulator-side process.
5. Complete the MCDU setup. Enter the cost index and cruise altitude on INIT, followed by zero-fuel weight, centre of gravity and block fuel on INIT B. On the PERF take-off page, enter valid V1, VR and V2 speeds, flap configuration, trim and FLEX temperature where applicable. Do not reuse speeds from a different weight or runway. Our Airbus MCDU programming walkthrough covers the shared A320-family workflow in detail.
6. Inspect the flight plan. Step through every leg on the display. Remove only unintended discontinuities; a discontinuity associated with radar vectors or a manual leg may be deliberate. Check for sharp turns, duplicate waypoints and an arrival that sends the aircraft back towards the airport.
7. Prepare the FCU and cockpit. Set the initial cleared altitude, arm the flight directors and confirm that the required lateral mode is available. Set take-off trim, select the planned flap setting, arm the spoilers and select the appropriate take-off autobrake setting. Close the doors and complete the ECAM take-off configuration check.
8. Start the engines. With the beacon on, APU available and APU bleed supplying air, place the engine mode selector at IGN/START. Start engine 2 and then engine 1, monitoring each until stable before starting the next. Return the selector to NORM, configure the bleeds and switch off the APU after its cooling period.
9. Taxi carefully. Release the parking brake, test the brakes immediately and use only enough thrust to start moving. The A321 often needs little or no added thrust once rolling. Before entering the runway, verify flaps, trim, spoilers, flight controls, cabin status, transponder and the absence of a red take-off configuration warning.
10. Take off. Align on the centreline, let the engines stabilise at intermediate thrust, then move both levers together into FLEX/MCT or TOGA. Use FLEX only when a valid FLEX temperature has been calculated. Rotate smoothly at VR, establish the initial climb attitude and retract the landing gear after a positive rate is confirmed.
11. Set climb thrust. When LVR CLB appears, move the levers to the CL detent. The levers then remain there while autothrust commands the required engine power. Retract the flaps on schedule using the PFD speed cues and engage the autopilot once the aircraft is stable and above its minimum engagement height.

How do the A321 managed and selected modes work?

Managed mode follows targets calculated by the flight-management system, while selected mode follows a value chosen on the FCU. In Airbus terminology, pushing a knob normally requests managed guidance and pulling it requests selected guidance, although the exact mouse gesture depends on the MSFS cockpit-interaction mode.

• Managed NAV: follows the lateral MCDU route.
• Selected heading: flies the heading shown in the FCU window.
• Managed climb or descent: follows the computed vertical profile, subject to the altitude selected on the FCU.
• Open climb or descent: disregards the calculated vertical path and uses the selected altitude with an appropriate climb or descent speed target.
• Selected speed: uses the speed displayed in the FCU window rather than the MCDU target.

The coloured text across the top of the PFD—the flight-mode annunciator or FMA—is the final authority. Do not assume the aircraft captured NAV, the localiser or the glideslope merely because you pressed a button. Our explanation of Airbus FCU, autothrust and autopilot modes covers these indications and the push-versus-pull logic.

How do I descend and land the iniBuilds A321?

Prepare the arrival before top of descent, then command a lower altitude and verify the resulting mode on the FMA. Managed descent follows the calculated profile; selected vertical speed or open descent is more useful when ATC requires an early descent, a level segment or a specific rate.

1. Load the arrival. Select the landing runway, STAR and approach in the MCDU, then inspect the revised route for discontinuities or an incorrect transition.
2. Complete PERF APPR. Enter the destination pressure setting, temperature, wind and approach minima. Confirm the landing configuration and resulting approach speed rather than guessing them.
3. Intercept the approach correctly. For an ILS, display the landing system information and arm APPR when cleared and established on a sensible intercept. Approach from below the glideslope; an aircraft that is high, too close or approaching from the wrong side may not capture it.
4. Configure in stages. Use the green-dot, S and F speed references, remain below each flap limit, lower the landing gear and progress through the flap settings. Arm the spoilers, select landing autobrake as required and confirm that the landing memo has no unresolved items.
5. Flare and stop. Disconnect the autopilot for a manual landing unless you have deliberately configured and monitored an autoland. Make a small flare near the runway, bring the thrust levers to idle at the retard callout, lower the nose without holding it off excessively, then use reverse thrust and braking as required.

Why will the iniBuilds A321 not follow the route or autothrust?

Most guidance failures come from incomplete MCDU data, the wrong FCU mode or throttle levers sitting outside the expected detent. Diagnose the active mode from the FMA before pressing more buttons.

Can I fly the A321 without programming the whole MCDU?

Yes, for a basic manual or heading-mode flight, but managed navigation, calculated performance and a dependable descent require proper MCDU setup. A runway-ready aircraft with selected heading, speed and altitude is useful for practising take-offs and landings; it is not a substitute for learning the Airbus workflow.