[FIXED v1.3.1] VNAV going nuts after dct skipping whole STAR and its restrictions

[Siwymaligan]

So the situation 1 is as follows: 

I'm flying into EPWA getting DCT to AGAVA and getting cleared for AGAVA5U arrival. Before descend towards FL190 or below at AGAVA I get DCT to ERLEG (chart 2)

At that point VNAV goes nuts- it wants me to start my descend, via 3deg path, at more than 153nm from ERLEG, from FL370. As per my calculations TOD should be at around 110nm. In the screenshot below we can see, that VNAV says, that I'm too high at 153nm from ERLEG (by 3 deg path I'would have to be at FL490 to be at 3deg descend a that distance).

 

I disregarded that, and flew the descend manually, but today almost same thing happened:

I was flying DCT to LOGDA, being cleared for LOGDA5U arrival, again for ILS 33Y. This time I began my descend to reach LOGDA at or below FL190:

After that I received DCT to WA533 (IF for the same appch). Here's what happened:

Path deviation indicator shows, that I'm below descend path, while VNAV calc in FMC says, that I'm already at 3.3deg descend to ERLEG (next point after WA533).

Here is VNAV descend settings page showing, that the descend was programmed as 3deg:

When I've managed to reach nominal descend of 3deg, path deviation indicator shows, that I'm below descend path

 

Best regards,
Adam

Edited January 25, 2022 by Siwymaligan

[Siwymaligan]

Anyone?

[Graeme_77]

Thanks Adam, That does seem wrong. Thanks for the detailed report, and don't feel bad about bumping this thread, sorry I missed it first time.

I'll add this to the list of issues to investigate. 

Edited February 1, 2022 by Graeme_77

[Graeme_77]

Report 2557

Fixed in v1.3.1, February 08, 2022