I was all ready for a nice flight tonight, Albany, NY to Dulles in an Indedpendence Air CRJ. Shortly after take-off, ATC vectored me to heading 190 and that was the last vector I ever got from them. I got all the altitude changes, all the hand-offs, but never got turned. I expected a turn to the southwest before Newark, but I just kept trucking along nearly due south, out over the ocean.I tried switching to GPS mode, but they told me to return to 190. Got all the way to Virginia Beach and, in desperation, turned 270. "Please expedite your turn to 190." Ok, back to 190. Got as far south as Myrtle Beach, SC but way out to sea. Finally, when they told me to contact New York center, I knew things were gone amok and I quit the flight. Fortunately this is rare but it's frustrating nonetheless.Jim

I had the same problem some time ago. I also got all hand-offs, but no new vectors. Finally, I cancelled the flight. :-(Yesterday, I enjoyed a very short flight from Innsbruck (LOWI) to Salzburg (LOWS), and everything was quite fine. But then, some five miles off the runway, ATC told me to descend by 8000 ft... I once read that the FS9 ATC has some problems with "steep" approaches. Obviousely, it's not yet perfect...Greetings,Holger

>I was all ready for a nice flight tonight, Albany, NY to>Dulles in an Indedpendence Air CRJ. Shortly after take-off,>ATC vectored me to heading 190 and that was the last vector I>ever got from them. I got all the altitude changes, all the>hand-offs, but never got turned. I expected a turn to the>southwest before Newark, but I just kept trucking along nearly>due south, out over the ocean.>>I tried switching to GPS mode, but they told me to return to>190. Got all the way to Virginia Beach and, in desperation,>turned 270. "Please expedite your turn to 190." Ok, back to>190. Got as far south as Myrtle Beach, SC but way out to sea.> Finally, when they told me to contact New York center, I knew>things were gone amok and I quit the flight. >>Fortunately this is rare but it's frustrating nonetheless.>>Jim>If you have this happen again, try cancelling IFR and then reopen your flight plan again , and see if this straightens it out.

I found that what you need to do is ignore the vector, contine to your next fix on your flight plan. Once within a few miles of the fix bring up ATC, choose option 2 to request a new destination. It will send you to the flight planning screen. Reload your flight plan(it should be saved) for teh origianl destination. ATC will give you clearance to your "new" destination as filed, and since you are so close to a fix on the flight plan, they just vector you toward that fix (which you are already heading) and tell you proceed under your own navigation. usually teh flight goes well after that...rinse and repeat if you have the same problem later on in the flight.Just remember to request the "new" destination within a few miles of the next fix.

Hi Jim,I'll bet that if you check your flight plan you'll find that the first fix is very near the departure airport; it is likely a VOR and it is likely on a heading of about 190 degrees from the airport. If it is so near the airport that you can't turn quickly enough to hit that first waypoint, then ATC seems to get confused. They seem to think that all you have to do is fly that initial heading (190) and sooner or later you'll get to the waypoint.I just delete the first waypoint if it is close to the airport. Try it. R-

Hmmm, I have to check that out. Its possible I had that issue when the first fix was the VOR colocated at the airport. Deleting that VOR fix may be another option for me also.

If I get too far off, will cancel the IFR flight, then reload it enroute, and call ATC. You sometimes can have a glitch in memory which can corrupt the flightplan. It seems to happen mostly after running certain programs before loading FS. Since I began using FSautostart, this stopped happening. It removes all unneeded programs, and defrags memory before loading the FS.

I had a related problem yesterday on approach. ATC never lost track of me, but instead vectored me and didn't turn me for final until I was 45 nm, (!) past the airport. Talk about a loooonnng final :-) Anybody using the beta for Radar Contact? I'm hoping when the final version comes out this month it will sovle some of these issues. Mike