I've been trying to no avail to fly a route from KATL to KMSY. It seems ATC doesn't want to direct me to the route. I made up the flight plan in FS's default flight planner. Using PMDG's 737NG I punched in the same plan into the FMC. Once I takeoff ATC will direct me to say 210 degrees and that's it. ATC never directs me to the proper heading to intercept the route. If it weren't for the FMC showing how far off course I'm flying, I would never know there's something screwing up (I

I've had it out of seattle before a couple of times. I do all of my flying on Vatsim now though - actual people controlling you is far better www.vatsim.net

Ill give it a try with a FS Navigator filed flight plan and see what happens. As far as MSY what approach or you accepting or are you asking for a special one. Are you using any SIDS or STARS. Those will surely make you think ATC has gone bonkers, especially ot of Atlanta. Just as in real life Atlanta is so busy they route you all over the place.Jim

Hi Dillon,You can probably fix the problem by deleting the first waypoint; it is likely too close to the airport (KATL). If the first waypoint is so near the departure airport that you can't turn quickly enough to cross it, then you'll never get the "resume own navigation" message.Further, I'll bet that the heading (in the KATL - KMSY route) from KATL to the first waypoint is 210*. So 210 is all that MSFS ATC knows, at that point, and they just assume that if you fly 210* forever, you'll eventually get to your first waypoint and thus get to your route. Given that, you can also ignore the heading given you by ATC (210*) and just fly to the first waypoint. They won't scold you and you'll get a RON message when you get there.R-

Hey Jim thanks... I use no STARS on approach; I just let ATC clear me to the default active. It just clears me in the wrong direction of where I should be to intercept the ILS for the active runway...

ATC always tell me "resume own navigation" and I follow my own flight plan, as long as I don't deviate from the plan too much they tend to leave me alone.XP Home SP2Asus P4P800-SE Intel 3.0GHZDDR 400 D/C 2x512MBLeadtek 6800GT 256MB (71.84)SB AudigyMSFF2 & X45 throttleSee you in the fence...CYYZ

Ron you hit the nail on the head!!! :-jumpy You are very right here... It seems if the starting waypoint is too close to the airport, ATC screws up. Same goes for landing. Both starting and ending waypoints were too close the airports causing major problems. Thanks so much for the tip, I'm sure others will find this info helpful as well...

You can probably fix the problem by deleting the first waypoint; it is likely too close to the airport (KATL). Bingo.Thats always been the problem when I've seen that...IE: I fly out of KHOU a lot...If you plan out of there, your first waypoint will be the HOU VOR which is on the airport...:( I've also had this problem out of Dallas LoveI think, and maybe St. Louis Lambert..???? Forgot...Anyway, I just delete the first waypoint, if it's real close to the airport...What will happen is you need to make a U turn, but if a jet, you are usually a bit fast to make the turn, and keep on course. Then , you miss the first waypoint, and all goes goofy from there, unless you turn again, to recatch that first waypoint...:( I think I did three circles in one town before I finally got heading the right direction...I think thatwas outa Dallas Love one night....So, yea, I also gotta delete the first waypoints, "probably cowboy VOR", when I leave the big Din my pseudo Southwest 737's...I've gotten in the habit of checkingfor any close ones, every time I file a flight now... MK

I had the same problem on a FP from KDEN to PHNL. HOWEVER, my first waypoint was about 50 miles from the end of the runway on a heading of about 275. ATC vectored me on a slight NNW heading which I eventually ignored and turned toward the waypoint on my own.ATC kept telling me to turn back to the previous heading about about 5 minutes and eventually as I got closer to the waypoint they shut up and handed me off to another DEN CTR controller. The new DEN CTR controller gave me the right heading and released me to resume on now.I think that inherently that there is a *bug* in the FS9 ATC that rares itself at random times. In my case the fist waypoint wasn't too close, and ATC just got a little confused but then had no problems for the rest of the 2200 mile flight so who knows.I used to utilize VATSIM religiously in the past and it does at a great amount of realism vs the default FS9 ATC...BUT...the fact that all AI traffic is gone (e.g. empty airports), limited ATC facilities leaving larges gaps between ATC controllers, and often contacting Center for clearance delivery from large airports killed a little of it for me. Regards,Mike T.

I just tune ATC to hear the great AI chatter that I spent days putting in from peoples great flight plans. I create a flight plan and follow it but would rather not hear the bug ridden ATC try to pathetically direct me. And I agree about online flying, empty airports are boring!

"I used to utilize VATSIM religiously in the past and it does at a great amount of realism vs the default FS9 ATC...BUT...the fact that all AI traffic is gone (e.g. empty airports), limited ATC facilities leaving larges gaps between ATC controllers, and often contacting Center for clearance delivery from large airports killed a little of it for me."This is the exact same reason I could never get into VATSIM nor Radar Contact (although RC is not online, it doesn't work with FS9's AI system)...And I thought it was just me... :-lol