My role here is limited. I consider first to assertively say what i am convinced, absolutely sure and this must be said. Because was important in the crash.
I am available to explain by
voice the "practical solution" to an interested pprune member. Simple, just call me and i can teach what to do.
Actually most EE knows that. Simple DSP techniques used extensively in the industry.
In simple words: We need to perform a DSP of the air (analog output obviously) speed information and:
1) Inform IMMEDIATELY to the crew the UAS onset.
2) Block IMMDIATELY GI to ELIMINATE GO (GIGO played a pivotal role)
In a previous post i mentioned an Airbus SAS paper that shows the opposite: The crew must diagnose. IMO this is a serious error. In many aspects.
So important specially when you do not have redundancy at all. (Important sensors failing SIMULTANEOUSLY).
Degrade a System and wait for the crew diagnose is a COMPLETE ABSURD. The chances could be dim even for a designer acting as pilot depending on behavior of the System.
The approach used is WRONG. And SHOULD be changed:
1) UAS DSP detector
2) Actions by crew/System or System/crew