Boeing was starting to look like it was fighting back. Maybe getting back on track, and then the MAX landed another upper cut
https://www.reuters.com/article/us-boeing-737max-software-idUSKBN1ZG28M
14 replies (most recent on top)
@1qll
Yes and Thank You.
So many people bite at the first bit of info that is way too often published
By so called journalist, whose first interest is to publish first, dam the details.
just like the people who can’t wait to start a new thread.
LOL
Then there’s no critical thinking, wait a minute Boeing you stated you’re testing
The new Co-dependent FCC and now Boeing has stated they just added code
So the two computers could talk to each other. Boeing is caught in another lie.
Or there incredibly incompetent.
Either way we all lose and they will spin it all into a bigger payday for the board.
These Shysters Need To Go > back to banking and Wall Street
We need them out of aviation and we need to dismantle cronyism in Boeing
It was NEW code? Seriously?
They created a new requirement
They created new PRs
They created new code
They should have created new requirement based test points
And
They should have tested those requirements BEFORE they tested them in front of the FAA. This is software development 101.
When you can come upstairs and role with the big boys.
The disappointments are far larger.
It’s sicken, I can’t wait to get out.
We have not completed the MCAS software audit yet.
The software audit was to be completed 60 days ago.
The FAA tossed Boeing out on their ear for shoddy documentation, remember.
The bug was found during an audit of the Max jet's {on-board technology},
That was held last weekend with America's aviation regulator.
These technical reviews are expected to turn up glitches and gremlins
for Boeing engineers to fix, so this is kind of to be expected.
The audit has to completed before the FAA can take the updated Max on
A test flight, and ultimately certify it to fly again with passengers.
Two of the flight computers stopped communicating with each other during
The aircraft's start-up sequence. The plane is on the ground.
This disrupted the power-on monitoring systems.
Boeing had just added the code to allow the two flight computers to talk to
Each other – Previously They Operated Independently. {This is New}
But co-dependency of the FCC was an initial workaround for the failed MCAS
So it is Mud on the face of Boeing to even bring this to the FAA for a test.
- It’s a new software tweak they just put in and it failed.
The real question is, What have they been testing?
This, in light of the fact that they have Never passed an MCAS software audit
So what have they been doing this whole time?
My whole point is, This is Boeing smoke and mirrors, Nothing has changed.
Management is incapable of being straightforward and honest.
Lying to the FAA to their employees and to the share holders is all they know.
For me it’s frustrating that anyone expects anything different from this gang.
Boeing has murdered for profit, They will do it again
And they will lie about it again; it is what I expect of them. What do you expect?
Boeing Management is an embarrassment i.e. So is Boeing
I see no apologies to the OP for being wrong, calling stupid, calling it click bait, saying it was an old recycled article....
But then again, these are the same people who have been wrong for 10 months predicting layoffs, so, I guess it's not surprising that they can't admit they are wrong.
Apparently the issue is so bad the plane can’t even power on correctly.
Some people here like to laugh, before they even see the news
Hell, it was just reported on ABC world news.
Another new issue for Boeing
This is not an OLD issue,
this is NOT they original MCAS issue
This is NOT the wiring issue they found
This is NOT the software issue they found in July
This is a brand new Software issue announced TODAY
No!!! Leave them to the click bait
LOL
Do you think we should tell em?
How many new threads are going to be started on this Old issue?
Do you work at Boeing? to pour to pay attention?
If you would kindly explain to me what is stupid?
It was reported that the FAA/EASA testing would start on Jan 15, a good sign by all accounts.
Then today there is news that yet ANOTHER software issue has been found.
I am sorry you don't get the reference or the colorful way I chose to describe it, that's your problem, not mine.
I have to ask how it is that we are finding these issues now and not during the original testing. Did we not look?
Life is like a box of chocolates
Some are simple Some have nuts
Some are simpletons and have nuts