Brief Summary
This video tells the story of a US Airways flight that experienced a near-catastrophic incident during takeoff. The incident was caused by a combination of human error and a misunderstanding of aircraft systems. The crew failed to properly verify the flight management computer (FMC) settings after changing the runway, leading to a situation where the aircraft was accelerating without proper takeoff speeds and thrust settings. The captain, experiencing confusion and doubt, ultimately decided to reject the takeoff after the aircraft had already rotated, resulting in a violent impact and damage to the aircraft.
- The crew failed to properly verify the FMC settings after changing the runway.
- The captain rejected the takeoff after the aircraft had already rotated, resulting in a violent impact and damage to the aircraft.
The Incident
The video begins by introducing the captain and first officer involved in the incident. Both were highly experienced pilots with extensive flight hours. On March 13th, 2014, the crew was operating a US Airways flight from Philadelphia to Fort Lauderdale. The weather conditions were clear with strong gusty winds in the Philadelphia area. The crew was assigned to operate three flights in total, starting with a flight from Charlotte to Tampa.
During the aircraft change in Philadelphia, the first officer mistakenly entered the wrong runway into the FMC. This error was not caught during the later route clearance verification procedure. The crew then received clearance to line up and wait on runway 27 left, but the captain noticed the incorrect runway setting in the FMC. Instead of calling back the air traffic control (ATC) to request a hold, the captain instructed the first officer to quickly change the runway setting.
The Consequences
Changing the runway in the FMC automatically cleared all performance data, including the takeoff speeds and flex temperature. The first officer, in her rush to change the runway, missed the amber scratchpad message and red speed select message on the primary flight displays, leaving the performance fields blank. The aircraft was now lined up and ready for departure without proper takeoff speeds and thrust settings.
As the aircraft accelerated, the captain moved the thrust levers into the flex detent, triggering an ECAM warning indicating that the engine thrust levers were not set correctly. The captain attempted to correct the issue by moving the thrust levers back into the climb detent and then back into the flex detent, but the warning persisted. The aircraft continued to accelerate, and the captain missed the 80-knot callout, which marks the transition from the low-speed to the high-speed takeoff regime.
The Rejection
As the aircraft passed 86 knots, an oral alert activated, causing confusion for the crew. The captain realized that they were missing the V-speeds and called out, "Uh what did you do you didn't load we lost everything." The aircraft was now well above 100 knots, and the captain decided against rejecting the takeoff in the high-speed regime. He continued the takeoff, with the alert still blaring in the background.
The captain, likely experiencing a combination of confusion, the blaring alert, and the absence of callouts from the first officer, suddenly decided that the aircraft was unsafe to fly. As the aircraft accelerated past 167 knots, he abruptly moved the thrust levers to idle and pushed his side stick forward. This action resulted in a violent pitch forward, causing the nose gear to slam into the runway. The aircraft bounced back into the air before finally coming to a stop with the nose gear completely collapsed.
The Aftermath
The aircraft sustained significant damage and was eventually written off. All 154 passengers and crew evacuated safely with only two minor injuries. The investigation concluded that the probable cause of the accident was the captain's decision to reject the takeoff after the aircraft had already rotated and above V1. The investigation also highlighted the crew's failure to follow standard operating procedures by not verifying the FMC settings after changing the runway.
The video concludes with a reminder for young pilots to speak up if they notice any errors or inconsistencies during flight operations. The captain will ultimately make the final decision, but it is crucial for the crew to communicate any concerns and ensure that standard operating procedures are followed.
