In AIRAC 2013, the data doesn’t appear to do its thing. On approach, the STAR didn’t have frequency information available for the ILS and I had to input into the aircraft manually but once i did that, it knew where it was, if that makes sense.
In the SIDs, the runways 28L and 28R are unavailable but 28 shows. Because the RW info is incorrect, you cant use a SID for departure as the FMC shows NO SID. In AIRAC 2012, 28L/R were available.
Hi Graeme,
EIDW has only a 10R/28L and 16/34 runways - there is no 28R runway therefore no SID, STAR nor any approaches.
The issue is more in XP11.50 because the runways are incorrect
100 45.00 1 1 0.25 1 2 0 10 53.42242908 -006.29006788 0 0 3 2 1 1 28 53.42025908 -006.25057188 0 0 3 2 1 0
100 61.00 1 0 0.25 0 2 0 16 53.43698649 -006.26197078 0 0 3 1 0 0 34 53.41990249 -006.24958678 0 0 3 6 0 0
You see, XP11.50 offers only 10/28 and 16/34 which is wrong and therefore the FMC can´t assign the runways correctly. Sorry, but thats an XP issue - please report it there.
I can not see how it is Xplanes problem, last airac 28L and 10R was shown with its Sid’s and STARS . It’s since updating to 2013 that it has reverted to 10 and 28 without SID’s and STARS
Hi,
I have posted the XP11.50 issue in their airport-file:
These two lines are in the apt.txt file which will be delivered from XP and not from us. In these two lines, you see the 10/28 and 16/34 runway (both values are bold). When you compare this now to the chart which I have posted, you see, that there is a miss match in the runway-idents because it should be 10R/28L and 16/34 …
Possible, that was due an XP update, I didn´t know, but all I can say is, that the data and XP doesn´t fit and therefore the terminal procedures can´t assigned to a runway because the data uses 10R/28L (according our charts) and XP uses 10/28 which are completely different.
Sorry, please report this to Laminar, we can´t do anything on it - this file (apt.dat) will be provided and maintained by XP.
