Lesson Overview

This module teaches students how to install, configure, operate and test two of FlyByWire Simulations’ major freeware aircraft:

• FlyByWire A32NX, based on the Airbus A320neo.
• FlyByWire A380X, based on the Airbus A380.

Both aircraft are installed through the official FlyByWire Installer. The installer supports MSFS 2020 and MSFS 2024, allows students to switch between simulator installations and manages Stable and Development builds. Current FlyByWire releases support both simulators, although the project now maintains simulator-specific development branches and feature parity between MSFS 2020 and MSFS 2024 should not always be assumed.  

The A32NX and A380X share several common systems, including:

• flyPad electronic flight bag.
• SimBrief integration.
• Navigraph chart integration.
• Throttle calibration.
• Fuel and payload tools.
• Airbus-style managed and selected automation.

However, they are not interchangeable.

The A32NX is a narrow-body A320neo designed for short- and medium-haul flights. The A380X is a four-engine, wide-body aircraft with greater weight, larger displays, more complex ground handling and a substantially heavier performance workload.

This lesson provides a complete practical introduction within 40–45 minutes. It does not replace the full FlyByWire documentation or cover every abnormal procedure.

Lesson Objectives

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

Install the A32NX and A380X correctly.

Select the correct simulator and build version.

Understand Stable and Development releases.

Keep MSFS 2020 and MSFS 2024 packages separate.

Install compatible liveries.

Configure navigation data.

Set up the flyPad.

Link SimBrief and Navigraph.

Calibrate A320neo and A380 throttle controls.

Configure payload and fuel.

Program a basic flight plan.

Prepare either aircraft from cold and dark.

Start the engines.

Use managed flight modes.

Complete climb, cruise, descent and approach.

Land and shut down.

Compare Stable and Development performance.

Diagnose loading, livery, EFB and add-on conflicts.

STEP 1 – INSTALLATION

Installing the FlyByWire Aircraft

1. Download the Official FlyByWire Installer

The safest and recommended installation method is the official FlyByWire Installer.

The installer can:

• Install the A32NX.
• Install the A380X.
• Manage MSFS 2020 and MSFS 2024 separately.
• Install Stable and Development builds.
• Update existing installations.
• Manage A380X texture variants.
• Detect or configure Community Folder locations.  

Installation Procedure

1. Close Microsoft Flight Simulator.
2. Download the installer from the official FlyByWire website.
3. Run the installer.
4. Allow it to update itself if requested.
5. Open the simulator selector.
6. Choose MSFS 2020 or MSFS 2024.
7. Confirm the Community Folder path.
8. Select the A32NX or A380X.
9. Choose the required build.
10. Select Install.
11. Wait for the process to complete.
12. Do not move the installed aircraft folder manually afterwards.

2. Confirm the Correct Community Folder

Students with both simulators installed must confirm that the installer is targeting the correct package location.

The MSFS 2020 and MSFS 2024 Community Folders are separate.

Do not:

• Install the 2020 package into the 2024 Community Folder.
• Install the 2024 package into MSFS 2020.
• Manually copy the aircraft between simulators.
• Keep an old manual installation beside the installer-managed version.

FlyByWire now uses separate simulator-specific releases. A feature or fix appearing in one simulator branch may not arrive in the other at exactly the same time.  

3. Stable and Development Versions

The installer normally offers at least two main release channels.

Stable

The Stable build is intended for normal flying.

It generally provides:

• Tested features.
• Greater predictability.
• Fewer daily changes.
• Better suitability for VATSIM flights.
• A stronger choice for students learning the aircraft.

Development

The Development build contains newer changes and fixes before they reach Stable.

It may provide:

• New systems.
• Updated EFB features.
• Recent bug fixes.
• New flight-management functions.
• Performance improvements still under evaluation.

However, Development may also introduce:

• New bugs.
• Incomplete features.
• Changed procedures.
• Unexpected performance behaviour.

FlyByWire describes Stable as its tested release while Development receives the latest additions and ongoing changelog updates.  

4. What About Experimental Builds?

Older A32NX installations were commonly discussed in terms of Stable, Development and Experimental.

Students should follow what is currently shown inside the official installer rather than relying on an old tutorial. Current release options and names may change over time.

If an Experimental or specialised branch is offered:

• Use it only for a specific feature.
• Expect reduced stability.
• Do not use it for an important online flight without testing.
• Keep benchmark records separate from Stable.
• Never install several variants of the same aircraft simultaneously unless the installer explicitly supports it.

For normal academy training, use Stable first.

5. A32NX Installation

Inside the installer:

1. Select the correct simulator.
2. Open the A32NX page.
3. Select Stable.
4. Choose Install.
5. Wait for completion.
6. Launch MSFS.
7. Search for the FlyByWire A320neo.
8. Do not accidentally choose the default Asobo A320neo.

A common mistake is loading the default A320 and assuming the flyPad or FlyByWire systems are missing. FlyByWire specifically notes that a missing flyPad can simply mean the wrong A320 was selected.  

6. A380X Installation

Inside the installer:

1. Select the correct simulator.
2. Open the A380X page.
3. Select Stable.
4. Choose the appropriate texture option.
5. Install the aircraft.
6. Allow the large download to complete.
7. Confirm sufficient free SSD space.
8. Launch MSFS.
9. Select the FlyByWire A380X.

The A380X requires substantially more storage and graphics memory than the A32NX. FlyByWire’s installation guidance recommends an SSD for the stronger experience and lists significantly higher storage and hardware expectations for the A380X.  

7. A380X Texture Options

Depending on the current installer and simulator build, the A380X may offer texture variants such as:

• 4K.
• 8K.
• A performance-focused or reduced-cabin variant.

Use a texture package suited to the GPU’s VRAM.

4K Textures

Recommended for:

• Mid-range GPUs.
• Lower VRAM cards.
• 1440p.
• Busy premium airports.
• Students prioritising smoothness.

8K Textures

Suitable for:

• High-end GPUs.
• Large VRAM capacity.
• High-resolution displays.
• Users prioritising cockpit and exterior texture detail.

The latest native MSFS 2024 A380X work also introduced a modular, performance-focused architecture including a “No Cabin” option intended to reduce VRAM usage and improve frame rate. Availability can vary by release branch, so students should check the current installer.  

8. MSFS 2024 Compatibility

Current stable A32NX and A380X releases are officially compatible with MSFS 2024. Earlier compatible releases were initially based on MSFS 2020 package architecture rather than native 2024 packages. FlyByWire has since moved towards separate native development for the two simulators.  

For MSFS 2024:

• Use the latest installer.
• Select MSFS 2024 explicitly.
• Install the aircraft branch shown for MSFS 2024.
• Do not copy the MSFS 2020 folder manually.
• Review simulator-specific release notes.
• Expect some differences between the 2020 and 2024 versions.

9. Updating the Aircraft

Before flying:

1. Close MSFS.
2. Open the FlyByWire Installer.
3. Select the correct simulator.
4. Review the installed aircraft.
5. Select Update if available.
6. Allow the update to finish.
7. Record the aircraft version.
8. Read the changelog after major updates.

The A32NX and A380X are designed for current simulator builds, and FlyByWire advises using the latest supported simulator and aircraft versions.  

10. Installing Liveries

Use liveries created specifically for:

• FlyByWire A32NX.
• FlyByWire A380X.
• Your simulator version.
• The current aircraft model.

Do not assume that a default Asobo A320neo livery is fully compatible with the A32NX.

For each livery:

1. Read the installation instructions.
2. Confirm the supported aircraft.
3. Check whether the installer or Community Folder is used.
4. Remove old versions first.
5. Install one copy only.
6. Load the aircraft using the default livery first.
7. Test the third-party livery afterwards.

For the A380X, use liveries explicitly designed for the FlyByWire aircraft. FlyByWire recommends compatible community liveries rather than assuming unrelated A380 packages will work.  

11. Navigation Data

The aircraft can use navigation information for:

• Airways.
• Waypoints.
• SIDs.
• STARs.
• Approaches.
• Navaids.

Compare the navigation cycle shown by:

• SimBrief.
• Aircraft MCDU or FMS.
• Navigraph.

A mismatch can cause:

• Waypoint not found.
• Airway not available.
• Missing procedures.
• Route discontinuities.
• Invalid entries.

A Navigraph subscription is not required merely to use SimBrief integration, but current Navigraph data helps keep SimBrief, charts and aircraft procedures aligned.  

12. Avoid Duplicate Default-Aircraft Modifications

The A32NX is a separate aircraft package.

Avoid:

• Old community A320 modifications.
• Legacy A32NX folders.
• Default A320 replacement mods.
• Multiple development copies.
• Manually installed and installer-managed versions together.
• Outdated cockpit or systems modifications.

Before troubleshooting:

1. Confirm only one A32NX package is active.
2. Remove older manual installations.
3. Test using the default FlyByWire livery.
4. Disable other A320 modifications.
5. Restart the simulator.

STEP 2 – CONFIGURATION AND FLYING

Part A – flyPad and Aircraft Setup

13. flyPad Setup

The flyPad is FlyByWire’s electronic flight bag used across the A32NX and A380X.

It provides access to areas such as:

• Dispatch.
• SimBrief.
• Fuel and payload.
• Ground services.
• Performance calculations.
• Charts.
• Checklists.
• Presets.
• Aircraft settings.
• Failures.
• Online ATC tools.

The dashboard is the default flyPad page and acts as the central access point for aircraft preparation.  

14. Initial flyPad Configuration

Open the flyPad and review:

• Units.
• SimBrief or Navigraph account.
• Realism options.
• Aircraft state.
• Cabin and sound settings.
• Fuel-loading speed.
• Boarding speed.
• Ground services.
• Throttle calibration.
• Flight-planning options.

Use the same units in:

• SimBrief.
• flyPad.
• MCDU or FMS.
• Performance pages.

15. Link SimBrief

The current integration uses the Navigraph account-linking process inside the flyPad.

Setup

1. Open flyPad Settings.
2. Open 3rd Party Options.
3. Select Link Account beside the Navigraph account option.
4. Follow the authentication process.
5. Generate a new SimBrief OFP.
6. Return to the flyPad.
7. Load the latest flight.

The integration itself does not require a paid Navigraph subscription.  

Use:

• A20N with the FlyByWire airframe for A32NX.
• The correct A380 aircraft type and FlyByWire airframe for A380X.

FlyByWire provides a maintained A32NX SimBrief airframe for the A20N type.  

16. Navigraph Charts

With an active Navigraph subscription, charts can be viewed through the flyPad.

Students can access:

• Airport diagrams.
• SID charts.
• STAR charts.
• ILS charts.
• RNAV charts.
• En-route charts.
• Moving-map functionality where supported.

FlyByWire documents direct Navigraph-chart access in the flyPad.  

Test both:

• Charts open in the flyPad.
• Charts closed.

This helps determine whether chart rendering affects EFB responsiveness on the student’s system.

17. Throttle Calibration

The A32NX and A380X use Airbus-style detents.

The flyPad provides a throttle-calibration system for both aircraft.  

Typical positions include:

• Full reverse.
• Reverse idle.
• Idle.
• Climb.
• Flex/MCT.
• TOGA.

Calibration Procedure

1. Open flyPad Settings.
2. Open throttle configuration.
3. Select the correct number of throttle axes.
4. Move each physical lever to full reverse.
5. Save the reverse range.
6. Move to idle.
7. Save idle.
8. Move to CL.
9. Save the climb detent.
10. Move to FLEX/MCT.
11. Save the detent.
12. Move to TOGA.
13. Save the final detent.
14. Apply the configuration.
15. Move the levers slowly through every position.

Confirm the cockpit or display shows the correct detent name.

Poor calibration can cause:

• LVR CLB warnings.
• Incorrect autothrust behaviour.
• Unexpected TOGA or FLEX selection.
• Failure to reach idle.
• Reverse thrust problems.  

18. A380 Throttle Considerations

The A380X uses four engines.

Students may have:

• Four physical throttle axes.
• Two axes controlling paired engines.
• One combined throttle axis.

Configure the flyPad for the actual hardware.

Test:

• Engines 1 and 2.
• Engines 3 and 4.
• Detent alignment.
• Reverse thrust.
• Symmetrical lever movement.

The A380’s reverse-thrust controls and engine indications differ from those of the A320neo and should be checked on the Engine/Warning Display.  

19. Cockpit Realism

Recommended training setup:

• Realistic flight model.
• Failures disabled initially.
• Default assistance reduced where practical.
• Standard Airbus automation.
• Realistic boarding or loading speed only when time allows.
• No random failures during the first flights.

Students should first learn normal operation before enabling advanced failure scenarios.

20. Sound Settings

Review:

• Cockpit sounds.
• Cabin ambience.
• Engine volume.
• Warning volume.
• Passenger announcements.
• Environmental sounds.
• PTU and system sounds on the A32NX.
• Four-engine and cabin audio on the A380X.

Avoid combining several external sound enhancements until the aircraft works correctly in its default configuration.

21. Payload and Fuel

After loading the SimBrief plan:

1. Open flyPad Dispatch or Ground.
2. Review passenger count.
3. Review cargo.
4. Review block fuel.
5. Begin loading.
6. Confirm Zero Fuel Weight.
7. Confirm centre of gravity.
8. Confirm take-off weight.
9. Compare values with the SimBrief OFP.

Use one coordinated loading method.

Do not independently load the aircraft through:

• flyPad.
• MSFS Weight and Balance.
• GSX.
• Another external loader.

unless the integration is specifically designed to synchronise those systems.

Part B – MCDU and FMS Programming

22. A32NX MCDU Preparation

On the A32NX:

1. Open the MCDU.
2. Review the aircraft and navigation cycle.
3. Open INIT.
4. Enter or import the route.
5. Confirm From/To.
6. Enter the alternate.
7. Enter the flight number.
8. Enter Cost Index.
9. Enter cruise altitude.
10. Review the flight-plan page.
11. Insert departure and arrival procedures.
12. Resolve only genuine discontinuities.
13. Complete weight and performance pages.

FlyByWire provides a dedicated beginner guide for A32NX MCDU preparation.  

23. A380X FMS Preparation

The A380X uses a more modern and extensive flight-management interface.

General preparation includes:

1. Load the SimBrief plan.
2. Verify the origin and destination.
3. Review the route.
4. Enter or confirm cost index.
5. Enter cruise altitude.
6. Review the departure runway and SID.
7. Review the arrival and approach.
8. Confirm fuel and weight.
9. Calculate take-off data.
10. Review route constraints.

FlyByWire provides a separate beginner guide for preparing the A380X FMS.  

Do not assume that every A32NX MCDU page appears identically in the A380X.

Part C – Cold and Dark Startup

24. A32NX Cold and Dark

At the stand:

1. Parking brake set.
2. Thrust levers at idle.
3. Engine masters off.
4. Battery 1 and Battery 2 on.
5. Connect external power through the flyPad.
6. Select external power on.
7. Set ADIRS selectors to NAV.
8. Arm emergency lights.
9. Set passenger signs.
10. Load fuel and payload.
11. Program the MCDU.
12. Prepare the overhead panel.
13. Start the APU before pushback.
14. Turn APU bleed on.
15. Disconnect external power when ready.

25. A380X Cold and Dark

The A380 requires more preparation because it has:

• Four engines.
• More electrical and hydraulic systems.
• Larger cabin and payload.
• More display and flight-management pages.
• More extensive ground-service requirements.

A condensed setup is:

1. Parking brake set.
2. Batteries on.
3. External power connected where available.
4. Navigation systems aligned.
5. Fuel and payload loaded.
6. Flight plan prepared.
7. Performance data calculated.
8. APU started.
9. APU generators and bleed configured.
10. Doors closed.
11. Beacon on.
12. Pushback clearance confirmed.

Use the aircraft checklists and flyPad presets to support learning, but do not rely on presets without understanding the resulting aircraft state.

Part D – Engine Start

26. A32NX Engine Start

Before start:

• Fuel pumps on.
• Beacon on.
• APU available.
• APU bleed on.
• Packs configured automatically or as required.
• Area clear.

Sequence:

1. Set 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 stable.
8. Return Engine Mode Selector to NORM.
9. Turn APU bleed off.
10. Shut down the APU when no longer required.

27. A380X Engine Start

The A380 has four engines.

Use the sequence recommended by the current aircraft checklist and operating guide.

A general simulator flow is:

1. Confirm APU power and bleed availability.
2. Confirm fuel pumps and fuel system.
3. Set engine-start controls.
4. Start the planned engine pair or sequence.
5. Monitor each engine’s rotation, fuel flow, EGT and oil pressure.
6. Confirm each engine stabilises before continuing.
7. Confirm all four generators and systems.
8. Configure bleed and packs after start.
9. Shut down the APU when appropriate.

Do not rush four-engine start monitoring. A stable start must be confirmed for every engine.

Part E – Managed Flight

28. Airbus Managed and Selected Modes

Both aircraft use Airbus flight-guidance principles.

Managed Mode

The aircraft follows the programmed flight-management target.

Examples:

• Managed speed.
• NAV.
• Managed climb.
• Managed descent.

Selected Mode

The pilot manually commands a target.

Examples:

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

As a general Airbus principle:

• Push for managed.
• Pull for selected.

Always confirm the actual mode on the Flight Mode Annunciator.

29. Take-off

Before take-off:

• Flight controls checked.
• Flaps set.
• Spoilers armed.
• Autobrake configured.
• Flight directors on.
• Initial altitude set.
• Take-off speeds confirmed.
• FLEX or TOGA calculated.
• Runway and SID checked.

Take-off flow:

1. Align with the runway.
2. Stabilise engine thrust.
3. Move thrust levers to FLEX/MCT or TOGA.
4. Confirm the correct FMA indication.
5. Maintain runway centreline.
6. At V1, continue.
7. Rotate at VR.
8. Follow the flight director.
9. Select gear up after positive climb.
10. Retract flaps according to the speed schedule.
11. Move thrust levers to CL when prompted.

On the A380X, monitor the performance of all four engines and use slower, deliberate control inputs appropriate to the aircraft’s size and inertia.

30. Climb

During climb:

• Confirm managed or selected mode.
• Follow ATC altitude clearances.
• Monitor speed and constraints.
• Confirm thrust levers remain in CL.
• Monitor engine indications.
• Check pressurisation.
• Compare fuel remaining with SimBrief.
• Monitor the FMA after every change.

31. Cruise

At cruise:

• Confirm level-off.
• Review fuel progress.
• Check destination weather.
• Review arrival charts.
• Prepare the descent.
• Monitor systems.
• Check the alternate.
• Confirm landing runway and approach.

For the A380X, long-haul flights require additional attention to:

• Fuel planning.
• Step climbs.
• Aircraft weight.
• Memory usage over several hours.
• Destination landing weight.

32. Descent

Before top of descent:

1. Select and verify the STAR.
2. Select the approach.
3. Review altitude constraints.
4. Enter destination weather.
5. Enter landing minima.
6. Calculate landing performance.
7. Set the cleared altitude.
8. Use managed descent where appropriate.
9. Use selected modes when ATC instructions require them.
10. Monitor the descent profile.

33. Approach

For an ILS approach:

1. Confirm the correct runway.
2. Confirm the ILS identifier.
3. Review the approach course.
4. Intercept from a suitable position.
5. Arm approach mode.
6. Monitor localiser capture.
7. Monitor glideslope capture.
8. Extend flaps progressively.
9. Lower the landing gear.
10. Stabilise the aircraft.
11. Complete the landing checklist.

For an RNAV approach:

• Confirm the procedure and minima.
• Monitor lateral and vertical guidance.
• Review the Flight Mode Annunciator.
• Do not treat RNAV exactly like ILS guidance.

34. Landing

For manual landing:

1. Disconnect the autopilot at a comfortable altitude.
2. Maintain stable approach speed.
3. Use small control inputs.
4. Begin the flare close to the runway.
5. Reduce thrust to idle.
6. Touch down on the main landing gear.
7. Lower the nose.
8. Select reverse thrust.
9. Monitor autobrake or apply manual braking.
10. Reduce reverse thrust as speed falls.

The A380 has considerably greater mass and wingspan than the A32NX. Students must account for:

• Slower response.
• Greater inertia.
• Higher cockpit eye position.
• Longer landing distance.
• Careful centreline control.
• Appropriate taxi speed.

35. Taxi-In and Shutdown

After leaving the runway:

• Flaps retract.
• Spoilers disarm.
• Landing lights off.
• Strobes off.
• Taxi lights on.
• APU start when required.
• Weather radar off.
• Transponder set appropriately.

At the stand:

1. Parking brake set.
2. External power connected or APU power established.
3. Engine masters off.
4. Beacon off.
5. Fuel pumps off.
6. Passenger signs adjusted.
7. Doors opened when engines are stopped.
8. Complete parking checks.

For full securing:

• Navigation systems off.
• Emergency lights off where appropriate.
• External power removed.
• Batteries off.

STEP 3 – PERFORMANCE AND COMPATIBILITY TESTING

36. Stable vs Development Test

Use identical conditions.

Record: