How did MCAS software contribute to the fatal dive?

Question

Accepted Answer

Preliminary Report Indicates MCAS Software Played a Role in Fatal Dive

The preliminary report into the Ethiopian Airlines Flight 302 crash is expected to detail how the MCAS anti-stall software, triggered by faulty sensor data, contributed to the aircraft's fatal dive. Investigators are examining whether the flight crew's actions, specifically their decision to restore electrical power to the system after initially disabling it, exacerbated the situation by re-engaging the automated nose-down movements.
Faulty Sensor Data and MCAS Activation

Evidence suggests that the MCAS software, designed to prevent stalls by lowering the aircraft's nose, activated due to erroneous airflow data from a single sensor measuring the 'angle of attack.' This issue mirrors the circumstances of the earlier Lion Air crash, where the same software is suspected of malfunctioning. The faulty data caused the system to repeatedly push the nose of the Ethiopian Airlines jet downwards, an action intended to increase airflow under the wings.
Crew's Attempt to Disable and Subsequent Re-engagement

In contrast to the Lion Air crew, the pilots of Ethiopian Airlines Flight 302 successfully used switches to disengage the MCAS system. However, reports indicate that the software later re-engaged. The upcoming report is anticipated to provide crucial insights into the specific reasons behind the crew's decision to restore electrical power to the system, a move that could have reactivated the problematic automated commands.
Potential Pilot Actions and Aircraft Attitude

One theory under investigation is that pilots may have deliberately re-activated the MCAS system to simplify aircraft control and trimming procedures. This action, however, may have led to them being overwhelmed by the rapid counter-movements initiated by the software. Initial flight data suggests the aircraft was in a nose-heavy attitude when the pilots activated the cut-out switches, a condition that would have made managing the situation more challenging. Standard cockpit procedures typically require the MCAS system to remain disengaged for the remainder of the flight once it has been shut off.

Reading history

Hide →

This history is cleared when the page is closed.

How did MCAS software contribute to the fatal dive?

Loading

Was this article helpful?

Helpful

Not helpful

Report an issue

1

0

0

Share with friends