I am probably doing something wrong but after LOC capture and i hit APP, then CMD 'B', i suddenly realize i am wandering off my approach and glide slope. On glancing over at my CMD buttons, they are off and my FD indicates that i have no autopilot on (i.e. No green 'CMD' or yellow CH1, just FD).

I am assuming it is my F.O. doing this.

Any ideas as to what i'm doing wrong?

Hi Rick,

 

FO's not turning anything off unless you're commanding him.

 

Check your speech log to see if maybe some uncommanded commands were heard by the system.

 

Chers,

Bryan. Do i have a problem here?

 

Edit: And i've done a search, but can't find.

Hi Rick,

 

Not sure, try re-installing FS2Crew.

Bryan. Is that file folder created on initial install of Fs2Crew?

Update. Reinstalled Fs2Crew and now have a CVR log. Ran a quick preflight and start routine and then checked log to see that it is recording and everything is recorded exactly as i said. Had to shut down because sleep calls. However, i did notice something that i may have missed. In the brief panel APP TYPE = (FAIL OPP) My settup in my MCP is set at (FAIL PASS), so if my briefing panel is not set to the same, could this cause my ils approach problems?

Will try a short flight tomorrow an see.

Regards,

Update. Reinstalled Fs2Crew and now have a CVR log. Ran a quick preflight and start routine and then checked log to see that it is recording and everything is recorded exactly as i said. Had to shut down because sleep calls. However, i did notice something that i may have missed. In the brief panel APP TYPE = (FAIL OPP) My settup in my MCP is set at (FAIL PASS), so if my briefing panel is not set to the same, could this cause my ils approach problems?

Will try a short flight tomorrow an see.

Regards,

 

Hi Rick,

 

I don't think that could be the cause of the problem, there is a "fail pass" option as well, could it be joystick noise that caused it to "kick" off the autopilot ?