PPRuNe Forums - View Single Post - AF 447 Thread No. 10
View Single Post
Old 7th Sep 2012, 17:46
  #322 (permalink)  
DozyWannabe
 
Join Date: Jul 2002
Location: UK
Posts: 3,093
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by Lyman
There's a civil question. My question from the beginning, since it is likely that the crew had more experience with autopilot loss due to exceeded control limits than "UAS".
And your basis for that conclusion is?

Originally Posted by Lyman
Nomenclature. The ADR(s) were not faulty. That is a mistake made by someone who cannot separate a sensor from a computation.
No, the FCOMs are pretty clear on the term "fault" being synonymous with "rejected", and as such can mean either in this case. The source of the problem is immaterial - all that matters is the data cannot be relied upon.

So it occurs to me that a conference among computers should have extended an invitation to the flightcrew to be privy...
Have a look at HN39's post and look closely at the times:

Originally Posted by HazelNuts39
ˆˆ The ADR 2 speed fell between 2 h 10 min 03.5 et 2 h 10 min 05;
ˆˆ the ADR 1speed fell for less than one second from 2 h 10 min 04 s to 2 h 10 min 05, causing:
- the disconnection of the autopilot,
- the triggering of “PITOT PROBE” monitoring in the FCPC causing the transition to alternate 2B law;
ˆˆ The ADR 3 speed fell temporarily from 2 h 10 min 07 s to 2 h 10 min 10 s, causing, in the following second, the loss of autothrust and the disappearance of the Flight Directors; it then fell again at 2 h 10 min 14,
ˆˆ The speed on ADR 1 fell again at about 2 h 10 min 08 s, causing the loss of the autothrust and of the flight directors within the next second.
Then look at the link I posted a short while ago. The time between the onset of the problem and the systems working out the problem (that's from normal > single ADR out > multi ADR out > UAS) is approximately 5 seconds - and it only took that long because the detection algorithms must determine a trend. The human brain would have to process that same information and divine what it meant visually, and that's presuming looking straight at the indication. There's simply no way displaying the speeds from each would have made any difference.

The "ALTERNATE LAW" call was made by the PNF, and the PF should have been listening. The idea that the turbulence would have caused AP disconnection is utter fiction.

Last edited by DozyWannabe; 7th Sep 2012 at 17:50.
DozyWannabe is offline