Skip to content
Microsoft Flight Simulator 9 min read

How do you fly a complete Fenix A320 flight in MSFS 2020?

Ian Stephens
In short

Fly a complete Fenix A320 flight in MSFS 2020, from cold-and-dark setup and MCDU programming through managed descent, landing and shutdown.

To fly a complete Fenix A320 flight in MSFS 2020, load at a gate, power and initialise the aircraft, enter and check the route, calculate take-off data, start and taxi, fly the departure in managed modes, prepare the arrival before descent, complete the approach and landing, then park and shut down.

The Fenix A320 in Microsoft Flight Simulator 2020 is a PC add-on. Start at a parking stand rather than a runway, allow the Fenix companion application and aircraft systems to finish loading, and use the aircraft EFB for its panel state, fuel and payload.

For the cleanest setup, select only the airport and gate on the World Map, then build or import the route inside the aircraft. If you want MSFS built-in ATC, create a matching World Map plan but compare it carefully with the MCDU; the two routes should not be assumed to remain synchronised.

Complete Fenix A320 flight sequence

A normal complete flight runs from electrical power and route preparation through engine shutdown, with the FMA checked after every mode change.

  1. Establish electrical power. Select the cold-and-dark state in the EFB if required, switch on both batteries and connect external power when available. Without ground power, start the APU and wait for it to become available. Turn up the display brightness if an apparently unpowered screen is merely dim.

    Set all three ADIRS selectors to NAV early because alignment takes time. Our dedicated Fenix cold-and-dark start sequence covers the individual overhead-panel actions in more detail.

  2. Load fuel and payload. Enter passengers, cargo and fuel through the Fenix EFB, then let loading finish or use the instant option. Record the resulting zero-fuel weight, centre of gravity and block fuel. If the load changes later, recalculate the take-off data rather than retaining obsolete speeds and trim.

  3. Program and inspect the MCDU. Enter the departure and destination, flight number, cost index and cruise level. Add the departure runway, SID, en-route legs, arrival, STAR and expected approach. Work through the F-PLN page and inspect the route on the Navigation Display at different ranges.

    Complete INIT B with the zero-fuel weight, centre of gravity and block fuel before engine start. The separate MCDU route and performance setup guide explains airway entry, procedure selection and discontinuity checks.

  4. Calculate take-off performance. Use the EFB performance tool for the selected runway and conditions. Enter the resulting flap setting, flex temperature, V1, VR, V2 and take-off trim on the PERF TAKE OFF page, then set the physical pitch trim to match. Confirm that the runway in the calculator, MCDU and outside view is the same.

    Set the cleared altitude on the FCU, switch on both flight directors, confirm the initial navigation mode and review thrust-reduction and acceleration altitudes. Do not copy performance figures from another flight, even if the route and aircraft look similar.

  5. Prepare for pushback and start the engines. Close the doors, remove ground equipment and switch on the beacon. Confirm APU availability, APU bleed, fuel pumps and pneumatic air before selecting IGN/START. Start engine 2 and then engine 1, watching for a stable start rather than moving immediately to the next switch.

    Once both engines are stable, return the engine mode selector to NORM. Switch off APU bleed and stop the APU when it is no longer needed. A ground power unit supplies electricity, not the pneumatic air required for an engine start.

  6. Configure and taxi. Perform the flight-control check, set the calculated flap and trim, arm the ground spoilers and select MAX autobrake. Use the take-off configuration test and clear every warning before moving. Set the transponder and exterior lights as required, release the parking brake and taxi with small thrust changes.

  7. Take off. Line up on the correct runway, stabilise the engines at intermediate thrust, then place both thrust levers in the calculated FLX/MCT detent or TOGA when full thrust is required. Check the FMA for the expected thrust mode, SRS and lateral guidance before continuing.

    Rotate smoothly at VR, select gear up after a positive climb and follow the flight director. Autopilot 1 can be engaged after take-off once the aircraft is stable; many sim pilots wait until several hundred feet rather than engaging it at the first permitted moment.

  8. Climb and cruise. At thrust-reduction altitude, move both thrust levers into the CL detent. Leave them there for normal autothrust operation until the landing flare. Select standard pressure when passing the local transition altitude and monitor the FMA, route, fuel prediction and any altitude constraints.

    The aeroplane will normally follow managed speed, NAV and CLB modes, but it still needs supervision. Our explanation of A320 FCU and autopilot mode logic is useful if pushing and pulling the controls produces an unexpected result.

  9. Prepare the arrival before top of descent. Confirm the landing runway, STAR and approach, then check every modified leg. Enter destination QNH, temperature, wind, landing configuration and minima on the PERF APPR page. Calculate landing performance in the EFB and brief the missed approach as well as the landing.

    Set the next cleared altitude and push the altitude knob at top of descent to command managed DES. When flying online, a top-of-descent marker is not permission to leave the cleared altitude. If the approach changes, revise the MCDU first and verify that the new route has not introduced a turn back towards an obsolete waypoint.

  10. Fly the approach and land. For an ILS, verify the tuned frequency and identifier, display the LS scales and intercept the localiser from a sensible angle below the glideslope. Arm APPR and confirm LOC and G/S capture on the FMA. The full Fenix ILS approach procedure covers configuration, minima and autoland setup.

    Extend flaps progressively as speed reduces, lower the gear and select CONF 3 or FULL according to the landing calculation. Confirm the landing memo has no blue items and that the aircraft is stabilised by the applicable gate. Disconnect the autopilot for a manual landing, flare gently and move the thrust levers to idle at the RETARD call. Use reverse thrust and wheel braking, then clear the runway and clean up only when safely established on the taxiway.

  11. Park and shut down. Start the APU before reaching the stand if external power will not be available. At the stand, set the parking brake until chocks are confirmed, place both engine masters off and wait for the engines to spool down before switching off the beacon.

    Turn off the fuel pumps, seat-belt signs and unnecessary lights, set the transponder to standby and connect external power if required. For a full shutdown, switch the ADIRS selectors off, stop the APU after it is no longer needed, disconnect external power and switch the batteries off last.

How do managed and selected modes work in the Fenix A320?

Pushing an FCU knob generally requests a managed FMS target, while pulling it requests a pilot-selected target; the FMA confirms what the aircraft actually accepted.

ControlPush for managed modePull for selected mode
SpeedFMS speed schedule and constraintsSpeed shown in the FCU window
HeadingNAV guidance from the active routeSelected heading or track
AltitudeManaged CLB or DES with route constraintsOpen climb or open descent towards the selected altitude
Vertical speedReturn towards managed vertical guidance where availableSelected vertical speed or flight-path angle

Do not judge the active mode from knob positions alone. Read the top of the Primary Flight Display after every selection: green modes are active, while blue modes are armed. A common mistake is expecting NAV while the FMA still shows HDG, or expecting managed descent while OP DES is active.

Can the Fenix A320 fly the whole route on autopilot?

The autopilot can fly from shortly after take-off through an automatic landing, but it cannot make the complete flight unattended.

The pilot must initialise the aircraft, start the engines, taxi, manage clearances, set FCU targets, configure flaps and landing gear, monitor the FMA and handle the rollout. For an autoland, use a suitable ILS, engage both autopilots and confirm the expected LAND, FLARE and ROLLOUT annunciations. If those modes do not appear, disconnect and land manually or go around.

Why will the Fenix A320 not follow the route or descend?

Route and descent problems are usually caused by the wrong active mode, an unresolved flight-plan leg or an altitude that has not been set and commanded correctly.

  • The aircraft stays in heading mode: intercept the programmed path, push the heading knob and confirm NAV arms or activates. If the route is too far away, use a suitable direct-to waypoint rather than forcing an extreme intercept.
  • The aeroplane turns towards an unwanted waypoint: inspect the active leg and use direct-to when appropriate. Do not delete every discontinuity automatically; vector and manual legs may intentionally require pilot action.
  • Managed descent will not begin: set an altitude below the aircraft, push the altitude knob and look for DES on the FMA. A restrictive constraint or an incomplete route can prevent the expected profile.
  • LVR CLB keeps flashing: move both thrust levers accurately into the CL detent. Leaving them in FLX/MCT prevents normal autothrust operation.
  • The engines will not start: confirm the APU is available, APU bleed is on, fuel pumps are on, IGN/START is selected and the relevant engine master has been moved on.
  • The ILS will not capture: verify the selected approach and ILS frequency, arm APPR and intercept from below the glideslope. Merely pressing the LS display button does not arm approach capture.
  • Controls move by themselves: disable conflicting MSFS piloting assists and remove duplicate controller assignments. Axis noise can also disconnect the autopilot or move the thrust levers out of their detents.
  • Displays or systems stop responding: check electrical power, screen brightness and the Fenix companion application before resetting the flight.
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