Hi Bill,I had already tried that. It works fine in FSX and like I stated, I can't even control the plane with the keyboard or mouse.Being behind the plane when it is flying, I can see the ailerons fluttering and mostly in a right bank configuration. I had previously posted that the plane does a sharp bank to the left when I meant to say to the right. Senior moment.What is so confusing is that it worked ok right after the original download. It was only after I had gone to the options menu and tried to assign the axis to my yoke that the problem occurred. Going back to the default selections didn't correct it back.Jim

I just went so far a disconnecting the yoke to see if I could fly with the mouse or keyboard. Same results. I installed the game on my other computer and it works fine. Even copied the cfg from the good computer and replaced the bad computer cfg. Same results.Again I removed Flight and every folder associated with it. Reinstalled Same results.This does not make any sense to me at all. What is keeping me from controling the plane? It does the exact thing every time. Sharp bank to the left and nose dive into Hawaii turf. Getting desparate here.Jim

I assume you have also deleted the following folder before the reinstall?..UsersYourUserNameAppDataLocalMicrosoftFlight

Yeah, I deleted that one too.Jim

Man that is just too wierd.Gotta be an explanation and a resolution in there somewhere, hope you can find it soon!

Make sure you don't have two controllers mapped to the same axis. E.g Saitek X-52 X axis and CH Pro Pedals Z axis both mapped to ailerons. I'm not sure if this possible in Flight, but when this happens in other sims - the effect is exactly what you describe. The two controllers 'fight' each other for control of the same axis and mayhem ensues.

deltatango, you are the man. Some of the flight control axis were also assigned to my Ch Throttle Quadrant. There was a definite conflict that caused my problem. Don't know if I inadvertantly did that while trying to assigned the axis in the first place, but I'm willing to bet I did. A classic case of operator error. Thanks a bunch for your advice on this.Jim

Fantastic planenut, glad you finally got it sorted out!You da man deltatango!