Professional Documents
Culture Documents
Boeing Engineering Flaw Analysis
Boeing Engineering Flaw Analysis
The fact that the software was programmed to automatically lower the plane is
indicative of engineering flaw of a plane where engine was moved up and
forward and had an inclination, [not just when pilot moved the plane up but
even when the plane was moving even keeled to point up…. This makes sense
that they injected 5 to 10second rounds of automated stalling mechanism as a
desperate attempt to cover the design and engineering flaws of the plane. If it
were an issue of an angle of how much the pilot nosed up the plane, then a
simple directive in the manual would have rectified that, but the plane pushed
up when its throttled ,not when the pilot moved the nose up and the designers
hoped to trick and disguise this glitch with the software presuming that the
automated 5 second automatic directives of the program to push the plane down
would not be observable since they estimated that the plane would tend to
point up every 5 to 10 second interval and therefore would balance It out..… but
the pulse to balance was at least significantly off. but the flaw was observable
and it looked to the pilots whom did not know of the program that their was
something wrong with the plane rather than a software malfunctioning that
was spurting our commands and therefore could be manageable.
They did not mention MCAS in the manuals because it would compromise the
sales front of the product , thus if communicated that the device was
compensating for a flaw of which would be immediately apparent, then people
would have raised questions and the company would not have sold as many
planes.
The new engine placement increased risk of stalling and especially at low
speed” rogue Boeing 737 max planes 60 minutes program , this indicates that
the problem was integral and not activated when the pilot pitched the plane up
as I first assumed with the first video. They were too close to certification to
change the design.