'Software delivered to Boeing' now blamed for 737 Max warning fiasco

Engineers knew of problem in 2017. Management didn't until after fatal crash


As the 737 Max scandal rolls on, "software delivered to Boeing" has been blamed by the company for the malfunctioning of a safety display.

In a statement issued over the weekend, the American airliner manufacturer admitted that its software was not properly displaying fleet-standard warning captions to pilots. This admission comes after sustained media reporting over cockpit angle-of-attack (AOA) displays and warnings, one of which was sold by Boeing to airlines as an optional extra for their aircraft.

Warning captions (wording that flashes up on the pilot's display screen) on the 737 Max included one, AOA Disagree, which alerted the pilots if the 737 Max's two AOA sensors were delivering different readings from each other. If the two go out of sync, the logic goes, one must therefore be faulty.

Worse, Boeing engineers knew about the problem in 2017 – months before the fatal Lion Air and Ethiopian Airways crashes. The company only revealed this to US Federal Aviation Authority regulators after Lion Air flight JT610 crashed in October 2018, claiming in this week's statement that "the issue did not adversely impact airplane safety or operation".

"Senior company leadership was not involved in the review and first became aware of this issue in the aftermath of the Lion Air accident," added Boeing.

The AOA sensors feed the controversial MCAS trim system, another software feature that did not work properly. Improper MCAS activations seemingly caused by faulty AOA readings are suspected to have contributed to two fatal Boeing 737 Max crashes within the last year, costing hundreds of lives.

Boeing said the 737 Max's "display system software did not correctly meet the AOA Disagree alert requirements", adding that "software delivered to Boeing linked the AOA Disagree alert to the AOA indicator, which is an optional feature on the Max" and earlier versions of the 737.

"Accordingly," continued Boeing, "the software activated the AOA Disagree alert only if an airline opted for the AOA indicator."

This was not what should have happened. Even if an airline didn't pay extra for the AOA indicator display gauge (pictured here on a schematic for earlier 737 versions than the Max), if the sensors went out of sync, a warning should have been shown to the pilots.

AOA gauges have been offered as a feature on Boeing 737s since the mid-1990s 737-600 model, known in marketing terms as the first of the 737 Next Generation (NG). The NG series, comprising the 737-600, -700 and -800 models, preceded the controversial Max series.

Boeing is now issuing a display system software update to correct this fault, it said. This is on top of a promised software update to MCAS to stop it from attempting to push the 737 Max's nose towards the ground. ®

Similar topics

Broader topics

Narrower topics


Other stories you might like

  • Nvidia open-sources Linux kernel GPU modules. Repeat, open-source GPU modules
    A Turing point for the graphics chip giant, perhaps?

    Nvidia on Wednesday published the R515 driver release of its Linux GPU kernel modules under an open source, dual GPL/MIT license.

    The chip biz has made the source code available via the Nvidia Open GPU Kernel Modules repo on GitHub, a move that suggests the need to respond to AMD's long-standing open-source driver initiative.

    "This release is a significant step toward improving the experience of using Nvidia GPUs in Linux, for tighter integration with the OS and for developers to debug, integrate, and contribute back," claimed Ram Cherukuri, senior product manager, Shirish Baskaran, senior system software manager, Andy Ritger, Linux OpenGL driver engineer, and Fred Oh, senior product marketing manager, in a blog post. "For Linux distribution providers, the open-source modules increase ease of use."

    Continue reading
  • Mystery of industry-targeting backdoored NPM JavaScript packages solved
    Snyk, JFrog, ReversingLabs spend weeks investigating modules that turn out to be pen-test code

    Malicious packages in the NPM Registry that security researchers for weeks believed were being used to stage supply-chain attacks against prominent industrial companies in Germany turned out to be part of a penetration test run by a cybersecurity company.

    Researchers at Snyk in late April published a blog post about a JavaScript package that stood out among others they had found because it contained both encrypted and obfuscated files.

    More recently, software maker JFrog and cybersecurity firm ReversingLabs this week released their own findings about the multiple malicious libraries in the NPM Registry that all used the same payload and belonged to the same malware family as the one analyzed by Snyk. The goal appeared to be to launch dependency-confusion attacks in which applications within German companies end up using, through a misconfiguration or something like that, malicious npm modules rather than legitimate packages with similar or plausible names. If successful, developers within specific corporations would be fooled into introducing backdoors into their code bases.

    Continue reading
  • Google shows off immersive maps, AR-flavored search, Pixel 7, and more
    Your essential de-hyped guide to what the Chocolate Factory teased at developer shindig

    Google IO Google I/O, the ad biz's annual developer conference, returned to the Shoreline Amphitheater in California's Mountain View on Wednesday, for the first time in three years. The gathering remained largely a remote event due to the persistence of COVID-19 though there were enough Googlers, partners, and assorted software developers in attendance to fill venue seats and punctuate important points with applause.

    Sundar Pichai, CEO of Google parent Alphabet, opened the keynote by sounding familiar themes. He leaned into the implied sentiment, "We're here to help," an increasingly iffy proposition in light of the many controversies facing the company.

    He said he wanted to explain how Google is advancing its mission in two ways, "by deepening our understanding of information so that we can turn it into knowledge and advancing the state of computing so that knowledge is easier to access no matter who or where you are."

    Continue reading

Biting the hand that feeds IT © 1998–2022