Guys I was searching for a solution to a problem that has bugged me for ages which was breakthrough of the Maroochydore ATIS on to the Bribane ATC approach freq, which meant I could not respond as the ATIS breakthrough conflicted with my attempts to respond using the ATC menu keys (double transmitting=hash) and as I have voicepack installed with fast voices it always happens to quick to do anything about. This always resulted in the vectors and plan being cancelled on the final intercept vector for the RWY 19 ILS at YBBN. End result out over the ocean for awhile, reload the flight plan, get the clearance and then back over the top for more vectors for the ILS, which is frankly interesting but a pain. This used to repeatedly happen with the 727 as well as the 707. I would dread going to YBBN with this problem ongoing and would pray for a RWY01 approach not the 19 approach from the south.

Seems that your earlier discussion: http://www.captainsim.org/yabb2/YaBB.pl?num=1309352775

re com radio settings is the fix. Silly me for not paying much attention to the switch settings here.

MarkOz - yep I have exactly the same problem. IN the 707 or 727 Using the com switches is interesting at BN because if I manually select the ATIS on 125.5 I get no voice but if I select it from the ATC menu I get voice but it seems nothing will stop the overlap of CTL on 119.8 and the Maroochydore ATIS being on 119.8 as well and that is correct in terms of the frequencies.

The 119.8 frequency for control and it being the Maroochy ATIS as well issue drives me nuts as well. Not sure what causes it but I suspect that there is something amiss in the scenery reference files (possibly FSX default and the frequencies in that area. In real life breakthrough is possible when two same frequencies are reasonably close together and at altitude you hear both but down low nothing. Reloading ORBX has not done anything to fix the problem not sure if there is a patch or navaid/radio frequency file somewhere that could be put into FSX, there used to be but I have not seen one that I would trust for FSX yet.

I don't have a clue how FSX handles or sets radio frequency ranges but I guess there is a default setting somewhere in the files. I note that with NDBs (ADF) for instance all the distances are the equivalent to low frequency set ups (no more than about 40 nm range) but in real life some are good for hundreds of miles (Sydney, Perth and Townsville) were all 200-400 nm ranges (to help the international flights inbound to OZ) but not in FSX, love to be able to change it but as I said beyond me.

Yep, I agree completely ruins using BN IFR in FSX. The problem is that you cannot get rid of it because the wav  loop for the ATIS runs in such a way that there is a mismatch or overlap between the CTL wav file and the ATIS wav file so that you cannot respond. I have found that if you change the com frequency immediately it gets rid of the problem but leaves you with another problem, your IFR plan is cancelled automatically and so then I head out over the ocean for a bit do the submit the plan and req clearance then request an ILS via overhead which seems to get you back in. That being said there is something weird about the way the ATC and other frequencies are set up for BN. For example on taxy you cannot select tower until you at the threshold no matter what even though in real life you would go to twr approaching the threshold, especially  on a long run taxyway with no intersection. Very frustrating somedays. The end result is that I have been avoiding flights that go into or out of BN unless you come in from the north, that seems to work ok (sometimes).

Let us know how you go with the flight following VFR flight.

same problem with papua new guinea, port morseby, jacksons int. atis overlaps tower.
looks like its not the only 2 ports with that problem.

MarkOz and Windplayer, ditto the Port Moresby overlap, discovered that taking the 707 in there the other day. Found it could be managed by just ignoring the ATIS land then bring up the ground freq. Very annoying though!. I am doing some research but no answers yet.