I encountered an issue while setting up the FMC for an approach into RCKH.
While selecting the LUGIA 2B arrival with the ILS 27 approach, I noticed that the expected transition, which is present in the actual aircraft database, was missing from the simulator’s navigation data.
The ILS 27 procedure at RCKH begins with a DME arc from the IAF. However, due to the absence of the appropriate transition in the database, a route discontinuity occurs, and the arc segment cannot be properly loaded.
Could you please confirm whether this issue is known, and if a correction could be included in a future AIRAC cycle update?
This issue is more likely a coding limitation.
Both fixes FORKY and SK10 on chart are defined by NDB SK, but the arc is defined by IKAS.
Since they are not on the same reference navaid, this arc cannot be coded.
Hi,
This transition can’t be coded due to the DMEARC. A few mandatory parameters must be set to code a DMEARC.
One of them is that the ARC must reference a VOR/VORDME or a TACAN VOR. You can’t code it in the data when this is not the case (as here with the FORKY transition).
You see the reference navaid is the IKAS ILSDME; therefore, it is not codable.
So, it is not missing or wrong; it is simply not codable according to the standard ARINC424 rules.