# \[FSLabs A321neo / MSFS 2024\] Duplicate STAR waypoints at RJTT with AIRAC 2610 **URL:** \ **Category:** SID/STAR/APPR\ **Created:** [October 13, 2026, 8:45am UTC](https://forum.navigraph.com/t/fslabs-a321neo-msfs-2024-duplicate-star-waypoints-at-rjtt-with-airac-2610/24539 "2026-10-13T08:45:08Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![sansuke1005](https://avatars.discourse-cdn.com/v4/letter/s/97f17d/32.png) [@sansuke1005](https://forum.navigraph.com/u/sansuke1005)\ **Post date:** [October 13, 2026, 8:45am UTC](https://forum.navigraph.com/t/fslabs-a321neo-msfs-2024-duplicate-star-waypoints-at-rjtt-with-airac-2610/24539/1 "2026-10-13T08:45:08Z")
Hi, I’ve noticed an issue with the FSLabs A321neo for MSFS 2024 when using AIRAC 2610. When selecting certain STARs at RJTT (e.g. XAC1K), every waypoint appears twice consecutively in the MCDU flight plan. This does not happen with AIRAC 2609, and the FSLabs version has not changed between the two cycles. I’m using the latest available version of the aircraft. I compared the .rom databases using SQLite and found the following difference in the AIRPORT\_PROCEDURE table: AIRAC 2609: TRANSITION\_IDENT = RW34B (one common transition) AIRAC 2610: TRANSITION\_IDENT = RW34L / RW34R (two separate transitions with identical waypoint sequences) This change affects 20 RJTT STARs, including the AKSE, AROS, GODI, POLI and XAC procedures. As a test, I modified a local copy of the AIRAC 2610 database to restore the previous RW34B structure. This resolved the duplicate waypoint issue with XAC1K. I’ve attached a screenshot showing the duplicated waypoints with the original AIRAC 2610 database. Could you check whether this change was intentional and if it might be causing a compatibility issue with FSLabs? Thanks! ![cdu](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/c/0/c0cc03383c613360cd8551ae360409bb9bc7a631.png) ---
**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:** [October 13, 2026, 8:52am UTC](https://forum.navigraph.com/t/fslabs-a321neo-msfs-2024-duplicate-star-waypoints-at-rjtt-with-airac-2610/24539/2 "2026-10-13T08:52:04Z")
Hi, Thanks for the report - I will check it. I will inform you here when it is fixed and/or when I have an update on this issue. Thanks again for your details and your time, Richard ---
**Author:** ![sansuke1005](https://avatars.discourse-cdn.com/v4/letter/s/97f17d/32.png) [@sansuke1005](https://forum.navigraph.com/u/sansuke1005)\ **Post date:** [October 13, 2026, 9:05am UTC](https://forum.navigraph.com/t/fslabs-a321neo-msfs-2024-duplicate-star-waypoints-at-rjtt-with-airac-2610/24539/3 "2026-10-13T09:05:41Z")
Hi Richard, Thanks for looking into this! Just a quick update: I also tested a STAR at RJBB (Kansai International Airport) and confirmed the same duplicate waypoint issue. I checked the AIRAC 2609 and 2610 databases further and found the same runway transition structure change at several other Japanese airports, including RJAA, RJFF, RJOO, and ROAH. It seems this issue may affect multiple airports, not just RJTT. Thanks again! ---
**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:** [October 13, 2026, 9:21am UTC](https://forum.navigraph.com/t/fslabs-a321neo-msfs-2024-duplicate-star-waypoints-at-rjtt-with-airac-2610/24539/4 "2026-10-13T09:21:13Z")
Thanks again; it seems FSLabs has the same problem with multiple runway segments as PMDG 😉 … because this is new in our source (B-Runways are now split into multiple segments). We have built a fix for this that restores the original state, and we are now using it in FSLabs as well. Here, with revision 2: ![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/3X/a/0/a028ae6b299445d69c57d75c0af502fe6db1ea39.jpeg) I´m currently building the package and will upload it asap. Will inform you here when revision 2 is online, but you can expect it within the next couple of minutes. Cheers, Richard ---
**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:** [October 13, 2026, 9:28am UTC](https://forum.navigraph.com/t/fslabs-a321neo-msfs-2024-duplicate-star-waypoints-at-rjtt-with-airac-2610/24539/5 "2026-10-13T09:28:54Z")
Revision 2 is online … please go to the Hub and update the FSLabs add-on. This should solve this issue (in general), not only for the example RJTT airport. Let me know if I can do more for you & thank you for the report! Cheers, Richard ---
**Author:** ![sansuke1005](https://avatars.discourse-cdn.com/v4/letter/s/97f17d/32.png) [@sansuke1005](https://forum.navigraph.com/u/sansuke1005)\ **Post date:** [October 13, 2026, 9:50am UTC](https://forum.navigraph.com/t/fslabs-a321neo-msfs-2024-duplicate-star-waypoints-at-rjtt-with-airac-2610/24539/6 "2026-10-13T09:50:25Z")
Thanks for the quick fix! I’ve tested revision 2 and can confirm that the duplicate waypoint issue is resolved. Really appreciate your help! ---
**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:** [October 13, 2026, 9:57am UTC](https://forum.navigraph.com/t/fslabs-a321neo-msfs-2024-duplicate-star-waypoints-at-rjtt-with-airac-2610/24539/7 "2026-10-13T09:57:25Z")
No probs - I like such easy fixes 😉 Thanks for your feedback! Enjoy your day … 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:** [October 15, 2026, 9:58am UTC](https://forum.navigraph.com/t/fslabs-a321neo-msfs-2024-duplicate-star-waypoints-at-rjtt-with-airac-2610/24539/8 "2026-10-15T09:58:05Z")
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.