Pilot Who Hitched a Ride Saved Lion Air 737 Day Before Deadly Crash (bloomberg.com)
As the Lion Air crew fought to control their diving Boeing 737 Max 8, they got help from an unexpected source: an off-duty pilot who happened to be riding in the cockpit. Bloomberg reports: That extra pilot, who was seated in the cockpit jumpseat, correctly diagnosed the problem and told the crew how to disable a malfunctioning flight-control system and save the plane, according to two people familiar with Indonesia's investigation. The next day, under command of a different crew facing what investigators said was an identical malfunction, the jetliner crashed into the Java Sea killing all 189 aboard.
The previously undisclosed detail on the earlier Lion Air flight represents a new clue in the mystery of how some 737 Max pilots faced with the malfunction have been able to avert disaster while the others lost control of their planes and crashed. The presence of a third pilot in the cockpit wasn't contained in Indonesia's National Transportation Safety Committee's Nov. 28 report on the crash and hasn't previously been reported. The so-called dead-head pilot on the earlier flight from Bali to Jakarta told the crew to cut power to the motor driving the nose down, according to the people familiar, part of a checklist that all pilots are required to memorize. Further reading: Flawed Analysis, Failed Oversight: How Boeing, FAA Certified the Suspect 737 MAX Flight Control System.
The previously undisclosed detail on the earlier Lion Air flight represents a new clue in the mystery of how some 737 Max pilots faced with the malfunction have been able to avert disaster while the others lost control of their planes and crashed. The presence of a third pilot in the cockpit wasn't contained in Indonesia's National Transportation Safety Committee's Nov. 28 report on the crash and hasn't previously been reported. The so-called dead-head pilot on the earlier flight from Bali to Jakarta told the crew to cut power to the motor driving the nose down, according to the people familiar, part of a checklist that all pilots are required to memorize. Further reading: Flawed Analysis, Failed Oversight: How Boeing, FAA Certified the Suspect 737 MAX Flight Control System.
Is this a 737 Max 8 problem or a training problem?
We just don't know how to use the search button anymore
https://www.news.com.au/travel/travel-updates/incidents/lion-air-crash-pilot-on-previous-flight-made-distress-call-before-continuing-to-fly/news-story/7fa1bd3b49f4dbe76444f27cc52bca41
Date: Nov 2, 2018
Abagnale would pose as a pilot to sit in airline jump seats and get a free ride. I don't know why, but the image of the pilot turning to him for help just crossed my mind.
What's remarkable in the Lion Air flight is that the company didn't ground the plane until the angle-of-attack sensor problem was resolved.
I dunno manually removing power to a motor that a control system is erroneously commanding you and 300 people to die should be something that gets raised for serious review and corrective action. Someone really missed an opportunity to save a lot of lives.
Not really. You also memorize a whole bunch of things for exams, but that doesn't mean you have actually learned how to put that knowledge to use in a real scenario. It's the whole problem at the core of teaching to the test.
-=This sig has nothing to do with my comment. Move along now=-
Only difference was the the faulty sensors on the Airbus usually screwed up at altitude.
They still lost one however.
727 had similar pilot training issues losing several right off the bat (two within three days of one another). Difference was that it was a completely new type, not advertised as being the same plane.
https://i.imgur.com/YwuKQkp.png
Pilots instead of Computers should fly the damn plane.
The smoking gun for this incident isn't going to be what the final report says. It'll be on some notes by some engineer when this project started saying everything above. There isn't a way that this project made it this far without some intelligent engineers speaking up and getting over ruled by management.
I lasted exactly 45 days in Aerospace and it was terrifying, they picked a "COTS" architecture that hasn't been "COTS" since the Macintosh moved away from 68k. I was told to 'deal with it'. Other people quipped that "this wasn't the worst design decision he's seen". The schedule was everything because customers had already bought what we were working on.
But everything HAD to move forward according to THIS timeline because someone already bought it. In those 45 days I had to work on trial versions of everything, they couldn't figure out how to get us licensed in to their network. Everyone else on the project had always been in aerospace, so this was 'par for the course'. I came from automotive where we actually did put safety first (at least where I worked).
I want to see the MIL/SIL/HIL reports. This should have been caught in the plant model long before it came to market. There should be a high-fidelity model that shows this exact scenario and how it plays out. It was buried for some reason or another. If there isn't then they didn't test as comprehensively as they should have (because of rushing to market).
There are a lot of people, that have been coming to similar conclusions about the MAX8. It's an 'unstable pendulum' that they thought they could just 'fix it in software'. Good hardware design is crucial to a good controllable system.
Someone spoke up, either they have an e-mail in a safe (like Audi's Dieselgate) or they're no longer with Boeing (or one of their subcontractors like GE, or GE's subcontractors) because they did speak up and were told they were 'toxic to the project'.
This is the boring un-sexy parts of engineering. But 'Failure Mode and Effects Analysis (FMEA)s' are important. We literally sit down and go "What happens if this fails" and then write out a full plan in software. Plus a full test plan.
dSpace makes aerospace hardware-in-the-loop (HIL) test benches. They make them for automotive and off highway too. We literally 'drive' around a vehicle for thousands of hours for software releases.
I don't have a doubt this was caught by someone somewhere. Management got involved and now this is going to be another Challenger O-Ring example for freshmen engineers.
Is ignoring a plugged sensor a bad idea? Absolutely. Should the failure mode be plowing into the ground an full tilt after fighting the pilots? No.
One of the bigger long-term consequences of these MAX-8 incidents will be the impact on the FAA's influence in the civil aviation world. One little commented fact is that when the MAX-8s were grounded it was the Chinese civil aviation authorities who led the world in grounding the 737 MAX. This was unprecedented, as most civil aviation authorities have tended to follow the lead certification authority of the manufacturer, the FAA in this case, before issuing a grounding. This was the case in previous grounding - the 787 dreamliner in 2013 and DC-10 groundings in 1979 were both led by the FAA.
Additionally, it now appears both Transport Canada and EASA are no longer willing to accept FAA certification. Other aviation authorities have in the past accepted FAA certification without challenge. if other authorities no longer trust the FAA to do its oversight properly Boeing will be forced to carry out multiple certification assessments for each civil aviation authority, and that will carry with it a considerable delay and financial burden.
I'd love it if people were more willing to be methodical when the situation demands it, but most pilots will not get out a paper checklist while in the middle of a nosedive.
They did write it down into the maintenance log, as they should have.
They have written about "IAS and ALT Disagree shown after Take Off" and "Feel Differential Pressure Light Illuminated".
The tech crew flushed the left pitot tube and static port, cleaned the connector of the elevator force feedback unit and quickly tested both system on the ground, finding nothing wrong.
So the aircrew didn't really write about the runaway stabiliser and the tech crew didn't bother to run comprehensive checks because it would have taken too much time and some specialised equipment they probably didn't have at hand.
And here you have it all coming together - a crappy airplane, dilettante pilots and overworked technicians, resulting in a crash.
"It's such a fine line between stupid and clever" -- David St. Hubbins, Spinal Tap
This system should be using a myriad of sensors to activate, not the least of which is the air speed indicator, backed up by GPS, the altimeter, also backed up by GPS, and the bank indicator. For one thing, the stall angle of attack is completely different at one speed versus another. This is because flight envelopes are not squares. Second of all, if altitude or GPS show the plane about to go below the ground level for the specific location, it shouldn't be driving the nose down.
Although I haven't been in the aviation arena for some years, I recall that this should have been disseminated in a NOTAMN (notice to airmen) --- why didn't that aircrew spread that correction to others within the airport and airlines????? If they did not, it displays a massive show of irresponsibility on their part!
I believe an employee (pilot here) won't be allowed to share on-job details on a public or outside company channels. Because it may affect the reputation of the company and its partners [eg Lion Air may look bad if it bought a bad plane; and boeing looks bad for engineering a bad plane / not requiring better pilot training]. And all these may affect the corporate's bottom line.
Toyota had a runaway throttle caused by recursive software. People died as a result.
Toyota's response - replace the floormats!
Someone should have gone to prison over this.
The fact that an aircraft that almost crashed because of a fault wasn't immediately grounded and instead was allowed to fly the next day IS ABSOLUTELY UNCONSCIONABLE!
~Any apparent grammatical or typographic errors are caused by defects in your display device.
So they knew about the problem, and instead of fixing it, they created a "procedure,' one that had to be memorized and remembered or you and your crew and every person on the plane would surely die. Sound right to you?
E Proelio Veritas.
After a "near crash" accident like this, how come all the plains were not grounded?
I suppose this "Fight Club" scene may be relevant?
https://www.youtube.com/watch?...
4wdloop
Former avionics troop here. Given a malfunction, tech data directs appropriate troubleshooting and maintenance. If AOA sensor replacement is in the fault/troubleshooting tree, you replace that sensor. When a sensor is replaced follow-on maintenance like self tests and operational checks is required. The replacement sensor may have passed causing the techs to assume the problem was fixed, but they were ON THE GROUND.
What tech data error permitted the aircrew to fly with an AOA or other malfunction? What idiot permitted the aircraft to fly after REPEATED malfunctions and on what grounds?
Not every malfunction grounds an aircraft nor should they, but AOA is important enough for grounding and if in-flight verification of a fix is required or desired, a functional check flight is performed by aircrew, not "aircrew and fucking passengers".
"This post is an artistic work of fiction and falsehood. Only a fool would take anything posted here as fact."
How's life in the hypocrite lane?