Fly the iniBuilds A350 in MSFS 2024: set up the FMS, use Airbus managed modes correctly, and handle take-off, descent and landing.
To fly the iniBuilds A350 in Microsoft Flight Simulator 2024, load or build a route in the aircraft’s FMS, complete the take-off performance data, then use Airbus managed guidance for climb, cruise and descent. Keep the thrust levers in the correct detents, monitor the FMA, and practise first in clear weather at a long runway.
What should I set up before taxi?
Set the aircraft’s state, fuel, payload and controls before programming the performance pages. Changing the runway, mass or weather afterwards can invalidate the take-off speeds and flex-temperature calculation.
- Choose an aircraft state: for the first flight, use a ready state if the aircraft offers one. Starting from an unpowered gate is more realistic, but it adds electrical, ADIRS, APU and bleed-air work; our complete cold-and-dark A350 start sequence covers that separately.
- Load fuel and payload: use the aircraft’s EFB or loading interface rather than changing the mass after completing the FMS performance entries. Avoid carrying full fuel for a short practice sector.
- Check assistance settings: disable AI piloting, assisted take-off and assisted landing if they interfere with the throttles, rudder or flight controls. Visual navigation aids can remain enabled.
- Test the controller: confirm pitch, roll, rudder, brakes, nosewheel steering and throttle axes move in the correct direction. Calibrate the Airbus throttle detents and remove duplicate throttle or brake bindings.
- Use the checklist: the A350 has enough interdependent systems that skipping one item can create a fault several minutes later. Our phase-by-phase A350 checklist workflow explains the cockpit preparation, departure, approach and shutdown sequence.
The EFB layout and some control interactions may change between aircraft updates, but the underlying Airbus workflow remains the same.
How do I program the A350 FMS?
Build or import the route, initialise the aircraft, select the runways and procedures, then complete the weight and performance pages. Do not assume that a route created in the MSFS 2024 world map has transferred perfectly into the A350’s custom avionics.
- Initialise the flight: enter or confirm the origin, destination, aircraft position, flight number, cost index and planned cruise level.
- Build the route: select the departure runway and procedure, add the en-route waypoints or airways, and choose the expected arrival and approach.
- Inspect every leg: look for route gaps, unexpected turns and duplicate waypoints. Remove a discontinuity only when the next leg is genuinely meant to connect; a vectors segment may be intentional.
- Verify the weights: check zero-fuel weight, centre of gravity and block fuel against the loaded aircraft. A route can be valid while its performance data is not.
- Calculate take-off performance: use the EFB performance page for the selected runway and conditions, then enter or confirm V1, VR, V2, flap configuration, flex temperature and trim data requested by the FMS. Recalculate after changing runway, weather, anti-ice use or aircraft mass.
- Set the initial clearance: put the cleared altitude in the FCU, confirm the flight directors and check that the first lateral leg makes sense before taxiing.
How do Airbus managed and selected modes work?
On the A350, pushing an FCU knob normally requests a managed FMS mode, while pulling it requests a pilot-selected mode. The Flight Mode Annunciator at the top of the primary flight display is the final authority: it shows what the aircraft is actually doing, not what was merely selected.
| Control | Push: managed mode | Pull: selected mode |
|---|---|---|
| Speed | Follows the FMS speed schedule and constraints | Follows the speed selected in the FCU window |
| Heading | Captures or follows the programmed route in NAV when conditions permit | Flies the heading or track selected by the pilot |
| Altitude | Uses the managed climb or descent profile towards the set altitude | Uses open climb or descent towards the set altitude |
After take-off, leave the thrust levers in the CL detent when the aircraft calls for it. Airbus autothrust changes commanded engine power without physically moving the cockpit levers. Moving them above or below the intended detent can limit or override autothrust.
For a fuller explanation of FMS guidance, mode capture and engagement logic, see our Airbus airliner autopilot guide.
Take-off and climb
The critical take-off actions are selecting the calculated thrust setting, rotating smoothly at VR and moving the levers to CL when prompted. Before entering the runway, verify the runway, departure path, initial altitude, flap setting and take-off speeds one final time.
- Line up: centre the aircraft, check the runway heading and confirm there are no warning messages that prohibit take-off.
- Set take-off thrust: stabilise the engines, then move the levers to FLX/MCT when using calculated flex thrust or TOGA when full take-off thrust is required.
- Read the FMA: confirm the expected thrust, SRS and lateral guidance indications. Stop the take-off if the modes or configuration are plainly wrong.
- Rotate at VR: apply a smooth nose-up input rather than pulling abruptly. Establish a positive climb, retract the landing gear and follow the flight-director commands.
- Engage the autopilot: do so once safely airborne and stabilised, if desired. Confirm that the FMA shows NAV or the intended selected heading mode.
- Set climb thrust: when
LVR CLBappears, move the thrust levers into the CL detent and leave them there. - Clean up: retract flaps and slats according to the marked speed schedule, not simply at a guessed altitude. Continue climbing to each cleared altitude.
The A350 is a large aeroplane. Taxi slowly, begin turns with enough room for the main landing gear, and avoid using excessive thrust to start moving because the aircraft will continue accelerating after the engines spool up.
Descent, ILS approach and landing
A successful A350 arrival is prepared before the top of descent by selecting the approach, checking its path and entering the destination weather and minima. Waiting until the aircraft is already high and close to the airport usually leads to excessive speed, speedbrake use and missed captures.
- Prepare the arrival: select the expected arrival and runway, review altitude and speed constraints, and enter the required approach data. Check the route again after making any runway change.
- Start the descent: set the cleared lower altitude and command managed descent at or before the calculated descent point. If the aircraft is high, selected descent or carefully used speedbrake may be necessary.
- Set up the ILS: confirm the correct runway, ILS identifier, frequency and inbound course. Displaying the ILS scales does not itself arm the approach.
- Capture from a sensible position: approach the localiser at a modest intercept angle and normally from below the glideslope. Arm APPR and verify
LOC*followed byLOC, thenG/S*followed byG/Son the FMA. - Configure progressively: reduce speed, select flaps in sequence, lower the landing gear and complete the landing checklist. Do not extend everything early solely to correct a badly planned descent.
- Land: disconnect the autopilot when ready for a manual landing, maintain the approach path and make a small flare. At the retard call, move the thrust levers to idle, touch down on the main gear, lower the nose gently and use reverse thrust and braking as required.
For autoland, arm the required autopilot channels and continue only if the FMA displays the expected landing capability. The selected runway, ILS, aircraft configuration and weather must all support the operation; pressing APPR alone does not guarantee an automatic landing.
Why won’t the iniBuilds A350 follow the flight plan?
The usual causes are an incomplete route, a selected heading mode, an incorrect FCU altitude or thrust levers outside the required detent. Diagnose the active mode from the FMA before changing several controls at once.
- It remains on a heading: selected heading is active, NAV has not captured, or the next FMS leg is invalid. Correct the route and push the heading control for managed NAV when the aircraft is in a suitable capture position.
- It will not descend: the FCU altitude may still be above the aircraft, managed descent was not commanded, or the descent point has already been passed. Set the cleared lower altitude and select the appropriate descent mode.
- Autothrust will not control speed: check that autothrust is armed and the levers are in CL during normal climb, cruise and descent. Also remove duplicate throttle assignments and recalibrate the detents.
- The ILS will not capture: verify the runway and ILS identifier, intercept from below the glideslope, and arm APPR. The LS display button only shows guidance scales.
- Take-off speeds are missing: the runway, aircraft mass or performance fields are incomplete. Recalculate the performance data rather than entering guessed speeds.
- The cockpit is blank or the aircraft never finishes loading: that is an installation or package-streaming problem rather than a flying error. Work through these A350 loading and blank-cockpit checks before rebuilding the flight.
A sensible first A350 practice flight
Choose a short daylight sector between two airports with long runways, light winds and a straightforward ILS. Use a moderate payload, practise the same departure and arrival more than once, and let the autopilot handle the middle of the flight while you concentrate on FMS setup, mode awareness and a stable landing configuration.