Flight plan/waypoint distance shortening bug. Route SABE-SAZM

Support
1

Hi guys, hope you’re doing well.

I just finished doing a flight between SABE and SAZM on the E190. I had my VNAV configured for descent from 30000ft into waypoint AKRO at 3000ft, with a distance to that waypoint of 144nm. All of a sudden, the distance shortened to 55nm, and the aircraft did a dive in order to reach 3000ft. Needless to say, I went above 250kts at 10000ft, and had to make a 360° turn in order to level off and slow down for landing. It’s the first time I encounter this bug. Hope it isn’t a widespread issue on the fleet and is just locked to the Ejets.

I’m attaching a 1:45 video showing the bug, which I think will be more helpful than a bunch of screenshots, which I’ll upload anyways.

I have the latest version of IF and I’m using a Samsung Galaxy S21 with Android 14.

Screenshot_20241207_003420_Gallery
Screenshot_20241207_003420_Gallery1920×864 127 KB

Screenshot_20241207_003434_Gallery
Screenshot_20241207_003434_Gallery1920×864 141 KB

Screenshot_20241207_003506_Gallery
Screenshot_20241207_003506_Gallery1920×864 130 KB

Screenshot_20241207_003517_Gallery
Screenshot_20241207_003517_Gallery1920×864 134 KB

Screenshot_20241207_003531_Gallery
Screenshot_20241207_003531_Gallery1920×864 145 KB

1 Like
2

Anyone that can chime in? I wouldn’t like my next flight to end like this one.

@schyllberg can you help me?

3

There is an issue with your flight plan:

image
image1096×915 57.1 KB

The plane thought you were going back and forth between VOTRA and AKROG. This repeated segment is causing the total length of FPL to be incorrectly extended.

ae5d77e23805fefd356fb534676a5ec
ae5d77e23805fefd356fb534676a5ec1030×1031 77.1 KB

1 Like
4

So that was the issue, glad to know it was on me. I got curious and made the fpl again, and it had a big distance difference. I’ll redo the flight later today and see if I have this issue again.

Thanks!

1 Like