August 9, 201114 yr Hey guys minor issue. I was flying from YYC to YOW and was level at cruise altitude. All of a sudden a wind came up and the A/P Disengaged causing the plane to begin spinning to the ground. i did save it and level off. But CMD1 would not re-engage. I tried CMD2 and it did re-engage. Was just wondering if it's a pilot error(most likely lol) or a minor glitch. Anyways its a great product and love using it!! Great job PMDG!! Brad Cherrington [email protected] CYYC Based
August 9, 201114 yr Something similar happened to me. When I checked the failures page in the CDU it said that CMD A had failed, so I bet this happened to you also. Greg Hetherington
August 9, 201114 yr Author As i read your reply the master warning sound came from the other room. Came back to find the plane planted into the Ontario soil lol. Is there anything i could do to prevent this from happening in the future. Thanks for the help! Brad Cherrington [email protected] CYYC Based
August 9, 201114 yr There is a condition where the FCC would fail if you yank the wheel badly (manual says more than 110 lbs control force on the real deal), rendering the respective AP INOP for the remainder of flight (in fact so long as to next maintenance, obviously). So I might assume eventual control spikes from hardware controls might trigger that event, because it is modelled. If you want to try it out on purpose, just pull back hard for example during automatic flight. But you really have to pull back hard to really break it, otherwise you'll only disconnect the autopilot.
August 9, 201114 yr Author Thank you! That does make sense. It is amazing that they can actually model so much detail its really cool!! I might just turn winds aloft off. Cause it does say in the introduction to turn that kind of default fsx weather stuff off. I appreciate your response i was really having trouble with it. I will play around with it. Brad Cherrington [email protected] CYYC Based
Create an account or sign in to comment