S1/S18 Incorrect routing

Athos

Hi,
I recently played on S1 and S18 and noted that the LFPO group arrival are routed via XAMAB instead of SITET, and this is quite game changing on S1 and S18.

Also, S1 is aware of the points throug Brest M and S sector axis XAMAB-RESMI then either DISAK/KETEX/OGULO/PEKIM/TEPRI. With that, IRL S1 can send traffic on parrallel HDG and position them depending on the WPT after RESMI
![](https://)

Dave

Hi Athos,
Thanks for the report.
I only found 1 LFPO arrival via XAMAB...however I'm working now with the 2509 update files which will be different to yours currently. Anyway that was corrected. Whist doing so I did find the LFPO ARRs from the NAT region were filed as PG arrivals (i.e. via XIDIL)...so they were amended too.

The onward routings through adjacent FIRs is still WIP.

Unfortunately, this amendment has missed the forthcoming 2509 update...so will be released with 2513 in Dec.

Athos

Looking at an history of flight plan to LFPO and using Eurocontrol route catalog.
LFPO arrival via London are using the segment GWC N859 SITET A34 BOBSA. The route varies before GWC depending on the chosen routing: below some routing example extracted from IRL FPL

DOGAL DCT BEXET DCT OSGAR DCT GTG DCT MORAG DCT NUCHU L18 VAPID UN859 GWC N859 SITET A34 BOBSA
DOGAL DCT BEXET DCT KURUM DCT NORLA DCT PEWBI DCT OXLOW M140 SAM Y8 GWC N859 SITET A34 BOBSA
DOGAL DCT BEXET DCT MORAG DCT NUCHU L18 VAPID UN859 GWC N859 SITET A34 LGL H20 BOBSA
RESNO DCT NETKI DCT CON DCT RINUS DCT MORAG DCT NUCHU L18 VAPID UN859 SITET A34 BOBSA