Fly the Airbus A330 in X-Plane 12 from cold and dark to landing, with MCDU setup, throttle detents, managed modes and common-error fixes.
To fly the Airbus A330 in X-Plane 12, power the aircraft, initialise the MCDU route and performance pages, start the engines, taxi with the thrust levers near idle, take off in FLX/MCT or TOGA, then use managed autopilot modes for climb, cruise, descent and approach while checking every Flight Mode Annunciator change.
Which A330 does this procedure cover?
This procedure is written for the A330-300 included with X-Plane 12. Third-party A330 aircraft may use different tablets, performance tools and system logic, so follow the documentation supplied with the installed aircraft where it conflicts with the stock model.
Before loading at the gate, assign and calibrate pitch, roll, yaw, toe brakes and throttle axes. Our instructions for calibrating X-Plane 12 controls and removing conflicting assignments cover the essential setup. A noisy throttle axis can pull the levers out of the CL detent and make the autothrust appear faulty.
A330 flight procedure from cold and dark
A normal X-Plane 12 A330 flight is completed in the following order, with the MCDU and Flight Mode Annunciator checked at every phase.
- Set payload and fuel. Load the planned passengers, cargo and block fuel before calculating take-off performance. Changing the mass afterwards invalidates the centre of gravity, trim and V-speeds.
- Establish electrical power. Switch on both batteries and connect external power, or start the APU and place its generator online. Set the inertial reference selectors to NAV and allow alignment to finish. For the complete switch sequence, use our cold-and-dark A330 power and engine-start procedure.
- Programme the MCDU. Enter the origin and destination, flight number, cost index and cruise level. Build or import the route, select the departure runway and SID, and inspect every leg. Delete a discontinuity only when the legs on either side really should connect. Our A330 SimBrief import and MCDU workflow explains route transfer and fuel-data handling.
- Complete performance data. Enter zero-fuel weight, centre of gravity and block fuel, preferably before engine start because some Airbus MCDUs restrict the secondary INIT page afterwards. On the take-off page, enter the planned flap setting, trim, transition altitude, thrust-reduction and acceleration altitudes, V1, VR and V2. Use speeds calculated for the actual runway, mass and weather; fixed example speeds are unsafe and often produce poor rotation behaviour.
- Start the engines. Turn on the beacon and fuel pumps, confirm APU bleed air is available, then set the engine mode selector to IGN/START. Start engine 2 followed by engine 1, monitoring N2, fuel flow, EGT and stable idle. Return the selector to NORM, configure the bleed system and shut down the APU when it is no longer needed.
- Configure and taxi. Check the flight controls, set the calculated pitch trim and take-off flaps, arm the spoilers and select maximum take-off autobraking. Release the parking brake and use idle thrust where possible; apply only enough breakaway thrust to start moving. The A330 gathers speed slowly but carries considerable momentum, so brake early rather than riding the brakes continuously.
- Take off. Line up, stabilise the engines at roughly 50 per cent N1, then move both levers positively into FLX/MCT if a valid flex temperature is entered, or TOGA if full thrust is required. Confirm MAN FLX or MAN TOGA on the Flight Mode Annunciator. At VR, rotate smoothly at about 3 degrees per second and follow the flight-director pitch command. Select gear up after a positive climb.
- Climb and cruise. At thrust-reduction altitude, move the levers to the CL detent and leave them there while autothrust is active. Retract the flaps on schedule using the F and S speed indications, then engage the autopilot once the aircraft is stable. Set each cleared altitude on the FCU and select the intended managed or open-climb mode; merely turning the altitude knob does not command a climb.
- Descend and approach. Enter destination weather, landing runway, approach, minimums and landing configuration in the MCDU. At the calculated top of descent, set the cleared lower altitude and push the altitude knob for managed descent. For an ILS, verify the frequency and course, display the landing system and arm APPR while established on a sensible intercept below the glideslope.
- Land and shut down. Reduce speed early, extend flaps in stages below their limiting speeds, lower the gear and stabilise at VAPP. At the RETARD call, bring both thrust levers to idle; after touchdown, use reverse thrust, spoilers and braking while maintaining the centreline. Our detailed A330 flare, autoland and rollout guidance covers the final approach and go-around decisions. At the stand, set the parking brake, establish ground or APU power, switch off both engine masters, then secure the fuel, lights, inertial reference system and batteries.
How do Airbus managed and selected modes work?
On the Airbus FCU, pushing a knob normally asks the aircraft to use an MCDU-managed target, while pulling it selects a pilot-controlled target. Always confirm the result on the Flight Mode Annunciator; the panel setting alone does not prove that a mode has engaged.
| FCU control | Push for managed | Pull for selected |
|---|---|---|
| Speed | Uses the MCDU speed schedule | Uses the speed shown in the FCU window |
| Heading | Arms or engages NAV to follow the active route | Commands the selected heading or track |
| Altitude | Uses managed climb or descent and observes the programmed profile | Uses open climb or open descent towards the selected altitude |
| Vertical speed | Returns towards managed vertical guidance when available | Commands the selected vertical speed |
Open modes can leave the programmed vertical profile and require closer monitoring of restrictions. Green FMA text shows an active mode, while blue normally indicates an armed mode waiting for its capture conditions.
How should you hand-fly the X-Plane 12 A330?
Hand-fly the A330 with small, deliberate side-stick inputs and allow its fly-by-wire system to stabilise the response. In normal operation, automatic pitch trim handles routine trimming, so repeatedly moving the manual trim wheel can create an unwanted out-of-trim condition.
Do not chase every small flight-director movement. Centre the stick as the desired attitude develops, anticipate the aircraft's inertia and make power changes early. During rotation, an abrupt pull can produce excessive pitch; during the flare, a large flare can cause a float and long landing.
Why will the A330 not follow the flight plan or autopilot?
Most A330 guidance failures come from an incomplete route, the wrong FCU mode or thrust levers outside the expected detent rather than a broken autopilot.
| Symptom | Likely cause and fix |
|---|---|
| The aircraft ignores the magenta route | Check for a discontinuity, an incorrect active leg or selected heading mode. Use an appropriate direct-to if required, then push the heading knob and verify NAV on the FMA. |
| It will not climb or descend | Set the new altitude, then push or pull the altitude knob deliberately. Check for an altitude constraint and confirm CLB, DES, OP CLB or OP DES on the FMA. |
| Autothrust does not control speed | Place both levers exactly in the CL detent after take-off. Recalibrate the axes and remove duplicate throttle bindings if the virtual levers flicker or move by themselves. |
| The engines will not start | Confirm pneumatic pressure, APU bleed, fuel pumps, IGN/START and the relevant engine master. An APU that is merely running may not have its bleed air selected. |
| The ILS does not capture | Verify the correct ILS frequency and front course, arm APPR and intercept the localiser at a shallow angle from below the glideslope. APPR mode cannot recover a poor intercept reliably. |
| Managed speed remains too fast | Check that the arrival and approach are inserted and that the approach phase has activated. Activate it manually near the appropriate point if required, but not early in the descent. |