When planning a flight in the A320Neo (flybywire mod), I encountered an issue.
So I have selected LFMT as departure, SID MEN6N and LFPO as destination, STAR MOU9W, Appr ILS RWY 24 (MOLBA).
In Navigraph, everything is ok and waypoint are the following (from STAR, SID is ok)
MOU AVLON OKRIX EBOMA MOLBA (and then appr) MLN PO610 CI24 FI24
There are some constraints (OKRIX max FL180, EBOMA max FL120, MOLBA exact FL100 and then CI24 at 3000ft)
But when entering the data in the FMS of A320Neo, there is a new waypoint (USR) between PO610 and CI24 which is about 12nm from CI12 and has the alt contraints of MOLBA (10000ft)…
Going down from 10000ft to 3000ft in 12 miles is… quite hard…
I don’t know where the USR waypoint come from (GPS from MSFS which adds it or navigraph ??)
Also, in the A320Neo, one of the waypoint (EBOMA if I remember), have an alt constraint of 0… shouldn’t it keep the last known constraint ?
Speed constraints are also not respected (MOLBA don’t have speed constraint on the chart, so for the A320Neo, instead of keeping the last known constraint, go back to full speed…)
I’m far from an expert so I may be doing things wrong.
The speed can easily handled by going to selected speed mode and setting it to whatever you need but the alt constraint on USR waypoint is a killer for me.