SCIP ILSZ10 coding error

Navigation Data SID/STAR/APPR
1

The ILS Z 10 approach via IPA VOR has multiple coding errors.
The waypoint after IPA/10 should not be OGTEG but a Course to Intercept (CI) 193 instead of a Heading to intercept 133. OGTEG is not part of this approach via IPA.

OGTEG is part of another approach, via OGTEG or flying the 11DME ARC IPA.

The way this is coded in 2608 (maybe earlier versions as well) is resulting in the FMS going bezirk and the aircraft steering away from the ILS LOC intercept course.

2

Hi,
Thank you for your report. I have checked this approach, and it seems more of an add-on issue than a coding issue on our side. Not sure what aircraft you mentioned here, but anyway, what we have in our database and what we offer:

There are two transition approaches available: IPA and OGTEG. The final approach starts at OGTEG. The basics.

PIA transition:
The end leg is a VI (so a heading to Intercept) 133° (intercept approx. final approach course 103° + 30°) and has no OGTEG as a waypoint.

OGTEG transition:
The end leg is a HF (holding) and ends at OGTEG.

Final approach:
The leg starts with the IF (Initial Fix) OGTEG down on heading 103° to ILS runway 10.

That is, what we have in our database, and this is correct so far. I assume your aircraft does not correctly “merge” the transition into the final approach, resulting in such a strange flight path. It seems this aircraft also uses the IF OGTEG for the final approach sequence, which is not correct according to the ARINC424 rules in this case.

Here, the exact coding from our source:

SCIP;I10-Z;IPA;IF;IPA;
SCIP;I10-Z;IPA;FD;IPA;3000
SCIP;I10-Z;IPA;VI;;1330
SCIP;I10-Z;OGTEG;HF;OGTEG;1030
SCIP;I10-Z;;IF;OGTEG;
SCIP;I10-Z;;CF;FF10;1030
SCIP;I10-Z;;CF;RW10;1030
SCIP;I10-Z;;VA;;1020
SCIP;I10-Z;;DF;IPA;

You see the correct sequence, so I guess it is limitation of your aircraft what you are using.

Hope that helps,
Richard

3

That is exactly what is wrong. It should be:
SCIP;I10-Z;IPA;FD;IPA;3000
SCIP;I10-Z;IPA;CI;;1930
SCIP;I10-Z;;CF;FF10;1030
SCIP;I10-Z;;CF;RW10;1030
SCIP;I10-Z;;VA;;1020
SCIP;I10-Z;;DF;IPA;

OGTEG shouldn’t be in this approach and it’s not a Heading to Fix (VI). It’s not a big deal, I fixed it manually in the database. I grabbed an older database and there it was correctly coded. It’s not that I fly this Airport daily :smiley: but I thought I report it anyways.

Doesn’t really matter what sim, appearantly they all have the same bug.

4

aaah I see! To both the transitions are coded in 1 ILS. Ok back to the drawing table…

5

Yes, Jeppesen does not duplicate code any sequence - so you have two transitions + one final approach. The point here is the first leg of the final approach, which is the “merging” waypoint, and this waypoint must be skipped when you use a transition, but this is a part of the flight management computer and not a data issue.

Cheers,
Richard

6

It is in the Aerowinx PSX database btw, so maybe the conversion fails at that point. Anyway, I patched it myself, it’s not that a big deal. Thanks for taking your time to answer so extensively!

7

Hi,
Yep, could be. In most such cases, it is a logical issue in the data conversion or directly in the FMC. I would ask Hardy from Aerowinx. I guess he can analyze it much better in the PSX.

Sorry and thanks for your kind words :wink:
Cheers,
Richard

8

What looks pretty obvious, seems quite strange: I checked multiple MSFS aircraft and all display a different ILSZ10. In PSX changed VI to CI and that seemed to be the solution, OGTET got removed and the ILS is displayed correctly.

Interesting to see al the major addons do this wrong. Special Airport this is :wink:

Edit: Hardy fixed it in PSX!