EDIT: Worked for me. No more CTD around Washington DC.

Here's the thread on the MSFS Forums where the fix was discovered:

https://forums.flightsimulator.com/t/kadw-andrews-ctd-analysis-by-community-contributions/465405/131

I've been playing with the SDK to fix up KBWI a little. When I renamed that file, the main terminal at BWI disappeared. I thought I nuked it with the SDK, but restoring that file put it back. 

Another oddity I noticed is that there is an orange traffic cone hovering about 60' above gate C11 at KBWI. I can't select it, exclude it, or see it in the object list. You have to get the drone very close to and above C11 or C9 to see it. I'll bet it is part of that file. The SDK says that there is an "Object Test Radius". Here is the definition. "This is the radius around the airport reference point in which you are permitted to place any of the listed airport objects. In the world, this can be seen rendered as a dark blue circle.". In the scenery editor, the blue circle is just big enough to cover the airport you are working on. It does not say what happens if you place a "listed" object outside of the airport. Maybe the sim crashes? Could this one cone be causing the problem? Inquiring minds...

And here's how my version of BWI is coming along... If I can get a few issues worked out with the gates, finish up tuning up the navigational aides and their positions, and getting the taxiway signs fixed, maybe I might put it up on flightsim.to. I'll need to redo the background images to a lower resolution, though. The current ones are 775 Mb. I think that's too large to distribute. I'm not going to mess with the terminal building for now. It sure was nice departing gate A7 yesterday and getting the correct taxi instructions using the correct names all the way to runway 33L . I think that stupid orange cone is messing up my jetways. All of them work fine up to C11 where that cone is, and then the jetway at every gate after that is wrong. No matter which gate you are at, when you call for the jetway, the jetway at the gate to the right of the one you are parked at tries to connect. If you dock at C9 and call the jetway, gate C7's jetway tries to connect to the right side door. I'm stumped.

On 11/1/2021 at 9:55 AM, MDFlier said:

It crashed because there is NO runway 22 at KBWI... Well, not in real life anyhow. 🤣

I can't believe that MSFS released with KBWI looking like it does. The improvements to runway 15R-33L were completed and it was returned to service at the end of 2014. Runway 4-22 actually had to be "upgraded" to meet current FAA standards for use as a taxiway. It was gone at the end of 2014 when it was converted to a taxiway. 

If you fly IFR, none of the SIDs or STARS are available at KBWI due to 15R-33L being missing. I was able to add it in using the SDK and they work fine now.   

Unfortunately, the current aerial photo of KBWI in Bing Maps still shows the old runway 04/22, so this photo is pre-2014 - and that is what was used to create the KBWI in MSFS. Both Google and Apple Maps have a much more recent aerial photo.