Tried the download from the home page yesterday, that worked ok, the link on the forum didn't.

Just tried that, got error as attached.

I guess like zillions of others I had to update MSFS2020 yesterday, and on compiling the new database I hit this bug. Thanks Picnic for the solution as above.

I wouldn't trust airport names to MSFS. I complained about duplicate names (e.g. Khorixas Airport) and was told they sourced the data externally, it wasn't their fault there were errors in the data. Good Luck!

I use Plan-G running on another networked PC, over the years using FSX, P3d, and now MSFS2020. I also experience CTDs running MSFS2020, and if you look at the MSFS2020 forum you will see it occurs all too frequently. I understand the latest update has been delayed due to a number of issues with the beta testing.
I would suggest that perhaps the CTDs you are experiencing are down to MSFS2020, rather than Plan-G, they might cease when the latest update appears - if we are lucky!

In the early 1980s I was employed by a group of PC retailers in a technical capacity. At the time, the IBM PC had been launched, and a number of manufacturers wanted to join the market, and produced PCs that were marketed as being compatible. It was thought at the time that a good test of compatibility was the flight simulator program, and so a copy of this found its way onto my desk. I took it home to play with it, and got hooked. I've since flown all succeeding versions, and a number of other flight sims. I now am pretty well fixed on MSFS2020.

During the last 40 odd years I've joined a number of FS interest groups, those I remember include the UK Flight Scenery Group, JHB Airlines, the CIX VFR Group, FS Developer, and the group that were in at the start of Plan-G.

I hope that gives you a clue!

The radio beacons are part of the simulator scenery, so they would need to be created as scenery elements. You might like to pose the question about how to create these in FS2020 on the FSDeveloper forum, there are plenty of people there who could help you.

Transferring the data there would be just like using your FSX data when flying in MSFS2020, they would show on the map, but wouldn't work in the sim.

Hope that helps.

It just struck me as odd that they know the airfield exists - or existed - because landing there puts the correct ICAO code into the log, but then they don't allow you to start a flight there.

Just tracked down the first problem airfield - KDBQ - my log says I landed there, but I can't select it as a start location.

I have been using Plan-G to plan hops across the USA, and I have come across a couple of airfields not fully recognised by MSFS2020. The first one I just thought was odd - I could land there, and it appeared in my log, but I could not select it to take off from. I did appear with yellow crosses on the runway. I'm sorry I've lost the ICAO.

The second one - KXNI - appears to have the same symptoms. I didn't land there but diverted to KZUN, but it did have the yellow runway crosses. I am concluding that both these airfields are now disused, but Plan-G has identified them as live. Is this correct ?

This software has certainly evolved over the years since we first tested it, I didn't know themes existed!

I tried using the yellow and cyan, but the problem is with the font of the data itself; the headings in bold show up nicely, is it possible to use bold for the data?

I know my eyes aren't what they used to be, but I am struggling to read the data provided at the bottom of the screen. Admittedly I am peering from beneath my VR headset, but the normal black font against the grey background doesn't help, I wondered if it would be possible to either use the bold font as per the headings, or maybe a light colour against the grey background?

Sorry to be a nuisance again Tim.

Confirm fixed in v4 v258, thanks Tim.

I am attempting to fly around the world from Oxford, UK, in MS2020, and so far I have used Plan-G to plan each step eastwards, and I have arrived in the south island of New Zealand. I am trying to plan the next few steps, going north to Fiji, and then east to.......well I don't know because Plan-G crashed when I tried to go east.......
Is this something we are stuck with, or is there a workaround?

If you switch from one data set, e.g. FSX, to another, e.g. MS2020, before loading any plan at all, the bug manifests itself.