XPlane 12 wrong airway altitude data

Hi there,

I recently found out that the XPlane 12 data for airways is somehow shuffled regarding the airways segments lower/upper altitudes.

For example :

DIPER LF 11 VESAN LF 11 F 1  65 195 L613
VESAN LF 11 RATUK LF 11 F 1  65 195 L613
RATUK LF 11 SOVAT EG 11 F 1 100 430 L613
SOVAT EG 11 SANDY EG 11 F 2 260 430 L613
SANDY EG 11 STOAT EG 11 F 2 260 430 L613
STOAT EG 11 MOGLI EG 11 F 2 260 430 L613
MOGLI EG 11 BETAX EG 11 F 2 260 430 L613
BETAX EG 11 MAMUL EG 11 F 2 260 430 L613
MAMUL EG 11 HALIF EG 11 F 2 260 430 L613
HALIF EG 11 ABKAT EG 11 F 2 260 430 L613
ABKAT EG 11   TLA EG  3 F 2   0   0 L613

You can see that the last segment here ABKAT-TLA has 0 for lower and upper altitude, which is strange.
The segment RATUK-SOVAT is declared from FL100 to FL430. Yet, according french AIP, it is only existing from FL65 to FL195.
However, the SOVAT-SANDY segment, which is FL260-FL430 in XPlane file should normally be FL100-FL430, according UK AIP.

So, I hope the pattern is visible here, the altitudes of airway segments are shifted up here, and the last segment is missing altitude data then.

L613 airway is just one of many example I found in this file. It does seem to be like this for at least a year, as similar issue are found in AIRAC 2301 data as well.
Can anyone from Navigraph have a look on it, and confirm or not what I think is wrong here ?

The data in Navigraph Charts for example is correct, so it looks like that only the Xplane formatting process is buggy, not the raw data you have from Jeppesen.

For reference (links are being blocked by the system, so here they “are”) :

  • French AIP : www (dot) sia (dot) aviation-civile (dot) gouv (dot) fr/dvd/eAIP_22_FEB_2024/FRANCE/AIRAC-2024-02-22/html/index-fr-FR.html
  • UK AIP : nats-uk (dot) ead-it (dot) com/cms-nats/opencms/en/Publications/AIP/
  • XPlane AWY file structure I use as reference : developer (dot) x-plane (dot) com/article/navdata-in-x-plane-11/

Thank you !

Hi,
thank you very much for your report. After a first and indeed fast view, I would confirm your observation but please let me make more checks. I will also cross-check this with the X-Plane devs. I will keep you inform here, but please be patience …

Thank you,
Richard

1 Like

Hi,
just an short update - I can now confirm the bug and we will try to fix it asap … Thanks for your input here. Will keep you inform, when it´s fixed :wink:

Cheers,
Richard

Hi Richard,

Thank you for the quick feedback !
Happy to help :wink:

Romain

1 Like

I’ve identified the problem and coded the fix. As you suspected, it was a shift by one position, a classic fence post error.

Fixed data will be available in a future update cycle.

2 Likes

Excellent, thank you guys. That was fast !

Cheers,
Romain

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.