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

They’ve done it again. Gojko Adzic, David Evans and, in this book, Tom Roden, have written another ‘50 Quick Ideas’ book. And this one is equally as good as the previous book on user stories. If not even better.  
With this edition of LogiGear Magazine, we introduce a new feature, Mind Map. A mind map is a diagram, usually devoted to a single concept, used to visually organize related information, often in a hierarchical or interconnected, web-like fashion. This edition’s mind map, created by Sudhamshu Rao, focuses on tools that are available to help ...
Has this ever happened to you: You’ve been testing for a while, perhaps building off of a branch, only to find out that, after all of this time, there is something big wrong. It’s a bad build and now you have to go backwards, fix something, and get a new build. Basically, you just wasted ...
Introduction Keyword-driven methodologies like Action Based Testing (ABT) are usually considered to be an Automation technique. They are commonly positioned as an advanced and practical alternative to other techniques like to “record & playback” or “scripting”.
Creative Director at the Software Testing Club, Rob Lambert always has something to say about testing. Lambert regularly blogs at TheSocialTester where he engages his readers with test cases, perspectives and trends. “Because It’s Always Been Done This Way” Study the following (badly drawn) image and see if there is anything obvious popping in to ...
With complex software systems, you can never test all of the functionality in all of the conditions that your customers will see. Start with this as a fact: You will never test enough! Step 2 in getting started is to read and re-read The Art of Software Testing by Glenford Myers. This classic will set the ...
I’ve been intending to write a book review of How We Test Software At Microsoft, by Alan Page, Ken Johnston, and Bj Rollison, but for whatever reason I just never found the time, until now. In general, I like this book a lot. It’s a nice blend of the tactical and the strategic, of the ...
MARCH 2016_ TEST DESIGN ISSUE
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 ...
I’ve been reviewing a lot of test plans recently. As I review them, I’ve compiled this list of things I look for in a well written test plan document. Here’s a brain dump of things I check for, in no particular order, of course, and it is by no means a complete list. That said, if you ...
Introduction This article discusses the all-too-common occurrence of the time needed to perform Software Testing being short changed as specification, development, and unforeseen “issues” cause the phases prior to testing to expand. The result is that extreme pressure is placed upon the testing organization to perform the testing function within a reduced time frame. The ...
Please note: This article was adapted from a blog posting in Karen N. Johnson’s blog on July 24, 2007. Introduction The password field is one data entry field that needs special attention when testing an application. The password field can be important (since accessing someone’s account can start a security leak), testers should spend more ...

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news

Subscribe