We're still not together guys :-))) I'm probably not explaining this right so hang in there with me just a bit longer :-))

 

Here's the exact picture;

I'm sitting STATIONARY at the run up area for runway 9 at KILG. I'm in the A2A civilian P51 Mustang.

Behind me about 1/2/ mile on taxiway K sits a Cessna Caravan.

I'm on 121.7 having not yet gone to 126.0 for a takeoff clearance. I'm listening and watching the ATC tape as ATC speaks to the STATIONARY Caravan in a single continious voice.

"Cessna so in so, use caution for the Mustang on the taxiway. Cessna so in so resume taxiing. Cessna so in so, use caution for the Mustang on the taxiway. Cessna so in so resume taxiing. There is NO HESITATION between these ATC instructions to the Cessna. He sits. They just keep these alternating instructions going out to him.

The Caravan doesn't move during all this. If I didn't change frequency to 126.0, this loop would continue on indifinately without stopping. I actually let it go on about 10 times watching it print out each line as ATC spoke.

Something is obviously stuck causing this audio loop. I'm just wondering if I can do anything to reset ATC back into a normal routine.

Don't worry if there isn't a quick answer to this as I understand it might be a complex issue. I just thought I'd throw it out here in the hope someone might have experienced this and found out what was causing it.

DH

 

There is one thing that can be done about it, but there is a downside. I can mod the Phraseology to mute the voice, so you won't hear it anymore, but the downside is it will do the same when the call is legitimate. (ie AI crossing in front of you) Also because the call requires a response, you'll get the text message but not the audio when the call is directed at you. You'll have to respond, again with text only. Let me know if you want me to make such a modification?

Thanks. I think I'll leave well enough alone with this one. It's no big deal really. Just unusual and something new popping up in FSX that I thought might have an answer out here somewhere.

It's probably something conflicting somewhere deep in the code. Not a deal killer :-))

Thanks everybody who took an interest in the post and Happy New Year to everyone.

DH