Most likely it is an issue with the airport layout in X-Plane not matching the real world. This types of issues will not be fixed until the scenery is corrected and included in an update.
On my game, I was in DFW International Airport getting set up going to San Antonio International Airport than it said “Procedures can be loaded,missing runway RW12 in KSAT
I imported this this airport into WED to modify it for personal use and discovered there are 61 validation errors in this package to be addressed before I begin work. I really cannot understand how it was approved or recommended. I suggest the person who contributed the airport package correct these errors so others do not have to waste time doing so.
Validation changes over time because X-plane changes, we learned about things that turned out to cause problems in X-plane or just because the "standards" for the gateway have been raised.
So part of the deal that gives you a free to use copy of someone else' work is that you have to help "upgrading" older airports to current gateway standards. Fair enough ?
Unable to plan flight to Ksat in FMC. System does not see it correctly. Currently on 1706rev1
Jennifer Roberts June 15, 2017 9:48 AM
Most likely it is an issue with the airport layout in X-Plane not matching the real world. This types of issues will not be fixed until the scenery is corrected and included in an update.
On my game, I was in DFW International Airport getting set up going to San Antonio International Airport than it said “Procedures can be loaded,missing runway RW12 in KSAT
Braylontate15 August 15, 2018 5:20 AM
I meant can’t^
Jennifer Roberts February 23, 2021 3:56 PM
Closing reports that were last updated 1 year ago or more in bug base clean up. These are most likely fixed due to Gateway scenery cuts in that time.
Approach procedures do not show up in the C172 Garmin 430/530 in Plane 11.26. Message about Runway R12 Missing pops up.
Philipp Ringler December 8, 2018 1:34 AM
Airport scenery is correct. The current runways in San Antonio are 04/22, 13L/31R and 13R/31L. See https://www.airnav.com/airport/KSAT
If you are missing a runway 12R that means your navdata is out of date and wants the old airport. Update your navdata and it'll work.
I imported this this airport into WED to modify it for personal use and discovered there are 61 validation errors in this package to be addressed before I begin work. I really cannot understand how it was approved or recommended. I suggest the person who contributed the airport package correct these errors so others do not have to waste time doing so.
Michael Minnhaar January 19, 2019 10:29 PM
Validation changes over time because X-plane changes, we learned about things that turned out to cause problems in X-plane or just because the "standards" for the gateway have been raised.
So part of the deal that gives you a free to use copy of someone else' work is that you have to help "upgrading" older airports to current gateway standards. Fair enough ?
Modularis January 22, 2019 9:20 PM
I'm working on a fix. Should be uploaded soon.
Jan Vogel February 28, 2021 2:35 PM
Airport has been updated recently, this report can be closed.