# Navigation data issues on MSFS2024 - G1000

**URL:** <https://forum.navigraph.com/t/navigation-data-issues-on-msfs2024-g1000/22046>\
**Category:** General MSFS Data\
**Created:** [December 27, 2025, 6:45pm UTC](https://forum.navigraph.com/t/navigation-data-issues-on-msfs2024-g1000/22046 "2025-12-27T18:45:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![snipeg](https://avatars.discourse-cdn.com/v4/letter/s/13edae/32.png) [@snipeg](https://forum.navigraph.com/u/snipeg)\
**Post date:** [December 27, 2025, 6:45pm UTC](https://forum.navigraph.com/t/navigation-data-issues-on-msfs2024-g1000/22046/1 "2025-12-27T18:45:58Z")

</div>

Today I reported an issue in the MSFS forums related to the G1000 not working as expected in MSFS2024 when loading an approach into EHGG, while it works perfectly well on MSFS2020

You can read it here:

> **[G1000. The system works incorrectly. It doesn't load altitudes nor distances...](https://forums.flightsimulator.com/t/g1000-the-system-works-incorrectly-it-doesnt-load-altitudes-nor-distances-when-selecting-a-procedure/752212)**
>
> Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub. 3 tags are required...

However, after some debugging I uninstalled the navigraph data completely and all of a sudden it started working almost as expected. See below.

### _MSFS2024 stock airac data_

 ![Screenshot 2025-12-27 193943](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/0/b/0bd138e7b63ad03605cd568f5ed45e3d5d8a1572.jpeg)

 ![Screenshot 2025-12-27 193927](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/d/5/d574a5a7de5219ccaff441d8e3c4449165920610.jpeg)

As you can see here, the issue looks much better when stock airac data is used.

Is there an active issue?

---

<div class="post-metadata">

**Author:** ![NAVData](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/navdata/32/30549_2.png) [@NAVData](https://forum.navigraph.com/u/NAVData)\
**Post date:** [December 27, 2025, 7:05pm UTC](https://forum.navigraph.com/t/navigation-data-issues-on-msfs2024-g1000/22046/2 "2025-12-27T19:05:11Z")

</div>

Hi,  
I´m pretty sure that this is not a data issue - it´s more of an issue somewhere on your system. In nearly all cases, with third-party sceneries and/or the `content.xml` file. Do you use any 3rd party scenery for this airport?

Please try the following steps and report the results back.  
[https://forum.navigraph.com/t/faq-msfs2024-su3-and-above-airport-procedure-waypoint-3rd-party-flightplan-import-issues/20653?u=navdata](https://forum.navigraph.com/t/faq-msfs2024-su3-and-above-airport-procedure-waypoint-3rd-party-flightplan-import-issues/20653)

I can´t reproduce your report:

MSFS2024 1.6.34.0 with stock EHGG - AIRAC 2513:

EFB:

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/f/c/fc5dbf09151b872b7513285ec87e3d6d2b34573f.jpeg)

… and here from the stock 172 with the G1000:

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/c/7/c7f565fcce4c1a968926ba48c75fa9b6f13167a3.jpeg)

You see the distances and the altitude constraints - it´s the same as in the EFB.

Cheers,  
Richard

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/1X/4cc83e90d70ab312b1bd2d7527bddad309607265.png) [@system](https://forum.navigraph.com/u/system)\
**Post date:** [December 30, 2025, 5:18pm UTC](https://forum.navigraph.com/t/navigation-data-issues-on-msfs2024-g1000/22046/3 "2025-12-30T17:18:29Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.