Skip to content
Microsoft Flight Simulator 7 min read

How do you use the A320neo V2 FMC in MSFS 2024?

Ian Stephens
In short

Learn how to use the A320neo V2 FMC in MSFS 2024: enter a route, load SID and STAR procedures, set performance data and fix common errors.

To use the A320neo V2 FMC in MSFS 2024, power and align the aircraft, enter or import the route in the MCDU, add the runway, SID, STAR and approach, complete weight and performance pages, then inspect every leg before using managed guidance. The MCDU is the cockpit interface to the aircraft's FMGS.

What is the FMC in the A320neo V2?

In Airbus terminology, the system is the Flight Management and Guidance System, or FMGS, while the keypad and screen are the MCDU. Simmers often call the whole arrangement the FMC. Both MCDUs in the iniBuilds A320neo V2 supplied with Microsoft Flight Simulator 2024 access the same active flight plan.

Entries first appear in the scratchpad at the bottom of the screen. Press the appropriate left or right line-select key to move that entry into a field. Our page-by-page Airbus MCDU programming guide explains the underlying Airbus interface in more depth.

A320neo V2 FMC setup step by step

A usable A320 flight plan needs more than a line between two airports. We recommend loading fuel and payload first, programming the route while the inertial reference systems align, and calculating take-off data only after the runway and aircraft mass are settled.

  1. Power and align the aircraft. Establish electrical power, set the three inertial reference selectors to NAV and complete the position alignment when prompted. You can programme the MCDU during alignment, but navigation guidance will not be ready until alignment finishes.
  2. Complete INIT A. Select the FMGC function if the MCDU menu appears, then open INIT. Enter the departure and destination ICAO codes in FROM/TO, followed by the flight number, cost index and planned cruise level. Cost index affects the managed speed profile; it is not the fuel quantity.
  3. Enter the en-route section. Open F-PLN and insert fixes in sequence. For an airway, open the lateral revision from the appropriate waypoint, select the airways function and enter the airway and exit fix. Check any similarly named waypoints against the intended route before accepting them.
  4. Add the departure procedure. Select the origin airport on the flight-plan page, choose DEPARTURE, then select the runway, SID and transition. Commit the temporary plan with the displayed insert prompt only after checking it. Our guide to loading SIDs and STARs correctly covers procedure selection and transition mistakes.
  5. Add the arrival and approach. Select the destination airport, open ARRIVAL, and choose the expected approach, STAR, transition and any applicable approach via. The exact options depend on the navigation database. If ATC later changes the runway, rebuild the arrival and recalculate the landing data.
  6. Inspect every leg. Use the ND's PLAN mode and scroll through the MCDU flight plan. Look for route reversals, duplicate fixes, impossible turns and F-PLN DISCONTINUITY entries. Select INSERT to commit a valid temporary plan or ERASE to discard it.
  7. Complete INIT B. Before engine start, move to the second INIT page and enter zero-fuel mass, centre of gravity and block fuel using the figures from the loaded aircraft. Confirm whether the aircraft is displaying kilograms or pounds. After engine start, this page is normally replaced by fuel-prediction information.
  8. Fill in PERF TAKEOFF. Enter calculated V1, VR and V2 speeds, flap and trim configuration, transition altitude, thrust-reduction and acceleration altitudes, and a FLEX temperature if one has been calculated. Do not invent V-speeds or reuse figures after changing the runway, flap setting, weather or aircraft mass.
  9. Prepare the approach page before descent. Enter destination QNH, temperature, wind and the correct barometric or radio minimum. Confirm the landing configuration and VAPP. Loading an approach does not mean you should activate the approach phase early; premature activation can reduce the managed speed sooner than intended.

Can you import an MSFS 2024 EFB flight plan?

Yes, the MSFS 2024 EFB can transfer a prepared route to supported aircraft avionics, but that transfer does not replace a full MCDU check. Use the EFB's send-to-avionics function, allow the aircraft time to receive the plan, then inspect the A320's INIT and F-PLN pages.

Runways, procedures, constraints and performance entries may be incomplete or interpreted differently by the simulator planner and the aircraft navigation database. Our guide to building and transferring an MSFS 2024 EFB flight plan explains the simulator side of that process.

Manual entry is slower but gives the clearest control over airway joins, procedure transitions and discontinuities. Imported and manually entered routes both require INIT B and PERF data.

Should you clear every flight-plan discontinuity?

No, only remove a discontinuity when the two surrounding legs are meant to connect directly. Press CLR, then select the line containing F-PLN DISCONTINUITY; the MCDU joins the adjacent legs.

A discontinuity after a vectors or manual leg is often deliberate. It tells the crew to fly a heading until cleared towards another fix. Deleting it blindly can create a sharp turn back towards the airport or connect two procedure legs that were never intended to meet. In that situation, fly selected heading and use DIR to activate the cleared waypoint.

Why will the A320neo V2 not follow the FMC route?

The aircraft follows the programmed route only when a valid leg is active and managed NAV mode is armed or engaged. The MCDU creates the plan, but it does not switch on the flight directors, engage the autopilot or guarantee that the aircraft can intercept the active leg.

On the Airbus FCU, pushing the heading knob commands managed navigation while pulling it selects a heading. If the aircraft is far from the route, use selected heading to intercept it or press DIR, choose a suitable downstream waypoint and insert the temporary direct-to plan. Watch the Flight Mode Annunciator for NAV, CLB and DES; it is the authoritative indication of what the aircraft is doing.

For the flying sequence after MCDU setup, including thrust detents and managed modes, use our complete iniBuilds A320neo V2 flight workflow.

Common A320neo V2 FMC problems

Most MCDU failures come from an invalid entry, an uncommitted temporary plan or a mismatch between the active leg and the aircraft's position.

ProblemLikely causeFix
NOT IN DATABASEThe identifier is mistyped or absent from the loaded navigation data.Check the ICAO code or waypoint name and use a fix available in the aircraft's database.
FORMAT ERRORThe scratchpad entry does not use the format expected by that field.Clear the entry and re-enter only the required value, slash or decimal format.
The imported route is missingThe EFB transfer was not sent, the avionics were not ready or the aircraft did not accept that plan element.Power the aircraft fully, send the route again, wait for processing and enter any missing legs manually.
The ND shows a gapA discontinuity remains or a temporary revision has not been inserted.Review the surrounding legs and remove the gap only if they should connect directly.
The aircraft ignores the magenta lineSelected heading is active, the active waypoint is behind the aircraft or NAV cannot capture the route.Use a direct-to or intercept heading, then push the heading knob for managed NAV and verify the FMA.
The ILS or arrival is wrongThe runway changed or the procedure selection does not match the intended arrival.Reselect the arrival, inspect the temporary plan and verify the tuned approach on the RAD NAV page.
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