Navigraph Masterclass

Lesson Overview

Welcome to Module 8 of the Flight Sim Mastery Academy.

This module focuses on Navigraph, one of the most important navigation tools available for serious flight simulation.

Navigraph provides access to:

  • Current navigation data.
  • Jeppesen airport and procedure charts.
  • En-route maps.
  • Airport diagrams.
  • Moving-map tracking.
  • SimBrief integration.
  • In-simulator charts.
  • Aircraft EFB integrations.
  • Navigation-data updates for supported aircraft and simulators.

Navigraph Hub can update the core navigation data used by both Microsoft Flight Simulator 2020 and Microsoft Flight Simulator 2024. It is also used to install supported avionics plugins and the Charts In-Game Panel.  

This lesson teaches students how to install and configure Navigraph, understand the charts required during a flight, connect it to supported aircraft and test whether the software creates any loading, memory or compatibility problems.


Lesson Objectives

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

Create and configure a Navigraph account.

Understand the role of a Navigraph subscription.

Install and operate Navigraph Hub.

Update MSFS 2020 and MSFS 2024 navigation data.

Install supported aircraft navigation packages.

Install and configure Navigraph Charts.

Import a SimBrief flight plan.

Read airport diagrams.

Understand SID and STAR charts.

Read approach plates.

Use en-route charts and moving maps.

Use the MSFS Charts In-Game Panel.

Connect Navigraph to PMDG, Fenix, iniBuilds and FlyByWire aircraft.

Identify AIRAC mismatches.

Test loading time, RAM use and in-game panel performance.

Diagnose database and Community Folder conflicts.


Understanding the Navigraph Ecosystem

Navigraph is not a single application.

It is a collection of connected services.

Navigraph Charts

Used for:

  • Airport charts.
  • SID and STAR charts.
  • Approach plates.
  • En-route maps.
  • Moving maps.
  • Weather overlays.
  • Flight-plan viewing.
  • SimBrief OFP access.

Navigraph Hub

Used for:

  • MSFS navigation-data installation.
  • Aircraft navigation-data packages.
  • Avionics plugins.
  • Charts In-Game Panel installation.
  • Updating and removing supported packages.

SimBrief

Used for:

  • Operational flight planning.
  • Route generation.
  • Fuel planning.
  • Payload planning.
  • Alternates.
  • Operational Flight Plans.

The Navigraph Charts application can import a SimBrief flight plan and display its route and Operational Flight Plan.  

Simlink

Used to communicate the live aircraft position from the simulator to supported Navigraph applications.

This enables moving-map tracking in applications running outside the simulator.


STEP 1 – INSTALLATION

Installing and Setting Up Navigraph


1. Creating a Navigraph Account

Open the official Navigraph website and create an account.

The same account can be used for:

  • Navigraph Charts.
  • Navigraph Hub.
  • SimBrief.
  • Aircraft chart integrations.
  • In-game panels.
  • Mobile applications.

Record:

Navigraph email:

Navigraph username:

Subscription status:

SimBrief username:

SimBrief Pilot ID:

Use one consistent account across all applications. Using several accounts can result in SimBrief plans, subscriptions and aircraft integrations appearing under different profiles.


2. Understanding the Subscription

Navigraph’s free services and subscription services have different purposes.

SimBrief can be used without a paid subscription, but a current Navigraph subscription provides access to features such as:

  • Current Jeppesen navigation data.
  • Worldwide IFR charts.
  • Charts applications.
  • Current AIRAC data in SimBrief.
  • Supported aircraft and simulator database updates.
  • Extended chart integrations.

AIRAC navigation data changes on a standard 28-day cycle, reflecting updates to airways, waypoints, frequencies, runways and procedures.  

Subscription prices and packages can change, so students should review the current official pricing page rather than relying on a value shown in an older recording.  


3. Downloading Navigraph Hub

Navigraph Hub is the main installation manager for MSFS navigation products.

It supports navigation-data updates for:

  • Microsoft Flight Simulator 2020.
  • Microsoft Flight Simulator 2024.
  • Supported aircraft add-ons.
  • Charts In-Game Panel.
  • Avionics integrations.  

Installation Procedure

  1. Close Microsoft Flight Simulator.
  2. Download Navigraph Hub from the official Navigraph website.
  3. Run the installer.
  4. Sign into the Navigraph account.
  5. Allow Hub to identify installed simulators.
  6. Confirm MSFS 2020 if installed.
  7. Confirm MSFS 2024 if installed.
  8. Check the displayed package paths.
  9. Do not install products until the selected simulator is correct.

Students with both simulators installed must check the simulator selector before every installation.


4. MSFS 2020 Setup

Inside Navigraph Hub:

  1. Select Microsoft Flight Simulator 2020.
  2. Locate the core MSFS navigation-data package.
  3. Select Install.
  4. Wait for installation to finish.
  5. Install the Charts In-Game Panel if required.
  6. Install supported avionics plugins only when needed.
  7. Restart Navigraph Hub.
  8. Launch MSFS 2020.
  9. Load a test aircraft.
  10. Confirm the expected AIRAC cycle.

Navigraph Hub replaces or overrides the default MSFS 2020 navigation data with the current Jeppesen data while the package is installed.  


5. MSFS 2024 Setup

For Microsoft Flight Simulator 2024:

  1. Select MSFS 2024 inside Navigraph Hub.
  2. Install the MSFS 2024 navigation-data package.
  3. Install supported MSFS 2024 chart or avionics packages where required.
  4. Confirm the correct Community Folder.
  5. Launch the simulator.
  6. Test a supported aircraft.
  7. Review the navigation cycle shown in its avionics.

Navigraph states that the default MSFS 2024 data is not permanently deleted when the Navigraph package is installed; it can be restored by removing the Navigraph replacement package.  

Do not manually place the MSFS 2020 package into MSFS 2024.


6. Installing Aircraft Packages

Some aircraft use the simulator’s core navigation database.

Others require a separate aircraft-specific database.

Navigraph Hub may show supported packages for aircraft such as:

  • Fenix.
  • PMDG products.
  • iniBuilds aircraft.
  • Other third-party avionics.

The exact list depends on:

  • Installed products.
  • Simulator version.
  • Current developer support.
  • Aircraft architecture.

Installation Procedure

  1. Close MSFS.
  2. Close any aircraft background applications.
  3. Open Navigraph Hub.
  4. Select the correct simulator.
  5. Locate the installed aircraft package.
  6. Select Install or Update.
  7. Wait for completion.
  8. Launch the aircraft.
  9. Open its IDENT or database page.
  10. Confirm the AIRAC cycle.

Do not assume updating the core simulator database automatically updates every third-party aircraft.


7. Installing Navigraph Charts

Navigraph Charts can normally be used as:

  • A Windows desktop application.
  • A web application.
  • A mobile or tablet application.
  • An in-game panel.
  • An integrated aircraft EFB or tablet.

Desktop Installation

  1. Open the Navigraph downloads page.
  2. Download Navigraph Charts for Windows.
  3. Install the application.
  4. Sign into the Navigraph account.
  5. Allow the app to install Simlink if required.
  6. Start MSFS.
  7. Load into a flight.
  8. Confirm the aircraft position appears on the moving map.

The external desktop application runs separately from the simulator and is often the most performance-efficient way to access charts.


8. Installing Simlink

Simlink transmits the simulator aircraft’s live position to Navigraph.

It can support moving maps on:

  • The desktop app.
  • A browser.
  • A tablet.
  • A mobile device.

Check that:

  • Simlink is running.
  • The correct simulator is detected.
  • The correct Navigraph account is signed in.
  • A flight is loaded.
  • The moving-map icon is enabled.

If the chart opens but the aircraft symbol does not appear, Simlink is one of the first areas to check.


9. Installing the Charts In-Game Panel

The Charts In-Game Panel allows students to access Navigraph without leaving fullscreen or VR.

It is installed through Navigraph Hub.  

Installation Procedure

  1. Close MSFS.
  2. Open Navigraph Hub.
  3. Select the correct simulator.
  4. Locate Navigraph Charts In-Game Panel.
  5. Select Install.
  6. Confirm installation.
  7. Launch MSFS.
  8. Load a flight.
  9. Open the simulator toolbar.
  10. Select the Navigraph icon.
  11. Sign in if requested.
  12. Confirm charts and moving map work.

If the toolbar icon does not appear, check:

  • Correct simulator selected.
  • Correct Community Folder.
  • Package installed only once.
  • Toolbar packages not conflicting.
  • Simulator restarted after installation.

10. SimBrief Integration

Navigraph Charts can import the latest generated SimBrief plan.

Setup

  1. Sign into SimBrief with the same Navigraph account.
  2. Generate a complete flight.
  3. Open Navigraph Charts.
  4. Select the SimBrief import option.
  5. Import the latest plan.
  6. Confirm origin and destination.
  7. Confirm the route.
  8. Open the OFP.
  9. Pin the departure, arrival and approach charts.

A subscription helps keep SimBrief, Navigraph Charts, MSFS and supported aircraft on matching current navigation data.  


STEP 2 – CONFIGURATION AND OPERATION

Using Navigraph Throughout a Flight


11. Understanding Chart Types

Navigraph includes several chart types.

Students must know when each chart is used.

Airport Diagram

Used during:

  • Gate preparation.
  • Pushback.
  • Taxi.
  • Runway crossing.
  • Taxi-in.
  • Parking.

SID Chart

Used during departure.

It describes:

  • Runway connection.
  • Departure routing.
  • Altitude restrictions.
  • Speed restrictions.
  • Navigation requirements.
  • Communication information.

STAR Chart

Used during arrival.

It describes:

  • Entry transitions.
  • Waypoints.
  • Altitude constraints.
  • Speed restrictions.
  • Runway or approach connections.

Approach Plate

Used during the final approach.

It includes:

  • Approach frequency.
  • Final course.
  • Minimum altitudes.
  • Missed-approach procedure.
  • Minimums.
  • Runway information.

En-Route Chart

Used for:

  • Airways.
  • Waypoints.
  • Navaids.
  • Airspace.
  • Route planning.
  • Flight progress.

12. Airport Diagrams

Airport diagrams show the ground layout.

Common information includes:

  • Runways.
  • Taxiways.
  • Stands.
  • Terminals.
  • Holding points.
  • Hotspots.
  • Aprons.
  • Navigation frequencies.
  • Runway dimensions.

How to Use Them

Before pushback:

  1. Locate the parking stand.
  2. Identify the expected runway.
  3. Plan the likely taxi route.
  4. Note runway crossings.
  5. Identify hotspots.
  6. Keep the diagram open during taxi.

Do not wait until the aircraft is moving before trying to understand the airport layout.


13. SID Charts

A Standard Instrument Departure connects the runway environment to the en-route airway structure.

Review:

  • Chart name.
  • Runway applicability.
  • Initial heading or track.
  • Altitude restrictions.
  • Speed restrictions.
  • Required climb gradient.
  • Transition.
  • Navigation requirements.

Example Questions

  • Is there a maximum speed below a waypoint?
  • Is a minimum altitude required before turning?
  • Is there a climb-gradient requirement?
  • Does the SID require RNAV capability?
  • Does the selected transition match the SimBrief route?

The procedure shown in the aircraft must match the chart being briefed.


14. STAR Charts

A Standard Terminal Arrival Route guides the aircraft from the en-route structure towards the destination.

Review:

  • Entry transition.
  • Expected runway.
  • Waypoint sequence.
  • Altitude constraints.
  • Speed constraints.
  • Direction of turns.
  • Approach connection.
  • Communication notes.

A STAR does not necessarily take the aircraft all the way to the runway. ATC may provide vectors or issue a different approach transition.


15. Approach Plates

Approach plates are among the most important charts.

For an ILS approach, identify:

  • ILS frequency.
  • Localiser identifier.
  • Final approach course.
  • Glideslope intercept altitude.
  • Initial approach fix.
  • Decision altitude or decision height.
  • Missed approach.
  • Airport elevation.
  • Runway length.

For an RNAV approach, identify:

  • Required navigation type.
  • Waypoint sequence.
  • Vertical path.
  • Minima type.
  • Missed approach.
  • Any equipment requirements.

Always verify that the approach selected in the FMC or MCDU matches the chart.


16. En-Route Charts

En-route charts show the airway network between airports.

They may display:

  • High-altitude airways.
  • Low-altitude airways.
  • Waypoints.
  • VORs.
  • NDBs.
  • Airspace boundaries.
  • Reporting points.
  • Route restrictions.

Use the chart to understand how the SimBrief route is structured rather than treating the route as a random sequence of letters.


17. Moving Map

The moving map displays the aircraft’s live simulator position.

It can help students:

  • Monitor taxi position.
  • Confirm runway alignment.
  • Track the SID.
  • Monitor route progress.
  • Check arrival positioning.
  • Maintain situational awareness.

The moving map should assist navigation, not replace understanding.

Do not rely on it as the only way to know where the aircraft is.


18. Importing and Organising a Flight

After importing SimBrief:

  1. Confirm departure.
  2. Confirm destination.
  3. Confirm alternate.
  4. Review the en-route path.
  5. Pin the airport diagram.
  6. Pin the SID.
  7. Pin the STAR.
  8. Pin the approach.
  9. Open the OFP.
  10. Save the flight if required.

A professional workflow ensures all required charts are ready before pushback.


19. Weather and Chart Information

Depending on the current application features, Navigraph may display:

  • METAR.
  • TAF.
  • Winds.
  • Radar or weather layers.
  • Runway information.
  • NOTAM-related information.
  • ATIS where supported.

Use weather information to help determine:

  • Departure runway.
  • Arrival runway.
  • Approach type.
  • Crosswind.
  • Visibility.
  • Alternate suitability.

Always compare chart information with current simulated conditions and ATC instructions.


In-Game and EFB Integration

20. Using the In-Game Panel

The in-game panel is useful when:

  • Flying fullscreen.
  • Using one monitor.
  • Flying in VR.
  • Avoiding task switching.
  • Quickly reviewing a chart in the cockpit.

Recommended Workflow

  1. Open the toolbar.
  2. Open Navigraph Charts.
  3. Import or select the flight.
  4. Resize the panel.
  5. Pin the current chart.
  6. Close or minimise it when not needed.

Leaving complex panels open may use more simulator resources than running the desktop application separately.


21. External App vs In-Game Panel

Desktop or Tablet App

Advantages:

  • Runs outside MSFS.
  • Often lower direct impact on simulator frame rendering.
  • Easier to use on a second monitor.
  • Larger viewing area.
  • Can remain visible continuously.

Disadvantages:

  • Requires task switching or another screen.
  • Needs Simlink for moving-map position.

In-Game Panel

Advantages:

  • Available inside MSFS.
  • Convenient for one-monitor users.
  • Useful in VR.
  • No need to leave fullscreen.

Disadvantages:

  • Shares simulator resources.
  • May affect MainThread or frame pacing on some systems.
  • Smaller viewing area.
  • Toolbar conflicts are possible.

Navigraph staff have noted that the in-game panel shares resources with the simulator, meaning panel responsiveness and simulator performance can influence each other.  


Aircraft Integration

22. PMDG Integration

PMDG aircraft may provide Navigraph support through their tablet or Universal Flight Tablet.

Possible features include:

  • SimBrief OFP access.
  • Navigraph chart display.
  • Airport charts.
  • Moving maps.
  • Flight-plan information.

The PMDG 737 tablet supports Navigraph Charts and SimBrief integration.  

Setup

  1. Open the PMDG tablet.
  2. Open account or Navigraph settings.
  3. Begin authentication.
  4. Follow the browser-code process.
  5. Authorise the aircraft.
  6. Import the SimBrief flight.
  7. Open the required charts.
  8. Test responsiveness.

The aircraft FMC navigation data and tablet chart display are related but not the same system.


23. Fenix Integration

Fenix aircraft may use:

  • Navigraph-updated aircraft navigation data.
  • EFB chart integration.
  • SimBrief route import.
  • Moving-map or chart functionality.

Students should separately verify:

  • Fenix AIRAC cycle.
  • SimBrief AIRAC.
  • Navigraph chart cycle.
  • EFB authentication.

A chart opening correctly does not prove that the MCDU database has also been updated.


24. iniBuilds Integration

iniBuilds aircraft such as the A300 and A350 may provide:

  • OIS or EFB charts.
  • SimBrief import.
  • Navigraph authentication.
  • Airport maps.
  • Updated aircraft databases.

After account linking:

  1. Import a flight.
  2. Open charts.
  3. Confirm origin and destination.
  4. Verify the aircraft database cycle.
  5. Test route procedures.
  6. Confirm no waypoint errors occur.

Different iniBuilds aircraft can use different database architectures, so each aircraft should be checked individually.


25. FlyByWire Integration

FlyByWire aircraft can link a Navigraph account through the flyPad.

Possible features include:

  • SimBrief plan retrieval.
  • Navigraph Charts.
  • Airport diagrams.
  • Approach charts.
  • Moving maps.

Linking the account for SimBrief does not necessarily mean every premium chart function is available without an active subscription.

Test the A32NX and A380X separately because their flyPad and flight-management implementations can differ.


AIRAC Cycles

26. What Is an AIRAC Cycle?

AIRAC stands for Aeronautical Information Regulation and Control.

It is the system used to schedule navigation-data updates.

A cycle contains information such as:

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

A new cycle is normally published every 28 days.  


27. Reading an AIRAC Number

An AIRAC cycle uses a four-digit format.


 

Example

2607


 


 

This broadly means:

  • 26 – the year 2026.
  • 07 – the seventh cycle of that year.

Check the current cycle in:

  • Navigraph Hub.
  • SimBrief.
  • Aircraft FMC or MCDU.
  • Navigraph Charts.
  • Simulator avionics.

28. Why Matching Cycles Matter

Suppose SimBrief uses a newer database than the aircraft.

The route may include:

  • A new waypoint.
  • A renamed runway.
  • A changed SID.
  • A new STAR.
  • A modified airway.

The aircraft may then display:

  • NOT IN DATABASE.
  • INVALID ENTRY.
  • AIRWAY NOT FOUND.
  • Missing procedure.
  • Route discontinuity.

The best solution is to align the databases rather than manually replacing every missing point.


29. Charts vs Aircraft Data

Charts and aircraft navigation data are related but different.

Charts

Show the published procedure.

Navigation Database

Allows the aircraft to load and fly the procedure.

A student can have:

  • Current charts.
  • Outdated aircraft data.

This creates a situation where the chart shows a procedure that the FMC cannot select.

Always check both.


STEP 3 – TESTING

Performance, Compatibility and AIRAC Validation


30. Establish a Baseline

Before installing the optional panel and avionics plugins, record:

  • Simulator startup time.
  • Flight loading time.
  • Average FPS.
  • 1% lows.
  • MainThread status.
  • GPU utilisation.
  • RAM usage.
  • VRAM usage.
  • Community Folder package count.

Use the permanent Performance Academy benchmark.


31. AIRAC Mismatch Test

Create a route containing:

  • A SID.
  • Airways.
  • A STAR.
  • An instrument approach.

Record the cycle shown by:

System

AIRAC cycle

SimBrief

Navigraph Charts

Core MSFS data

Aircraft FMC/MCDU

Aircraft EFB


 


 

Then import the route.

Check for:

  • Missing waypoints.
  • Missing airways.
  • Missing SIDs.
  • Missing STARs.
  • Missing approaches.
  • Runway-number differences.
  • Route discontinuities.

Document every mismatch.


32. Loading-Time Impact

Measure:

Before Navigraph Packages

  • Launch to main menu.
  • Main menu to cockpit.

After Core Navdata

  • Launch to main menu.
  • Main menu to cockpit.

With In-Game Panel Installed

  • Launch to main menu.
  • Main menu to cockpit.
  • Time for panel to open.

Small differences may be normal.

Large increases may suggest:

  • Duplicate panel installation.
  • Incorrect package.
  • Community Folder conflict.
  • Network authentication issue.
  • Damaged installation.

33. RAM Usage

Compare RAM usage with:

  1. Navigraph not running.
  2. Desktop Charts open.
  3. In-game panel installed but closed.
  4. In-game panel open.
  5. Several charts open.
  6. Moving map active.

Record:

  • MSFS RAM usage.
  • Navigraph desktop-app RAM.
  • Simlink RAM.
  • Total system RAM.

The external app may use some additional Windows memory while placing less direct load inside the simulator.


34. In-Game Panel Performance

At the benchmark airport:

  1. Record FPS with the panel closed.
  2. Open the panel.
  3. Load the airport chart.
  4. Activate the moving map.
  5. Open an approach plate.
  6. Resize the panel.
  7. Close it.
  8. Record whether performance returns.

Monitor:

  • Average FPS.
  • 1% lows.
  • MainThread.
  • Frame-time spikes.
  • Panel responsiveness.

35. External App vs Toolbar Panel Test

Use identical benchmark conditions.


 

 

Measurement

Desktop Charts

In-Game Panel

Average FPS

1% Low

MainThread status

Total RAM usage

Panel/app response

Moving-map smoothness

Ease of use


 


 

The most visually convenient option is not always the most performance-efficient.


36. Aircraft Database Compatibility

Test each aircraft individually.

PMDG

  • Check FMC AIRAC.
  • Import the route.
  • Check SID and STAR availability.
  • Test tablet charts.

Fenix

  • Check MCDU AIRAC.
  • Test EFB charts.
  • Import SimBrief.
  • Review procedures.

iniBuilds

  • Check database cycle.
  • Test OIS or EFB authentication.
  • Import the route.
  • Review waypoint and procedure availability.

FlyByWire

  • Check MCDU or FMS data.
  • Test flyPad account link.
  • Import SimBrief.
  • Open charts.

Do not assume one successful aircraft proves all databases are correct.


37. Conflict Checks

Possible conflicts include:

  • Old Navigraph packages.
  • Duplicate in-game panels.
  • Manual and Hub-installed copies.
  • Incorrect MSFS 2020 package inside MSFS 2024.
  • Outdated aircraft navigation package.
  • Toolbar panel conflicts.
  • Old avionics plugin.
  • Community Folder priority issues.

Conflict-Test Procedure

  1. Close MSFS.
  2. Open Navigraph Hub.
  3. Remove the suspected package.
  4. Check the Community Folder for leftovers.
  5. Restart the PC.
  6. Reinstall through Hub.
  7. Test a default airport and aircraft.
  8. Add aircraft packages one at a time.
  9. Add other toolbar panels gradually.

38. Missing Procedure Test

If a procedure is missing:

  1. Confirm it exists on the current chart.
  2. Check the chart AIRAC.
  3. Check SimBrief AIRAC.
  4. Check aircraft AIRAC.
  5. Check core simulator AIRAC.
  6. Confirm the airport package is current.
  7. Test default scenery.
  8. Test with Navigraph data removed.
  9. Reinstall the correct aircraft package if necessary.

A missing procedure can result from:

  • Database mismatch.
  • Airport scenery conflict.
  • Incorrect runway naming.
  • Aircraft database issue.
  • Incomplete installation.

39. Moving Map Troubleshooting

If the aircraft symbol is missing:

Check:

  • Simlink is running.
  • The correct account is signed in.
  • MSFS is detected.
  • A flight is loaded.
  • Moving-map tracking is enabled.
  • Firewall or security software is not blocking Simlink.
  • The aircraft position is valid.
  • The desktop app and in-game panel are updated.

40. Common Problems

Hub Does Not Detect the Simulator

Check:

  • The simulator has been launched at least once.
  • Correct Microsoft Store or Steam path.
  • Custom package location.
  • Hub version.
  • User permissions.

Aircraft Still Shows Old AIRAC

Check:

  • Correct aircraft package installed.
  • Aircraft background app was closed during update.
  • Correct simulator selected.
  • No old manual package is taking priority.
  • Aircraft uses its own database rather than core MSFS data.

Charts Work but FMC Procedures Are Missing

The chart service is working, but the aircraft database is not aligned.

Update the aircraft-specific navigation package.

In-Game Panel Is Missing

Check:

  • Panel installed through Hub.
  • Correct Community Folder.
  • Toolbar enabled.
  • No duplicate panel.
  • Simulator restarted.

In-Game Panel Loads Forever

Check:

  • Account authentication.
  • Network connection.
  • Panel update.
  • Duplicate package.
  • Community Folder conflict.
  • Temporary service issue.

Route Differs From SimBrief

Check:

  • AIRAC cycles.
  • Route changed inside Navigraph Charts.
  • Different SID or STAR selected.
  • Aircraft modified the imported plan.
  • World Map changed the route.

Student Practical Assignment

Install, Configure and Validate Navigraph


Part 1 – Account and Installation

Navigraph account created: Yes / No

Subscription active: Yes / No

Navigraph Hub installed: Yes / No

Simulator: MSFS 2020 / MSFS 2024

Core navigation data installed: Yes / No

Charts desktop app installed: Yes / No

Simlink running: Yes / No

In-game panel installed: Yes / No


Part 2 – Flight Preparation

Choose a route with:

  • A SID.
  • An airway section.
  • A STAR.
  • An ILS or RNAV approach.

Record:

Departure:

Destination:

SID:

STAR:

Approach:

SimBrief AIRAC:

Navigraph AIRAC:

Aircraft AIRAC:


Part 3 – Chart Review

Confirm:

☐ Airport diagram opened.

☐ Pushback stand located.

☐ Taxi route reviewed.

☐ SID chart reviewed.

☐ En-route route reviewed.

☐ STAR chart reviewed.

☐ Approach frequency checked.

☐ Final approach course checked.

☐ Minimums identified.

☐ Missed approach reviewed.


Part 4 – Integration Test

Test one or more:

  • PMDG.
  • Fenix.
  • iniBuilds.
  • FlyByWire.

Confirm:

☐ SimBrief plan imported.

☐ Charts opened.

☐ Route matched.

☐ AIRAC matched.

☐ Procedures were available.

☐ Moving map worked.


 


 

Part 5 – Performance Test


 

 

Measurement

Before Navigraph

Desktop app

In-game panel

Startup time

Flight loading time

Average FPS

1% Low

MainThread status

MSFS RAM usage

Total RAM usage


 


 

Student Checklist

Navigraph account configured.

Subscription understood.

Navigraph Hub installed.

Correct simulator selected.

Core navigation data installed.

Aircraft packages reviewed.

Charts application installed.

Simlink tested.

SimBrief imported.

Airport diagram understood.

SID chart understood.

STAR chart understood.

Approach plate reviewed.

En-route chart used.

Moving map tested.

In-game panel tested.

PMDG integration reviewed.

Fenix integration reviewed.

iniBuilds integration reviewed.

FlyByWire integration reviewed.

AIRAC cycles compared.

Loading-time impact measured.

RAM usage measured.

External app and in-game panel compared.

Conflict-testing process understood.


Lesson Summary

You have now installed, configured, used and tested Navigraph with Microsoft Flight Simulator 2020 or Microsoft Flight Simulator 2024.

Remember:

  • Navigraph Hub manages core MSFS navigation data and supported aircraft packages.
  • MSFS 2020 and MSFS 2024 packages must remain separate.
  • Navigraph Charts and SimBrief serve different but connected purposes.
  • Airport diagrams should be prepared before pushback.
  • SID and STAR charts contain important altitude, speed and routing restrictions.
  • Approach plates must be reviewed before the final approach.
  • Simlink enables external moving-map tracking.
  • The in-game panel is convenient but shares simulator resources.
  • Desktop or tablet Charts may produce a lower direct simulator workload.
  • Current charts do not guarantee the aircraft database is current.
  • SimBrief, Charts, MSFS and the aircraft should use matching AIRAC cycles whenever possible.
  • Every supported aircraft database must be tested separately.
  • Hub-managed packages should not be duplicated manually.
  • Missing waypoints and procedures should be investigated as database or scenery issues before rebuilding the whole simulator.

Knowledge Check

  1. What is the purpose of Navigraph Hub?
  2. What is the difference between Navigraph Charts and SimBrief?
  3. What does Simlink do?
  4. Why must MSFS 2020 and MSFS 2024 packages remain separate?
  5. What information does an airport diagram provide?
  6. What is a SID?
  7. What is a STAR?
  8. Which information should be checked on an ILS chart?
  9. What is an AIRAC cycle?
  10. How often is a new AIRAC cycle normally released?
  11. Why might an aircraft reject a waypoint shown in SimBrief?
  12. Why can charts be current while the aircraft database is outdated?
  13. What is the advantage of the desktop Charts application?
  14. What is the advantage of the in-game panel?
  15. Why might the in-game panel affect simulator performance?
  16. How should PMDG, Fenix, iniBuilds and FlyByWire databases be tested?
  17. What can cause a missing SID or STAR?
  18. What should be checked when the moving-map aircraft symbol is missing?
  19. Why should duplicate Hub and manual installations be avoided?
  20. What evidence confirms that Navigraph is fully integrated and ready for use?
1 2 3 4 5 6 7 ADD-ON Masterclass