4 ms·
It's ironic that it's a Boeing with bad software (or sensors) interfering between yoke and plane. After all, historically, Boeing has had the philosophy of trus
by samcheng 8y ago
It's ironic that it's a Boeing with bad software (or sensors) interfering between yoke and plane. After all, historically, Boeing has had the philosophy of trusting the pilot with direct control of the plane. This is in comparison with Airbus, where controls are by stick instead of yoke, and pilots are taught to trust the flight computer and move the controls less. (Of course, these days both manufacturers build fly-by-wire planes.) [1]
The addition of a 'maneuvering characteristics augmentation system' seems very unlike Boeing. I guess it became necessary after adding too-big engines without otherwise adjusting the airframe... [2]
This "we'll fix it with software later" attitude works well with CPU errata and maybe Teslas, but it doesn't look like we're there yet for airplanes, unfortunately.
[1] https://www.pprune.org/tech-log/10321-stick-vs-yoke-airbus-v.. https://www.pprune.org/tech-log/10321-stick-vs-yoke-airbus-v....
[2] https://theaircurrent.com/aviation-safety/what-is-the-boeing.. https://theaircurrent.com/aviation-safety/what-is-the-boeing....
- goodcanadian 8y agoThis "we'll fix it with software later" attitude works well with CPU errata and maybe Teslas, but it doesn't look like we're there yet for airplanes, unfortunately. I'm sure I'm preaching to the choir here, but I'm absolutely against the "fix it with software" attitude. I'm working with embedded systems, now, and while we can often make it work by tweaking the software, it always results in a less than optimal solution. Fix the hardware; get it right, preferably before manufacturing a few thousand units.
- iSnow 8y agoDoesn't work in the current speed of development any more. Time to market is more critical than maturity, sadly. That's why every system can be fixed in software now, and that's also why every system can be pwned now.