Wrong speed constraints with the TFDi MD-11

Navigation Data SID/STAR/APPR
1

The following SID is missing mandatory speed constraints and in addition there are two non-existent speed constraints added.

EFVA RWY34 GUBTU2B

image
image1247×184 53.3 KB

180 KT at CECFI and 210 KT at WORWE are missing. Also there are, for some reason, 230 KT constraint at NUBRO and 240 KT constraint at GUBTU.

The problem lies in the navdata. The procedure is in the file TermID_2105.json and it has these 230 and 240 constraints in there and missing the 180 and 210 constraints and the plane inserts these correctly according to the navdata. However, I have seen that it works correctly in another plane so I presume the problem is MD11-specific. I’ve seen similar issues before but disregarded them as bugs in the FMS but it seems it all comes down to faulty navdata.

2

Hi,
Thank you very much for the bug report. I can confirm this observation, and I have checked the speed constraints in the source. We do have this information according to the AIP, so it´s a parser issue that will be fixed with the next AIRAC cycle 2506, latest.

Thanks again for the report!

Cheers,
Richard

1 Like
3

Hi again,
I have built an AIRAC 2505 revision 2 for the TFDi MD-11, which fixes this reported issue. It was a bit tricky because it was a generic issue in the TFDi exporter, which has not worked correctly in the past.

Here are the new legs for EFVA / GUBT2B departure with AIRAC 2505 rev. 2:

image
image503×451 65.3 KB

But anyway, it´s fixed now, and revision 2 is online. Please confirm if it´s also fixed for you.
Thanks again for the bug report … enjoy your weekend!

Cheers,
Richard

PS: the FMS Data Manager files for Prepare3D v4,5 and 6 will be updated too as soon as possible

1 Like
4

Hi Richard. Thanks for the quick fix. I confirm it is inserted and shown correctly. I also checked multiple other departures around the globe that have had issues and seems they are all fixed now :+1:

1 Like
5

You’re welcome - thank you very much for your feedback.

It was a general bug in the TFDi MD11 exporter from day one on, but nobody has reported it till now :sweat_smile:

So, I’m happy and thankful that you have identified and reported it! Thank you again—it’s much appreciated.

Have a nice day,
Richard

1 Like
6

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.