I had it at 2:10:11, but whatever...
You can't keep bashing away at this, the data is there. The A/P commanded nothing untoward, the pitch-down and roll was induced by turbulence and the climb was as a result of sidestick input.
The *very* start of the PF's sidestick trace is unfortunately obscured by the data points of the PNF's sidestick trace. The "zipper" could be many things - I suspect it's wonky data (it looks too uniform to me to be anything else), but, for the sake of argument it could alternatively be pitch corrections made by the autopilot in MANAGED mode to maintain assigned altitude in turbulence. In any case, the vertical speed and altitude traces show that there is no major deviation from assigned altitude during the time it is happening, and even *if* the autoflight was commanding one of these corrections when it tripped out (which doesn't tie in with the trace - at 2:10:05, it's commanding 0 ft/sec), then a small pitch correction is all that is needed to bring the nose back up. But this is not what the PF does - he pulls back and holds it there for several seconds and commands a climb.
The CG readings given in the interim report #3 (which was the first issued with actual data) are 27.5, 28.7 and 29.1% MAC respectively. Where do you get the other number from? If it's from an earlier report it would have been an estimate because they had no data - hardly their fault.
Last edited by DozyWannabe; 27th November 2011 at 03:52.