Originally Posted by
averow
Journalist Jon Ostrower ( @jonostrower) on Twitter has discussed this issue in an article on his website
www.theaircurrent.com . Some good, detailed reporting on how this latest issue was identified. IMHO it may be a long time before this plane flies again in commercial service.
Interestingly, it refers to a different scenario, to what has been discussed here before "The deliberately broken microprocessor...". This was to simulate a hardware fault in the microprocessor unit (not specified?), which resulted in a slow system response to the pilot's action during runaway stabiliser recovery checklist. Test pilot had difficulty to correct ND input from stabiliser. This was not related to MCAS and faulty AOA sensor activation per se, but highlights another fault scenario in which 737-MAX aircraft's flight control response is deemed "chatestrophical" by FAA. The solution Boeing wants to implement is to re-route data to different processor units.. The end of summer RTS is indeed doubtful now, as it might promt evaulaution of another possible fault scenarios, which might be either misclassified or not properly assessed.