I’m quite sure it’s a matter of time and they’ll fix everything (hope soon).
It turns out they decided to ignore airports with part time towers. The comment being they have a CTAF frequency. Interestingly, almost all airports have a CTAF frequency when they’re towered, so that response is confusing to me. It’s also confusing me because the tower was still missing when I included my 2020 airport, which I know deletes the frequencies and adds them back in again. So the Tower frequency is definitely defined. I’m not sure yet why 2024 is ignoring it.
ARINC-424 data does not contain any airport layout information whatsoever other than runways. Additionally, in Flight Simulator (going back as far as I can recall, certainly even earlier than FSX) runways aren’t quite in the navdata, they’re actually part of the scenery itself. So that presents a challenge in that you can’t just overwrite the scenery with ARINC-424 gross runway data. This is an area that WorldHub is intended to address, as was the case with the equivalent in XPlane (for the same reasons).
There is a bug in the current cycle where A-424 frequency entries which have the same frequency at a given airport for CTAF and Tower (or CTAF with a tower flag) are getting CTAF only. It’s a tricky situation because technically both are true; but for many of these airports the reason is that they are towered during the day but CTAF only at night. We anticipate a potential fix for this in the next cycle update to favor tower, which we presently are targeting for one of the announced upcoming patches in the next week or so.
However, I see procedures just fine in the EFB procedure selection for that airport. If you are looking specifically for approach charts, be advised that for some airports the approaches are listed under ALL instead of the specific runways, as FAA charts data does not contain runway relations for procedures at all; instead we have to manually parse the chart titles to attempt to match them to runways. There are some cases which we are still finding, and new cases emerging as new titles show up and/or get renamed.
All FAA charts that were in the cycle are included. Our inclusion of FAA charts is not related or based on LIDO coverage.
This is not the case. LIDO A-424 data is not related at all to their chart coverage. The data is worldwide coverage sourced from state and aerodrome AIPs, has no limitations based on approach aircraft class, and is extremely complete. The FAA data is also used in its entirely to fill in any gaps, and is, again, not based on what LIDO’s coverage is.
Ome thing to keep in mind is that, for airport scenery with runways that don’t match the A-424 runway layout data, there may be procedures dropped, as was previously the case.
Hope that all helps,
Matt
3 Likes
That does help. Thanks so much Matt. You helped me figure out how to use the EFB to find the charts, I was doing it wrong. I also got a similar response at DevSupport, but this makes much more sense, and explains why the Tower doesn’t exist even though it’s defined.
I hope the bug gets fixed. It seems like if the airport has a Ground Control frequency, the CTAF/Tower confusion issue is a non-issue, and a Tower frequency should be created based on the definition. But you’re right that KASH is only towered 7-9pm 7 days a week.
It is weird that KKIC is a controlled airport in the sim, however, as the FAA data only has CTAF.
Is this why KFIT is not available for use in Careers, since it’s AIRINC data doesn’t match FS’s current airport configuration (Runway 2-20 was closed several years ago) ?
KFIT has a couple of flight schools on it (and is going to be my home airport soon). I thought it was interesting that KFIT wasn’t available for careers, but 2B2 was, even though KFIT is small jet capable, and 2B2 is a really teeny airport with pretty short runways.
1 Like
I flew the C152 from KSBP to KSBA this morning and noted issues at each airport.
Both are towered.
Leaving KSBP I tune 120.600 for ground and 124.000 for tower at take off. In 2024, there is no 124.00. At the hold short, I had to request take off clearance from the same 120.600 ground frequency.
On approach to KSBA, I tuned to 121.700 for tower, when it is meant to be 119.700. 121.700 is ground there. After landing I was told by 121.700 to contact ground on 121.700, when I was already tuned to it.
In both cases, the correct CTAF frequency was unavailable and I did all tower communications on the ground frequency.
There is definitely something wrong with the way the nav data is being interpreted in 2024.
I have a Navigraph sub, but haven’t tried their beta 2024 implementation, yet. I’m wondering if I will see these issues if I do.
And im getting Center frequencies for towered airports such as RPLL and RPVB.
1 Like