FLIGHT SIM MASTERY ACADEMY

Module 3 – iFly Boeing 737 MAX 8 Operations

Microsoft Flight Simulator 2020 & Microsoft Flight Simulator 2024 — PC

Estimated Lesson Time: 30–40 Minutes
Structure: Install → Configure and Operate → Test

---

Lesson Overview

Welcome to Module 3 of the Flight Sim Mastery Academy.

This lesson focuses on the iFly Boeing 737 MAX 8, the 737 MAX aircraft you currently use.

The iFly MAX 8 is a detailed simulation of the Boeing 737 MAX flight deck and aircraft systems. Flight1 currently distributes the MSFS product through the Flight1 Agent. The MSFS 2020 purchase also includes access to an MSFS 2024 compatibility version, which Flight1 currently describes as experimental. Students should therefore verify the latest compatibility status and product notes before using it in MSFS 2024.  

This module is designed to get students from installation to a complete basic flight without becoming a several-hour aircraft course.

Students will learn how to:

• Install the aircraft correctly.
• Update it through the Flight1 Agent.
• Configure its tablet and aircraft options.
• Connect SimBrief.
• Load fuel and payload.
• Program a basic FMC route.
• Prepare the aircraft from cold and dark.
• Start the engines.
• Use LNAV, VNAV and the autopilot.
• Complete a descent, approach, landing and shutdown.
• Test the aircraft for FPS, frame-time and compatibility problems.

---

Lesson Objectives

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

Install the correct iFly MAX 8 package.

Verify MSFS 2020 or MSFS 2024 compatibility.

Update the aircraft and manage liveries.

Connect the aircraft to SimBrief.

Configure essential tablet and aircraft options.

Set up basic flight controls.

Load fuel and payload correctly.

Program a basic FMC route.

Complete a simplified cold-and-dark startup.

Use LNAV, VNAV, autothrottle and the MCP.

Complete a basic arrival and landing.Compare the MAX’s performance with the PMDG 737.

---

STEP 1 – INSTALLATION

Installing the iFly Boeing 737 MAX 8

---

1. Confirm Your Simulator Version

Before installing, confirm whether you are using:

• Microsoft Flight Simulator 2020.
• Microsoft Flight Simulator 2024.

The Flight1 product currently provides the established MSFS 2020 version and an MSFS 2024 compatibility upgrade described as experimental. Students using MSFS 2024 should expect that compatibility, behaviour and update requirements may change as development continues.  

Do not manually copy the MSFS 2020 aircraft folder into MSFS 2024 unless current official instructions specifically direct you to do so.

Use the Flight1 Agent and the installation option intended for your simulator.

---

2. Install the Flight1 Agent

The Flight1 Agent manages the purchase, installation and updates for the iFly MAX 8. The aircraft is listed as an Agent-managed MSFS product.  

Installation Procedure

1. Close Microsoft Flight Simulator.
2. Download the Flight1 Agent from Flight1’s official website.
3. Run the installer.
4. Sign into the Flight1 account used to purchase the aircraft.
5. Allow the Agent to detect your installed simulator.
6. Confirm whether MSFS 2020, MSFS 2024 or both are detected.
7. Do not proceed until the selected simulator path is correct.

Students with both simulators installed must check the destination carefully.

---

3. Purchase or Register the Aircraft

Inside the Flight1 Agent:

1. Locate iFly 737 MAX8 for MSFS.
2. Purchase the aircraft or open the registered product.
3. Confirm that the licence is linked to the correct account.
4. Select the correct simulator installation.
5. Begin the download.
6. Allow the entire installation to finish before launching MSFS.

Do not interrupt the installation or move the package manually afterwards.

---

4. Install Updates

Before the first flight:

1. Open the Flight1 Agent.
2. Select the iFly MAX 8.
3. Check for updates.
4. Read any available update notes.
5. Install the latest compatible version.
6. Confirm that the update completed successfully.
7. Record the aircraft version in your Performance Profile.

Updates may affect:

• Aircraft systems.
• Displays.
• Flight model behaviour.
• SimBrief integration.
• Liveries.
• Performance.
• MSFS 2024 compatibility.

Complete a short test flight after major updates before using the aircraft on VATSIM or a long route.

---

5. Install Liveries

Liveries should match the iFly MAX 8 specifically.

Recommended Procedure

1. Use the livery system supported by the Flight1 Agent or the livery developer.
2. Confirm that the livery is made for the iFly MAX 8.
3. Confirm support for your simulator version.
4. Install only one copy.
5. Launch the simulator.
6. Check that the livery appears under the correct aircraft.
7. Inspect the exterior for missing or low-resolution textures.

Avoid keeping old and updated versions of the same livery active.

Begin with only a few liveries. Large livery collections can increase storage use and package-scanning time.

---

6. Check Navigation Data

The aircraft’s FMC uses navigation data containing:

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

Compare the AIRAC cycle shown in:

• SimBrief.
• The iFly FMC.
• Navigraph, where used.

An AIRAC mismatch may cause:

• Waypoint not found.
• Airway not found.
• Missing departure procedure.
• Missing arrival procedure.
• Invalid entry.

This does not necessarily mean the aircraft is installed incorrectly.

---

7. Create the Correct SimBrief Profile

In SimBrief, select the correct aircraft type:

B38M – Boeing 737 MAX 8

Use an iFly-specific airframe profile where an official or trusted profile is available.

Confirm:

• Aircraft type.
• Engine type.
• Units.
• Registration.
• Passenger configuration.
• Basic weight.
• Fuel capacity.

Do not use a PMDG 737-800 NG profile for the MAX 8. The aircraft have different engines, weights, performance and fuel characteristics.

---

8. First Installation Test

For the first load, use:

• A default airport.
• A parking stand.
• Clear Skies.
• Daytime.
• AI traffic disabled.
• Default iFly livery.

Confirm:

• The aircraft appears in the selection menu.
• The cockpit loads.
• The tablet loads.
• The displays initialise.
• No missing-texture warning appears.
• No crash occurs.

Allow the aircraft to finish loading before operating switches.

---

STEP 2 – CONFIGURATION AND OPERATION

Configuring and Flying the MAX 8

---

9. Configure the Tablet

The aircraft tablet or EFB should be your main starting point for configuration.

Review:

• Aircraft state.
• Fuel.
• Payload.
• Ground services.
• SimBrief connection.
• Performance options.
• Units.
• Doors.
• Maintenance or failure options.
• Display or sound settings.

For the first flight, keep advanced failures disabled.

Use a simple, known-good configuration before adding airline-specific options.

---

10. Select the Correct Units

Choose:

• Kilograms, or
• Pounds.

Use the same unit in:

• SimBrief.
• Tablet.
• FMC.
• Payload page.
• Performance calculations.

A unit mismatch can produce incorrect fuel and weight figures.

---

11. Configure Aircraft State

Choose an initial state such as:

Cold and Dark

All major systems are off.

Best for learning the complete startup.

Turnaround

The aircraft is powered and partially prepared.

Best for quicker normal flights.

Ready for Take-off

Useful for testing but not recommended for learning normal preparation.

For this module, use Cold and Dark so students understand the basic aircraft flow.

---

12. Configure Controls

Check the following axes:

• Elevator.
• Aileron.
• Rudder.
• Throttle 1.
• Throttle 2.
• Brakes.
• Nose-wheel steering or tiller.
• Reverse thrust.

Remove duplicate controller bindings.

Test the throttle levers in the cockpit and verify:

• Engine 1 and Engine 2 respond correctly.
• Both reach idle.
• Both reach full forward travel.
• Reverse thrust does not activate accidentally.
• No axis jumps or flickers.

Use small dead zones only where hardware drift exists.

---

13. Load the SimBrief Flight

Generate a new flight using the B38M profile.

Then:

1. Enter the SimBrief username or Pilot ID in the tablet or aircraft settings.
2. Request the latest flight.
3. Confirm the departure airport.
4. Confirm the destination.
5. Confirm the flight number.
6. Review the planned block fuel.
7. Review passengers and cargo.
8. Import the flight where supported.

A full route import still requires verification in the FMC.

---

14. Load Fuel and Payload

Use one primary loading method.

Recommended approach:

1. Retrieve the SimBrief plan.
2. Open the tablet’s fuel and payload page.
3. Load the planned passengers.
4. Load the cargo.
5. Load the planned block fuel.
6. Confirm the resulting Zero Fuel Weight.
7. Confirm the estimated Take-off Weight.
8. Compare the figures with the SimBrief OFP.

Do not load weight simultaneously through:

• The iFly tablet.
• The MSFS Weight and Balance menu.
• GSX.
• Another external loader.

One system may overwrite the other.

---

Basic Cold-and-Dark Startup

The following is a condensed training flow. It is designed to get the student flying safely in the simulator rather than replace the complete manufacturer or aircraft documentation.

---

15. Establish Electrical Power

1. Set the parking brake.
2. Confirm the battery switch is ON.
3. Set standby power to the normal or automatic operating position.
4. Connect ground power through the tablet if available.
5. When ground power becomes available, select it ON.
6. Confirm that the cockpit displays and panels receive power.

If ground power is unavailable, the APU will be used later to supply electrical power.

---

16. Begin IRS Alignment

On the overhead panel:

1. Set both IRS selectors from OFF to NAV.
2. Open the FMC position-initialisation page.
3. Confirm the airport reference position.
4. Copy the current GPS or gate position.
5. Insert it into the required IRS position field.
6. Allow the alignment process to complete.

The displays may not provide full navigation information until alignment finishes.

---

17. Prepare the Overhead Panel

Complete a basic scan:

• Electrical power established.
• Emergency lights armed where appropriate.
• Window heat set as required before departure.
• Passenger signs configured.
• Fuel pumps left off until fuel and engine-start preparation requires them.
• Hydraulic pumps configured for the current stage.
• Air-conditioning packs reviewed.
• Anti-collision light left off until pushback or engine start.
• Probe heat left off while parked unless procedure requires otherwise.

The exact airline flow may vary. This module teaches a general simulator setup.

---

Basic FMC Programming

---

18. IDENT and POS INIT

On the FMC:

1. Open the IDENT page.
2. Confirm the aircraft model.
3. Check the navigation-data cycle.
4. Open POS INIT.
5. Enter the reference airport.
6. Confirm the aircraft position.
7. Complete IRS position entry.

---

19. Route Page

Enter or import:

• Origin.
• Destination.
• Flight number.
• Departure runway where known.
• Route or company route.

After importing:

1. Open the LEGS page.
2. Step through the route.
3. Check for missing waypoints.
4. Check for route discontinuities.
5. Do not delete a discontinuity blindly.
6. Confirm the route before pressing EXEC.

---

20. Departure and Arrival Procedures

Open the departure and arrival page.

Select:

• Departure runway.
• SID.
• SID transition.
• Arrival STAR.
• STAR transition.
• Approach where known.

Runways and procedures may change during the flight, especially when using VATSIM or BeyondATC.

Always review the route after inserting a procedure.

---

21. Performance Initialisation

Enter or confirm:

• Zero Fuel Weight.
• Reserves.
• Cost Index.
• Cruise altitude.
• Transition altitude where appropriate.

Check the SimBrief OFP for these values.

---

22. Take-off Reference

Enter or calculate:

• Flap setting.
• Centre of gravity.
• Trim.
• Take-off thrust setting where supported.
• V1.
• VR.
• V2.

Verify that:

• The weight is correct.
• The runway is correct.
• The flap setting matches the planned configuration.
• The trim is set before take-off.

Do not use copied V-speeds from a previous flight.

---

23. Configure the MCP

Set:

• Initial cleared altitude.
• Runway or departure heading where required.
• Initial speed where appropriate.
• Flight directors on.
• Autothrottle armed.
• LNAV armed if the route and runway conditions support it.
• VNAV armed if the performance pages are complete.

Do not set the cruise altitude in the MCP if ATC has only cleared the aircraft to a lower initial altitude.

---

Engine Start

---

24. Prepare for Pushback

Before pushback:

1. Confirm doors are closed.
2. Confirm fuel and payload loading is complete.
3. Turn the anti-collision light on.
4. Start the APU if ground power will be disconnected.
5. Switch APU generators on when available.
6. Configure fuel pumps.
7. Configure pneumatic air for engine start.
8. Confirm the area is clear.

---

25. Start the Engines

A typical sequence is:

1. Start Engine 2 first.
2. Move the Engine 2 start switch to GRD.
3. Monitor N2 rotation.
4. At the required N2 indication, move the Engine 2 fuel control lever to IDLE.
5. Monitor oil pressure, EGT, N1 and N2.
6. Confirm the engine stabilises.
7. Repeat for Engine 1.
8. Confirm both generators are supplying power.

Never introduce fuel if there is no engine rotation.

---

26. After-Start Configuration

After both engines stabilise:

• Generators confirmed.
• Probe heat on.
• Engine bleeds on.
• Packs configured.
• APU bleed off.
• APU shut down when no longer required.
• Hydraulic pumps configured.
• Flaps set.
• Flight controls checked.
• Trim confirmed.
• Taxi light on when moving.

---

Taxi and Take-off

---

27. Taxi

Release the parking brake and apply only enough thrust to begin moving.

During taxi:

• Maintain a controlled speed.
• Use the tiller for larger turns.
• Use rudder inputs gently.
• Check the flight instruments.
• Check the brakes.
• Confirm the take-off configuration before entering the runway.

The MAX can accelerate quickly at light weights, so avoid excessive thrust.

---

28. Before Take-off

Confirm:

• Flaps set.
• Trim set.
• Speedbrake armed.
• Autobrake set to the planned rejected-take-off mode.
• Flight directors on.
• Autothrottle armed.
• MCP altitude correct.
• V-speeds displayed.
• Runway and route verified.
• Landing lights on.
• Strobe lights on.

---

29. Take-off

1. Align with the runway centreline.
2. Stabilise the engines at an intermediate thrust.
3. Press the take-off/go-around command.
4. Monitor thrust setting.
5. Maintain centreline.
6. At V1, continue the take-off unless a serious simulator emergency demands otherwise.
7. At VR, rotate smoothly.
8. Establish the initial climb.
9. Select gear up after a positive rate of climb.

Follow the flight director rather than making aggressive pitch changes.

---

LNAV, VNAV, Climb and Cruise

---

30. LNAV

LNAV commands the aircraft to follow the lateral FMC route.

Before relying on it:

• Confirm the active waypoint.
• Confirm the route is executed.
• Check that there are no unexpected discontinuities.
• Monitor the aircraft’s initial turn.

Automation must be monitored rather than assumed to be correct.

---

31. VNAV

VNAV manages vertical guidance based on:

• FMC route.
• Altitude constraints.
• Aircraft weight.
• Speed schedule.
• Performance data.

VNAV will not work correctly if the FMC setup is incomplete.

Monitor:

• Speed.
• Thrust mode.
• Pitch mode.
• Altitude restrictions.
• Flight Mode Annunciator.

---

32. Autopilot Engagement

Engage the autopilot only after the aircraft is safely established in the climb and above the minimum permitted engagement height represented by the simulation and procedure being followed.

After engagement:

• Confirm the correct lateral mode.
• Confirm the correct vertical mode.
• Confirm autothrottle mode.
• Monitor the aircraft’s path.

Always read the Flight Mode Annunciator after selecting an automation mode.

---

33. Climb

During climb:

• Retract flaps according to the speed schedule.
• Monitor engine parameters.
• Check pressurisation.
• Verify the cleared altitude.
• Update the MCP when cleared higher.
• Monitor LNAV and VNAV.
• Check fuel balance.

Do not allow VNAV to climb through an ATC restriction that has not been cleared.

---

34. Cruise

At cruise:

• Confirm the aircraft levels correctly.
• Check fuel remaining against SimBrief.
• Monitor pressurisation.
• Check weather ahead.
• Review the arrival.
• Confirm destination and alternate weather.
• Prepare the descent before reaching the top of descent.

---

Descent and Approach

---

35. Prepare the Arrival

Before descent:

1. Review destination weather.
2. Confirm the expected runway.
3. Insert the STAR and approach.
4. Review altitude constraints.
5. Check for route discontinuities.
6. Enter approach reference information.
7. Set landing minimums.
8. Complete the approach briefing.

Do not wait until final approach to program the arrival.

---

36. Descent

Set the cleared lower altitude on the MCP before the top of descent.

VNAV may begin the descent automatically when:

• The route is valid.
• The descent path is calculated.
• The MCP altitude permits descent.
• The correct mode is active.

Monitor the vertical path carefully.

Use speedbrake only when needed and retract it when no longer required.

---

37. ILS Approach Setup

For an ILS approach:

1. Confirm the correct ILS frequency.
2. Confirm the final approach course.
3. Set both where required by the aircraft.
4. Confirm the localiser identifier.
5. Arm the approach mode when cleared and appropriately positioned.
6. Monitor localiser capture.
7. Monitor glideslope capture.
8. Configure flaps progressively.
9. Lower the landing gear.
10. Set landing flaps.
11. Confirm landing checklist complete.

Do not arm the approach from an incorrect intercept angle or altitude and expect automation to recover the situation.

---

38. Landing

For a manual landing:

1. Disconnect the autopilot at a comfortable height.
2. Continue monitoring speed and vertical path.
3. Maintain runway alignment.
4. Begin a gentle flare near the runway.
5. Reduce thrust smoothly.
6. Touch down on the main landing gear.
7. Allow the nose to lower.
8. Deploy reverse thrust.
9. Monitor autobrake or apply manual braking.
10. Reduce reverse thrust as the aircraft slows.

Avoid holding the aircraft off the runway excessively.

---

Taxi-In and Shutdown

---

39. After Landing

After leaving the runway:

• Retract flaps.
• Disarm speedbrake.
• Turn off landing and strobe lights as appropriate.
• Turn on taxi light.
• Start the APU if required at the stand.
• Review transponder and weather radar configuration.

Do not complete the full after-landing flow while still occupying the active runway.

---

40. Shutdown

At the stand:

1. Set the parking brake.
2. Connect ground power or start the APU.
3. Confirm electrical power is available.
4. Move both fuel control levers to cutoff.
5. Turn off the anti-collision light.
6. Turn off fuel pumps.
7. Configure hydraulic pumps.
8. Turn off probe heat.
9. Set passenger signs appropriately.
10. Open doors only after the engines have stopped.
11. Complete the parking checklist.

For complete securing:

• IRS selectors off.
• Emergency lights off where appropriate.
• Battery off after external power has been removed and the aircraft is fully secured.

---

MAX-Specific Differences From the 737 NG

The MAX 8 retains the general Boeing 737 cockpit philosophy but includes important differences from the PMDG 737 NG.

These include:

• Larger cockpit displays.
• LEAP-1B engines.
• Different engine indications.
• MAX-specific system logic.
• Updated flight-deck presentation.
• Different performance and fuel behaviour.
• Different weights and take-off calculations.
• Modified flight-control and alerting features represented by the add-on.

Flight1 describes the iFly aircraft as modelling MAX 8-specific differences from the 737 NG rather than simply reproducing an NG cockpit with new engines.  

Students should not copy PMDG 737-800 performance figures directly into the MAX.

---

STEP 3 – TESTING

Performance and Compatibility Testing

---

41. Establish a Fair Comparison

Compare the iFly MAX 8 with the PMDG 737 under identical conditions.

Use the same:

• Airport.
• Parking stand.
• Weather.
• Time of day.
• Graphics settings.
• Traffic settings.
• Camera view.
• Route where practical.

Record the aircraft version used in each test.

---

42. Systems-Performance Load

While parked with both aircraft fully powered, record:

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

A difference between aircraft does not automatically mean one is badly optimised.

Each aircraft may use different:

• Systems calculations.
• Display technology.
• Texture resolution.
• Tablet processes.
• Sound systems.
• Exterior modelling.

---

43. Display Refresh Test

The MAX’s large cockpit displays may place a noticeable load on the system.

Test:

1. Cold-and-dark cockpit.
2. All displays powered.
3. Map range changed.
4. FMC pages changed.
5. Tablet opened.
6. Tablet closed.
7. Exterior view selected.
8. Cockpit view restored.

Record any:

• FPS reduction.
• Frame-time spike.
• Delayed display movement.
• MainThread increase.
• GPU load increase.

If the aircraft provides display-performance options, test one change at a time.

---

44. Premium-Airport Test

Load the aircraft at:

1. A default airport.
2. A detailed premium airport.

Keep all other conditions identical.

Record:

• Loading time.
• FPS.
• 1% lows.
• MainThread status.
• VRAM.
• Overall smoothness.

If performance falls only at the premium airport, investigate:

• Airport object density.
• Static aircraft.
• AI traffic.
• Airport workers.
• Ground vehicles.
• High-resolution textures.

Do not immediately blame the aircraft.

---

45. Livery Impact

Compare:

• Default iFly livery.
• One third-party airline livery.

Record:

• Loading time.
• Exterior VRAM usage.
• Texture quality.
• FPS.
• Missing textures.
• CTDs.

A badly packaged or extremely high-resolution livery may use more VRAM or load more slowly.

If only one livery causes a problem, remove that livery rather than reinstalling the full aircraft.

---

46. SimBrief Import Test

Generate a fresh B38M plan.

Confirm:

• Correct origin.
• Correct destination.
• Correct route.
• Correct cruise altitude.
• Correct units.
• Correct fuel.
• Correct payload.
• No old flight remains loaded.

Record the retrieval time.

If the plan does not appear, check:

• A new plan was generated.
• The correct SimBrief account is entered.
• Internet connection.
• Aircraft integration.
• AIRAC cycle.

---

47. Traffic Compatibility

Test the aircraft with:

• No traffic.
• MSFS traffic.
• FSLTL or another injector.

Do not run several traffic systems together.

Record:

• MainThread status.
• 1% lows.
• Taxi smoothness.
• Approach smoothness.
• AI model loading.

Traffic is usually a major CPU variable at busy airports.

---

48. GSX Compatibility

When using GSX:

1. Load the aircraft at a compatible stand.
2. Confirm doors are recognised correctly.
3. Test boarding.
4. Test baggage loading.
5. Test pushback.
6. Confirm payload values are not being overwritten unexpectedly.
7. Watch for duplicate ground vehicles.
8. Monitor FPS and frame times.

Use either GSX or the aircraft tablet as the primary loading method unless the supported integration coordinates both systems correctly.