ATR 72: Waypoints set to zero with Simbrief / EFB

ATR FOR MSFS2024

Flightplan with wrong waypoints

I have a small but annoying problem with the ATR72-600 for MSFS2024: I create the flight plan with Simbrief and load it from the ATR EFB, then add the takeoff and landing runways, SIDs, STARs, and the planned RNAV or ILS approaches, eliminating any discontinuities.

If I scroll through the plan, some waypoints have latitude and longitude values ​​set to zero, completely altering the route, creating legs of over 1,000 miles.

I checked the Simbrief file generated in the ATR folder, and it contains the exact coordinates for the offending points.

These zero values ​​persist even if I add the same waypoints manually, as if the ATR NAVDATA had incorrect information.

This doesn’t happen with other aircraft.

I have a regular Navigraph subscription, and the Airacs are up to date.

Sorry for the length, but I was wondering if you’ve checked this as well. I’d appreciate it if you could confirm how to update the ATR navdata, even though it looks like it’s from MSFS2024.

The ATR CDU reports MSFSNAVDB CURRENT.

Thanks

I have the exact same annoying problem. This problem also has the A330 in MSFS 2024 from inibuild. Can this be fixed otherwise the plane is not useable for me

Bug has been logged here and the developer has already fixed internally, just waiting for it to release. Referenced in this thread is the same report for the iniBuilds issues which might be the exact same error, but up to Microsoft to have it fixed there specifically.

I don’t use MSFS2024’s native EFB to create and import flight plans.

In particular, if I set a route in the CDU with arrival at LIPB runway 01 using the RNAV and Star VIC1X procedure, the Star waypoints display coordinates of 0 (zero), rendering the procedure unusable.

It seems the sim doesn’t know those waypoints.

If I arrive at LIPB by manually creating the final leg with waypoints from the Navigraph charts, they have the correct coordinates.

Can this issue be replicated in other aircraft that use default navdata?

If I’m understanding your issue correctly, I am unable to replicate it:

Do you have custom scenery for LIPB? That can overwrite/conflict with default navdata causing issues like this.