Exclusive: High speed, then a failed climb for doomed Ethiopia flight

 in.reuters.com  03/17/2019 05:52:00 

ADDIS ABABA (Reuters) - Ethiopian Airlines flight 302, which crashed killing 157 people, had an unusually high speed after take-off before the plane reported problems and asked permission to climb quickly, said a source who has listened to the air traffic control recording.

Villagers walk past flowers set to commemorate the Ethiopian Airline Flight 302 victims that crashed near the town of Bishoftu, near Addis Ababa, March 14, 2019. REUTERS/Tiksa Negeri

A voice from the cockpit of the Boeing 737 MAX requested to climb to 14,000 feet above sea level - about 6,400 feet above the airport - before urgently asking to return, the source told Reuters on condition of anonymity because the recording is part of an ongoing investigation.

The plane vanished from radar at 10,800 feet.

“He said he had a flight control problem. That is why he wanted to climb,” the source said, adding there were no further details given of the exact problem and the voice sounded nervous.

Experts say pilots typically ask to climb when experiencing problems near the ground in order to gain margin for manoeuvre and avoid any difficult terrain. Addis Ababa is surrounded by hills and, immediately to the north, the Entoto Mountains.

The New York Times reported Captain Yared Getachew’s voice was on the recording but the Reuters source was not familiar with his voice or that of the first officer Ahmed Nur Mohammod Nur to verify which man was speaking. However, it was the same voice throughout, the source said.

The U.S. Federal Aviation Administration on Wednesday followed other countries in grounding the 737 MAX, citing satellite data and evidence from the scene that indicated some similarities and “the possibility of a shared cause” with October’s Lion Air crash in Indonesia that killed 189 people.

On Saturday, investigators began studying the cockpit voice recorder. Along with the flight data recorder, the information will be evaluated by Ethiopian authorities, teams from Boeing, and U.S. and EU aviation safety authorities to try to determine the cause of the crash.

HIGH SPEED, FAILED CLIMB

The Ethiopian flight was set to follow the Standard Instrument Departure (SID) from the airport and followed standard procedure with a first contact just after departure, the source said. Everything appeared normal.

After one or two minutes, the voice on the air traffic control recording requested to remain on the same path as the runway and to climb to 14,000 feet, the source said.

The aircraft’s ground speed after departure was unusually high, the Reuters source said, reaching around 400 knots (460 miles per hour) rather than the 200 to 250 knots that is more typical minutes after departure.

“That is way too fast,” the source said.

No more than two minutes later, the air traffic controller was in communication with other aircraft when the voice from Ethiopian Airlines flight 302 interrupted, saying “break, break” - signalling that other nonurgent communications should cease. He sounded very scared, the source said.

“He requested permission to return. Air traffic control granted him permission to turn on the right because to the left is the city,” he said. “Maybe one minute passed before the blinking dot on the radar disappeared.”

After starting the turn, the plane disappeared from radar at an altitude of 10,800 feet above sea level, the highest it reached during the six-minute flight. Addis Ababa’s runway is at a high elevation of around 7,600 feet, suggesting the doomed jet made it about 3,000 feet into the sky.

Flight tracking website FlightRadar24 had data covering the first half of the flight but it dropped out at 8,600 feet.

Other satellite data tracking the plane has not been made available publicly. In the Lion Air crash, investigators are examining the behaviour of a new anti-stall system installed on the 737 MAX that led to the plane gaining and losing altitude as the pilots fought for control against the automated system.

Boeing is expected to finalise a software fix for that system within a week to 10 days, sources familiar with the matter said earlier on Saturday.

Reporting by Maggie Fick; Additional reporting by Katharine Houreld, Jamie Freed, Tim Hepher; Editing by Leigh Thomas, Editing by William Maclean

Our Standards:The Thomson Reuters Trust Principles.

« Go back