Boeing Software Scandal Highlights Need for Full Lifecycle Testing

It’s a bird! It’s a plane! It’s a software defect of epic proportions.

On March 10, 2019, Ethiopian Airlines Flight 302 crashed just minutes after takeoff. All 157 people on board the flight died. Similarly, in October of 2018, Lion Air Flight 610 also crashed minutes after taking off. Both flights involved Boeing’s 737 MAX jet.

The MAX jet, aimed to be more fuel-efficient than rival aircrafts, featured slight design changes than that of a regular 737 including upgraded engines and design. The changes, however, led to a problem with the nose of the plane: it would push it upwards. In order to counteract this issue, Boeing implemented the Maneuvering Characteristics Augmentation System (MCAS), a software that would automatically bring the nose of the plane down. Black box data from both flights suggest multiple similarities in the accidents, primarily revolving around the automated MCAS system.

Due to design, the 737 MAX jet featured engines more forward on the plane than other models; this caused the nose of the plane to lift to a higher degree than what is deemed safe. In order to amend this, a sensor towards the front of the plane, called the angle of attack indicator, was used to prevent stalling. This sensor along with the MCAS was designed to bring the nose of the plane back down to a safe level.

The problem? Well, there are two: (1) the software overpowered all other flight functions trying to mediate the nose lift and (2) many pilots did not know this system existed. The pilots in the Lion Air incident had as little as 40 seconds to identify the problem and correct it. Boeing had originally claimed that the MAX jet was similar enough to the original 737 that pilots would not need to go through extensive retraining, and, thus, pilots were trained via an iPad. Investigators on the Ethiopian crash case stated that the pilots on Flight 302 were using procedures highlighted by Boeing in the training that should have disengaged the MCAS system, but the plane was in an unrecoverable nosedive. All 737 MAX jet planes are now grounded worldwide following these two similar crashes that occurred just months apart.

What is worse is the fact that Boeing admitted to knowing about the software defect one year before the Lion Air crash in 2018. Engineers reportedly discovered the issue in 2017, but determined it was not an immediate issue. Originally, senior company leadership claimed to be unaware of the defect, but recent coverage has found those claims to be false. Furthermore, airlines were alerted to problem at drastically different times; Southwest told reporters they were informed of the problem in November of 2018 while United said they were not made aware of the issue until March of 2019. Boeing CEO Dennis Muilenburg explained to Business Insider why they did not inform pilots of this issue. “It’s fundamentally embedded in the handling qualities of the airplane. So when you train on the airplane, you are being trained on MCAS. It’s not a separate system to be trained on,” said Muilenburg.

Moving forward, Boeing has since apologized for both incidents and disclosed their plans for remedying the situation. They will be releasing a software update that will allow pilots to exert more control over the MCAS system as well as scaling back the software itself in order to prevent it from overpowering other cockpit commands. The system, if needed, will only activate once for a short duration and a warning light-which was previously an extra cost-0will now come standard to inform pilots of the software enabling. More importantly, Boeing additionally stated that pilots of the 737 MAX jet will undergo more extensive training programs in order to properly educate pilots on the MCAS system.

For now, Boeing is still working with regulators and is awaiting the Federal Aviation Administration’s approval for both the software and training updates. Nonetheless, Muilenburg vowed that the 737 MAX jet will be “one of the safest planes to ever fly” once the plane returns to the sky.

Note: This is a developing story. New information may come out following the publication of this article.

LogiGear Staff
LogiGear Corporation provides global solutions for software testing, and offers public and corporate software testing training programs worldwide through LogiGear University. LogiGear is a leader in the integration of test automation, offshore resources and US project management for fast, cost-effective results. Since 1994, LogiGear has worked with Fortune 500 companies to early-stage start-ups in, creating unique solutions to meet their clients’ needs. With facilities in the US and Viet Nam, LogiGear helps companies double their test coverage and improve software quality while reducing testing time and cutting costs.

The Related Post

The Testing Domain Workbook is the most extensive and exhaustive work you will ever find on a specific testing technique (or related techniques if you include equivalence class analysis and boundary testing as the book does). What I like best is the combination of academic background and roots combined with practical experience and industrial practice. All the concepts are ...
LogiGear Magazine March Testing Essentials Issue 2017
Karen N. Johnson began as a technical writer in 1985 and later switched to software testing in 1992. She maintains a blog at TestingReflections, a collaborative site where she is featured as a main contributor. In her latest entry, she discusses search testing with different languages. Here is an excerpt from her blog: “I started ...
Alexa Voice Service (AVS): Amazon’s service offering for a voice-controlled AI assistant. Offered in different products. Source: https://whatis.techtarget.com/definition/Alexa-Voice-Services-AVS Autopilot Short for “automatic pilot,” a device for keeping an aircraft on a set course without the intervention of the pilot. Source: https://en.oxforddictionaries.com/definition/us/automatic_pilot Blockchain Infrastructure: A complex, decentralized architecture that orchestrates many systems running asynchronously over the ...
At VISTACON 2011, Harry sat down with LogiGear Sr. VP, Michael Hackett, to discuss various training methodologies. Harry Robinson Harry Robinson is a Principal Software Design Engineer in Test (SDET) for Microsoft’s Bing team, with over twenty years of software development and testing experience at AT&T Bell Labs, HP, Microsoft, and Google, as well as ...
Having developed software for nearly fifteen years, I remember the dark days before testing was all the rage and the large number of bugs that had to be arduously found and fixed manually. The next step was nervously releasing the code without the safety net of a test bed and having no idea if one ...
Test design is the single biggest contributor to success in software testing. Not only can good test design result in good coverage, it is also a major contributor to efficiency. The principle of test design should be “lean and mean.” The tests should be of a manageable size and at the same time complete and ...
Reducing the pester of duplications in bug reporting. Both software Developers and Testers need to be able to clearly identify any ‘Bug’, via the ‘Title’ used for the ‘Bug Report’.
Plan your Test Cases with these Seven Simple Steps What is a mind map? A mind map is a diagram used to visually organize information. It can be called a visual thinking tool. A mind map allows complex information to be presented in a simplified visual format. A mind map is created around a single ...
LogiGear Magazine March Issue 2018: Under Construction: Test Methods & Strategy
Introduction Keyword-driven testing is a software testing technique that separates much of the programming work of test automation from the actual test design. This allows tests to be developed earlier and makes the tests easier to maintain. Some key concepts in keyword driven testing include:
Test plans have a bad reputation, and perhaps, they deserve it! There’s no beating around the bush. But times have changed. Systems are no longer “black boxes” where QA Teams are separated from design, input, and architecture. Test teams are much more technically savvy and knowledgeable about their systems, beyond domain knowledge. This was an old ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe