Hoi JD,I love RC3 and fly mostly not without it. I run the latest beta 3.01So, my little problem is that when I have had to select and call missed approach, I take vectors and get vectored to the point where I get handeled to approach control. He gives me the same wrong runway I got first time. First time I changed the runway, 'cause FS2k2 ATIS told me the other one. Well, RC3 seems not to remember my change of runway. I had to change it all again. And that by flying a B733, not a single prop GA. Why is it often that RC3 gets the wrong runway and not the one FS2k2 ATC gets by listening to ActiveSky? FS2k2 is very correct with every Airport, 'cause ActiveSky tells the correct one. But RC3 doest care. Will you look into this for the upcoming update?ThanxTorben.

i believe that if you request a specific approach for a specific runways (ndb rwy18) for instance, and then miss, and take vectors, you will get the ndb rwy18 the second time.if you just request a different runway, and then miss, rc uses the same runway it originally gave you, which to me makes sense. rc doesn't know why you changed the runway.if this is a huge issue, and everybody thinks it needs to be changed, and more importantly if doug/larry think it is important, then i'll change it.

I have no problem with the change so long as it wouldn't ball up a dozen other things in doing so.

I reported this a month back, so it's good to see another user confirm that the runway selection on missed approach works the same as I reported.My choice would be to give the user the same runway as selected by the user and not what RC issued originally. The user is going to have a specific reason for choosing another runway, so why not stick with that selection? If it would mess up other code, then it may not be worth it, but by all means, let the user have the final say in the runway selection.Bruce

Yo Doug,How would this be handled in the real world?Sidney Schwartz [KPDX]MyTraffic/Radar Contact/FSMeteo/FSSE/FSassist/FDC