Currently the datastructs of MS2020 and MS2024 support only the following runway designation letter values:
Designator of the primary end of the runway, one of the following values:
0: NONE
1: LEFT
2: RIGHT
3: CENTER
4: WATER
5: A
6: B
7: LAST
Where 1…4 are usually abbreviated with L,R, etc
There are however runways using T, especially in NZ south pole region (e.g. NZWD RW07T)
Those are referenced by Navigraph content but will not match the MS airport/runway data. i.e. causing the need to patch data on a guess base.
Btw: T is used (in NZ area but may be not worldwide) for True referenced runways.
→ It would be beneficial to extend the definitions and also reference the correct runways in the MS/Asobo FSim world.
That is to flag True north referenced facilities (VORs have it added in FS2024)
and to allow for T as runway designation letter.
While I understand that extending datastructs is a far stretch… at least allowing and using ‘T’ to be added for runways idents would eliminate inconsistencies when using Navigraph or other data matching the real world naming.