Comment by tavavex

I don't really understand what's so jaw dropping about input averaging. Let's be clear - this is a fallback state that handles a situation that should never come up. Pilots aren't supposed to try to control the aircraft from both seats at the same time, both fly-by-wire and not. What we're talking about isn't a deficiency that can sporadically cause a dangerous situation, like the MAX, but a situation where the pilots have already made a massive mistake and the automation didn't bail them out. It's not like there's no workaround, either. Making conflicting commands results in the plane blaring a 'dual input' warning at you, and if one of the pilots desires exclusive control, they can press the side stick priority button. A further improvement of the system would be to add force feedback to the side sticks, to simulate the linked yokes of a non-fly-by-wire aircraft, but even without it, I feel like this issue is given way more publicity, and it's used as the scapegoat for the ultimate cause, pilot error. All incidents that involved this were ruled as being caused by pilot error - in the crash this article is about, the PF was literally holding his side stick full back until almost the very end. A force feedback system might've helped them realize it sooner, or it might not have - there's plenty of historical incidents where pilots managed to stall conventional aircraft out of nowhere in a similar fashion, but those were ruled to be their mistake only.