Sort:  

Part 1/9:

The Tragedy of Emirates Flight 521: A Detailed Analysis of a Go-Around Gone Wrong

On August 3, 2016, Emirates Airlines Flight 521, a Boeing 777, made a fateful approach to Dubai International Airport when a series of unfortunate decisions and unforeseen circumstances led to a catastrophic incident. This detailed analysis seeks to unravel the factors that contributed to this tragedy, illustrating the complexities often involved in aviation incidents that may seem straightforward at first glance.

The Flight in Context

Part 2/9:

Flight 521 was operating a routine service from Thiruvananthapuram, India, to Dubai. The aircraft was manned by a proficient crew: a 34-year-old captain with substantial experience, having logged nearly 7,500 flight hours, with over 5,000 hours on the Boeing 777; and a 37-year-old first officer with nearly 8,000 hours of total time but only 1,300 hours on the 777. Both pilots reported feeling well-rested and in good spirits ahead of the flight, which boded well for professionalism on board.

As the flight approached Dubai under less than ideal weather conditions, they received necessary updates about potential wind shear generated by gusty winds and the local weather patterns. The possibility of thermals, which create pockets of rising warm air, was also discussed in the cockpit.

Part 3/9:

Pre-Approach Briefing

The pilots engaged in thorough preparatory discussions about the RNP approach to Runway 12 Left. During this briefing, the captain emphasized the importance of being ready for a wind shear escape maneuver, especially considering the predicted changes in wind conditions. The crew's familiarity with procedures and their ability to communicate effectively showcased sound cockpit resource management (CRM).

Part 4/9:

Despite the good communication, it is critical to highlight that Emirates Airlines mandated the use of auto-throttle for all phases of flight, which complicated the approach. Both pilots had trained primarily with this assistive technology guiding their throttle settings, but the manuals contained little emphasis on situations where autothrottle might become irrelevant—an aspect that would prove fatal during the incident.

The Final Moments Before the Approach

As Flight 521 began descending towards Dubai, they made contact with the approach controller. However, they were unaware of two preceding flights that had gone around for similar wind conditions. This lack of information likely contributed to their subsequent complacency regarding the approach.

Part 5/9:

When cleared for the landing, the pilots were informed of wind conditions indicating a tailwind that steadily increased as they approached. This shift should have raised alarms, but the pilots trusted in the aircraft's capabilities and their own training.

At 750 feet, the captain disengaged the autopilot, preparing for a manual landing—a common and expected procedure for experienced pilots. However, the increasing tailwind was becoming problematic as the aircraft moved through the final stages of the approach.

The Go-Around Decision

Part 6/9:

As the aircraft crossed the threshold, the pilots may have sensed a deteriorating situation. At about 54 feet, a critical decision point approached. The aircraft, now floating above the runway due to a sudden increase in wind status, prompted the captain to initiate the go-around procedure. However, a significant oversight took place here: the autothrottle was inhibited after touchdown, which meant that the engines remained at idle thrust when they should have been powered up for a climb.

Caught in the moment, the crew did not notice the lack of thrust, relying heavily on their training which conditioned them to expect the autothrottle to manage engine power. This created a dire situation as the aircraft descended back towards the runway despite the captain's best efforts.

The Crash

Part 7/9:

With engines still at idle, the aircraft could not maintain altitude. After a series of alarms and additional attempts to regain control, the Boeing 777 ultimately crashed onto Runway 12 Left at Dubai Airport, its rear touching ground first. The impact caused one of the engines to separate from the fuselage, igniting fires that spread rapidly.

Miraculously, all 300 people on board survived, largely due to the commendable efforts of the cabin crew during the evacuation, even as thick smoke filled the cabin. Unfortunately, the chaos resulted in the death of a firefighter who was responding to the scene when the aircraft's fuel exploded.

Investigation and Lessons Learned

Part 8/9:

Immediately following the incident, investigations began, revealing a systemic failure fueled by multiple factors: over-reliance on automation, training shortcomings regarding go-arounds, procedural neglect of thrust verification, and a lack of cockpit warnings regarding inhibited switches.

Key recommendations stemmed from this tragedy, focusing on improving CRM training, enhancing pilot training procedures related to go-arounds, and reconsidering when ATC should communicate with an aircraft during critical phases like landing. Moreover, airlines were urged to reevaluate their operational procedures concerning automation, particularly in high-stakes scenarios.

Conclusion

Part 9/9:

The case of Emirates Flight 521 serves as a profound reminder of the complexity of aviation operations and the intricacies of human factors in crisis situations. It underscores the importance of maintaining vigilance, even in familiar environments, and illustrates how adherence to procedure can be lifesaving. Ultimately, aviation safety hinges not just on technology, but also on human performance, comprehensive training, and a thorough review of operational protocols to foster an environment where tragedies like this can be prevented in the future.