Connect Navigraph to the FlyByWire A32NX in MSFS: authorise flyPad Charts, install AIRAC navdata, link SimBrief and fix common failures.
To connect Navigraph to the FlyByWire A32NX in Microsoft Flight Simulator, open the flyPad EFB's Navigraph or Charts page and authorise the displayed code in a browser. Install Navigraph navdata through Navigraph Hub for matching AIRAC data. Add your SimBrief Pilot ID separately for flight-plan imports; Simlink is not required.
What does each Navigraph connection control?
The A32NX treats Charts, AIRAC navdata, SimBrief and Simlink as separate services, so connecting one does not connect the others.
| Feature | How it connects | What it provides |
|---|---|---|
| Navigraph Charts | Browser authorisation from the flyPad | Airport, departure, arrival and approach charts inside the EFB |
| AIRAC navdata | Navigraph Hub package for the correct simulator | Updated procedures, waypoints and database cycles for route calculation |
| SimBrief | SimBrief Pilot ID entered in the A32NX | Operational flight plan and route import |
| External Charts moving map | Simlink running on the PC | Aircraft position in the separate Navigraph Charts application |
Chart access requires a Navigraph plan that includes Charts. Installing navdata alone does not unlock charts, while authorising the flyPad does not install an AIRAC database.
How do I connect Navigraph Charts to the flyPad?
You connect the flyPad by authorising its one-time device code through your Navigraph account.
- Confirm that you loaded the FlyByWire aircraft. The aircraft selector should identify the FlyByWire A32NX, not the default Airbus A320neo. If it is not installed correctly, follow our A32NX installation and Community folder walkthrough before continuing.
- Install the matching navdata package. Close Microsoft Flight Simulator, open Navigraph Hub and install navdata for the simulator installation used by the A32NX. Our complete Navigraph setup for MSFS 2020 covers Hub, package locations and Simlink. For a supported MSFS 2024 installation, use the MSFS 2024-specific Navigraph connection steps instead.
- Start the simulator and power the aircraft. Open the flyPad EFB and select the page labelled Navigraph, Charts or Navigation. The exact label can differ between A32NX branches.
- Authorise the device code. Scan the displayed QR code or enter its address in a browser, sign in to Navigraph and approve the one-time code. You can use a browser on the simulator PC, a phone or another device.
- Check the connection. Search for an airport and open a chart. For navdata, compare the AIRAC cycle shown on the MCDU database or status page with the cycle installed by Navigraph Hub.
- Configure SimBrief separately if required. In the flyPad's third-party or account settings, enter the requested SimBrief Pilot ID, normally the numeric ID associated with the account. Chart authorisation does not automatically populate this field.
This installation workflow is intended for PC. Console editions do not permit manual installation of the FlyByWire Community package or Navigraph Hub packages in the same way.
Do I need Simlink for the A32NX?
Simlink is not required for charts displayed natively inside the A32NX flyPad.
The aircraft supplies its own position to the EFB integration. Simlink is needed when you want the aircraft symbol to move in the separate Navigraph Charts application on another screen or device. Reinstalling Simlink will therefore not usually fix an empty flyPad Charts page.
Why is Navigraph not working in the A32NX?
Most A32NX connection failures come from loading the wrong aircraft, mixing simulator installations or confusing Charts authorisation with SimBrief and navdata setup.
- No Navigraph or Charts page: verify that you loaded the FlyByWire A32NX rather than the stock A320neo, then update the aircraft through its installer. Stable and development branches can expose changed EFB layouts.
- The code is accepted but charts remain unavailable: confirm that the signed-in account has chart access. Sign out within the flyPad, restart the aircraft and authorise a fresh code if the saved token is stale.
- The MCDU shows an old AIRAC: close the simulator fully, check that Navigraph Hub installed its package against the correct MSFS installation and remove any duplicate, manually installed navdata package. Navdata is loaded during simulator start-up.
- SimBrief import says the user cannot be found: use the SimBrief Pilot ID requested by the EFB rather than a display name or email address. Then regenerate the operational flight plan and try the import again.
- The imported route contains missing procedures or discontinuities: compare the AIRAC cycle used to generate the SimBrief plan with the cycle installed through Hub. Different cycles can rename, add or remove procedures and waypoints.
- No aircraft symbol appears on a chart: enable the aircraft or moving-map overlay if the EFB offers that control and check that the selected chart supports georeferencing. If the problem occurs in the separate Charts application rather than the flyPad, confirm that Simlink is running.
Must I reconnect Navigraph after every A32NX update?
You normally do not need to reconnect Navigraph after every aircraft update because the flyPad stores its authorisation locally.
A major EFB change, cleared local data or a switch between A32NX branches can require a new device code. AIRAC updates remain separate: install each desired database cycle through Navigraph Hub, close Microsoft Flight Simulator before changing it, and restart the simulator afterwards.