Last night I was flying an IFR flight from KATL to KTLL (Tallahassee). Was in low clouds, and was vectored for visual approach to runway 9 (which wasn't ILS equipped.) ATC says to descend to 2300 and "report runway in site". At 2300, I was still in the clouds. Anyway, this was an IFR flight, yet I was vectored for a VFR landing when runway 21 and another were equipped for ILS. Basically, I couldn't see the runway that I was directed to until I was on top of it, which was too late to make a safe landing. Will RC3 handle this more appropriately? And, BTW, how would this be handled in real world? Would you be directed to another runway for an IFR landing even if that runway was going against the wind, for example?thx,John

John,In minimum conditions, you would not be vectored for a visual landing. You would be vectored for an ILS runway. RC should have done this as it will always give you the ILS runway. Did you request 9 instead?

rc will always give you an ils equipped runway first. same for version 3. but in version 3 you have several more types of approaches you can requestin this case, for version 2.2, declare missed approach, get vectored back around, and request the ils equipped runwayin version 3, you declare missed approach, stay at this airport and try again, either asking to be held as published, you can ask for delay vectors, you can request vectors back into the pattern, or ask to go to any one of 3 other airports (2 alternates, and your original departure airport)

Oops, minor detail left out: my situation was in using FS02 ATC, not RC2. This answer my question though. Thanks.

Thanks. Looking forward to v3.

minor detail :-lolyes, 2.2 does a better job than fs02 atc, and v3 will knock your socks off