This video provides a detailed analysis of the fatal crash of FedEx Flight 80, a McDonnell Douglas MD-11 cargo aircraft, at Tokyo's Narita International Airport on March 23, 2009. The narrative explores the complex chain of events leading to the accident, focusing on three primary factors: the notoriously challenging handling characteristics of the MD-11 during landing, severe weather conditions with strong and gusty crosswinds, and the potential for crew fatigue inherent in overnight cargo operations.
The analysis breaks down the final moments of the flight, detailing how a late flare and out-of-sync control inputs from the first officer led to a hard initial touchdown and a subsequent bounce. The core of the accident sequence was a pilot-induced oscillation (PIO), where the pilot, likely misperceiving the aircraft's state, made repeated incorrect nose-down inputs. These actions resulted in two subsequent, increasingly violent impacts with the runway. The final impact exceeded the structural limits of the landing gear, causing the left wing to fail and rupture, leading to a catastrophic fire as the aircraft flipped upside down. The video also delves into the MD-11's design compromises and the airline's training gaps regarding bounce recovery, which were contributing factors to the tragic outcome.
The Crash of FedEx Flight 80: A Cascade of Failures
00:00:05 - The Incident: On the morning of March 23, 2009, FedEx Flight 80, an MD-11 cargo plane, crashed violently upon landing at Narita International Airport in Tokyo. The accident involved a crew of two pilots on an overnight flight from Guangzhou, China.
00:01:25 - The Crew: The crew consisted of a highly experienced 54-year-old captain and a 49-year-old first officer. The first officer, who was the pilot flying, had significant military cargo experience but was relatively new to the MD-11 with 879 hours on the type.
00:04:26 - The Aircraft's Quirks: The MD-11 was known among pilots for being "twitchy" and difficult to handle, especially during landing. Design compromises made to improve efficiency, such as a smaller tail plane and specific weight distribution, made it prone to large bounces and pilot-induced oscillations if not handled with precision.
00:07:43 - The Role of Fatigue: The crew was operating on the "back side of the clock," a typical schedule for cargo pilots that disrupts circadian rhythms. The pilots acknowledged on the CVR that they were tired, which can slow reaction times and impair judgment.
00:13:27 - Difficult Weather Conditions: The landing was challenged by strong and gusty winds, reported at 30 knots with gusts creating a 20-knot speed variation. These conditions, combined with wind shear, made for a turbulent and unstable final approach.
00:32:52 - A Known Risk: FedEx had previously lost another MD-11 (Flight 14 in 1997) in a near-identical bounce-and-crash landing. While the crew of Flight 80 had received initial bounce recovery training, it was not part of their recurrent training, and it focused more on preventing tail strikes.
00:36:23 - The Unstable Landing and First Bounce: The first officer initiated the flare late and made a series of out-of-sync pitch inputs. The aircraft landed hard at 1.63 Gs and bounced back into the air.
00:38:16 - Pilot-Induced Oscillation: After the first bounce, the first officer, likely believing the aircraft was on the ground, pushed the yoke forward to lower the nose. This incorrect input caused the plane to slam into the runway a second time, nose-gear first, with a force of 2.2 Gs.
00:41:32 - The Catastrophic Final Impact: The second impact resulted in a much higher bounce, reaching 16 feet. With no corrective power input and continued forward pressure on the yoke, the aircraft hit the runway a third and final time, exceeding 3 Gs.
00:41:50 - Structural Failure and Fire: The immense force of the third impact caused the left main landing gear to collapse and rupture the wing's fuel tank. The dragging wing caused the aircraft to roll over, catch fire, and slide to a stop upside down, tragically killing both pilots.
00:46:02 - Final Report and Key Takeaways: The accident was officially caused by the first officer's large nose-down inputs and the captain's failure to intervene. It serves as a stark reminder of how a combination of a challenging aircraft design, severe weather, potential fatigue, and training deficiencies can create a fatal failure chain.