hello flying on msfs with the a320 Fenix or the 737 PMDG I notice that on the navigraph data there is a failure. Having flown on the real A320 on the LFBO SID FISTO6A there is an INTCPT before TOU which takes a different direction from what exists today in your data. You will find a screen of the present trajectory with the navigraph data and those in reality
Hi,
please can you explain the screenshots what is what? Also, I guess the legs page screenshot is from a real-world a/c … can you do the same from the Fenix and PMDG please that I can compere the wrong direction … Can you confirm, that you´re using the latest AIRAC cycle 2404?
I have tried to reproduce and can´t - here from the Fenix A320 (our AIRAC 2404 rev.1 installed):
… and here from the ND:
When I look on your real-world legs page screenshot the course is wrong with 356° instead of 354° according the AIP France. The course on the Fenix leg page is absolutely correct with 354°.
Sorry, I can´t reproduce it …
Cheers,
Richard
in fact these screenshots come from reality, I attach below screens of the FISTO6A with the missing INTCPT. I use the latest version of Airacs, in fact there is a variation of 2 degrees between the image and the charts due to the age of the image.
You will first find screens on the 737, secondly the a320 fenix and finally on the a32nx where the INTCP exists.
Sorry, I still can´t see an issue … the intercept is there because when the intercept wouldn´t there you wouldn´t see the correct course and on all your screenshots of the leg page (excluding the one of the real-world a/c) you see the correct, corresponding course to TOU VOR.
I don´t understand what you are missing here … the INTC pseudo point on the ND or what? When yes, then please contact the addon devs because we have no influence what will be shown or what not. We “only” offer the data behind …
… and in this case, the data are absolutely correct even, when this pseudo waypoint is not showing on the ND. The courses are all correct and the a/c also fly the procedure correctly.
Sorry, I still can´t see a navdata issue here, what we can fix … for missing information on the ND, please contact the 3rd party devs of the a/c.
Thank you very much,
Richard
I just want the plane to be in LNAV like in the first image which is from reality instead of the second image which is in MSFS
… but you can fly this absolutely correct with LNAV. The path could be differ due the turn rate to intervept the radial to TOU. Depending on aircraft, weight, … but again, the procedure is correct and can’t be flown with LNAV.
When you compare your first screenshot than you will see that the aurcraft reach the turn point far later (possible due the climb rate). Therefore looks the interecpt not so “round” as in the MSFS version. Also possible that this a/c had received a special heading for the intercept and so on, … When you compare the charts with the screenshots you see also the normal curve … Again, the data are correct.
The intercept is made before TOU on the correct course in both screenshots. One earlier, one later …
Hope that helps now.
Cheers
Richard
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
