Skip to content
X-Plane 6 min read

How do I use the A330-300 FMC in X-Plane 12?

Ian Stephens
In short

Learn the X-Plane 12 A330-300 FMC: route entry, SID and STAR selection, fuel and PERF pages, discontinuities and common fixes.

To use the X-Plane 12 A330-300 FMC, initialise the Airbus MCDU, enter or import the route, select departure and arrival procedures, resolve genuine discontinuities, add weight and fuel data, then complete the PERF pages. Check each temporary revision before pressing INSERT; the autopilot will not follow an incomplete or inactive flight plan.

Is the A330 FMC actually an MCDU?

The cockpit unit in the Airbus A330-300 is the MCDU, which provides access to the aircraft's flight management and guidance system. Simmers often call it an FMC, but recognising the Airbus terminology makes its pages and controls easier to understand.

This procedure applies to the default Laminar Research A330-300 in X-Plane 12. Older X-Plane 12 builds used a less complete implementation, so update the simulator if your pages or functions differ substantially. Third-party A330 aircraft may use another system entirely. Our Airbus MCDU page-by-page programming reference explains the underlying workflow in more detail.

How do I program the A330-300 MCDU?

The reliable order is power and alignment, aircraft loading, route entry, procedure selection, route inspection and performance data.

  1. Power the aircraft and align the inertial system. Supply electrical power from an external source or the APU, turn the three inertial-reference selectors to NAV and allow alignment to finish. The MCDU may be dark because it has no power or its brightness is turned down, not because it has failed.
  2. Load the aircraft before entering performance data. Set passengers, cargo and fuel through the aircraft's supported loading controls or X-Plane interface. Changing the load afterwards can make the MCDU's zero-fuel weight, centre of gravity and take-off speeds incorrect.
  3. Complete the INIT page. Enter the origin and destination in the FROM/TO field, normally in a format such as EGLL/KJFK. Add the flight number, cost index and planned cruise level. Type each value into the scratchpad, then press the line-select key beside the intended field.
  4. Build the en-route flight plan. Open F-PLN and enter waypoints or airway segments in route order. The first fix must connect correctly to the selected airway; an airway will be rejected if the entry fix is not part of it.
  5. Select the runway and procedures. Revise the origin to choose the departure runway, SID and transition. At the destination, select the expected runway, STAR, transition and approach. Press INSERT only after checking the temporary revision. For procedure-specific problems, see our guide to loading and checking SIDs, STARs and approaches.
  6. Inspect every leg. Scroll through F-PLN and use PLAN mode on the navigation display where available. Look for duplicated fixes, route reversals, implausible turns and discontinuities. A route that appears correct as text can still contain bad geometry.
  7. Enter weight and fuel figures. On INIT B or the relevant fuel page, enter the actual zero-fuel weight and centre of gravity, followed by block fuel. Use the values loaded into the aircraft, not figures copied blindly from a dispatch plan. INIT B may no longer be available after engine start, in which case use the available fuel-prediction page.
  8. Complete the PERF pages. On TAKEOFF, enter valid V1, VR and V2 speeds, the flap and trim setting, and a FLEX temperature only when one has been calculated. Do not invent a FLEX temperature or guess the speeds. Check the climb, cruise and descent pages, then complete APPR with destination weather, transition level and the correct decision altitude or minimum descent altitude before arrival.
PageMain purposeCommon mistake
INITRoute identity, cost index and cruise levelUsing the wrong destination or cruise level
F-PLNWaypoints, airways and proceduresInserting a revision without checking its legs
PERFTake-off, climb, descent and approach dataGuessing speeds or FLEX temperature
PROGFlight progress and navigation informationIgnoring an incorrect active waypoint
FUEL PREDFuel and arrival predictionsExpecting accurate predictions from incorrect weights
RAD NAVRadio-navigation tuning and verificationAssuming the selected approach tuned correctly

How do I import a SimBrief route into the A330?

A SimBrief import can fill much of the route, but it does not finish the MCDU setup. Use the aircraft's supported company-route or request function, then verify the origin, destination, runway, procedures, navdata cycle, weights and fuel. Our dedicated X-Plane 12 A330 SimBrief procedure covers the import sequence and the checks required afterwards.

If an imported waypoint produces NOT IN DATABASE, check its spelling and confirm that the flight plan and aircraft use compatible navigation data. Missing procedures usually indicate a navdata mismatch rather than an MCDU fault. Enter the route manually or substitute a valid database fix when an import cannot be reconciled.

Which flight-plan discontinuities should I clear?

Clear a discontinuity only when the preceding and following legs should connect directly. Press CLR, then the line-select key beside the discontinuity, and inspect the resulting track before inserting the change.

Do not automatically remove a discontinuity associated with a radar vector, manual leg or procedure boundary. Those gaps may be intentional. If ATC vectors the aircraft, use DIR to activate the appropriate next waypoint once established; forcing an early direct connection can cut across protected procedure routing.

Why will the A330 not follow the FMC route?

The A330 follows the route only when a valid leg is active and managed lateral guidance is engaged. Check these points in order:

  • The temporary flight-plan revision was confirmed with INSERT.
  • There is no unresolved discontinuity before the next waypoint.
  • The active waypoint is ahead of the aircraft rather than behind it. Use DIR to select the correct next fix when necessary.
  • The inertial-reference system has aligned and the aircraft has a valid navigation position.
  • Managed NAV is engaged. Pulling the heading control selects a heading; pushing it returns to managed guidance when the route permits.
  • The FCU altitude is set to the cleared altitude. The MCDU cannot command a climb or descent beyond the altitude selected by the pilot.
  • A lower altitude has been set and managed descent has been requested when passing the calculated descent point.

Pressing AP1 does not by itself activate an inactive route, and pressing the approach button does not load an approach into the MCDU. Programme the arrival first, verify the radio-navigation setup and then arm the appropriate approach mode. For the cockpit actions that follow MCDU preparation, use our complete X-Plane 12 A330 flying procedure.

AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members