Oh, I'm sorry, I saw that he was mentioned earlier and assumed he was developing the airport.
But please, don't just treat these issues as single cases only affecting one developer or single airport at a time like you did before. You guys need to discuss these issues with all of your airport developers, because it seems to affect a large portion of your MSFS catalog.
One example: I just checked EGLC, which had been released right after MSFS came out, and it has exactly the same issue. I'm even more surprised about that one, because I recall this issue had been discussed back then and I think I remember it was announced that it was solved in a patch.
I can only speculate, but I could imagine that a lot of these issues don't get noticed more often because a lot of people use Navigraph which overwrites a lot of these airport navdata entries, so the problem might not be visible when using Navigraph.