Quite often after takeoff, I will be given a heading by ATC which either crosses over my planned flightpath, or turns in a direction which is away and would not ever intercept the planned flight path. In these occurances, I never get the usual instruction to turn to another heading somewhat matching my planned heading along with "Resume Own Navigation".
There are other times when the ATC instructed heading pretty well matches my flight path to the first waypoint, I can engage my AP, and the flight continues with no problem or ATC instruction that seems out of order, although I never get the "Resume own navigation" instruction.
If I obey the ATC instruction for the bogus heading, I continue on that heading indefinitely and soon also receive ATC informing me that I am X miles off of my flight path, however, no correction heading is ever given, continuing on to oblivion.
If I ignore the ATC instruction for the bogus heading and fly my planned flight path, then request vectors, ATC informs me that I am on the flight path, and I can continue the flight with no problems to my destination (with periodical instruction to turn to the same bogus heading far off of my flight path).
With the exact same planned flightplan, conditions, and setup, I can often just pause, move my aircraft back to my origin airport, start over and all ATC is logical and as planned. At other times, I have restarted the computer and started over from scratch and everything worked just fine.
Anyone know my mistake, or have any ideas?
Thanks:
RTH
I experience the same issue that lead me to stop using PFE. Added to that, when I get the files compiled and I check the brf file, It contains centers that shouldn't be contacted by far : For instance on a flight between two airports in France I have to expect to contact Copenhagen control or Birmingham control. 