Lesson Overview

The PMDG 737 is a highly detailed Boeing airliner designed to recreate the systems, displays and operating behaviour of the real aircraft.

In this lesson, students will learn how to:

• Install the correct PMDG 737 version.
• Keep the aircraft and liveries updated.
• Connect SimBrief and Navigraph.
• Configure the essential aircraft options.
• Set up basic flight controls.
• Load fuel and payload.
• Confirm the aircraft works correctly.
• Test its effect on loading time, FPS, MainThread performance and VRAM.

This lesson focuses only on getting the aircraft installed, configured and ready to use.

A separate PMDG 737 flying module will later cover:

• Cold and dark startup.
• FMC programming.
• Engine start.
• Taxi.
• Take-off.
• LNAV and VNAV.
• Descent.
• Approach.
• Landing.
• Shutdown.

Lesson Objectives

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

Select the correct PMDG product for their simulator.

Install and update the aircraft correctly.

Install liveries without creating duplicate packages.

Configure the main aircraft and realism options.

Connect the aircraft to SimBrief.

 Confirm navigation data compatibility.

Configure basic throttle, rudder and tiller controls.

Load fuel and payload correctly.

Complete a basic aircraft functionality test.

Measure the aircraft’s effect on simulator performance.

STEP 1 – INSTALLATION

Installing the PMDG 737

1. Confirm Your Simulator Version

Before downloading anything, confirm whether you are installing the aircraft for:

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

Do not assume that one package automatically works in both simulators.

Use only the version officially listed as compatible with your simulator. Aircraft compatibility, installation tools and package locations may differ between MSFS 2020 and MSFS 2024.

2. Choose the Correct 737 Variant

The PMDG 737 family may be sold in separate packages or variants.

These can include aircraft such as:

• 737-600.
• 737-700.
• 737-800.
• 737-900.

Students should choose the variant they genuinely plan to fly.

The 737-800 is usually the most familiar choice because it is widely operated by airlines and supported by many liveries.

Each variant has differences in:

• Aircraft length.
• Passenger capacity.
• Weight.
• Fuel burn.
• Take-off performance.
• Handling.
• Available liveries.

3. Purchase and Download

Purchase the product through the official PMDG store or another officially supported platform.

After purchase:

1. Sign into the PMDG account used for the order.
2. Open the product download area.
3. Download the correct installer.
4. Confirm the file matches your simulator version.
5. Close Microsoft Flight Simulator before installation.
6. Run the installer.
7. Select the correct simulator when prompted.
8. Allow the installation to complete.
9. Restart the PC if requested.

Avoid unofficial aircraft downloads or modified installers. These may contain incomplete files, outdated versions or unsafe software.

4. PMDG Operations Center

The PMDG Operations Center is used to manage supported PMDG products.

It may provide access to:

• Product updates.
• Aircraft variants.
• Liveries.
• Installed-product information.
• Repair or maintenance options.

After installing the aircraft:

1. Open PMDG Operations Center.
2. Sign into the correct account where required.
3. Confirm that the aircraft appears.
4. Check for updates.
5. Install available product updates.
6. Restart Operations Center after updating if requested.

Always close the simulator before applying aircraft or livery updates.

5. Installing Liveries

Liveries change the aircraft’s external airline paint scheme.

To install one:

1. Open PMDG Operations Center.
2. Select the correct 737 variant.
3. Open the livery section.
4. Choose an available livery or import a supported livery package.
5. Complete the installation.
6. Launch the simulator.
7. Confirm the livery appears under the correct aircraft variant.

Do not install the same livery manually and through Operations Center simultaneously.

Duplicate liveries can:

• Increase Community Folder size.
• Create confusing aircraft entries.
• Cause outdated textures to remain active.
• Make troubleshooting harder.

Start with only a small selection of liveries. Hundreds of unused liveries add storage and package-scanning overhead without improving the flight.

6. Confirm the Aircraft Is Installed

Launch MSFS and open the aircraft-selection menu.

Confirm:

• The correct PMDG 737 variant appears.
• The aircraft thumbnail loads correctly.
• Installed liveries appear.
• No duplicate aircraft entries are present.
• The aircraft can be selected without an error.

For the first test, use:

• A default airport.
• Clear Skies.
• Daylight.
• No AI traffic.
• A parking stand rather than a runway start.

This creates a simple test environment.

STEP 2 – CONFIGURATION

Essential PMDG 737 Setup

7. Load the Aircraft Safely for the First Time

For the initial setup:

1. Choose a simple default airport.
2. Select a parking stand.
3. Use Clear Skies.
4. Disable unnecessary traffic.
5. Load the PMDG 737.
6. Allow the cockpit to initialise fully.
7. Avoid immediately pressing controls while the aircraft is loading.

The first load may take longer because the simulator is processing the aircraft and related files.

8. Aircraft Setup Pages

The PMDG 737 includes configuration pages through its cockpit systems and, depending on the product version, may also provide tablet-based options.

The setup areas generally control:

• Aircraft equipment.
• Display options.
• Units.
• Realism.
• Ground services.
• Fuel and payload.
• Panel states.
• Failures.
• Maintenance.

Students do not need to change everything.

Begin with the essential options only.

9. Set the Correct Units

Choose either:

• Kilograms.
• Pounds.

This should match the unit selected in SimBrief.

For example:

If SimBrief plans fuel in kilograms, configure the aircraft to display kilograms.

A unit mismatch may cause the student to load an incorrect amount of:

• Fuel.
• Cargo.
• Payload.

Confirm the unit before importing or manually entering weight information.

10. Configure Realism

For normal training, use realistic but manageable settings.

Recommended starting approach:

• Realistic flight controls.
• Normal system operation.
• Failures disabled.
• Service-based failures disabled initially.
• Assistance features used only where needed.

Failures should remain off while students are learning installation and basic operation. Random technical failures make it difficult to determine whether the aircraft has been configured correctly.

11. Equipment Options

Equipment options allow the virtual aircraft to represent different airline configurations.

These may include:

• Display types.
• Navigation equipment.
• Performance features.
• Warning systems.
• Cabin or exterior equipment.

For initial use:

• Leave most equipment at its default configuration.
• Avoid changing several items at once.
• Save advanced airline-specific configurations for a later lesson.

The objective is to establish a known-good aircraft before creating custom fleets.

12. Panel States

Panel states allow the aircraft to load in a particular condition.

Common examples include:

• Cold and Dark.
• Turnaround.
• Short turnaround.
• Ready for take-off.

For normal training, students should use either:

Cold and Dark

Best for learning the complete startup process.

Turnaround

Useful for quicker flights while still requiring normal cockpit preparation.

Avoid using a runway-ready state when testing installation because it skips much of the aircraft initialisation process.

13. Connect SimBrief

Before continuing, generate a valid SimBrief flight.

Then configure the PMDG integration.

Depending on the aircraft version, this may involve entering:

• SimBrief username.
• SimBrief Pilot ID.
• Navigraph account details through the supported interface.

After linking the account:

1. Generate a new SimBrief flight.
2. Open the PMDG flight-planning or route-request area.
3. Request the latest flight.
4. Confirm the correct departure and destination appear.
5. Check that an old flight has not been imported.

A full FMC-programming tutorial will come later. At this stage, students only need to confirm that the connection works.

14. Check Navigraph and AIRAC Data

Compare the navigation-data cycle shown by:

• SimBrief.
• PMDG FMC.
• Navigraph, where used.

If the cycles differ, the route may contain:

• Missing waypoints.
• Unavailable airways.
• Missing SIDs.
• Missing STARs.
• Invalid procedures.

Students without a current navigation-data subscription may still use SimBrief, but they should understand that some route differences can occur.

Do not assume a failed waypoint means the aircraft installation is broken.

15. Basic Control Configuration

Open the MSFS control settings and confirm the essential axes.

Configure:

• Pitch.
• Roll.
• Rudder.
• Throttle 1.
• Throttle 2.
• Brakes.
• Parking brake.
• Nose-wheel steering or tiller where supported.

16. Throttle Setup

Ensure that:

• Throttle 1 controls engine 1.
• Throttle 2 controls engine 2.
• Both axes move smoothly.
• Reverse thrust does not activate accidentally.
• No duplicate throttle bindings exist.

Move the physical throttle slowly while watching the cockpit levers.

The movement should be:

• Smooth.
• Correctly aligned.
• Free from sudden jumps.
• Able to reach idle and full forward travel.

Remove duplicate assignments from unused controllers.

17. Rudder and Tiller Setup

The rudder controls aircraft yaw and provides limited steering.

The tiller provides greater nose-wheel steering during taxi.

Depending on the student’s hardware:

• A separate tiller axis may be used.
• Rudder pedals may control steering.
• A combined setup may be configured through aircraft options.

Test at low speed before beginning a normal flight.

Avoid excessive steering sensitivity, which can cause the aircraft to move sharply across the taxiway.

18. Dead Zones and Sensitivity

Use small dead zones only when required.

A dead zone may help if:

• The controller produces unwanted movement.
• The rudder does not remain centred.
• The aircraft drifts without input.
• The throttle fluctuates.

Avoid applying large dead zones unnecessarily because they reduce control precision.

Begin close to the default sensitivity and make gradual adjustments.

19. Load Fuel and Payload

Open the PMDG fuel and payload system.

Compare it with the SimBrief OFP.

Confirm:

• Passenger count.
• Cargo.
• Zero Fuel Weight.
• Block Fuel.
• Estimated Take-off Weight.

Load the values through the method supported by the aircraft.

Do not simultaneously load weight using:

• PMDG.
• MSFS Weight and Balance.
• GSX.
• Another external tool.

Using multiple loading systems at once may overwrite values or create mismatches.

Choose one primary method and verify the final figures.

20. Ground Services

Review the available ground services.

These may include:

• Ground power.
• Air start unit.
• Chocks.
• Stairs.
• Doors.
• Catering.
• Baggage loading.

For the first test:

1. Set the parking brake.
2. Apply chocks if available.
3. Connect ground power.
4. Confirm the aircraft receives electrical power.
5. Test one door.
6. Confirm it opens and closes correctly.

Advanced GSX integration will be covered in its own module.

21. Sound and Cockpit Options

Review:

• Cockpit sound volume.
• Exterior sound volume.
• Warning volume.
• Cabin sound options.
• Display brightness.

Avoid setting every display to maximum brightness. Very bright displays can look unrealistic, particularly at night.

If the aircraft includes display-refresh or performance-related options, begin with the default setting. Test performance before reducing visual quality.

22. Save the Initial Configuration

Once the essential settings are correct, record:

• Units.
• Realism.
• Panel state.
• SimBrief account.
• Control profile.
• Fuel-loading method.
• Ground-service method.

Take screenshots where useful.

This creates a known-good starting point that can be restored if future changes introduce a problem.

STEP 3 – TESTING

Performance, Stability and Compatibility Test

23. Why Test the PMDG 737?

The PMDG 737 is more demanding than a simple default aircraft because it includes:

• Detailed systems.
• Multiple cockpit displays.
• Advanced flight management.
• High-resolution textures.
• Complex cockpit modelling.
• Background aircraft logic.

The objective is not to expect identical FPS to a Cessna.

The objective is to confirm that the aircraft’s performance is:

• Stable.
• Predictable.
• Appropriate for the student’s hardware.
• Free from unusual conflicts.

24. Establish a Comparison Aircraft

Choose a simple default aircraft and load it at the same airport and stand.

Record:

• Flight loading time.
• Average FPS.
• 1% lows.
• MainThread status.
• GPU utilisation.
• VRAM usage.
• RAM usage.

Then load the PMDG 737 using the same:

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

This creates a fair comparison.

25. Measure Loading Time

Record:

Default aircraft

Time from pressing Fly until the cockpit is ready.

PMDG 737

Time from pressing Fly until the aircraft is fully loaded and responsive.

A longer PMDG loading time is expected because the aircraft contains more complex systems and files.

Investigate only if loading is:

• Excessively long.
• Stuck.
• Repeatedly failing.
• Causing a CTD.

26. Monitor FPS and MainThread

Use the same monitoring tools taught in Performance Academy.

Record:

• Average FPS.
• 1% low.
• Frame times.
• MainThread status.
• GPU-limited status.

A complex aircraft often increases CPU workload.

Possible result:

• GPU utilisation falls.
• MainThread limitation increases.
• FPS decreases compared with a default aircraft.

That does not automatically indicate a fault.

It shows that the aircraft is using more CPU resources.

27. Monitor RAM and VRAM

Record:

• Total RAM usage.
• VRAM usage.
• GPU utilisation.
• GPU temperature.
• CPU temperature.

Look for:

• VRAM reaching capacity.
• Large frame-time spikes.
• Texture pop-in.
• Abnormal memory growth.
• Performance worsening over time.

Compare the results with the student’s normal Performance Profile.

28. Cockpit Display Test

While parked:

1. Look forward.
2. Pan across the cockpit.
3. Open the FMC.
4. Change display pages.
5. Adjust display brightness.
6. Open the aircraft tablet where available.
7. Close the tablet.
8. Switch to the external view.
9. Return to the cockpit.

Record any:

• Large FPS drops.
• Camera stutters.
• Delayed display updates.
• Frozen screens.
• CTDs.

Small performance differences between views may be normal. Severe or repeated problems require investigation.

29. SimBrief Import Test

Generate a fresh flight and import it.

Confirm:

• Correct origin.
• Correct destination.
• Correct flight number.
• Correct cruise altitude.
• Route available.
• No old flight loaded.
• No account error appears.

Record the time required to retrieve the plan.

A failed import is more likely to involve:

• Incorrect SimBrief account.
• No generated plan.
• Network problem.
• AIRAC mismatch.
• Aircraft integration issue.

It does not automatically mean the entire aircraft must be reinstalled.

30. Livery Test

Test the aircraft using:

1. The default PMDG livery.
2. One installed airline livery.

Compare:

• Loading time.
• VRAM usage.
• Texture quality.
• Exterior FPS.
• Any missing textures.

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

31. Community Folder Test

If the aircraft has problems:

1. Save the current add-on profile.
2. Disable unrelated Community Folder packages.
3. Leave only the PMDG aircraft and required components active.
4. Load at a default airport.
5. Retest.

If the problem disappears, re-enable packages by category:

• Airports.
• Traffic.
• Utilities.
• Liveries.
• Ground services.

This identifies conflicts without deleting the full simulator installation.

32. Common Problems

PMDG Aircraft Does Not Appear

Check:

• Correct simulator version.
• Installation path.
• Operations Center status.
• Product update.
• Duplicate or incomplete installation.

Aircraft Loads With Blank Displays

Allow the aircraft to initialise fully.

Then check:

• Electrical power.
• Panel state.
• Product version.
• Required background components.
• Add-on conflicts.

SimBrief Flight Does Not Import

Check:

• A flight has been generated.
• Correct username or Pilot ID.
• Internet connection.
• Correct origin and destination.
• Aircraft integration settings.

Missing Waypoints

Check the AIRAC cycle.

Throttles Move Incorrectly

Check:

• Separate axes.
• Duplicate bindings.
• Reverse-thrust assignments.
• Sensitivity and dead zones.

Poor FPS at a Premium Airport

Test:

• Default airport.
• AI traffic off.
• Static aircraft off.
• Airport workers reduced.
• Terrain and Object LOD.
• VRAM usage.

CTD When Loading

Test:

• Default livery.
• Default airport.
• Community Folder reduced.
• Aircraft updated.
• Driver stability.
• Reliability Monitor.

Student Practical Assignment

Install, Configure and Test the PMDG 737

Part 1 – Installation

Record:

Simulator: MSFS 2020 / MSFS 2024

PMDG variant:

Product version:

Operations Center updated: Yes / No

Liveries installed:

Aircraft visible in simulator: Yes / No

Part 2 – Configuration

Record:

Units: KG / LB

Panel state:

SimBrief connected: Yes / No

AIRAC checked: Yes / No

Throttle axes tested: Yes / No

Rudder tested: Yes / No

Tiller tested: Yes / No

Fuel-loading method:

Payload-loading method: