URGENT SUPPORT REQUEST: Missing Airport ICAO (BGKK) in All AIRAC Cycles

[GodZoo]

Summary of Issue

The destination airport BGKK (Kangerlussuaq, Greenland) is completely absent from all Navigraph AIRAC cycles currently available via the FMS Data Installer. This single omission causes a cascading system failure that prevents any flight plan involving this ICAO from being loaded, manually or automatically, in several high-fidelity aircraft.

The problem persists even after attempting every conceivable software fix, confirming the issue is with the provided data itself.

Observed Failure Symptoms (ToLiss A320neo & A340-600)

All failures are observed when attempting a flight plan between BIRK (Reykjavik) and BGKK (Kangerlussuaq).

1. ACARS Uplink Failure: Using INIT REQUEST∗ results in the error: “INVALID FLIGHT PLAN UPLINK”.

2. Manual Entry Failure: Attempting to manually enter BIRK/BGKK into the MCDU FROM/TO field results in the airport being rejected with an error such as: “NOT IN DATA BASE” (or similar database rejection).

3. Cross-Platform Failure: The exact same failure occurs in both the ToLiss A320neo (V1.2.1) and the ToLiss A340-600, proving the error is systemic to the shared NavData.

Troubleshooting Steps Attempted (All Failed)

The following extensive steps were taken, isolating the problem from user-error, aircraft configuration, and network issues:

1. Full Aircraft Reinstallation: Deleted and reinstalled the ToLiss A320neo completely.

2. Simbrief Account Reset: Deleted all previous Simbrief flight plans, deleted all custom aircraft profiles, and logged out/back into Simbrief.

3. Local Uplink Testing: The Simbrief Downloader was able to successfully save the BIRKBGKK01.fms file to the X-Plane FMS Plans directory, confirming the Simbrief flight plan data itself is valid.

4. Local Loading Attempts:

   • Attempted to load the .fms file via the MCDU SEC F-PLN function. Failed with the same INVALID FLIGHT PLAN error.

   • Attempted to load the .fms file via the X-Plane Menu Load FMS Flight Plan function. Failed.

5. NavData Troubleshooting:

   • Deleted and forced a reinstallation of the latest AIRAC cycle via the Navigraph FMS Data Installer (FDI) to the X-Plane/Custom Data/GNS430/ folder.

   • Attempted to roll back to the previous AIRAC cycle.

Conclusion

Based on the total failure of manual ICAO entry and the discovery that the failures persist across all AIRAC cycles tested, the root cause is confirmed: The ICAO code BGKK is missing from the underlying Navigraph master database.

Please investigate why BGKK (Kangerlussuaq, Greenland) is absent and include it in the next data update.

Why is an airport missing in the AIRAC cycle when the same airport is offered as an option in Simbrief?

The difference is that Simbrief uses a vastly larger, non-AIRAC specific database for planning, while Navigraph’s AIRAC cycles are curated, standardized datasets for simulation FMCs.

Here is the simple breakdown:

1. Simbrief’s Database (Global Planning): Simbrief (which is now owned by Navigraph) uses its own comprehensive database, which includes almost every airport with an ICAO code in the world. It is built for route planning and simply needs the airport’s coordinates and runway data to calculate fuel and time. It is not limited by strict AIRAC cycle rules.

2. Navigraph’s AIRAC Cycle Database (Simulation FMC): The monthly AIRAC cycle data provided by Navigraph to your simulator (ToLiss MCDU) is a standardized, highly structured database used for navigation and procedure validation. This data is packaged for specific formats (like the GNS430 format used by ToLiss).

The Conflict:

If a specific airport (BGKK) is flagged as non-operational, closed, or simply misses the strict processing cutoff for inclusion in the monthly AIRAC package, it will not appear in the FMC files, even though it still exists in the Simbrief planning tool.

The sequence is:

1. Simbrief confirms BGKK exists and calculates the route.

2. ToLiss MCDU receives the route (BGKK).

3. ToLiss MCDU checks its Navigraph AIRAC data files (located in the path you selected: X-Plane/Custom Data/GNS430/).

4. BGKK is missing from the AIRAC file, so the MCDU throws the error: “NOT IN DATA BASE”.

   Airport Existence: BGKK (Kangerlussuaq) is a major, real-world airport and a hub for Greenland travel. Since it exists in the Simbrief planning tool (which you own), you already have the core geographical data needed to incorporate it into their standardised AIRAC packages.

3 hours of drama at my end confirmed and interrupted my round the world trip and pulling my hair out that the local AIRAC files are missing the airport, while the cloud-based Simbrief tool knows it exists.

[NAVData]

Hi,
First and that is very important to understand:
We don´t offer any airport data for X-Plane - the only file is earth_aptmeta.dat this and here the airport is included in the latest AIRAC 2510:

BGKK BG 65.573611111 -37.123611111 117 C 3900 R 7000 FL085

… and I can also select this airport in X-Plane 12 and the C172 with G1000:

Additionally, I have verified our source, and we offer these airports in all our datasets. So, it must be an issue with your system and/or a ToLiss issue (possible due the runway length?). Check the airport with the G1000 please. I’m sorry.

Cheers,
Richard

PS: ToLiss uses the X-Plane default data - so the same as here shown via the G1000

[GodZoo]

Oh wow thank you Richard this was driving me insane!

[Rodeo314]

FWIW, it should be noted that the ToLiSS does have a minimum runway length of 1500 meters (1200 meters for the A319) and BGKK is below both at 1199 meters, also the wrong runway surface as it is a gravel runway.

Regards,

Tim

[GodZoo]

Here’s a question.. if BGKK was not a viable airport for the TOLISS why when I put that aircraft frame into SIM brief did it give me a perfect flight plan.

And yet only when I actually tried to import that flight plan into the Toliss it was rejected. Simbrief calculates fuel and weights etc for flights based on specific aircraft models.. if it’s aware of what aircraft I am using and will even let me know if the destination is out of range based on that specific aircraft awareness why does it not flag that my destination might be a tiny helipad in the mountains? But the Toliss planes did?

Here Simbrief is warning me that I can not fly from Iceland to New York in a Cessna.. can it not provide warnings for unsuitable airports too?

[NAVData]

@GodZoo

Here’s a question.. if BGKK was not a viable airport for the TOLISS why when I put that aircraft frame into SIM brief did it give me a perfect flight plan.

Because SimBrief doesn´t know anything about the restrictions/limitations of the addons, there is no connection between SimBrief and the addons. Finally, it is a pilot decision, not a tool decision, because there are many factors (such as runway conditions and wind) that must be considered. You can land an A319 on such short runways, on gravel, ice, … but again, it depends on so many factors like MLW, weather conditions, surfaces, …

Therefore, it makes no sense to limit this during flight planning. But you can add your request to our the wishlist.

Cheers,
Richard

[GodZoo]

Thank you Richard. I always assumed that when creating the flight plan that Simbrief would know based on the aircraft I chose and if it didn’t flag anything I accepted it was fine to go there. There are other apps that I use for creating flight plans and once I input what plane I’m in, it will automatically disclude all airports, runways etc that are unsuitable for my current aircraft in the search results.
In future I will be a bit more careful about my destinations choices.