T89 Double Runway Issue

Navigation Data Airport Scenery
1

There is a duplicate and offset runway at T89 Lajitas Airport in Texas. I have no scenery add-ons other than Navigraph.

2

image
image1920Ă—1080 232 KB

The darker one is the MSFS data.

3

I think I see what may have happened. Using Little Navmap I can see there are two assets overlaid:

MSFS Official
89TE
C:\Users\kenke\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\fs-base\scenery\0202\APX20210.bgl

Navigraph
T89
C:\Users\kenke\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\navigraph-navdata\scenery\fs-base-jep\scenery\0202\NAX20210.bgl
C:\Users\kenke\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\navigraph-navdata\scenery\fs-base\scenery\0202\APX20210.bgl

Given the FAA Identifiers mismatch that could be the cause of it.

Is submitted this to the MSFS Zendesk as well "“Request #132451 The FAA code for Lajitas Field is wrong”

Is there a way to disable one or the other until this is fixed?

4

Hi,
yes that is exactly the reason. The MSFS uses an outdated/former ICAO code, the real world one is T89. We compare the existing airports in the MSFS with the none-existing airport thru the ICAO codes, which are unique. If we don’t find it, we “create” the missing airport/runway that we can include all terminal procedures.

Sorry, this is a MSFS issue as you see. Please report this to ASOBO/MS. Thank you.

Cheers
Richard

1 Like
5

Thanks, I have created a zendesk ticket with Asobo. Interesting thing is 89TE is a current FAA designation for Plaza Medical Center Heliport in Fort Worth Texas. IMO they just typo’d something. At any rate I created a ticket with them. Is there a way to disable the conflicting Navigraph scenery until they fix it on my side besides deinstalling the whole thing? Honestly this particular airport is of no concern. I just ask in case I run into one I care about. For now this golf course can be posh with its two runways :slight_smile:

6

Hi again,
so now I was curious :slight_smile:

I have re-checked all - and have found out following:

The T89 was former the 89TE …
image

Now it´s Lajtas Intl

image
image1303Ă—338 26 KB

89TE is now the Plaza Medical Center

image
image1211Ă—388 27.9 KB

The FAA identifier for T89 is T89, but the official airport identifier is KT89 … I guess, because the Europeans has no FAA :wink: … very tricky :wink:

What I can do now is, that I don´t export the KT89 airport that you don´t see any double runways. But than you still have a wrong FAA/ICAO airport id for this airport (89TE), which is wrong in MSFS.

Cheers,
Richard

PS: it´s not a question of right or wrong here :slight_smile: … in one way you have double runways but the correct ICAO airport ID, or you have one one runway but the wrong ICAO airport ID :slight_smile: … both solutions are not good :slight_smile:

7

Thanks for the extended look into this issue. That is interesting about the temporal use of the 89TE designation. I agree there is no good solution here. This can’t be common enough to matter lol and God help anyone using MSFS for IRL navigation. (which is a no-no anyway). Hopefully Asobo fixes this. What site did you use for the ICAO lookup?

8

This is the direct FAA database :shushing_face:

Cheers & have a nice day,
Richard

9

Thanks! I love the product so far.

1 Like
10

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