KTUS Arrivals Not Listed

User Support Hub ATC, Traffic & NAVAIDs
, , ,
1

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.

I do have the KTUS Airport scenery from the Marketplace. I’ll try uninstalling it to see if it makes a difference.

Brief description of the issue:

I have the latest Navigraph AIRAC, and I’ve noticed that on G3000/5000 and GTN750 equipped planes (and perhaps others?) that there are no arrivals listed for Tucson International (KTUS). For what it’s worth, the airport IRL recently took 29L/11R out of service and renumbered 29R/11L to 12/30. I’m guessing that might be part of the issue. Navigraph data does have the new runway config.

Provide Screenshot(s)/video(s) of the issue encountered:

image

ICAO or coordinates (DevMode > Debug > Display position)

Detailed steps to reproduce the issue encountered:

Plan flight to Tucson, try to select an Arrival STAR in the FMC.

PC specs and/or peripheral set up if relevant:

N/A

Build Version # when you first started experiencing this issue:

SU-14 (though I think it coincided with the last Navigraph update, not FS version)

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

I’ll also perhaps put in a ticket with Navigraph in case it’s something with their database.

If relevant, provide additional screenshots/video:

3

Another note: On a flight to KTUS, when setting the landing perf data in the Longitude, it still lists the old runways. So I’m 99% sure this is a mismatch between the Navigraph data and FS2020 internal runway data.

I removed the KTUS Scenery (Marketplace) from the sim, the issue remains.

Workaround is to manually enter STAR waypoints and constraints.

Yet another note: I CAN select a STAR for KTUS in the Fenix A320 and PMDG 737. I can’t do so in the Longitude and the PMS50 GTN750 (Black Square aircraft). I haven’t yet tried other aircraft.

PMDG shows the correct runway association with the STAR (12 and 30).

image

4

Yep, because both use own, seperate databases and therefore you have more flexibility, as thr in-game BGL data and there steucture. The MSFS has the “feature” that when a terminal procedure can’t assign to a runway, the MSFS diaable the terminal procedure, even when they are still included.

The 3rd party addon developer are more independet from any sim/world update and any logic in the MSFS. They can code their own/correct logic. There are more than 300 airports worldwide, which are outdated and where you see such issues, sorry.

You and also we can’t do anything because there is no real possibility to change only the runway idents, which would be very helpful.

Cheers
Richard

2 Likes
5

Thanks for the explanation, Richard! I’ll just continue to manually enter waypoints for STARS into Tucson. Gives me something to do at cruise.

1 Like
6

This seems to be fixed! I’m not sure if it was included in the sim update earlier this week, or was part of the scenery update in the Marketplace for KTUS, but glad to have things squared away.

7

Moved to User Support Hub ATC, Traffic & NAVAIDs since solution has been marked.

8

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