Seems to me like redundancy and failure analysis was an afterthought for the design team. This is a case that proves, do a complete analysis before actually going ahead with a build. I have worked at many places where they wanted me to just design on the fly. I would fight them to let me do a complete requirements, failure, and design analysis before doing the full project. But, I was told otherwise.
For the record, that company was audited. After which, complete analysis was a requirement.
Reports suggest that the pilot believed the faulty airspeed readings and was pitching the aircraft up until it stalled. The aircraft was capable of flight, it just had a bad instrument. If I'm ever faced with a similar situation I hope I don't make the same mistake.
There was a crash in Washington DC back in the Eighties that was similar. The engine thrust sensors in the aircraft had iced up during takeoff and were giving an erroneous reading. Even though the aircraft was stalling the pilot never increased power because he believed that one instrument rather than the data he was collecting from all the other sources.
Festo's BionicKangaroo combines pneumatic and electrical drive technology, plus very precise controls and condition monitoring. Like a real kangaroo, the BionicKangaroo robot harvests the kinetic energy of each takeoff and immediately uses it to power the next jump.
Design News and Digi-Key presents: Creating & Testing Your First RTOS Application Using MQX, a crash course that will look at defining a project, selecting a target processor, blocking code, defining tasks, completing code, and debugging.
Focus on Fundamentals consists of 45-minute on-line classes that cover a host of technologies. You learn without leaving the comfort of your desk. All classes are taught by subject-matter experts and all are archived. So if you can't attend live, attend at your convenience.