How do I fly the Fenix A320 in MSFS 2024?

To fly the Fenix A320 in MSFS 2024, start it from cold and dark, load and verify the route in the MCDU, calculate take-off performance, start the engines, then use Airbus managed modes through climb, cruise and descent. Configure early for landing, monitor the FMA, and move the thrust levers when prompted.

Before loading the Fenix A320

The Fenix A320 is a PC add-on that relies on supporting software outside Microsoft Flight Simulator 2024, so it is not available on the Xbox or PlayStation versions. Install it through the Fenix installer rather than manually copying an older package; our Fenix installation and initial setup guide covers that prerequisite.

For a first flight, select a parking stand rather than a runway and load the cold-and-dark panel state. Disable AI piloting and any assistance that operates aircraft systems, because those features can move switches or throttles without warning.

Calibrate your throttle through the Fenix calibration controls before departure. The idle, climb, flexible take-off and TOGA detents must register reliably. A large share of apparent autothrust faults are actually badly calibrated lever positions or duplicate throttle bindings.

How do I start the Fenix A320 from cold and dark?

Bring the aircraft to life in the same order used by the electrical, navigation and pneumatic systems.

1. Connect electrical power. Switch both batteries on, then use external power when AVAIL is displayed. If ground power is unavailable, start the APU and wait for APU AVAIL.
2. Align the inertial reference systems. Turn the three ADIRS selectors to NAV. Alignment time depends on the selected aircraft option; complete the MCDU position initialisation rather than moving the aircraft early.
3. Load passengers, cargo and fuel. Set the required load through the Fenix EFB. Avoid changing fuel with the MSFS weight menu after programming the MCDU, as the figures may no longer agree.
4. Programme the route. Enter or import the origin, destination, departure, airway route, arrival and approach. Our Fenix SimBrief workflow explains importing the operational flight plan and loading data without mixing incompatible sources.
5. Enter performance data. Add the cost index, cruise level, zero-fuel weight, centre of gravity and block fuel. On the take-off page, enter the runway, flap setting, trim, V1, VR, V2 and calculated FLEX temperature where applicable.
6. Inspect the flight plan. Step through it on the navigation display. Remove only genuine discontinuities; do not erase a vectors leg or an intentional gap merely because the MCDU displays F-PLN DISCONTINUITY. For the complete sequence, use our A320 MCDU programming instructions.

Calculate take-off performance using the actual runway, intersection, wind, temperature, pressure, runway condition, anti-ice state and planned flap configuration. Check the EFB result against the MCDU entries instead of treating imported numbers as automatically correct.

Engine start, pushback and taxi

The normal engine start uses APU bleed air, with engine 2 commonly started before engine 1.

1. Close the doors, switch the beacon on and obtain clearance before pushback.
2. Confirm the APU is available, turn APU BLEED on and remove external power when appropriate.
3. Set the engine mode selector to IGN/START, then move engine master 2 to ON.
4. Monitor N2, fuel flow, EGT and oil indications. Start engine 1 only after engine 2 has stabilised.
5. Return the mode selector to NORM. Turn off APU bleed and shut down the APU once the engines are supplying the aircraft.

Before taxi, set the flaps and pitch trim shown on the take-off performance page, arm the ground spoilers and select maximum take-off autobraking. Check the flight controls, brakes and nosewheel steering, then press the take-off configuration test and resolve every warning.

Use only enough thrust to start rolling, then return the levers towards idle. The A320 can accelerate quickly at light weights, and riding the brakes produces an unnecessarily rushed taxi.

How do Airbus managed and selected modes work?

Push an FCU knob to request a managed mode and pull it to select a value yourself, but the Flight Mode Annunciator tells you what the aircraft has actually accepted.

Turning a knob does not by itself command a climb, descent or heading change. Set the cleared value, then push or pull the relevant knob. We see this mistake constantly: the altitude window has been changed, but the aircraft remains level because no vertical mode was engaged.

Read the FMA after every automation input. A lit button shows what you requested; the FMA shows which modes are active in green and armed in blue.

Take-off and climb

Stabilise the engines before selecting take-off thrust, then follow the FMA and thrust-lever prompts.

1. Line up, verify the runway and confirm the transponder, lights and take-off configuration.
2. Advance the levers to roughly 50% N1 and allow both engines to stabilise.
3. Move the levers to FLX/MCT when using valid FLEX data, or TOGA when full thrust is required.
4. Confirm the expected take-off indications on the FMA, maintain the centreline and rotate smoothly at VR.
5. Select gear up after a positive climb is established. Engage the autopilot when comfortably established if desired; hand-flying remains valid.
6. At thrust-reduction altitude, move the levers to the CL detent when LVR CLB appears.
7. Retract the flaps on schedule, respecting the displayed flap retraction cues and speed limits.

Leave the thrust levers in CL during normal climb, cruise and descent. Autothrust then commands engine thrust while the physical levers remain stationary. Moving them below or above the detent changes the available autothrust range and often causes unexpected speed behaviour.

Descent and approach preparation

Set up the arrival before top of descent, including the runway, approach transition, landing performance and missed-approach route.

Enter the destination pressure, temperature, wind and decision altitude or minimum descent altitude on the MCDU approach page. Let the approach phase activate at the calculated deceleration point unless ATC requires an early slowdown; activating it too soon commands approach speeds prematurely.

To start a normal managed descent, set the cleared lower altitude and push the altitude knob near the calculated descent point. Pulling it commands open descent instead, which disregards MCDU altitude constraints. If the aircraft is high, use selected speed or speedbrake deliberately rather than waiting until final approach.

Landing the Fenix A320

For an ILS, intercept the localiser from a sensible angle and from below the glideslope, then arm the approach and verify both capture modes on the FMA.

Reduce speed and configure in stages: Flaps 1, Flaps 2, gear down, then Flaps 3 or Full as performance and conditions require. Arm the spoilers, select the planned autobrake setting and complete the landing checklist. Our Fenix A320 ILS procedure covers frequency setup, localiser and glideslope capture, dual-autopilot use and common capture failures.

For a manual landing, disconnect the autopilot when stable, keep autothrust engaged and follow the flight directors or visual path. Make a small flare close to the runway; at the RETARD call, bring both thrust levers to idle. After touchdown, select reverse thrust, monitor deceleration and stow reverse before leaving the runway.

Why is the Fenix A320 not following my commands?

Most Fenix control problems come from an incorrect active mode, a broken route, a throttle outside its detent or competing MSFS bindings.

Parking and shutdown

Establish ground or APU electrical power before shutting down both engines if you want the cockpit to remain powered.

1. Park on stand, set the parking brake or fit chocks, and place the thrust levers at idle.
2. Start the APU and wait for it to become available, or connect external power.
3. Move both engine masters to OFF.
4. After engine shutdown, switch off the beacon, fuel pumps and unnecessary exterior lights.
5. Disarm the spoilers, retract the flaps and set the transponder as required.
6. For a complete shutdown, turn the ADIRS selectors off, disconnect external or APU power as appropriate, and switch the batteries off last.