# T89 Double Runway Issue

**URL:** <https://forum.navigraph.com/t/t89-double-runway-issue/6496>\
**Category:** Airport Scenery\
**Created:** [October 29, 2021, 7:34pm UTC](https://forum.navigraph.com/t/t89-double-runway-issue/6496 "2021-10-29T19:34:31Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![JSTK3N](https://avatars.discourse-cdn.com/v4/letter/j/f04885/32.png) [@JSTK3N](https://forum.navigraph.com/u/JSTK3N)\
**Post date:** [October 29, 2021, 7:34pm UTC](https://forum.navigraph.com/t/t89-double-runway-issue/6496/1 "2021-10-29T19:34:31Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![JSTK3N](https://avatars.discourse-cdn.com/v4/letter/j/f04885/32.png) [@JSTK3N](https://forum.navigraph.com/u/JSTK3N)\
**Post date:** [October 29, 2021, 7:36pm UTC](https://forum.navigraph.com/t/t89-double-runway-issue/6496/2 "2021-10-29T19:36:34Z")

</div>

![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/2X/9/974c7f22778f8161d0e5b225bca333c386cef56f.jpeg)

The darker one is the MSFS data.

---

<div class="post-metadata">

**Author:** ![JSTK3N](https://avatars.discourse-cdn.com/v4/letter/j/f04885/32.png) [@JSTK3N](https://forum.navigraph.com/u/JSTK3N)\
**Post date:** [October 29, 2021, 9:48pm UTC](https://forum.navigraph.com/t/t89-double-runway-issue/6496/3 "2021-10-29T21:48:19Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![NAVData](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/navdata/32/30549_2.png) [@NAVData](https://forum.navigraph.com/u/NAVData)\
**Post date:** [October 30, 2021, 6:15am UTC](https://forum.navigraph.com/t/t89-double-runway-issue/6496/4 "2021-10-30T06:15:55Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![JSTK3N](https://avatars.discourse-cdn.com/v4/letter/j/f04885/32.png) [@JSTK3N](https://forum.navigraph.com/u/JSTK3N)\
**Post date:** [October 30, 2021, 10:35am UTC](https://forum.navigraph.com/t/t89-double-runway-issue/6496/5 "2021-10-30T10:35:50Z")

</div>

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 🙂

---

<div class="post-metadata">

**Author:** ![NAVData](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/navdata/32/30549_2.png) [@NAVData](https://forum.navigraph.com/u/NAVData)\
**Post date:** [October 30, 2021, 11:35am UTC](https://forum.navigraph.com/t/t89-double-runway-issue/6496/6 "2021-10-30T11:35:45Z")

</div>

Hi again,  
so now I was curious 🙂

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

The T89 was former the 89TE …  
 ![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/2X/a/a017e2df757aa5a0fa2ea222af511c63780aea13.png)

Now it´s Lajtas Intl

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/2X/2/28daa8c865f90284849b9b91e3212b41ed37d920.png)

89TE is now the Plaza Medical Center

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/2X/6/6338bf04f62ad0f699e23eac07c8fde80624c11e.png)

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

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 🙂 … 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 🙂 … both solutions are not good 🙂

---

<div class="post-metadata">

**Author:** ![JSTK3N](https://avatars.discourse-cdn.com/v4/letter/j/f04885/32.png) [@JSTK3N](https://forum.navigraph.com/u/JSTK3N)\
**Post date:** [October 30, 2021, 2:24pm UTC](https://forum.navigraph.com/t/t89-double-runway-issue/6496/7 "2021-10-30T14:24:37Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![NAVData](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/navdata/32/30549_2.png) [@NAVData](https://forum.navigraph.com/u/NAVData)\
**Post date:** [October 30, 2021, 3:17pm UTC](https://forum.navigraph.com/t/t89-double-runway-issue/6496/8 "2021-10-30T15:17:41Z")

</div>

> [@JSTK3N](#):
>
> What site did you use for the ICAO lookup?

This is the direct [FAA database](https://enasr.faa.gov/eNASR/nasr/) 🤫

Cheers & have a nice day,  
Richard

---

<div class="post-metadata">

**Author:** ![JSTK3N](https://avatars.discourse-cdn.com/v4/letter/j/f04885/32.png) [@JSTK3N](https://forum.navigraph.com/u/JSTK3N)\
**Post date:** [October 31, 2021, 1:16pm UTC](https://forum.navigraph.com/t/t89-double-runway-issue/6496/9 "2021-10-31T13:16:57Z")

</div>

Thanks! I love the product so far.

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/1X/4cc83e90d70ab312b1bd2d7527bddad309607265.png) [@system](https://forum.navigraph.com/u/system)\
**Post date:** [November 2, 2021, 1:17pm UTC](https://forum.navigraph.com/t/t89-double-runway-issue/6496/10 "2021-11-02T13:17:49Z")

</div>

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