# Wrong WptDescrCode for Arrivial Procedure **URL:** \ **Category:** SID/STAR/APPR\ **Created:** [August 4, 2025, 12:03pm UTC](https://forum.navigraph.com/t/wrong-wptdescrcode-for-arrivial-procedure/20429 "2025-08-04T12:03:51Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![paul891014](https://avatars.discourse-cdn.com/v4/letter/p/59ef9b/32.png) [@paul891014](https://forum.navigraph.com/u/paul891014)\ **Post date:** [August 4, 2025, 12:03pm UTC](https://forum.navigraph.com/t/wrong-wptdescrcode-for-arrivial-procedure/20429/1 "2025-08-04T12:03:51Z")
Hi there, I found that there are some bugs with wrong waypoint\_descr\_code. Here are the codes for FSLabs below: ![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/9/4/94b3aee2d02fabec896e36f1145c552c2ef889b7.png) These data’s SUBS\_CODE = E, and the four characters for these data(A I F C) are only used in APCH (which is SUBS\_CODE = F) according to ARINC424-23. ![ee227f7c-277e-4d37-b763-aad64d881d3e](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/f/5/f58ecd2d9ff10d374169f4f60a516454a96e642a.png) Hope the team would give this issue a look, thanks in advance! ---
**Author:** ![NAVData](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/navdata/32/30549_2.png) [@NAVData](https://forum.navigraph.com/u/NAVData)\ **Post date:** [August 4, 2025, 12:58pm UTC](https://forum.navigraph.com/t/wrong-wptdescrcode-for-arrivial-procedure/20429/2 "2025-08-04T12:58:20Z")
Hi Paul, We use another ARINC424 version, but I haven´t understood the issue. What is the exact problem in the FSLabs? Cheers Richard ---
**Author:** ![paul891014](https://avatars.discourse-cdn.com/v4/letter/p/59ef9b/32.png) [@paul891014](https://forum.navigraph.com/u/paul891014)\ **Post date:** [August 4, 2025, 1:17pm UTC](https://forum.navigraph.com/t/wrong-wptdescrcode-for-arrivial-procedure/20429/3 "2025-08-04T13:17:58Z")
Currently not affect FSLabs I thought, but according to ARINC 424 ver(from 16-23), the wpt\_descr\_code is not align with all the specification as these data I mentioned here. It might affect to another model for reading the data like X-Plane CL650 or something else. Above all I suggest to modify it according to the specification if possible. ---
**Author:** ![NAVData](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/navdata/32/30549_2.png) [@NAVData](https://forum.navigraph.com/u/NAVData)\ **Post date:** [August 4, 2025, 2:13pm UTC](https://forum.navigraph.com/t/wrong-wptdescrcode-for-arrivial-procedure/20429/4 "2025-08-04T14:13:09Z")
Hi again, Does the X-Plane CL650 use the FSLabs database? You wrote “might affect.” Does this now mean you reported an issue or not? The marked line in your initial posting is considered IAF, not FAF. Do you have any evidence that this waypoint EN205 should be coded as FAF instead of IAF? Thank you, Richard ---
**Author:** ![paul891014](https://avatars.discourse-cdn.com/v4/letter/p/59ef9b/32.png) [@paul891014](https://forum.navigraph.com/u/paul891014)\ **Post date:** [August 5, 2025, 12:00pm UTC](https://forum.navigraph.com/t/wrong-wptdescrcode-for-arrivial-procedure/20429/5 "2025-08-05T12:00:18Z")
Sorry if there was any misunderstanding. What I mean is that, as far as I know, all aircraft are using the same source of ARINC 424 data which comes from Jeppesen and Navigraph(T data). This could be reflected in [Wrong procedure data in VHHX - #2 by NAVData](https://forum.navigraph.com/t/wrong-procedure-data-in-vhhx/20006/2) . orry for my earlier mistake on those pages, For example, `E RM` can be recognized under the ARINC 424-23 specification, but not in ARINC 424-18. So, if an aircraft is using navigation data based on ARINC 424-18, this might lead to errors. Sorry for my earlier mistake on that point. In summary, if some data does not comply with the ARINC specification that aircraft used, it might affect other related data as well. That’s why I opened this ticket. Referring to your reply [here](https://forum.navigraph.com/t/wrong-wptdescrcode-for-arrivial-procedure/20429/4), you mentioned that this line is considered as an IAF. However, according to the screenshot of the specification I provided, the last character `A` can only be used in APCH procedures, not in STARs. Please let me know if I have misunderstood anything. I look forward to your clarification. Thanks in advance! ---
**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/1X/4cc83e90d70ab312b1bd2d7527bddad309607265.png) [@system](https://forum.navigraph.com/u/system)\ **Post date:** [August 11, 2025, 12:04pm UTC](https://forum.navigraph.com/t/wrong-wptdescrcode-for-arrivial-procedure/20429/6 "2025-08-11T12:04:51Z")
This topic was automatically closed after 7 days. New replies are no longer allowed.