I understand that Navigraph cannot provide charts for this airport, but the airport identifier and the associated procedures are in the provided navigation data. So I was surprised to be unable to select the airport, runway and procedures in Charts Desktop today.
Can something be done about this?
Regards,
Tim
Hello, it looks like this topic was forgotten?
Regards,
Tim
Hello! Thank you for the reminder, this did indeed slip through unnoticed!
We currently add Kai Tak to our navigation data in what we call “Tailored records.” These records are for those who use scenery from when the airport was open and would like to mimic what the operations looked like then - in this context, it makes sense!
However, it does not make as much sense in the Charts application for several reasons. The real-world map has changed, and this area is no longer an airport, so the navigation data would line up with… nothing. Many users would also expect charts - of which there are none for this airport.
This means that we have currently decided not to include these tailored records in our Charts application. If you have further thoughts or motivations around this, feel free to elaborate!
Kind Regards,
Malte
The main issue I’ve encountered is, the tailored records are also added to Simbrief’s database, so you can plan a flight from/to VHHX on Simbrief, import into Navigraph Charts and get less-than-ideal results.
Regards,
Tim
Edit: Simbrief’s “Navigraph IFR” maps, meanwhile, has no trouble rendering the full route:
Yeah, SimBrief currently runs on navigation data that includes tailored records.
We’ll explore the available options. None are straightforward, and most have unwanted side effects. It is unlikely that we’ll be able to do anything about this situation in the near future.
We could remove the tailored records from SimBrief too, but for now that seems unnecessary given that not all SimBrief users use Navigraph Charts. I’ll try to let you know if we figure out a solution to this in the future!
Maybe an idea is to use the old charts (like te one given by ivao) and keep VHHX in the database with an option to have it or now
I’m also keen on this being implemented in the base navdata and charts app. As it stands on final to RW13 in the IniBuilds A350, the lack of (I believe) Charts data means that there is no ANF runway available, thus when you join final you get screamed at “RUNWAY TOO SHORT”
Which is obviously very distracting whilst doing that nice 50 degree turn.
Any chance of this being implemented using a single package containing the old charts e.g. as mentioned from IVAO or a small bespoke package for Kai Tak in the hub as an option?
That sounds like an implementation detail on the iniBuilds side. Why would it say that the runway is too short if it has no data for the runway? Sounds like that should be configurable?
There is no AMDB data for this airport, so there is nothing for us to provide in this case.
As for the “small package” approach, I can’t speak to it unfortunately. Providing outdated navigation data and charts (and figuring out how to do so) are not high on our priority list at the moment, but we’ll keep your suggestion in mind!
