Boeing 737 MAX crash and the rejection of ridiculous data
Do we actually have the raw data from the sensor in the flight recorder, or do we have the flight computer&#x27;s account of that sensor&#x27;s data?<p>&gt; IF AOA &gt; 15 AND AOA &lt; 25 THEN RUNAWAY_TRIM();<p>And if the AOA is frozen at 16 due to some fault?  What is a loss of signal interpreted as?  Does it use last-known value? 0? 100?<p>How often does the AOA get sampled?  Is there any attempt to smooth the data?  Was the data corrupted (bit errors) during transmission&#x2F;reception?  Perhaps there&#x27;s a flaw in the hardware (or microcode) protocol implementation of the data  bus (or whatever it would be in this case) doesn&#x27;t disregard packets with parity errors?  Or perhaps it only checks for 1 bit of parity and it needs to check for 3?  Or perhaps it&#x27;s sending int64 and the flight computer is expecting int32.<p>It&#x27;s all so simple to make completely uneducated guesses.<p>When Boeing made such obvious mistakes such as &quot;don&#x27;t re-command full-nose down after reset&quot; that should have been caught be any competent user acceptance &#x2F; QA testing, I have to call the entire engineering effort into question.  I cannot assume they did even 1 thing correct in this system, and it really needs to have an independent review of the entire system hardware and software implementation.