AIRAC 2606 rev 3
The URGA1D arrival to VTSP was flown incorrectly by the aircraft, requiring manual intervention:
When pointed out to the aircraft developers, they indicated that the aircraft behaved per design, and the Nav Data was incorrect. Attempting to insert Direct-Tos to subsequent waypoints in the arrival still drew a path ‘infinitely to the west’ and never connected to the airport.
Hi…,
So we can assist, please provide the info at Information requested when posting an issue.
Also, please include the developers’ advice on how the “Nav Data was incorrect”.
Cheers
Ian
The developer’s rationale was that the ETA spikes significantly from the last normal waypoint to the next, indicating that the FMS finds the distance to next waypoint to be incredibly high
The missing info is as follows:
EDIT: Actually, sceneries used are as follows:
Plus
Thanks, greetings to this dev, it is a scenery issue:
Here is the first page of the arrival of URGA1D into VTSP, with the 3rd-party scenery installed. URGAD is nearly 6000nm away:
Here is the same first page of the arrival URGA1D into VTSP, but using the stock scenery. Here, the legs are correct - URGAD is approx. 10nm away:
So, this is not navdata related, and the major reason is that the base scenery (which was designed for 2020) is not fully MSFS2024 SU3+ compatible, even when you install another package, and when the 3rd party dev means it is compatible. It is not as you see.
By the way, you can make this test on your own. Uninstall/remove both packages from your community folder, then check the MCDU leg page in your Inibuild A300.
Cheers,
Richard
That settles that, thanks Richard!
