Guest
On Monday, May 6, 2019 at 3:28:36 AM UTC-4, Jan Panteltje wrote:
By all indications it was not a software bug, from everything we've
seen the software did what the aerodynamic engineers and others spec'd
it to do. And it all was tested, including by test pilots, for
certification, including in extreme situations, where MCAS would be
involved. Apparently having a stuck AOA sensor wasn't part of the
testing.
That's ridiculous and what evidence do you have that the software developers
were spaced out? Aeronautical engineers and pilots certainly should have
been involved with what MCAS was and the specs for how it should operate.
This failure is clearly on them and the FAA. Could some software team
people have weighed in on some aspects of it? Sure. Like you'd think
someone might have said that part of the software should do a functional
test while the plane is still on the ground, to verify that the reading
from the AOA is normal there. And maybe they did, we won't know what all
went on until it's all been investigated. Also, whoever was writing that
code, that code module might not have access to the necessary data to
even know if the plane had just been started up, was still on the ground,
etc. and without that, you couldn't check.
Bottom line, people that were responsible, were knowledgeable at Boeing
and FAA were OK with this half-assed design where a single failed sensor
could shove the nose down, repeatedly. They considered it a serious
malfunction and evaluated the probabilities of various failures that
could cause it, by that measure, it met FAA and industry safety guidelines.
Another question in all this is what the root cause failure was? We've
heard nothing of that from either crash, which is very weird. These were
two sensors in two new planes that someone failed or were damanged, etc.
What exactly happened? You'd think they would suspect say a manufacturing
defect or something and have out a directive to inspect, replace, all
the similar AOAs out there.
Well, thankfully we have plenty of others willing or we'd be screwed.
No
On a sunny day (Sun, 5 May 2019 23:13:13 -0700) it happened Banders
snap@mailchute.com> wrote in <qaoj9p$1jpn$1@gioia.aioe.org>:
On 05/05/2019 08:25 PM, omnilobe@gmail.com wrote:
Weight and Balance of the 737 Max.
I looked at photos of 737 and 737 Max. The 737 has the front of
the engine at the front of the wing. The Max has the rear of the engine at the front of the wing. That makes it stall easily.
Actually, tail-heavy makes for an easy stall, and nose-heavy makes for a
dive. The crash planes weren't stalling, the AOA sensors just thought
they were. So you have it backward.
This photo should put your mind at ease.
https://www.colombotelegraph.com/wp-content/uploads/2019/03/Crash-Animation-of-Ethiopian-Airlines-flight-ET302-Boeing-737-Max-pl
ane.jpg
Normally software is tested and debugged, crashes happen,
bit of a nono to debug it in flights that carry people.
By all indications it was not a software bug, from everything we've
seen the software did what the aerodynamic engineers and others spec'd
it to do. And it all was tested, including by test pilots, for
certification, including in extreme situations, where MCAS would be
involved. Apparently having a stuck AOA sensor wasn't part of the
testing.
My opinion is that such software should be written by pilots,
not by spaced out no flying experience people.
That's ridiculous and what evidence do you have that the software developers
were spaced out? Aeronautical engineers and pilots certainly should have
been involved with what MCAS was and the specs for how it should operate.
This failure is clearly on them and the FAA. Could some software team
people have weighed in on some aspects of it? Sure. Like you'd think
someone might have said that part of the software should do a functional
test while the plane is still on the ground, to verify that the reading
from the AOA is normal there. And maybe they did, we won't know what all
went on until it's all been investigated. Also, whoever was writing that
code, that code module might not have access to the necessary data to
even know if the plane had just been started up, was still on the ground,
etc. and without that, you couldn't check.
Bottom line, people that were responsible, were knowledgeable at Boeing
and FAA were OK with this half-assed design where a single failed sensor
could shove the nose down, repeatedly. They considered it a serious
malfunction and evaluated the probabilities of various failures that
could cause it, by that measure, it met FAA and industry safety guidelines.
Another question in all this is what the root cause failure was? We've
heard nothing of that from either crash, which is very weird. These were
two sensors in two new planes that someone failed or were damanged, etc.
What exactly happened? You'd think they would suspect say a manufacturing
defect or something and have out a directive to inspect, replace, all
the similar AOAs out there.
I have bluntly refused to write code for things that I could not use myself.
Well, thankfully we have plenty of others willing or we'd be screwed.
Boeing and Trump standing there 'selling' it when whe got elected...
Does anybody see the link?
No