FACILITY DATA AIRPORT.RUNWAY missing ILS info

Version: SDK V1.1.2 MSFS2024 V 1.2.11

Frequency: Always

Severity: High

Similar MSFS 2020 issue: not checked

Context: FACILITY DATA AIRPORT.RUNWAY missing ILS info

Attachments: N/A, but can be provided upon request

Bug description:

FACILITY DATA AIRPORT.RUNWAY missing ILS info
at least one, did not checked further so far but likely the problem persists ..

Note: I have a DISABLED marketplace LSZH from 2020 in the streamed list
may be this is causing some issues - but as it is disabled it should be disabled…
I cannot otherwise remove this airport for testing.

some other airports I’ve checked return such ILS IDs

Request for FACILITY DATA for AIRPORT.RUNWAY of LSZH returns:

LSZH Runway 10/28 plain MSFS204 content

        ALTITUDE    422.9990234375  double
        LATITUDE    47.457773834466934  double
        LONGITUDE   8.5539378225803375  double
        PRIMARY_DESIGNATOR  0   int
        PRIMARY_ILS_ICAO    ""  string
        PRIMARY_ILS_REGION  ""  string
        PRIMARY_ILS_TYPE    0   int
        PRIMARY_NUMBER  10  int
        RwLength_m  2516.89258  float
        RwWidth_m   60  float
        SECONDARY_DESIGNATOR    0   int
-->     SECONDARY_ILS_ICAO  ""  string  SHOULD BE IZW
-->     SECONDARY_ILS_REGION    ""  string  SHOULD BE LS
        SECONDARY_ILS_TYPE  0   int
        SECONDARY_NUMBER    28  int
        SURFACE 0   int
LSZH Runway 14/32 plain MSFS204 content

        ALTITUDE    423.00003051757813  double
        LATITUDE    47.472192049026489  double
        LONGITUDE   8.5495729744434357  double
        PRIMARY_DESIGNATOR  0   int
-->     PRIMARY_ILS_ICAO    ""  string  SHOULD BE IKL
-->     PRIMARY_ILS_REGION  ""  string  SHOULD BE LS
        PRIMARY_ILS_TYPE    0   int
        PRIMARY_NUMBER  14  int
        RwLength_m  3303.29761  float
        RwWidth_m   60  float
        SECONDARY_DESIGNATOR    0   int
        SECONDARY_ILS_ICAO  ""  string
        SECONDARY_ILS_REGION    ""  string
        SECONDARY_ILS_TYPE  0   int
        SECONDARY_NUMBER    32  int
        SURFACE 0   int
LSZH Runway 16/34 plain MSFS204 content

        ALTITUDE    422.9990234375  double
        LATITUDE    47.460639104247093  double
        LONGITUDE   8.5463185608387 double
        PRIMARY_DESIGNATOR  0   int
-->     PRIMARY_ILS_ICAO    ""  string  SHOULD BE IZH
-->     PRIMARY_ILS_REGION  ""  string  SHOULD BE LS
        PRIMARY_ILS_TYPE    0   int
        PRIMARY_NUMBER  16  int
        RwLength_m  3716.02246  float
        RwWidth_m   60  float
        SECONDARY_DESIGNATOR    0   int
-->     SECONDARY_ILS_ICAO  ""  string  SHOULD BE IZS
-->     SECONDARY_ILS_REGION    ""  string  SHOULD BE LS
        SECONDARY_ILS_TYPE  0   int
        SECONDARY_NUMBER    34  int
        SURFACE 0   int

Impact: High, as the ILS is not reported how to find out which
one is located there ???

This is a common problem as scenery devs replace the runway with their own, and don’t add an <IlsReference /> in the XML. Runway Definition Properties

Thanks

only the addon is marked Disabled - so it should not be loaded at all??

With active ones this is causing then all kind of trouble I assume…

I’ll check with SU1beta (installed it just a minute ago)

EDIT
did not change - still no ILS entries in SU1 (V1.3.10)

I am not sure exactly about LSZH, but some of the hand-built airports that ship with the sim do break navdata in various ways unfortunately. It is worth reporting these so they can eventually all get fixed.

The workaround I have used to find the ILS for a runway is to look through ILS approaches for the airport + runway, and get the recommended navaid from the final leg of the approach.

I can confirm the same issue, and fixed it by disabling this package:
image

I will ‘borrow’ this one… thank you
Adding to the list of patches to be applied…

So it is the base apt not the ‘disabled’ one that fails

Hello @bm98 @tracernz

This particular case cannot be solved on our side and needs to be reported through Zendesk.
However, we can probably add a warning in the SceneryEditor when a runway has an empty IlsReference and a corresponding ILS exists.

Regards,
Sylvain

1 Like

Scenery Editor now references existing ILS by default when adding a new runway.

Regards,
Sylvain

3 Likes

This topic has been automatically closed after 60 days of inactivity since it was marked as fixed.

If there is important new information about this same report, you can use the “Request reopen” button below to ask the moderation team to review it again.
For other issues or broader discussion, please open a new topic in the appropriate category.