Boeing held off for months on disclosing faulty alert on 737 Max | TribLIVE.com
U.S./World

Boeing held off for months on disclosing faulty alert on 737 Max

1120565_web1_943237-ec462ed94e8d41d287af8f18583f1d50
AP file
This Thursday, March 14, 2019, file photo shows a Boeing 737 Max 8 airplane parked at Boeing Field in Seattle. America’s standing as the model for aviation-safety regulation will be on trial as congressional hearings begin Wednesday, March 27, 2019, into the Federal Aviation Administration’s oversight of Boeing before and after two deadly crashes of its best-selling airliner.

Boeing knew months before a deadly 737 Max crash that a cockpit alert wasn’t working the way the company had told buyers of the single-aisle jetliner.

But the planemaker didn’t share its findings with airlines or the Federal Aviation Administration until after a Lion Air plane went down off the coast of Indonesia in October, according to a Boeing statement Sunday as it provided additional details of an issue that first came to light last week. The accident occurred after erroneous readings by a single angle-of-attack sensor triggered software that pushed the jet’s nose down until pilots lost control.

Boeing’s latest disclosure raises new questions about the 737 Max’s development and testing — and the company’s lack of transparency. The alert was supposed to flash when two angle-of-attack vanes sent conflicting data about the relation of the plane’s nose to the oncoming air stream. Boeing had told airlines and pilots that the so-called AOA disagree warning was standard across the Max fleet, as on a previous generation of 737 jets.

The software delivered to Boeing linked the signal with a second cockpit gauge — available for a fee — that displayed the readings from the two vanes. As a result, the AOA disagree light, which warned pilots of issues with the sensors, functioned only for customers that purchased the optional indicator.

“The question I have is just like we asked them in Reno, ‘Is that all there is?’ That’s the biggest question,” said Jon Weaks, head of the Southwest Airlines Pilots Association, referring to a meeting union leaders had with Boeing after the Lion Air crash. “It’s obviously troubling that here is something else Boeing didn’t get to us.”

Through last week, Boeing had dropped 11% since the Ethiopia crash, the biggest decline on the Dow Jones Industrial Average.

The inactive alert was later deemed to be “low risk” by the FAA’s Corrective Action Review Board, the regulator said Sunday. “However, Boeing’s timely or earlier communication with the operators would have helped to reduce or eliminate possible confusion,” the FAA said.

Boeing engineers discovered the discrepancy “within several months” of the initial Max deliveries in May 2017, the company said. The disclosures followed criticism from airlines and crash victims’ relatives that Boeing hasn’t been forthcoming about issues with the 737 Max, which has been grounded since a second crash in March, in Ethiopia.

The two disasters killed 346 people.

The manufacturer’s own experts reviewed the issue and “determined that the absence of the AOA Disagree alert did not adversely impact airplane safety or operation,” according to the Boeing statement. The company’s review board decided the setup was acceptable until the two alerts could be unlinked with the next planned software update for the plane’s display system.

Rockwell Collins, which was acquired last year by United Technologies Corp., provides the cockpit displays and flight-control computers for the 737 Max. Another United Technologies division makes the angle-of-attack vanes for the plane.

United Technologies referred questions to Boeing. United Technologies declined 1.9% to $138.89.

Boeing said its senior leadership wasn’t involved in the review and first became aware of the issue after the Lion Air accident. The Chicago-based planemaker also broke the news of the glitch to Max operators such as Southwest Airlines Co. in the aftermath of the initial crash.

“Why weren’t the manuals changed? Until after Lion Air, our manuals said that worked,” Weaks said. “You can’t blame Southwest because that’s the information they had from Boeing. We don’t know what we don’t know.”

Boeing said it also told the FAA that company engineers had identified the issue in 2017, along with the findings from their internal review process. In December, a safety review board convened by the manufacturer confirmed that the absence of a functional AOA disagree light didn’t present a safety issue.

Boeing briefed the FAA’s Seattle aircraft certification office in November, and the information was forwarded to the agency’s Corrective Action Review Board for evaluation, an FAA representative said Sunday. The panel determined the issue to be “low risk,” and said Boeing would have to fix it as part of an overall package of enhancements to the Max in response to the Lion Air accident.

Before the Max returns to service, Boeing plans to issue a software update that will allow the AOA disagree light to operate as a standalone feature.

Boeing has separately been working to finalize a redesign of the software, known as MCAS, that was mistakenly triggered by the faulty sensor readings. The last major milestone is an FAA certification flight that the company expects to conduct shortly.

TribLIVE commenting policy

You are solely responsible for your comments and by using TribLive.com you agree to our Terms of Service.

We moderate comments. Our goal is to provide substantive commentary for a general readership. By screening submissions, we provide a space where readers can share intelligent and informed commentary that enhances the quality of our news and information.

While most comments will be posted if they are on-topic and not abusive, moderating decisions are subjective. We will make them as carefully and consistently as we can. Because of the volume of reader comments, we cannot review individual moderation decisions with readers.

We value thoughtful comments representing a range of views that make their point quickly and politely. We make an effort to protect discussions from repeated comments either by the same reader or different readers

We follow the same standards for taste as the daily newspaper. A few things we won't tolerate: personal attacks, obscenity, vulgarity, profanity (including expletives and letters followed by dashes), commercial promotion, impersonations, incoherence, proselytizing and SHOUTING. Don't include URLs to Web sites.

We do not edit comments. They are either approved or deleted. We reserve the right to edit a comment that is quoted or excerpted in an article. In this case, we may fix spelling and punctuation.

We welcome strong opinions and criticism of our work, but we don't want comments to become bogged down with discussions of our policies and we will moderate accordingly.

We appreciate it when readers and people quoted in articles or blog posts point out errors of fact or emphasis and will investigate all assertions. But these suggestions should be sent via e-mail. To avoid distracting other readers, we won't publish comments that suggest a correction. Instead, corrections will be made in a blog post or in an article.