Ah yes, The Fundemental Failure Mode Theorem[0] at work: Complex systems usually operate in failure mode.
Or, "That's why I'm skeptical of people who look at some catastrophic failure of a complex system and say, "Wow, the odds of this happening are astronomical. Five different safety systems had to fail simultaneously!" What they don't realize is that one or two of those systems are failing all the time, and it's up to the other three systems to prevent the failure from turning into a disaster." [1]
See also United 232 http://en.wikipedia.org/wiki/United_Airlines_Flight_232. The DC10 has three separate hydraulics systems, therefore the probability of all three failing is p^-3 right?? But wait, the lines are all grouped together through the tail, meaning if one is severed there, the other two are likely to be severed as well.
You might conclude from this that airliner designers are fools. An airliner is a very complex machine, and can have unexpected interactions between its components. Look at the other side:
1. the airframe held together despite an explosion at the back. The rudder and horizontal stabilizer stayed on.
2. the aircrew figured out how to control the airplane with no hydraulics, i.e. there was still some redundancy in the system.
3. the landing gear was designed so it could be extended and locked with no hydraulic power, and that worked
4. if the airplane or aircrew was any less, nobody would have survived
5. electric power stayed on
And, airframe companies learn from these disasters, which is why airplane travel is incredibly safe. Boeing airliners, for example, do not locate critical components inline with the turbines. Hydraulic lines do not extend past the inboard engine. There are a number of other improvements as well.
Having worked on 757 flight controls for three years, I can assure you that none of the engineers want any part of a defective design. None want to make any decisions that lead to a smoking hole in the ground. An awful lot of effort is spent pouring over the designs again and again looking for mistakes.
I don't know if they existed at design time, but hydraulic fuses could have prevented draining of all the fluid. That makes the design take longer, increases weight, introduces new scenarios such as the fuse activating when it shouldn't, increases cost, and increases maintenance & parts (cost of ownership).
As with these matters there is no one true correct answer, but rather a very complicated set of tradeoffs and probability estimates. In hindsight it is easy to see designs as defective, but they could all be done in good faith.
No offense meant to aircraft designers, my point is just that it's a common fallacy to assume that probabilistic events are independent when they are in fact dependent in some ways. In the case of debris penetrating the tail, if one hydraulic line is severed, the probability of the other two also being severed is high, therefore the probability of a triple failure is not equal to p^-3; you must add to that the probability of this single catastrophic event occurring.
That post from The Old New Thing[1] makes a fascinating point. Something like that ought to be required reading for anyone who does anything even vaguely engineering-like.
- what are the total number of failures that can happen?
- what is the probability of those failures occurring
- how many sets of those can combine into a catastrophic failure?
And then from those numbers you can derive the probability of a catastrophic failure occurring.
Yes, but the thing that the Fundamental Failure Mode Theorem tries to draw attention to is "what is the probability of those failures occurring".
i.e. it's possible that some of those failures have already occurred, and you just haven't noticed because the redundant systems are being redundant and preventing the overall system from failing catastrophically. Or you have noticed, but think that the redundant systems are sufficient, not realising how much closer they bring you to a single point of failure. So the probability of your whole system failing are higher than you'd expect, because you already have failures which you think are p < 1 (possibly p << 1) but are actually p = 1.
In the case of the Gimli glider, they had two independent FQIS systems and a floatstick in case of a single failure, and a rule that the airplane was non-servicable in case of both failing.
On the flight in question, one FQIS was non-servicable. The second was servicable but had been switched off, but due to a miscommunication it was thought that the no-fly rule had been overridden and the plane was OK with a floatstick measurement. Further, if the fuel calulation from the floatstick measurement had been correct, they would have refueled the plane and no-one would ever have heard about Air Canada Flight 143 because everything would have been fine.
The problem was that they were knowingly operating in a failure mode, without either FQIS and disregarding the no-fly rule, and thinking that the floatstick measurement was sufficient. Therefore it only needed one further failure - miscalculating the amount of fuel from the floatstick - to bring about disaster.
Well, we can observe that the probability of a catastrophic failure in an airliner is in fact extremely low, since they happen extremely infrequently. So even if systems are operating in a failure mode, there appears to still be enough redundancy left to lower the odds enormously.
I sort of take the opposite approach with comments that the odds of such a failure are astronomical. Given how safe airliners are these days, anything that causes a bad emergency with one must be an extremely unlikely event. If it weren't, more airliners would crash than actually do. I've seen this going around with MH370, for example. People will dismiss an idea for what caused the disappearance with a comment that such an event is extremely unlikely. Well sure, pretty much by definition, whatever caused it has to have odds of something like a billion to one.
I'd also like to bring up a minor quibble, in that Air Canada 143 did not end in disaster. It certainly came close, and should be regarded as a serious incident with lessons to be learned, but ultimately everybody survived and the airplane was returned to service, precisely because there weren't quite enough failures to cause a disaster. Various things went wrong, but the pilots managed to stop the chain of events by successfully responding to the in-flight emergency. The ability of the airplane to continue flying and somewhat functioning after fuel exhaustion is a type of redundancy, and it ultimately saved it.
Or, "That's why I'm skeptical of people who look at some catastrophic failure of a complex system and say, "Wow, the odds of this happening are astronomical. Five different safety systems had to fail simultaneously!" What they don't realize is that one or two of those systems are failing all the time, and it's up to the other three systems to prevent the failure from turning into a disaster." [1]
[0] http://en.wikipedia.org/wiki/Systemantics#System_failure
[1] http://blogs.msdn.com/b/oldnewthing/archive/2008/04/16/83984...