Night Before Crash, Boeing 737 MAX Encounters Same Solved Problems
- 5 years ago
The pilots of a Boeing 737 MAX quickly scoured a manual before their plane collided with the Java Ocean in October, executing every one of the 189 individuals ready.
Chronicles from the cockpit of the Lion Plane recommend that the pilots were attempting to comprehend why the stream was swaying downwards, however came up short on time before it hit the water.
Two minutes into the flight, the principal officer revealed a "flight control issue" to airport regulation and said that they proposed to keep up a height of 5,000ft.
The skipper was at the controls of the almost new plane when it took off from Jakarta, and as a marker demonstrated an issue on his presentation, he requested that the primary officer counsel a handbook containing agendas for unusual occasions.
For nine minutes, the stream cautioned pilots it was in a slow down - which means it couldn't create lift and continue flying - and drove the nose down accordingly.
In spite of the fact that the commander battled to keep climbing, the PC mistakenly detected a slow down and kept on driving the nose down.
Specialists are analyzing how a PC requested the plane to make a plunge reaction to information from a broken sensor, and whether the pilots were enough prepared to react to the crisis.
Already, it developed that an alternate team on the equivalent Boeing 737 MAX experienced comparative issues a night prior to the accident, yet had figured out how to tackle the issue in the wake of going through three agendas.
Be that as it may, the pilots in control at the season of the accident had not been completely advised about what occurred.
Chronicles from the cockpit of the Lion Plane recommend that the pilots were attempting to comprehend why the stream was swaying downwards, however came up short on time before it hit the water.
Two minutes into the flight, the principal officer revealed a "flight control issue" to airport regulation and said that they proposed to keep up a height of 5,000ft.
The skipper was at the controls of the almost new plane when it took off from Jakarta, and as a marker demonstrated an issue on his presentation, he requested that the primary officer counsel a handbook containing agendas for unusual occasions.
For nine minutes, the stream cautioned pilots it was in a slow down - which means it couldn't create lift and continue flying - and drove the nose down accordingly.
In spite of the fact that the commander battled to keep climbing, the PC mistakenly detected a slow down and kept on driving the nose down.
Specialists are analyzing how a PC requested the plane to make a plunge reaction to information from a broken sensor, and whether the pilots were enough prepared to react to the crisis.
Already, it developed that an alternate team on the equivalent Boeing 737 MAX experienced comparative issues a night prior to the accident, yet had figured out how to tackle the issue in the wake of going through three agendas.
Be that as it may, the pilots in control at the season of the accident had not been completely advised about what occurred.