Glideslopes all set too short (10nm) in Navdata

Navigation Data ILS
1

I am using the Navdata Cylces for X-Plane 10, and load them into FlightGear. When I fly approaches by the charts into airports with longer than 10nm glideslopes ( EDDF , EDDM , …) I am unable to intercept at the FAF as the GS will only come alive at 10nm.

I checked the earth_nav.dat file, and indeed, all the Glideslopes are set to standard 10nm range (cycle 2510) (see screenshot). This applies to every single GS entry in the file.

Bildschirmfoto_20251028_124544
Bildschirmfoto_20251028_124544592×469 51.4 KB

This seems like an error to me. GS range should be defined according to individual approach facilities, to allow flying by the chart. The old (2013) X-Plane dataset that comes with FlightGear indeed has differing values for indiviudal GSs.

(Also, every LOC is set to 18nm, discarding local differences).

2

I checked the X-Plane 11 data, and there, it seems GS has the same length as the LOC (default 18nm). So maybe a parsing problem when generating the X-Plane 10 data?

3

Hi,
We don´t have these values in our database, and therefore, it is set to a default value. In XP10, the default values are:

LOC = 18 NM
GS = 10 NM (-> from AIRAC 2511 on 18 NM)

I have also updated the default GS range to 18 NM. This change is expected to be available in the upcoming AIRAC cycle 2511.

I hope that helps,
Richard

4

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