Airway/waypoint mismatch in AIRAC Cycle 2509.rev1 MSFS 2020 BGL files

[bm9899]

Found some issues with routes in AIRAC Cycle 2509.rev1 MSFS 2020 BGL files

Compared the findings with the NGApp and commented accordingly

Format: Route PrevWyp ThisWyp NextWyp - Comment
Type.Name: PREV.Region(Type).. THIS.Region(Type).. NEXT.Region(Type)

VICTOR.B400: RC.FV(NDB).. VHA.FV(VOR).. VEDET.OY(NAMED) - NEXT is wrong should be KOBOD

BOTH.B400: VHA.FV(VOR).. VEDET.OY(NAMED).. RAPDO.OY(NAMED) - PREV is wrong should be ‘NONE’ (i.e. Start)

VICTOR.G854: (NONE).. FL.FT(VOR).. BOD.DA(VOR) - NEXT is wrong should be SIGAL

VICTOR.G855: FL.FT(VOR).. BOD.DA(VOR).. HOGAR.DA(NAMED) - PREV is wrong should be ‘NONE’ (i.e. Start)

VICTOR.M315: MOGDU.HC(NAMED).. UTINA.HT(NAMED).. IMKAL.FW(NAMED) -PREV is wrong should be ‘NONE’ (i.e. Start)

JET.N304C: MOGDU.HC(NAMED).. MUSAK.CY(NAMED).. TOPPS.K6(NAMED) -PREV is wrong should be ‘NONE’ (i.e. Start)

VICTOR.M313: MAV.HK(VOR).. MOGDU.HC(NAMED).. UTINA.HT(NAMED) -NEXT is wrong should be EGLOM

VICTOR.N304: EGSAP.HC(NAMED).. MOGDU.HC(NAMED).. MUSAK.CY(NAMED) -NEXT is wrong should be AVUSI

In addition the following have neither a PREV or NEXT entry

BOTH.W610: (NONE).. MILOP¬ZG(NAMED).. (NONE)
VICTOR.A405: (NONE).. TEVAS¬FQ(NAMED).. (NONE)
VICTOR.M313: (NONE).. EGLOM¬FS(NAMED).. (NONE)
BOTH.W523: (NONE).. QP¬ZG(NDB).. (NONE)
VICTOR.B400: (NONE).. KOBOD¬FV(NAMED).. (NONE)

I did not check the MSFS2024 content so far

hope it helps…

edited - removed the empty FL entry as it is listed above as wrong

[NAVData]

Hi,
Thanks, but may I ask about your issue with that? The airway implementation in 2020 was buggy, so we had to use a few workarounds.

Therefore, the question:
Please describe the issue you have.

Thank you
Richard

[bm9899]

Having an App that collects such data to visualize route and tracking on a secondary screen, incorrect data makes life for a developper quite hard as there are no rules to apply for patching or correcting such things on the fly.

BTW I checked the streamed 2024 data including NG installed and it contains the exact same problems.

I am aware of the MS data to connect routes that don’t belong together i.e. having incorrect Prev or Next where there should be none (there was a post where you mentioned that)

But there are now some which just connect wrong ones together screwing up valid routes.

I thought it would help to find an underlying issue with MSFS data production…

[NAVData]

Hi,
Thank you. I have added this to our internal task list: analyzing the current situation in both sims to improve the output in the future.

Thank you very much,
Richard

PS: I have changed the title a little bit to avoid confusion …

[bm9899]

I’ve done a quick validation run MSFS2020 BGL collected from NG content only vs. LNM NG database airways (the only NG source I have which I can query easily…)

Tried to find the segments from the Route tripplets in the NG database and complain if not found.

Format is the same as above, a route point is Prev - This - Next and the comment added is the offending segment either the incoming or the outgoing one.

~~~

VALIDATE: no NG segment for Rt:<JET.UL211>: MUNES¬SA(NAMED).. EKBED¬FA(NAMED).. ANTES¬FA(NAMED) PREV->THIS
VALIDATE: no NG segment for Rt:<JET.UL211>: MUNES¬SA(NAMED).. EKBED¬FA(NAMED).. ANTES¬FA(NAMED) THIS->NEXT
VALIDATE: no NG segment for Rt:<JET.UL211>: REKUL¬SA(NAMED).. GUXOR¬SA(NAMED).. ANKOK¬SA(NAMED) PREV->THIS
VALIDATE: no NG segment for Rt:<JET.UL211>: REKUL¬SA(NAMED).. GUXOR¬SA(NAMED).. ANKOK¬SA(NAMED) THIS->NEXT
VALIDATE: no NG segment for Rt:<JET.UL211>: EKBED¬FA(NAMED).. ANTES¬FA(NAMED).. ITLIK¬FA(NAMED) PREV->THIS
VALIDATE: no NG segment for Rt:<JET.UL211>: EKBED¬FA(NAMED).. ANTES¬FA(NAMED).. ITLIK¬FA(NAMED) THIS->NEXT
VALIDATE: no NG segment for Rt:<JET.UL211>: GATOS¬SA(NAMED).. PAGAD¬SA(NAMED).. REKUL¬SA(NAMED) THIS->NEXT
VALIDATE: no NG segment for Rt:<JET.UL211>: KILOS¬SA(NAMED).. KAKIN¬SA(NAMED).. KETIS¬SA(NAMED) PREV->THIS
VALIDATE: no NG segment for Rt:<JET.UL211>: KILOS¬SA(NAMED).. KAKIN¬SA(NAMED).. KETIS¬SA(NAMED) THIS->NEXT
VALIDATE: no NG segment for Rt:<JET.UL211>: KETIS¬SA(NAMED).. MORSI¬SA(NAMED).. MUNES¬SA(NAMED) PREV->THIS
VALIDATE: no NG segment for Rt:<JET.UL211>: KETIS¬SA(NAMED).. MORSI¬SA(NAMED).. MUNES¬SA(NAMED) THIS->NEXT
VALIDATE: no NG segment for Rt:<JET.UL211>: MORSI¬SA(NAMED).. MUNES¬SA(NAMED).. EKBED¬FA(NAMED) PREV->THIS
VALIDATE: no NG segment for Rt:<JET.UL211>: MORSI¬SA(NAMED).. MUNES¬SA(NAMED).. EKBED¬FA(NAMED) THIS->NEXT
VALIDATE: no NG segment for Rt:<JET.UL211>: ITLIK¬FA(NAMED).. APKIN¬FA(NAMED).. (NONE) PREV->THIS
VALIDATE: no NG segment for Rt:<JET.UL211>: ANKOK¬SA(NAMED).. KILOS¬SA(NAMED).. KAKIN¬SA(NAMED) PREV->THIS
VALIDATE: no NG segment for Rt:<JET.UL211>: ANKOK¬SA(NAMED).. KILOS¬SA(NAMED).. KAKIN¬SA(NAMED) THIS->NEXT
VALIDATE: no NG segment for Rt:<JET.UL211>: PAGAD¬SA(NAMED).. REKUL¬SA(NAMED).. GUXOR¬SA(NAMED) PREV->THIS
VALIDATE: no NG segment for Rt:<JET.UL211>: PAGAD¬SA(NAMED).. REKUL¬SA(NAMED).. GUXOR¬SA(NAMED) THIS->NEXT
VALIDATE: no NG segment for Rt:<JET.UL211>: KAKIN¬SA(NAMED).. KETIS¬SA(NAMED).. MORSI¬SA(NAMED) PREV->THIS
VALIDATE: no NG segment for Rt:<JET.UL211>: KAKIN¬SA(NAMED).. KETIS¬SA(NAMED).. MORSI¬SA(NAMED) THIS->NEXT
VALIDATE: no NG segment for Rt:<JET.UL211>: GUXOR¬SA(NAMED).. ANKOK¬SA(NAMED).. KILOS¬SA(NAMED) PREV->THIS
VALIDATE: no NG segment for Rt:<JET.UL211>: GUXOR¬SA(NAMED).. ANKOK¬SA(NAMED).. KILOS¬SA(NAMED) THIS->NEXT
VALIDATE: no NG segment for Rt:<JET.UL211>: ANTES¬FA(NAMED).. ITLIK¬FA(NAMED).. APKIN¬FA(NAMED) PREV->THIS
VALIDATE: no NG segment for Rt:<JET.UL211>: ANTES¬FA(NAMED).. ITLIK¬FA(NAMED).. APKIN¬FA(NAMED) THIS->NEXT

VALIDATE: no NG segment for Rt:<VICTOR.R775>: MOGDU¬HC(NAMED).. APMIR¬HC(NAMED).. DANAK¬OE(NAMED) THIS->NEXT
VALIDATE: no NG segment for Rt:<VICTOR.R775>: GABDA¬HA(NAMED).. UNPAR¬FS(NAMED).. (NONE) PREV->THIS
VALIDATE: no NG segment for Rt:<VICTOR.R775>: HARGA¬HC(NAMED).. SOLUL¬HA(NAMED).. MOGDU¬HC(NAMED) PREV->THIS
VALIDATE: no NG segment for Rt:<VICTOR.R775>: LUBAR¬HC(NAMED).. HARGA¬HC(NAMED).. SOLUL¬HA(NAMED) THIS->NEXT
VALIDATE: no NG segment for Rt:<BOTH.R775>: ALNAB¬HA(NAMED).. GABDA¬HA(NAMED).. UNPAR¬FS(NAMED) THIS->NEXT

VALIDATE: no NG segment for Rt:<VICTOR.A405>: ADMIS¬FL(NAMED).. UDPIX¬FL(NAMED).. MAKIR¬FQ(NAMED) THIS->NEXT
VALIDATE: no NG segment for Rt:<VICTOR.A405>: UDPIX¬FL(NAMED).. MAKIR¬FQ(NAMED).. VHA¬FV(VOR) PREV->THIS

VALIDATE: no NG segment for Rt:<BOTH.R777>: APMIR¬HC(NAMED).. DANAK¬OE(NAMED).. LAKNA¬OY(NAMED) PREV->THIS

VALIDATE: no NG segment for Rt:<VICTOR.B400>: RC¬FV(NDB).. VHA¬FV(VOR).. VEDET¬OY(NAMED) THIS->NEXT
VALIDATE: no NG segment for Rt:<BOTH.B400>: VHA¬FV(VOR).. VEDET¬OY(NAMED).. RAPDO¬OY(NAMED) PREV->THIS

VALIDATE: no NG segment for Rt:<JET.UR778>: ILDOR¬FT(NAMED).. TONBA¬HL(NAMED).. (NONE) PREV->THIS

VALIDATE: no NG segment for Rt:<VICTOR.M315>: MOGDU¬HC(NAMED).. UTINA¬HT(NAMED).. IMKAL¬FW(NAMED) PREV->THIS

VALIDATE: no NG segment for Rt:<VICTOR.G854>: (NONE).. FL¬FT(VOR).. BOD¬DA(VOR) THIS->NEXT

VALIDATE: no NG segment for Rt:<VICTOR.G855>: FL¬FT(VOR).. BOD¬DA(VOR).. HOGAR¬DA(NAMED) PREV->THIS

VALIDATE: no NG segment for Rt:<BOTH.N304>: APKAK¬FS(NAMED).. AVUSI¬HA(NAMED).. GIBAX¬HA(NAMED) PREV->THIS
VALIDATE: no NG segment for Rt:<VICTOR.N304>: (NONE).. APKAK¬FS(NAMED).. AVUSI¬HA(NAMED) THIS->NEXT
VALIDATE: no NG segment for Rt:<VICTOR.N304>: EGSAP¬HC(NAMED).. MOGDU¬HC(NAMED).. MUSAK¬CY(NAMED) THIS->NEXT

VALIDATE: no NG segment for Rt:<JET.N304C>: MOGDU¬HC(NAMED).. MUSAK¬CY(NAMED).. TOPPS¬K6(NAMED) PREV->THIS

VALIDATE: no NG segment for Rt:<VICTOR.M313>: MAV¬HK(VOR).. MOGDU¬HC(NAMED).. UTINA¬HT(NAMED) THIS->NEXT

VALIDATE: no NG segment for Rt:<JET.UR778>: DEMOX¬FT(NAMED).. ILDOR¬FT(NAMED).. TONBA¬HL(NAMED) THIS->NEXT

VALIDATE: no NG segment for Rt:<BOTH.J154>: BUNGI¬OP(NAMED).. GOTKO¬OP(NAMED).. DELDA¬OP(NAMED) THIS->NEXT

~~~