Hi,
It´s not double, the STAR has two parts. One main part ends at FOWR, and one transition part starts at FOWR. You see this very well in the leg path type. TF (terminal fix) FLOWR is the end fix for the STAR, and IF (initial fix) FLOWR is the starting point for the transition.
What issue do you exactly have with these “double” waypoints? I can´t see any issue nor any wrong sequence anywhere.
As you can see here, the add-on in question flew past VANTZ towards FLOWR. I’m just trying to make sure this isn’t a Navdata issue before I go to the add-on developer.
You notice the aircraft hasn’t overflown VANTZ, correct? Based on the ND range, we’re about 5nm from VANTZ. I’m just making sure this is the add-on, not the navdata.
Understood - I don´t see how far you are away from VANTZ; I only see that the active waypoint is FLOWR on the ND and on the FMC, but anyway, no I can´t see any navdata issue here. The sequence is correct, the legs are correct … So please report this to the developer of this aircraft, whatever it is …
