KASH is missing its Tower and Ground Frequencies that it had in 2020

Hi,
Has something changed in how an airport Tower and Ground frequencies are specified?

At KASH, a Class D towered airport in Nashua, NH, everything is fine in 2020, both the default and the airport package I created to replace the default properly have a Tower at 133.2 and Ground at 121.8, ATIS at 125.1, and supports ground services and have their approach procedures.

In default 2024, KASH no longer has it’s Tower, though it does have a traffic frequency at 133.2, and it’s missing it’s approach and departure procedures, at least as far as the charts are concerned, both LODI and FAA.

When 2020 was released, it suffered a similar problem (no procedures), but it did have its Tower, and the procedures were eventually added about a year later.

So I imported my airport scenery into 2024 (available at flightsim.to KASH), and, while all of the features of the airport are there (the taxiway lights are missing their stalks, though), it doesn’t have the Tower still. In the 2020 airport definition, I did delete the frequencies and added them back in. In fact, since it was originally missing its navdata, I added it in manually. When it was eventually fixed, I removed my navdata from the package. (Hmm, I’ll have to check if I uploaded that version to flightsim.to, I think I did, but it is what I’m using to test)

So, my question is, what’s stopping the Tower and Ground from showing up in 2024 with my 2020 compiled airport added?

I haven’t recompiled the airport yet with the 2024 SDK. Any idea if it will work then, or is there some overarching 2024 ATC thing that’s blocking these smaller airports from having their correct data?

I did see another similar report for another airport, KRDM, over at the forums in the bug reports.

I’ll update the post when I have a chance to recompile the airport with the 2024 SDK.

In the meantime, will the navdata eventually be fixed to include these smaller airports again? Or is this the result of moving to LODI and FS will no longer have the navdata for smaller airports like this?

Hi,

In the navdata cycle currently available in MSFS2024 tower frequencies that are not 24h were often marked as CTAFs, as they have the CTAF flag in source data. This will be changed in the next update as we decided it’s better to err on the side of having a tower frequency.

KASH has no SIDs nor STARs from the FAA; it does have some approaches and those are present in the sim. If they disappear when your package is installed, make sure you aren’t using the deleteAirport flag, as this will delete the airport coming from the base data with all the navdata attached to it rather than merging with it. Also double-check that the lat/lon for the airport match the base sim data.


Thanks for the response. Matt gave a more detailed explanation of the CTAF issue, and it makes sense what the problem is. Hopefully you can all fix it.

I was looking in the wrong place for the approach charts, they are there. I think part of the problem is I think there’s a bug in the Carenado 530 Garmins in activating approaches. Either that or I was doing something wrong again.