TFDi MD-11 navdata issue at EFHK

[joon44]

The departures at EFHK 22R are wrong. They are defind as RWY TRACK until 2.5 DME HEL VOR. Runway track is 217.

The navdata however refers to course 217 from the VOR itself.

{“ID”:10449,“TerminalID”:1905,“Type”:“5”,“Transition”:“ALL”,“TrackCode”:“CD”,“WptID”:null,“WptLat”:null,“WptLon”:null,“TurnDir”:“”,“NavID”:576,“NavLat”:60.33781667,“NavLon”:24.95373056,“NavBear”:null,“NavDist”:null,“Course”:217,“Distance”:2.5,“Alt”:“00680A”,“Vnav”:null,“CenterID”:null,“CenterLat”:null,“CenterLon”:null,“IsFlyOver”:0,“SpeedLimit”:null,“IsFAF”:0,“IsMAP”:0}

This leads to the first waypoint being left of the runway and the plane commanding a left turn when airborne.

Anything to fix this?

[NAVData]

Hi,
Sorry for the delay in getting this answer, but we (nearly the whole team) are currently at the FSExpo.

If it is okay, I will check this later and get back to you with any updates. I hope that is ok for you. Let me know when it’s urgent, please.

Thanks and greetings from Providence
Richard

[jpschuchna]

The coding itself is correct. It looks more like an implementation issue on TFDI side.
The reference of the recommended navaid HEL is only used to generate the WPT based on the distance and it should use the track based on the current aircraft position.

It looks like CD-Legs are Interpreted the same way as FD-Legs.

For comparison the same leg on the PMDG 737 where it looks much better.
Magvar is not an issue here despite the real RWY heading in the sim based on Magdec.bgl is 218 vs. 217.

If aircraft developers would make use of ARINC 424 Procedure Design Magvar (PMDV) records and Navigraph would include them in their database, then those issues could be solved as well as the aircraft would then be completely independent from the Magdec.bgl in regards to the path terminator leg construction. The compass would however then still display the readings based on Magdec.bgl but the construction of the leg would be correct as the tracks and the magvar would always match to each other.