747 progress display (PROG) shows wrong distance to go DTG and fuel remaining for destination airport

[TraveledWave93]

Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you on Xbox, Steam or Microsoft Store version?

store

Are you using Developer Mode or made changes in it?

no

Brief description of the issue:

In the progress display (PROG) the final destination distance-to-go DTG resets at every waypoint and does not show the correct DTG and estimated fuel remaining at the destination.

In the first picture the progress display shows 89 NM to waypoint PPT and 7079 NM to VABB but at this point VABB is only about 850 NM away. The distance to VABB does count down between waypoints but when the progress display resets at each new waypoint, the distance to VABB resets as well to the original distance between departure and destination (in this case a long-haul flight from Honolulu to Mumbai).

In the second picture even though the plane has gone about 89 NM (just passed PPT with X as the next waypoint), the distance to VABB increased by 65 NM (7144 - 7079 = 65).

The third picture shows the LEGS total distance to the destination runway as 7144 NM (Honolulu to Mumbai).

(side note - I created a separate bug report for the ATA and ETAs in the ND and PROG not being in UTC as well as for the POS INIT clock not being in UTC)

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

have a flight plan - does not matter whether the flight plan is created automatically through the world map (free-flight mode) or entered manually in the FMC

PC specs and/or peripheral set up if relevant:

N/A

Build Version # when you first started experiencing this issue:

1.23.12.0 (1st discovered at this version, I had not used PROG before)

---

For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

[MeridianSquid71]

Hmm, do not know if this is applicable. When I created a couple of FP’s. It gave me multiple points using the same waypoint, and I had to selected the correct one mostly the closest one. I have NOT setup and flown BA plane in while in sim, because still trying to learn FMS in C-17 in X-Plane 11.

Excellent video on YouTube from Gripper SIm on the FMS/Flight Plan and Autopilot. I have watched it and it is very good, see if that also helps in this. Know, BA Planes in MSFS are buggy. So it may be showing exactly what is in it’s database for sim.

[Jimfly3408]

I always have the same problem with 747 and Progress page/ distance to go.DTG reduces correctly to start with then when I go back to the PROG page again it has increased!,never noticed this was happening at each waypoint which is interesting,roll on Pmdg 747…

[TraveledWave93]

In this screenshot the PROG correctly shows the leg after next as KSEA at 110 NM with an estimated 1000 lbs of fuel remaining. The final destination should have the same values but shows KSEA at 1154 NM with -27000 lbs fuel remaining.

[Anthem4179]

I’m just now learning airliners and been trying for days to make sense of that number. Relieved to learn it’s not just me.

[Anthem4179]

@Jimfly3408 's post made me look closer at what happens at waypoints, and at each waypoint it resets itself to what my correct DTG was from from my departure airport – the entire flight distance.

Then it begins counting down properly, but as soon as I reach the next waypoint it resets to the entire flight distance from origin again. Rinse and repeat at every wp.

eg. Today’s flight is Vancouver to Martinique (cyvr-tfff) = 3,708NM and at every waypoint the DTG to TFFF jumps back to 3,708.

[ThomasFly17]

I have this same issue, and not just with the 747-8. The problem also occurs with the 787-10, and CS 777-200 (at least in my experience).

[Metafanwlg]

This problem has been known to Asobo for quite a while, I reported it on Zendesk in January 2021 and I’m sure I was not the first. Unfortunately, 15 months later, the bug still lives. I’m still hoping it will be resolved sooner rather than later.

[VivaLaFraggie]

Here too, seeing the same issue.

I’m currently flying from Orlando International (KMCO) to East Midlands (EGNX), I’m about halfway through the flight and I’ve just passed WP 4850N off the coast of Newfoundland. The remaining distance is around 1800NM but the FMC is showing me 3876NM. It resets every time I pass a waypoint.

[MimikriX]

I have a similar issue with the stock A320Neo and I’ll compare the reports in this thread during my next flight to see if it is exactly the same issue or just similar.

[RareBaton559128]

Having the same issue on 747-8. MSFS 1.32.7.0