Dissapearing Waypoints/legs in final stages of long-haul flights

Bug Reports ATC, Traffic & NAVAIDs
, ,
1

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

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons?

No

Brief description of the issue:

The final legs of flightplans dissapear causing the aircraft to fly in a circle.

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

Detailed steps to reproduce the issue encountered:

PC specs and/or peripheral set up if relevant:

Build Version # when you first started experiencing this issue:

Current build: 9991003 but first noticed it has been happening on previous versions since summer 2022.

:loudspeaker: 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:

On two different flights today this has happened. Firstly, Heathrow to JFK in the Concorde. I downloaded some historically accuraate Concorde flightplans created by another user. Boston ATC gives me my decent callouts. When I’m eventually in New York airspace at about 10,000ft and begin my final sharp turn to the right over the New York/New Jersey bight, the last few remaining legs of the flightplan suddenly dissapeard and the Concorde banks sharply to the left and seems to begin to fly in a circle. The second time this happened, I was in the 78X flying LAX to Heathrow. I was finally in UK airspace over Liverpool but hadn’t yet had my decent callouts. I’d say I had about 20 mins of a 10+ hour flight left when again, the final legs of the flightplan dissapeared and the plane banked heavily to the right and began to fly in a circle. Unlike Concorde, this was a flightplan created entirely within the world map. I first noticed this last year on previous versions. It sadly doesn’t happen all the time and I can’t get it to reproduce consistantly. But twice in one day and on two completely different flights has caused me to log it as a bug here. The only mods I’ve used is currently FSTraffic. Before that FSLTL and before that AIG.

If relevant, provide additional screenshots/video:

2

I have same problem

3

I noticed this too since opting in for the AAU1 beta. In the beta forum (now not available anymore?) this was mentioned also. From what i remember this happens after the enroute part of the FP and forces you to manually active the arrival phase. So once you reach your final waypoint on your enroute FP, manually activating the selected arrival solves this. According to the beta forums, this is expected behavior…

1 Like
4

Interesting as it never used to behave like this. So this is now considered “normal”?

5

I have the same probblem in the stock Airbus.

I set up the flightplan using the world map view including the approach and ils/rnav details. The flightplan is present in the FMS on take off.

Once in the descent stage there is the approach msg from ATC confirming the rwy and at that point the FMS inserts a USER waypoint. This waypoint is not present until the ATC call.

The USER waypoint sends the aircraft on some random path.

Interestingly with flying the stock Citation using the same method of flightplanning there are often discontinuities that show in the FMS around this stage. You can cancel these out very easily and at least they are visable breaks.

1 Like
6

Not had this happen for a while but I’ve learned to match departures and arrivals numbers to the runway numbers on the world map screen. That helps a lot.