Creating a waypoint with an altitude constraint at ground level results in a mess of other constraints

[Likeusb]

Flying into UKCC and as it's not an actually present airport with active navdata, I have to manually program the STAR. Just for convenience, I decided to create a custom waypoint on the touchdown zone with the constraint of the airport elevation, partly to allow a theoretical RNP approach, and partly to act as an estimate for what time I land

However, it seems that the aircraft handled that in a really odd way.

In the autosave you can see the result, it decided to ignore other constraints and put the VNAV path in outer space

Dunno what exactly caused it but it's quite an odd issue to say the least

And to add extra details:

Navigraph navdata, MSFS 2024 A350-900 on v1.1.4, latest AIRAC

BUGGED.bin

Edited August 24 by Likeusb