MSFS(2024) ATC ignores all 8.33 kHz frequencies (e.g. 135.155 MHz) – falls back to 122.900 MHz

Bug Reporting Hub ATC, Traffic & NAVAIDs
, , , , ,
1

:small_airplane: Problem:

Since one of the recent Sim Updates, MSFS completely ignores all 8.33 kHz radio frequencies used at many airports in Europe (e.g. 135.155 MHz).
Instead of using the correct frequency for ATC or traffic, the sim falls back to 122.900 MHz, which results in:

  • Wrong ATC frequency being active
  • Hearing all traffic from nearby uncontrolled airports
  • Inability to manually tune to the correct COM frequency
  • Complete break of realism for local VFR traffic in Europe

:magnifying_glass_tilted_left: Example:

At EDKB (Bonn Hangelar, Germany) the correct tower frequency is 135.155 MHz (as per Navigraph, DFS, ICAO).

  • The World Map in MSFS shows the correct frequency (135.155)
  • But in-game ATC only gives 122.900 MHz
  • Manual COM input skips 135.155 (jumps from 135.150 to 135.175)
  • ATC and AI traffic all talk on 122.900

:repeat_button: Tested Troubleshooting:

  • Cleared content.xml :white_check_mark:
  • Deleted SceneryIndexes :white_check_mark:
  • Fresh install of AIRAC cycle via Navigraph Hub :white_check_mark:
  • Clean Community folder :white_check_mark:
  • Custom frequency mod to override EDKB COM1 → still fails :cross_mark:
  • MSFS just won’t allow 8.33 kHz frequency activation

:paperclip: Related thread (too specific):

EDKB Frequency bug: ATC always 122.900 ← (insert your real link here)

That thread shows the problem, but it’s not just EDKB – many airfields across Europe use 8.33 kHz, and they’re all affected.

:warning: Why this matters:

Since 2018, 8.33 kHz spacing is mandatory in most of Europe.
If MSFS can’t handle it:

  • ATC is unreliable in huge parts of the world
  • VATSIM and other realistic networks are impacted
  • Every local VFR airport suffers from broken communication

:white_check_mark: Request:

Please implement full support for 8.33 kHz radio frequencies in:

  • ATC logic
  • Aircraft radio tuning (manual entry)
  • World map + COM selection + scenery parsing

Even just rounding the frequency to the nearest supported 25 kHz value in logic (e.g. 135.155 → 135.150) would be better than fallback to 122.900.

:pilot: Please vote if this affects you too.
It’s a core realism issue for every serious VFR pilot in Europe.

Thanks!

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?
•

Provide extra information to complete the original description of the issue:
•

If relevant, provide additional screenshots/video:
•

2

Do you have the same issue if you follow the OP’s steps to reproduce it?
• yes

Provide extra information to complete the original description of the issue:
• base sim (no AIRAC cycle via Navigraph Hub installed)
In my case, I have the issue when only 1 FSS frequency is available on the world map
Example LSZM
World-Map lists FSS 134.830 MHz (correct IRL frequency for that airport)
Once in flight and the com panel opened, a frequency of 127.850 MHz is listed at the top (don’t know where it comes from) and the only frequency that can be selected is 122.900 MHz
Once 122.900 MHz is selected, runway list for landing is empty

If relevant, provide additional screenshots/video:
•

Screenshot (1217)
Screenshot (1217)1914×939 288 KB

Screenshot (1218)
Screenshot (1218)1916×1032 160 KB

Screenshot (1219)
Screenshot (1219)1914×1027 157 KB
3

Good evening,

Here’s my experience on subj with the SR22 aircraft.

With 8.33 Khz channel spacing mode selected in the MFD, manual entries via the COMM rotary knobs work as advertised BUT the center console alphanumeric keyboard entries DO NOT WORK properly.

Example: CYOW (Ottawa) Departure is 128.175 and the only way to enter this frequency is via the COMM stacked rotary knobs. The SR22 alphanumeric keypad has a bug; you cannot enter the last digit xxx.xx5.

It appears that all previous 25Khz frequencies ending in xxx.xx5 have not been “converted/Coded”? properly to the 8.33 Khz channel spacing (118.075, 118.125, 118.175, 118.225, etc.) in the sim by MS/AS or by third party Working Title Simulations.

I am unsure if this a G1000 specific issue or something else…?

Screenshot 2025-10-22 235231
Screenshot 2025-10-22 235231860×1324 117 KB
5

Pertaining to EDKB above, it’s still not 135.155…

As of 23 Oct 2025, MS24 Beta 4 - ATC panel provides “Tune EDKB Traffic on 123.525”.

If you select this freq the menu selection to announce taxi, takeoff, etc.. appears.

Did you enter this Airport specific bug in the Forum?

Cheers.

6

seems like not enough people are even aware this problem (it is crucial to me) exists so I dont think it will ever be fixed. Its sad ms/Asobo do not care about realistic simulation. As real as it gets. Yeah

1 Like