Lesson Overview

This module teaches students how to install, configure, operate and test the Fenix Airbus A319 and A320.

The Fenix A320 is the base product. The A319 is included through the separate A319/A321 expansion, so students who want to fly the A319 must own and install both the base A320 and the expansion. The aircraft has native support for MSFS 2020 and a separately built MSFS 2024 package using the newer simulator SDK and modular aircraft system.  

This lesson is designed to provide a practical foundation within 30–40 minutes. It will not cover every Airbus abnormal procedure or airline-specific checklist. Instead, students will learn enough to:

• Install the correct aircraft version.
• Configure the Fenix App and EFB.
• Connect SimBrief and Navigraph.
• Calibrate the throttles.
• Load fuel and passengers.
• Prepare the aircraft from cold and dark.
• Program a basic route.
• Start, taxi, take off and use Airbus automation.
• Prepare and fly an ILS approach.
• Land, taxi in and shut down.
• Test the aircraft for performance and add-on conflicts.

Lesson Objectives

By the end of this module, students will be able to:

Install the Fenix A320 and A319 correctly.

Select the correct MSFS 2020 or MSFS 2024 package.

Update the aircraft and manage liveries.

Configure the Fenix App and display-rendering options.

Connect SimBrief and Navigraph.

Calibrate throttle detents.

Configure rudder and nose-wheel steering.

Load fuel, passengers and cargo.

Complete a basic cold-and-dark preparation.

Program the MCDU.

Start the engines and taxi safely.

Understand managed and selected Airbus modes.

Complete climb, cruise and descent.

Prepare and fly an ILS approach.

Land, taxi in and shut down.

Compare A319 and A320 performance.

Diagnose FPS, loading and CTD problems.

STEP 1 – INSTALLATION

Installing the Fenix A319 and A320

1. Create a Fenix Account

Create an account through the official Fenix website.

Use the same account for:

• Purchasing the aircraft.
• Downloading the installer.
• Activating the product.
• Installing updates.
• Accessing customer support.

Keep your login details secure. The licence is linked to the Fenix account used during purchase.

2. Select the Correct Product

Students who only want the A320 need the:

Fenix A320 Base

Students who also want the A319 need:

• Fenix A320 Base.
• Fenix A319/A321 Expansion.

The A319 expansion builds on the systems and aircraft package supplied by the base A320.  

3. Confirm Your Simulator Version

Before installing, confirm whether you use:

• Microsoft Flight Simulator 2020.
• Microsoft Flight Simulator 2024.
• Both simulators.

The Fenix Installer provides the appropriate package for each simulator. The MSFS 2024 aircraft was rebuilt using the 2024 SDK rather than being a simple copy of the MSFS 2020 version.  

Do not:

• Copy the MSFS 2020 package manually into MSFS 2024.
• Copy the MSFS 2024 package into MSFS 2020.
• Keep outdated compatibility versions active.
• Install duplicate aircraft copies manually.

4. Download and Install the Fenix Installer

1. Sign into the Fenix customer dashboard.
2. Download the latest Fenix Installer.
3. Close Microsoft Flight Simulator.
4. Run the installer.
5. Sign into your Fenix account.
6. Select MSFS 2020 or MSFS 2024.
7. Confirm the simulator package path.
8. Install the A320.
9. Install the A319/A321 expansion if owned.
10. Allow the process to finish completely.
11. Launch the Fenix App when prompted.

Fenix’s current setup process uses the customer dashboard and Fenix Installer. Once installation is complete, the installer can launch the Fenix App for further configuration.  

5. Confirm the Installation Path

If the aircraft does not appear, verify the simulator’s InstalledPackagesPath in UserCfg.opt.

The relevant file is stored in different locations depending on:

• MS Store or Xbox installation.
• Steam installation.
• MSFS 2020.
• MSFS 2024.

The path should point to the main package location containing the Official and Community folders, not directly to the Community folder itself.  

Do not manually change the path unless it is clearly incorrect.

6. Update the Aircraft

Before the first flight:

1. Open the Fenix Installer.
2. Check the A320 package.
3. Check the expansion package if installed.
4. Select Update where available.
5. Allow all packages to finish.
6. Record the installed version.
7. Restart the Fenix App before launching MSFS.

The installer is also used to apply aircraft updates and major feature packages.  

7. Install Liveries

Install only liveries designed for the correct:

• Fenix aircraft.
• Aircraft variant.
• Engine type.
• Simulator version.

For example, verify whether the livery is designed for:

• A319 CFM.
• A319 IAE.
• A320 CFM.
• A320 IAE.
• Wingtip-fence or Sharklet configuration.

Avoid keeping an old and updated version of the same livery active.

After installation:

1. Load the aircraft-selection menu.
2. Confirm the livery appears under the correct variant.
3. Inspect the exterior.
4. Check registration and engine type.
5. Remove it if textures are missing or the aircraft fails to load.

8. Update Navigation Data

A Navigraph subscription can update the Fenix navigation database.

To update:

1. Close MSFS.
2. Close the Fenix App.
3. Open Navigraph Hub.
4. Select the section for products installed outside the simulator.
5. Locate the Fenix A320 package.
6. Select Install or Update.
7. Wait for the process to complete.
8. Launch the aircraft and check the AIRAC cycle on the MCDU IDENT page.

Fenix’s support guidance specifically directs users to update the aircraft database through Navigraph Hub while both the simulator and Fenix are closed.  

9. Configure SimBrief

Generate a valid SimBrief Operational Flight Plan before attempting an import.

Then:

1. Open the Fenix EFB.
2. Open Settings.
3. Enter the SimBrief username.
4. Save the setting.
5. Generate a new OFP in SimBrief.
6. Return to the EFB.
7. Retrieve the latest flight.

The current Fenix integration stores the SimBrief username through the EFB Settings app, and a flight must be fully generated before it can be imported.  

Use the correct SimBrief type:

• A319 for the Fenix A319.
• A320 for the Fenix A320.

Use an add-on-specific airframe where available.

10. Required Background Application

The Fenix aircraft uses the external Fenix App alongside MSFS.

The app supports areas such as:

• Aircraft communication.
• Display rendering.
• Account and licence services.
• Aircraft systems integration.
• Optional ACARS configuration.

The Fenix App should normally be running before or while the aircraft loads. If the EFB reports that it cannot connect or the aircraft remains unpowered, verify that the app is running and that the required local connection is not being blocked.  

11. Correct Uninstallation

Do not remove random Fenix folders manually as the first step.

Use the Fenix Installer to uninstall the relevant package.

A clean removal process should include:

1. Close MSFS.
2. Close the Fenix App.
3. Open the Fenix Installer.
4. Select the installed product.
5. Choose uninstall.
6. Remove the A319/A321 expansion separately if required.
7. Restart Windows.
8. Confirm the aircraft no longer appears.
9. Reinstall only after the previous package has been removed correctly.

Use a clean reinstall only when normal updating or repair has failed.

STEP 2 – CONFIGURATION AND COMPLETE FLIGHT

Configuring and Flying the Fenix Airbus

Part A – Essential Configuration

12. Fenix App Settings

Open the Fenix App before loading the aircraft.

Review:

• Display-rendering options.
• Display Sync.
• Safe Mode options.
• ACARS or Hoppie code if used.
• Product and simulator selection.

Select Apply after making changes.

Avoid changing several display options simultaneously because some changes require returning to the main menu or restarting the flight.  

13. Display Rendering Options

The Fenix displays can be rendered using different methods depending on system configuration.

The correct choice depends on whether the computer has more available:

• CPU capacity.
• GPU capacity.
• Display stability.

Begin with the recommended default setting.

Only change it if you experience:

• Low display FPS.
• Delayed display movement.
• Display stuttering.
• Black or frozen displays.
• Excessive CPU or GPU load.

Fenix advises that display safe-mode and forced CPU-rendering options should generally remain disabled unless troubleshooting requires them.  

14. Display Sync

Display Sync attempts to keep the aircraft displays closely synchronised with the simulator.

Enable it when:

• The displays appear delayed.
• Display movement is visibly out of sync.
• The instruments stutter independently of the simulator.

It can have a small FPS impact on some systems, so leave it disabled when the displays already behave correctly.  

15. EFB Configuration

Open the EFB and review:

• SimBrief account.
• Units.
• Airline settings.
• Aircraft state.
• Fuel and payload.
• Performance calculator.
• Cabin announcements.
• GSX integration.
• Realism and failure options.

Use the same units across:

• SimBrief.
• EFB.
• MCDU.
• Performance calculations.

Use either kilograms or pounds consistently.

16. Aircraft State

Choose:

Cold and Dark

Best for the complete preparation sequence.

Turnaround

Useful for quicker flights.

Ready State

Useful for short testing but not ideal for learning.

For this lesson, load Cold and Dark.

17. Realism and Failures

For training:

• Use realistic aircraft behaviour.
• Leave random failures disabled.
• Leave manual failures disabled.
• Use default airline settings initially.
• Avoid changing advanced system options until the aircraft is stable.

The aircraft includes an extensive failure system, but failures should be introduced only after the student understands normal operation.  

18. Throttle Calibration and Detents

Airbus throttles use fixed detents:

• Reverse.
• Idle.
• Climb.
• Flex/MCT.
• TOGA.

Calibration is essential.

Basic Procedure

1. Open the EFB throttle-calibration page.
2. Select the correct throttle hardware.
3. Move both levers to full reverse.
4. Save the reverse range.
5. Move to idle.
6. Save idle.
7. Move to CL.
8. Save the climb detent.
9. Move to FLEX/MCT.
10. Save it.
11. Move to TOGA.
12. Save it.
13. Apply the configuration.
14. Test both levers slowly.

Confirm the cockpit indication changes correctly at each detent.

Do not rely on the visual position of the physical throttle alone. Confirm the aircraft’s on-screen detent message.

19. Cockpit Controls

Check:

• Pitch.
• Roll.
• Rudder.
• Throttle 1 and 2.
• Brakes.
• Parking brake.
• Spoilers.
• Flaps.
• Nose-wheel steering.

Remove duplicate assignments.

Airbus aircraft can behave unpredictably when the same function is bound to:

• A joystick.
• A throttle quadrant.
• A keyboard.
• Another controller.

20. Rudder and Tiller

Configure:

• Rudder pedals for yaw.
• A separate tiller axis where available.
• Combined nose-wheel steering only where required.

Test at low taxi speed.

Use small inputs. Excessive sensitivity can make the aircraft oversteer sharply.

21. GSX Integration

GSX can coordinate:

• Boarding.
• Passenger loading.
• Cargo.
• Fuel.
• Doors.
• Pushback.

Use the latest supported GSX version and follow Fenix’s current integration guide.  

Avoid loading the aircraft simultaneously through:

• Fenix EFB.
• GSX.
• MSFS Weight and Balance.

Choose one main loading method or use the supported Fenix–GSX integration so that both systems remain synchronised.

22. Cabin Announcements

The aircraft includes a cabin-announcement system.

Students may use:

• The included generic pack.
• Airline-specific sound packs.
• Custom packs using the required folder structure.

Cabin announcements can be configured through the EFB.  

Begin with the default pack before installing custom audio.

Part B – Complete Basic Flight

23. Cold and Dark Preparation

At the parking stand:

1. Set the parking brake.
2. Confirm throttles are at idle.
3. Confirm engine masters are off.
4. Turn Battery 1 and Battery 2 on.
5. Connect external power through the EFB.
6. Turn external power on when available.
7. Check the electrical indications.
8. Set the cockpit lights as required.

24. ADIRS Alignment

On the overhead panel:

1. Turn all three ADIRS selectors to NAV.
2. Open the MCDU.
3. Access the INIT page.
4. Confirm the departure and destination.
5. Enter or confirm the aircraft position.
6. Allow alignment to complete.

Do not begin taxi until the navigation displays and aircraft position are available.

25. Overhead Preparation

Complete a basic overhead scan:

• Batteries on.
• External power on.
• ADIRS in NAV.
• Fuel pumps configured later when fuel is loaded.
• Emergency lights armed.
• Passenger signs set.
• No smoking sign set according to configuration.
• Air-conditioning panel checked.
• Packs available.
• Engine bleed system checked.
• Probe and window heat left according to the required flight stage.
• Anti-collision light left off until pushback or engine start.

26. Load Fuel and Payload

From the EFB:

1. Retrieve the SimBrief flight.
2. Review passengers.
3. Review cargo.
4. Review block fuel.
5. Start the loading process.
6. Monitor the progress.
7. Confirm Zero Fuel Weight.
8. Confirm Zero Fuel Weight Centre of Gravity.
9. Compare the figures with the SimBrief OFP.

Do not begin engine start before loading is complete.

27. MCDU INIT Page

On INIT A, enter or import:

• From/To.
• Alternate.
• Flight number.
• Cost index.
• Cruise flight level.
• Cruise temperature where required.

Use the SimBrief data.

On INIT B, confirm:

• Zero Fuel Weight.
• Zero Fuel Weight Centre of Gravity.
• Block fuel.

The INIT B page is normally completed while the engines are not running.

28. Flight-Plan Import

After retrieving the SimBrief route:

1. Open the MCDU flight-plan page.
2. Confirm the departure airport.
3. Confirm the destination.
4. Step through every waypoint.
5. Check for route discontinuities.
6. Confirm airway connections.
7. Review any manual segments.
8. Verify the planned route against SimBrief or Navigraph.

Do not delete every discontinuity automatically. Some discontinuities reflect vectors or planned ATC intervention.

29. SID and STAR Selection

For departure:

1. Select the departure airport.
2. Select the expected runway.
3. Select the SID.
4. Select the correct transition.
5. Insert the procedure.
6. Review the route.

For arrival:

1. Select the destination.
2. Choose the expected runway.
3. Select the STAR.
4. Select the approach.
5. Select the appropriate transition or via.
6. Review all constraints.

Runways may change because of weather or ATC. The arrival can be revised during the flight.

30. Performance Pages

On the take-off performance page, enter or calculate:

• Runway.
• Flap setting.
• Centre of gravity.
• Trim.
• V1.
• VR.
• V2.
• FLEX temperature or TOGA thrust.
• Thrust-reduction altitude.
• Acceleration altitude.
• Engine-out acceleration altitude.

Use the EFB performance calculator where appropriate.

Do not reuse take-off speeds from a previous flight.

31. FLEX Temperature

FLEX allows the aircraft to use reduced take-off thrust when runway length, weather and aircraft weight permit.

A higher FLEX temperature generally commands less thrust.

Use only the value calculated for the current:

• Aircraft weight.
• Runway.
• Weather.
• Flap setting.
• Runway condition.

Use TOGA when the conditions or performance calculation require full thrust.

32. Flight-Control Check

Before pushback or during the appropriate procedure:

1. Move the sidestick fully left.
2. Move it fully right.
3. Move it fully forward.
4. Move it fully back.
5. Test the rudder.
6. Confirm the ECAM flight-control page responds correctly.
7. Return all controls to neutral.

33. Pushback and Engine Start

Before pushback:

• Doors closed.
• Fuel and payload complete.
• Beacon on.
• APU started.
• APU available.
• APU bleed on.
• External power disconnected.
• Fuel pumps on.
• Area clear.

Typical start sequence:

1. Set the Engine Mode Selector to IGN/START.
2. Move Engine Master 2 to ON.
3. Monitor N2, fuel flow, EGT and oil pressure.
4. Confirm Engine 2 stabilises.
5. Move Engine Master 1 to ON.
6. Monitor the start.
7. Confirm both engines are stable.
8. Return Engine Mode Selector to NORM.

34. After-Start Flow

After both engines stabilise:

• APU bleed off.
• APU off when no longer required.
• Engine anti-ice as required.
• Flaps set.
• Spoilers armed.
• Pitch trim checked.
• Rudder trim zero.
• Flight controls checked.
• Ground spoilers and autobrake configured.
• Taxi light on before moving.

35. Taxi

Release the parking brake and use minimal thrust.

During taxi:

• Maintain a safe speed.
• Use the tiller gently.
• Check brakes.
• Verify flight instruments.
• Review the take-off configuration.
• Confirm the runway and SID.

The A319 is shorter and can feel more responsive during taxi than the A320.

36. Take-off

Before entering the runway:

• Flaps confirmed.
• Spoilers armed.
• Autobrake MAX where appropriate.
• Flight directors on.
• Initial altitude set.
• Take-off speeds displayed.
• Landing lights on.
• Strobes on.

For take-off:

1. Align with the centreline.
2. Stabilise thrust.
3. Move the levers to FLEX/MCT or TOGA.
4. Confirm the FMA shows the correct thrust mode.
5. Maintain centreline.
6. At V1, continue.
7. At VR, rotate smoothly.
8. Follow the flight director.
9. Select gear up after positive climb.

37. Flight Mode Annunciator

The FMA at the top of the Primary Flight Display shows what the automation is actually doing.

Always read it after selecting a mode.

It displays:

• Autothrust mode.
• Vertical mode.
• Lateral mode.
• Approach capability.
• Autopilot and flight-director status.

Never assume a mode has engaged simply because you pressed the button.

38. Managed vs Selected Modes

Managed Mode

The aircraft follows values calculated by the FMGS.

Examples:

• Managed speed.
• NAV lateral guidance.
• Managed climb.
• Managed descent.

Selected Mode

The pilot manually chooses the value.

Examples:

• Selected heading.
• Selected speed.
• Open climb.
• Open descent.
• Vertical speed.

In the Airbus interface:

• Pushing a selector generally commands managed guidance.
• Pulling a selector generally commands selected guidance.

Always verify the result on the FMA.

39. Climb

During climb:

1. Retract the flaps according to the speed schedule.
2. Move the thrust levers to CL when prompted.
3. Confirm autothrust becomes active.
4. Monitor the FMA.
5. Check altitude constraints.
6. Monitor engine and pressurisation indications.
7. Set the cleared altitude as ATC permits.

40. Cruise

At cruise:

• Confirm the aircraft levels correctly.
• Check fuel against SimBrief.
• Review destination weather.
• Review the arrival.
• Check the landing runway.
• Prepare the approach before top of descent.
• Monitor ECAM and systems.

41. Descent Calculation

The FMGS calculates a top-of-descent point based on:

• Route.
• Altitude constraints.
• Aircraft weight.
• Wind.
• Speed profile.

Before descent:

1. Select the arrival.
2. Check constraints.
3. Enter destination weather.
4. Enter landing data.
5. Set a lower cleared altitude.
6. Push the altitude selector for managed descent when appropriate.

Use selected modes if ATC instructions do not match the managed profile.

42. Approach Preparation

Complete:

• Arrival and approach selection.
• Landing runway.
• Approach minimums.
• Landing flap selection.
• Autobrake setting.
• Landing performance calculation.
• Approach briefing.
• ILS frequency and course verification where required.

Use the EFB landing-performance calculator to check:

• Runway length.
• Runway condition.
• Wind.
• Aircraft weight.
• Flap setting.
• Autobrake requirement.

43. ILS Approach

For a basic ILS:

1. Confirm the correct ILS is tuned.
2. Confirm the identifier.
3. Confirm the final approach course.
4. Intercept the localiser from an appropriate heading.
5. Press the approach button when cleared.
6. Monitor LOC capture.
7. Monitor glideslope capture.
8. Lower the landing gear.
9. Extend flaps progressively.
10. Stabilise by the required altitude.
11. Confirm landing checklist complete.

44. RNAV Approach

For an RNAV approach:

• Confirm the procedure exists in the MCDU.
• Verify the approach minima.
• Review required navigation performance.
• Confirm the lateral and vertical path.
• Monitor the FMA carefully.
• Do not assume an RNAV approach behaves exactly like an ILS.

Use the relevant charts and aircraft documentation.

45. Autoland

For autoland:

• Use an authorised ILS.
• Confirm suitable approach capability.
• Engage both autopilots where required.
• Confirm the expected FMA indications.
• Monitor the approach continuously.
• Be prepared to disconnect and go around if the system does not behave correctly.

Autoland should not be treated as an unattended landing.

46. Manual Landing

For a manual landing:

1. Disconnect the autopilot at a comfortable altitude.
2. Keep autothrust active unless following a different procedure.
3. Maintain the flight path and speed.
4. Use small sidestick inputs.
5. Begin the flare close to the runway.
6. Reduce thrust to idle when prompted.
7. Touch down on the main landing gear.
8. Allow the nose to lower.
9. Select reverse thrust.
10. Monitor autobrake or use manual braking.

Do not hold the aircraft off the runway excessively.

47. Taxi-In and Shutdown

After leaving the runway:

• Flaps retract.
• Spoilers disarm.
• Landing lights off.
• Strobes off.
• Taxi light on.
• APU start where required.
• Weather radar off.
• Transponder configured.

At the stand:

1. Set parking brake.
2. Connect external power or use APU power.
3. Move both Engine Masters off.
4. Turn beacon off.
5. Turn fuel pumps off.
6. Set seat-belt signs appropriately.
7. Open doors when the engines have stopped.
8. Complete parking flow.

For complete securing:

• ADIRS off.
• Emergency lights off where appropriate.
• External power disconnected.
• Batteries off.

STEP 3 – PERFORMANCE AND COMPATIBILITY TESTING

48. Establish a Baseline

Compare the Fenix against a simple default aircraft using the same:

• Airport.
• Stand.
• Weather.
• Time.
• Graphics settings.
• Traffic.
• Camera view.

Record:

• Loading time.
• Average FPS.
• 1% lows.
• MainThread status.
• GPU utilisation.
• RAM usage.
• VRAM usage.
• CPU temperature.
• GPU temperature.

49. Fenix App CPU Usage

Monitor the external Fenix process through Task Manager or HWiNFO.

Test:

1. Fenix App running at the gate.
2. Aircraft displays off.
3. Aircraft fully powered.
4. EFB open.
5. EFB closed.
6. Aircraft in cruise.

A small background workload is expected.

Investigate:

• Abnormally high continuous CPU usage.
• Fenix process freezing.
• Memory usage increasing continuously.
• App closing unexpectedly.

50. Display-Rendering Test

Test the default display mode first.

Record:

• Cockpit FPS.
• Display smoothness.
• MainThread status.
• GPU utilisation.

Then change only one display option.

Repeat the same test.

Keep the alternative setting only when it improves:

• Instrument smoothness.
• Frame pacing.
• Stability.

Do not enable CPU safe rendering on a CPU-limited system unless it is required to resolve a specific display problem.

51. MainThread and VRAM Testing

The Fenix can add CPU load through:

• Systems simulation.
• Avionics.
• Displays.
• EFB.
• External app communication.

It can add GPU and VRAM load through:

• High-resolution cockpit textures.
• Displays.
• Detailed model.
• Liveries.
• Cabin and exterior assets.

Record whether the aircraft is:

• MainThread limited.
• GPU limited.
• Close to VRAM capacity.
• Stable over time.

52. A319 vs A320 Comparison

Use the same flight conditions.