I have done several flights using your IFR plan and something isn't right. I have tried several different aircraft, not just Captain Sim aircraft, and they ALL have the same problem. This leads me to believe that it's an FSX error. The heading, for example, from MSP (115.30) to DWN (109.00) in  the flight plans is 282^o. But if I set the VOR radial to 282^o, I wind up nearly 5nm off course. This means that the ATC is always telling me to change my heading so that I capture the track displayed on the GPS and not the radial to the VOR. I can follow the VOR radial if I set it to 275^o.

Mark

boeing247 wrote on May 16^th, 2011 at 3:29am:

What did you use to create the flight? The default FS Flight Planner or some other program?

I created the same flight with Flight Sim Commander 9 and using the latest AIRAC (1105) and the problem remains. So I still say that it is a fault/bug in FSX.

Mark

boeing247 wrote on May 14^th, 2011 at 3:50pm:


I tried a little experiment last night with the ATC vectoring me into Newark Liberty (KEWR) flying ILS for 22R about 54 miles out and followed the ATC intructions. Once instructed to contact KJFK, I was vectored towards the East Coast approaching McGuire AFB.  Just in case I set up my radios to intercept a VOR south of KEWR.  Continuing east on a heading of 63 degrees ended up 50 miles over the ocean and almost 98 miles south of KEWR. I simply contacted the tower and requested a different runway. They gave me 22L straight in a new vector directly.  Seems as though the ATC forgot about me for awhile.  Good news though, getting good at ILS aproaches with this old pig.

The problem has come back, but this time with a different VOR station. 

I haven't had time to check, but I was flying a payware prop a week or two ago, and it was giving me trouble with other VORs. Almost every VOR I've found has given me a route that's up to two nautical miles off the GPS.