Personal Comments and Observations
The AIRAC data must match an existing airport BGL file in the sim.
I learned a long time ago that if the physical airfield doesn’t exist as a BGL file, it will won’t get shown even if AIRAC says it’s there. There has to be a primary key, and in this case, it’s what’s understood to exist on the terrain, then overlay the Navigation data.
Similarly, if the BGL file is Overtaken By Events or more succinctly, the AIRAC data is newer than the BGL field, you will get mismatches - notably on Approaches as the usual situation is a runway closure or creation. That will show in digital FMS as being a missing Approach.
In your case, it’s the reverse, a BGL object exists where there shouldn’t be any. But the concept is the same - both data sets must reconcile.
Then there’s the additional complications of BlackShark making a pass to populate autogen SimObjects for airport buildings, but that’s a side issue.