Here’s a real obscure issue. The real world KFHR (Friday Harbor, WA) has a CTAF frequency of 128.25. In MSFS 2024, Navigraph lists that frequency as type MULTICOM. I was under the impression that there is only one MULTICOM frequency for the entire US, 122.9, which is used when there is no Tower frequency and no site-specific CTAF frequency. Shouldn’t 128.25 be listed as CTAF? Or am I wrong?
Thanks for raising this. We’re investigating.
Hi,
I have checked the database, and yes, the communication type is MULTICOM, but the service indicator is CTAF. I must look more deeply into the code and the SDK to determine whether I can use this additional information in MSFS. Please give me a little bit of time - I will check it!
Thanks for the hint,
Richard
No problem. Another developer pointed this out to me. Here’s the appropriate section of the AIM for what it’s worth:
Hi,
Thanks for the additional information. We have found a way to interpret such multicom frequencies correctly.
We must do some tests today to confirm that this fix works everywhere. After that, we will release a 2nd revision to distribute this fix and get global confirmation that it is fixed… but it looks good. Just an short update.
Thanks again for the time & hint
Richard
Hi again,
We have just uploaded revision 2 for MSFS2020 and MSFS2024. We have now slightly fixed the logic. When the frequency type is MULTICOM, and the indicator defines it as CTAF, we use CTAF, not MULTICOM, as the frequency type.
Here is the result with AIRAC 2607 rev. 2 with your KFHR example (but the fix is a general one and not only limited to this airport):
Hope that helps 
Enjoy your Sunday!
Cheers,
Richard
Thanks, I will pass this information along to the developer who raised the issue with me.