# ARINC 424.18 erroneous fields - X-Plane NavData **URL:** \ **Category:** General non MSFS data\ **Created:** [September 12, 2022, 9:28am UTC](https://forum.navigraph.com/t/arinc-424-18-erroneous-fields-x-plane-navdata/9191 "2022-09-12T09:28:02Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![RomainRMF](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/romainrmf/32/3256_2.png) [@RomainRMF](https://forum.navigraph.com/u/RomainRMF)\ **Post date:** [September 12, 2022, 9:28am UTC](https://forum.navigraph.com/t/arinc-424-18-erroneous-fields-x-plane-navdata/9191/1 "2022-09-12T09:28:02Z")
Hello Team, In the X-Plane NavData (11 or 12, AIRAC 2209 and previous ones), I have found a list of FIX with curious ARINC 424.18 fields regarding their definition in AIP. My sources to read these fields are : - X-Plane FIX Spec 1200 : [XP-FIX1200-Spec.pdf](https://developer.x-plane.com/wp-content/uploads/2021/09/XP-FIX1200-Spec.pdf) - The ARINC 424.18 field “decoding table” found [here](https://wiki.flightgear.org/User:Www2/XP11_Data_Specification#FIX) - French AIP, cycle 2209 : [AIP France](https://www.sia.aviation-civile.gouv.fr/dvd/eAIP_08_SEP_2022/FRANCE/AIRAC-2022-09-08/html/index-fr-FR.html) – Here is the list of suspicious fixes in my area of interest : - **BADPO** fix, with a Col27 field set to 0x49 - _Unnamed, Charted Intersection_. I would expect it to be 0x43, 0x52 or 0x57. It’s named, and used as an IF in VOR B 22 in LFMN. - **CANSU** fix, with a Col27 field set to 0x55 - ‘U’, not part of the ARINC table available. This fix however is listed in ENR 4.4 in french AIP, so I would expect it to be 0x43, 0x52 or 0x57 as well. - **DAMLO** fix, exact same thing as CANSU above. - **All RNAV fixes of LFBF** have a Col27 set to 0x49 - _Unnamed, Charted Intersection_. However, they are all RNAV Waypoint, defined in the AIP as such. So I would expect a 0x57 instead. (BF110, BF112, BF302, BF304, BF310, IBF11, IBF29, FBF11, FBF29) - **STG48** fix, as well with Col27 0x49 whilst it’s a defined RNAV waypoint, in the AIP, used in the INA RNAV 23 in LFST. All other similar fixes of this procedure are correctly categorized (STB40, STM27, …), but not this one. – It’s obviously not causing an issue in X-Plane as such. I’m locally using this fields outside of X-Plane sim. Question is, if the decoding table is still up-to-date, are you able to confirm that these fixes are not categorized as they should ? If yes, are you able to fix them for further AIRACs or is it down to Jeppesen/ANSPs to correct them ? Thank you ! ---
**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:** [September 12, 2022, 12:29pm UTC](https://forum.navigraph.com/t/arinc-424-18-erroneous-fields-x-plane-navdata/9191/2 "2022-09-12T12:29:30Z")
Hi, our record types are not exclusively only v18 - we use different versions on different record-types - so, we don´t use only 424-18 and the wikipedia link is not 100% complete. Additional to this - the data are coming directly from the specific countries. Jeppesen doesn´t re-code anything - special the coding of the waypoint types (but also other types) follow not always 100% the information in the AIP or better, what you expect it. When something is wrong, it must be fixed by the specific countries, and for that we nor Jeppesen has any influence on this. Sorry. Cheers, Richard ---
**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/1X/4cc83e90d70ab312b1bd2d7527bddad309607265.png) [@system](https://forum.navigraph.com/u/system)\ **Post date:** [September 19, 2022, 12:30pm UTC](https://forum.navigraph.com/t/arinc-424-18-erroneous-fields-x-plane-navdata/9191/3 "2022-09-19T12:30:07Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.