Weird VNAV / Route calculations into EVRA (Riga) airport

[SAS443]

Hello

I believe the VNAV calculations seem to have some flaws.
And I think we have a bug with (INTC) waypoints that is causing the issue described below.
This is the LAPSA 6A / GUDIN transition into ILS 18 at Riga Intl.

Consider the first screenshot and the VNAV distance to GUDIN (3630NM!)

b350appr.jpg (136.56 KiB) Viewed 1199 times

Now moments later, the route looks like this, again with a totally different VNAV distance (but equally erroneous, 16358NM)

b350appr2.jpg (141.05 KiB) Viewed 1199 times

The aircraft managed to get down to platform altitude (2500') but then I ran into another issue. The AP did not want to follow the FD steering commands all of a sudden. I ended up disconnecting the AP and flew the approach manually instead.

b350appr3.jpg (183.67 KiB) Viewed 1199 times

Could you try this yourselves?

ATS route was
ESGG LUKA3J LUKAX DCT DEREX DCT LAPSA LAPS6A EVRA

[jarek]

Hmm, this is what I see. I can see few other issues here, but not the one you are describing. Could you please verify your routing or could you provide detailed steps how you got these unexpected waypoints on the map? Is this default nav database?

[SAS443]

hello

I can confirm that your image is exactly what was displayed for me when I reviewed the arrival before ToD. But as I was approaching the (INTC)-leg before GUDIN (which calls to intercept R-051 from TUK VOR and steer towards GUDIN), things got out of hand when flying under VNAV guidance.

1913 Navigraph DB.

[jarek]

Good (even if it's bad). This helps anyway.

[Taguilo]

Hi,

I tried your route.
First, there is an error in Navigraph database that is including two waypoints with the same name - GUDIN - in the STAR. The second one is ~2000 nmiles away. You can remove it and leave the first GUDIN - distances normalize.

Second, and this is another Navdata issue: ILS freq for RWY 18 is 111.10, but P3D scenery ILS freq is 110.30. Consequence = NAV to NAV or any ILS approach mode won't work at all, as nav radio is set with Navdata freq info.

Because of all sim scenery compatibility, we must use sim loc frequencies for ILS approaches, therefore this kind of problems may appear in another cases.

Tomas

[SAS443]

Hi,

I tried your route.
First, there is an error in Navigraph database that is including two waypoints with the same name - GUDIN - in the STAR. The second one is ~2000 nmiles away. You can remove it and leave the first GUDIN - distances normalize.

Second, and this is another Navdata issue: ILS freq for RWY 18 is 111.10, but P3D scenery ILS freq is 110.30. Consequence = NAV to NAV or any ILS approach mode won't work at all, as nav radio is set with Navdata freq info.

Because of all sim scenery compatibility, we must use sim loc frequencies for ILS approaches, therefore this kind of problems may appear in another cases.

Tomas

Thanks for swift reply

regarding the second paragraph dealing with Navdata and Sim scenery ILS frequencies, I do not use default EVRA (but a scenery from Justsim) and I have also updated all "default" database with FS Aerodata. Should I still see the issue with nav-to-nav capture?

[Taguilo]

Thanks for swift reply

regarding the second paragraph dealing with Navdata and Sim scenery ILS frequencies, I do not use default EVRA (but a scenery from Justsim) and I have also updated all "default" database with FS Aerodata. Should I still see the issue with nav-to-nav capture?

I see in your pictures ILS freq is the same as I have: 111.10
But checking in MAP... display on P3D it shows 110.30 so I assume we had the same problem.

Tomas

[c.jurek]

Hello,

To update "stock" navaids and ILS to the latest cuurent AIRAC I would suggest this excellent site

https://www.aero.sors.fr

It's donationware

Regards
Georges