U.S. House Confronts Boeing CEO with New Documents on 737 Max (UPDATE)

Those documents included an email in which a Boeing engineer questioned in 2015 whether the Max was vulnerable to the failure of a single sensor — the scenario that led to crashes in Indonesia and Ethiopia. (Photo: Boeing CEO Dennis Muilenburg testifies before a Senate hearing on Capitol Hill in Washington, October 29, 2019. (Photo: Reuters)

The Washington Post

Oct. 30, 2019

House Committee Confronts Boeing CEO with New Documents on 737 Max Safety

House Democrats on Wednesday revealed key documents from their investigation into the deadly crashes of two 737 Max jets, pressing Boeing’s chief executive for more answers as he returned to Capitol Hill for a second day of hearings.

Those documents included an email in which a Boeing engineer questioned in 2015 whether the Max was vulnerable to the failure of a single sensor — the scenario that led to crashes in Indonesia and Ethiopia.

“This was raised by one of your engineers,” Rep. Peter A. DeFazio (D-Ore.) said to Boeing chief executive Dennis Muilenburg, and John Hamilton, chief engineer of the company’s commercial airplanes division.

DeFazio, chairman of the House Transportation Committee, was reading from a December 2015 email sent while the Max was in the middle of its safety certification process with the Federal Aviation Administration.

The critical sensors, known as angle of attack (AOA) indicators, are supposed to give pilots, and airplane systems, reliable information to help understand how the aircraft’s nose is pointed in relation to oncoming wind.

But in both crashes, faulty data from a single sensor caused an automated feature known as the Maneuvering Characteristics Augmentation System, or MCAS, to fire by mistake, repeatedly forcing the planes’ noses down as pilots struggled to regain control. Boeing’s decision to have MCAS rely on just one sensor, and not both of them, has been a key question in the crash investigations.

Read more »

Boeing CEO grilled at U.S. hearing: ‘We’ve made mistakes’


Oct. 29, 2019

WASHINGTON (Reuters) – Boeing Co Chief Executive Dennis Muilenburg was pressed by U.S. lawmakers at a hearing on Tuesday over what the company knew about its MCAS stall-prevention system linked to two deadly crashes, and about delays in turning over internal 2016 messages that described erratic behavior of the software in a simulator.

Muilenburg acknowledged errors in failing to give pilots more information on MCAS before the crashes, as well as for taking months to disclose that it had made optional an alarm that alerts pilots to a mismatch of flight data on the 737 MAX.

“We’ve made mistakes and we got some things wrong. We’re improving and we’re learning,” he said.

The hearing, the highest-profile congressional scrutiny of commercial aviation safety in years, heaps pressure on a newly rejigged Boeing senior management team fighting to repair trust with airline customers and passengers shaken by an eight-month safety ban on its 737 MAX following the crashes, which killed 346 people.

Taking turns to grill Muilenburg during his first appearance at a hearing on Capitol Hill in the year since the first crash in Indonesia, senators suggested Boeing had not been completely honest and expressed dismay that the 2016 instant messages did not prompt an immediate reaction from the company.

“You have told this committee and you have told me half-truths over and over again,” Senator Tammy Duckworth of Illinois, where Boeing is headquartered, said at one point.

Later in the hearing, Senator Jon Tester of Montana said: “I would walk before I would get on a 737 MAX … You shouldn’t be cutting corners.”

For months, Boeing had largely failed to acknowledge blame, instead vowing to make a “safe plane safer.” Tuesday’s hearing represents Boeing’s broadest acceptance of responsibility that it made mistakes, though Muilenburg and senior engineering executive John Hamilton stopped short of a game-changing display of contrition.

U.S. Senator Roger Wicker, chairman of the Senate Commerce Committee, questioned Muilenburg over the company’s delay in releasing internal messages. In those messages, a former test pilot described erratic behavior of a simulator version of the same software now linked to the crashes, and also mentioned “Jedi-mind tricking” regulators over training requirements.

Wicker said those messages revealed a “disturbing level of casualness and flippancy.”

Muilenburg said he apologized to the FAA administrator for the delay in turning over the messages, and said additional documents would likely be provided over time.

“We will cooperate fully,” he added.

In his opening remarks, Muilenburg walked the committee through software upgrades to limit the authority of the stall-prevention system that has been linked to both crashes. He also listed changes at the company and its board of directors to improve safety oversight and transparency.

During one particularly tense exchange, Senator Maria Cantwell of Washington grilled Muilenburg and Hamilton over the extent of testing on the MCAS system. Cantwell asked Hamilton whether it was a mistake for Boeing not to test a failure mode similar to the scenarios faced by pilots in the crashes.

“In hindsight, senator, yes”, Hamilton said. Both he and Muilenburg, however, pointed to extensive testing by engineers and pilots during the certification process that lasted years.

Muilenburg also acknowledged a “mistake on that implementation” for failing to tell the FAA for 13 months that it inadvertently made a so-called angle of attack disagree alert optional on the 737 MAX, instead of standard as on earlier 737s. The company insisted the missing display represented no safety risk.

“We got the implementation wrong,” Muilenburg said, referring to the angle of attack disagree alert.

He added: “One of the things we’ve learned … is we need to provide additional information on MCAS to pilots.”

At one point, Senator Richard Blumenthal of Connecticut referred to the 737 MAX as “flying coffins.”

Asked ahead of the hearing if he would resign, Muilenburg said that was “not where my focus is.” He also declined to say if he or the board were considering his resignation after the plane returns to service.

Boeing on Tuesday ran full-page advertisements in major newspapers expressing condolences to the families and loved ones of those killed in the crashes.

“These two accidents occurred on my watch and I have a keen sense of responsibility,” Muilenburg, who was stripped of his title as Boeing chairman by the board earlier this month, told reporters.

Family members, holding photos of victims of the crash, were seated just three rows behind Muilenburg during his testimony.

Wicker addressed the families, saying: “I promise to their loved ones that we will find out what went wrong and work to prevent future tragedies.”

Indonesian investigators reported on Friday that Boeing, acting without adequate oversight from U.S. regulators, failed to grasp risks in the design of cockpit software on the 737 MAX, sowing the seeds for the Oct. 29, 2018, crash of Lion Air Flight 610.

On Tuesday, Muilenburg denied that Boeing’s initial statements about the investigative findings from the Lion Air crash sought to shift blame onto pilots.

Muilenburg also rejected a characterization of Boeing’s “coziness with the FAA,” though he said the certification process “can be improved.”

Muilenburg was then asked why Boeing had not grounded the plane in the wake of Lion Air Crash. “If we could go back, we would make a different decision,” he said.

2 Years Before Deadly Ethiopia Crash, Boeing Staff Knew of 737 Max Problems
Boeing CEO Apologizes to Victims of Ethiopia, Indonesia Crashes
Ethiopian Airlines Slams Bloomberg’s Ex-Pilot Story as ‘Baseless & False Allegation’
Read Excerpt From Ethiopia Crash Report
Ethiopian Airlines Expresses Disappointment – Calls Out Media Outlets Eager to Blame Pilot

Watch: Ethiopian CEO on The Future of Boeing 737 Max Planes — NBC Exclusive

Watch: Ethiopia Releases 737 Max Preliminary Crash Report

Join the conversation on Twitter and Facebook.













Copy Protected by Chetan's WP-Copyprotect.