Stay up to date with notifications from The Independent

Notifications can be managed in browser preferences.

Lion Air crash: Boeing pilots had ‘40 seconds to fix error’ in simulation of deadly flight

All 189 people on board flight 610 died after plane nosedived into Java Sea

Jack Nicas,David Gelles,James Glanz
Tuesday 26 March 2019 16:33 GMT
Comments
Navy divers recover cockpit voice recorder of Lion Air jet that crashed into the Java Sea in October

Your support helps us to tell the story

From reproductive rights to climate change to Big Tech, The Independent is on the ground when the story is developing. Whether it's investigating the financials of Elon Musk's pro-Trump PAC or producing our latest documentary, 'The A Word', which shines a light on the American women fighting for reproductive rights, we know how important it is to parse out the facts from the messaging.

At such a critical moment in US history, we need reporters on the ground. Your donation allows us to keep sending journalists to speak to both sides of the story.

The Independent is trusted by Americans across the entire political spectrum. And unlike many other quality news outlets, we choose not to lock Americans out of our reporting and analysis with paywalls. We believe quality journalism should be available to everyone, paid for by those who can afford it.

Your support makes all the difference.

Flight simulations recreating the problems with the Lion Air plane that crashed last year have revealed pilots had less than 40 seconds to override an automated system to avert disaster, according to airline sources.

The pilots tested a crisis situation similar to what investigators suspect went wrong in Lion Air flight 610, which killed all 189 people on board after it crashed into the Java Sea.

In the tests, a single sensor failed, triggering software designed to help prevent a stall.

Once that happened, the pilots had just moments to disengage the system and avoid an unrecoverable nosedive of the Boeing 737 Max, according to two people involved in the testing in recent days.

Although the investigations are continuing, the automated system, known as MCAS, is a focus of authorities trying to determine what went wrong in the Lion Air disaster in October and the Ethiopian Airlines crash of the same Boeing model this month.

The software, as originally designed and explained, left little room for error.

Those involved in the testing had not fully understood just how powerful the system was until they flew the plane on a 737 Max simulator, according to the two people.

In a tacit acknowledgement of the system’s problems, Boeing is expected to propose a software update that would give pilots more control over the system.

This would make it less likely to trigger erroneously, according to three people familiar with the private meetings and who spoke on the condition of anonymity.

There are common procedures in place to counteract MCAS, as currently designed.

If the system starts pushing the plane’s nose down, pilots can reverse the movement via a switch at their thumb, a typical reaction in that situation. To fully neutralise the system, pilots would need to flip two more switches.

That would shut off the electricity to a motor that allows the system to push the plane towards the ground. Then the pilots would need to crank a wheel to correct whatever problems had emerged.

In the Lion Air crash, pilots used the thumb switch more than two dozen times to try to override the system.

Support free-thinking journalism and attend Independent events

The system kept engaging nonetheless, most likely because of bad readings from a sensor, until the plane crashed into the Java Sea, killing all 189 people on board.

The software changes require approval by the Federal Aviation Administration.

New York Times

Join our commenting forum

Join thought-provoking conversations, follow other Independent readers and see their replies

Comments

Thank you for registering

Please refresh the page or navigate to another page on the site to be automatically logged inPlease refresh your browser to be logged in