Recently subscribed to practice approaches / departures into airports in Alberta, Canada. Despite plates now being available seems the approaches etc. are not available for certain airports, specifically Edmonton Parkland Executive CYEP and Three Hills CEN3. CYEP was formerly CPL6 and is still given that identifier and has not been updated it seems.
I am using XPlane 11 and G1000 aircraft, the FMS Data Manager appears to have no problem recognising XPlane and downloading the current data so I can only assume the current Navdata is not correct and has not been updated. Prior to subscribing I checked the airports covered by Navigraph and both CYEP and CEN3 were stated as being covered? So as a newbie here any help would be appreciated to get what I need.
The airport identifiers are part of the scenery rather than the navigation data, and therefore cannot be updated by Navigraph.
X-Plane itself (meaning the scenery shipping by default with it) still has Edmonton Parkland as CPL6:
…and CEN3 as EN3:
Unfortunately since their in-sim identifiers do not match the identifiers used elsewhere (including in Navigraph’s database) of CYEP and CEN3, the procedures cannot be assigned to the airport by the default avionics.
If you use an aircraft with a self-contained database (such as the FlightFactor 757/767, possibly the 777v2 as well come to mind; maybe also the IXEG 737 Classic, the Rotate MD-80 and MD-11) you should have the airports listed in the avionics along with their associated procedures.
Unfortunately other aircraft that use the “native” X-Plane data where the airport identifiers are not part of the updatable database, will suffer from the same issue as the default avionics like the G1000 in your case.
Thanks for your response and explanation Tim, much appreciated. Since CYEP has only recently had its identifier changed and approaches etc. published I would assume even the latest version of XPlane or MSFS still has the old identifier CPL6 and so the only way these can ever be updated is when a new version with the correct identifier is released which could be years away? Assuming that to be the case is there no way possible that whoever updates the nav data could apply these approaches to the identifier currently in use CPL6, and the same to CEN3 (EN3). This would seem to be a viable solution? Is there a way to contact whoever controls the nav data directly to request this? I can see no direct contact for support aside from this forum.
Hi Jason,
Richard here - I´m one of the people responsible for the navdata on our team.
Unfortunately, this is not possible. I’m sorry. We use real-world data and produce every dataset from a single database of real-world data. When we “change” the airport ICAO code, we will change it everywhere, which is not what we want.
When such airport codes are outdated, the only way is to inform the developer … it´s the same for all simulators, from XP11 to MSFS2024. Sorry.