Hello, while using Beyond ATC, I noticed that the tower frequency at ENZV is wrong. In msfs ( with navigraph) there are two tower frequencies (118.350 AND 122.100) while in all charts and AIP there is only 118.350.
Hopefully this is an easy fix, have a good weekend!
Proof in the form of in game freq, Chart and AIP.
Nevertheless, as you see in the remark, that it’s a monitoring frequency. Thus it should be removed.
Also, as you can see from the screenshot I posted initially from t AIP 2.18, the frequency has been removed. Your screenshot is outdated I’m guessing?
Edit:
Here it is:
https://ais.avinor.no/no/AIP/View/133/2024-09-05-AIRAC/html/eAIP/EN-AD-2.ENZV-en-GB.html#ENZV-AD-2.18
… but also here, you have two tower frequencies, but with another frequency.
I assume, this TWR monitor frequency (122.100) will be removed and the new frequency (121.500) will be added within one of the next cycles, I expect it in 2412 latest. The current changes are from 5th of September 2024.
Hope that helps
Richard
I appreciate it, I would argue that 121.500 is the emergency frequency all towers monitor, and I do not think it would work as intended in the sim, while not being noticable if it was not present.
As you can see in the Norwegian AIP, all other towers in Norway have this frequency listed, even ENHD which in real life would interfere with ENZV if they actually used it, because of the close proximity.
Hope you take this into consideration before adding any other tower frequency than 118.350 
Really appreciate the work and quick response (even on a Friday!!!)
(Edit: wording)
The problem is, in the sim data I don’t have the possibility to “flag” frequencies, which are special. I’m very limited here. So in other words, when its a TWR frequency (and there is no visible information in the AIP that this frequency is only for emergency), than I must export it as TWR frequency.
BATC has decided to use the in-game data format and this format limits us. We must use it as it is. Say Intentions as an example, they use an external format and here we have all possibilities and can decide with the developer directly how we can handle such situation in the best way.
I assume, you will also see two TWR frequencies in the future and BATC should look how they can handle this.
Cheers
Richard
All aerodromes with towers have 121.500MHz listed as a frequency (at least in all of Norway and in all other EASA countries. Wouldn’t it be very extensive work to implement this frequency to ALL towers, I’m sure there is a reason it hasn’t already been done, and I think it would be odd to only implement it at ENZV
It doesn’t say anything about it in the AIP, because it comes from a higher level. As stated in ICAO 5.2.2.1.3: Aeronautical stations shall maintain a continuous listening watch on VHF emergency channel 121.5MHz during hours of service of units at which it is installed.
The AIPs are the source for the data-provider - but I have checked all other Norway airports and there are no 121.500 frequency included. So, this possible emergency frequency is not included in any Norwegian airport. So, I assume, it will be same at ENZV released in any upcoming cycles … only one TWR frequency 118.350 at this airport will be shown.
Cheers,
Richard
Then we’re on the same page 
Have a great weekend!
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
