What happened
The MD-11 was cleared for a visual approach to runway 24R, positioned three miles and approximately one minute behind a Boeing 747 that was landing on the parallel runway 24L. The two runways were separated by 550 feet, with the threshold of runway 2fly 24L staggered 4,300 feet beyond that of runway 24R.
During the final approach, the captain utilized the Visual Approach Slope Indicator (VASI), which provided a 3.25-degree glide path. A left crosswind of 21 knots diminished to approximately 5 knots during the descent. At 100 feet above ground level, the aircraft exhibited a left roll followed by a right roll and slight yawing. At approximately 50 feet above ground level, the aircraft entered a high sink rate.
The captain initiated a go-around and raised the aircraft's nose. During this maneuver, the lower aft fuselage struck the runway, causing the aircraft to bounce. The captain then discontinued the go-around attempt, and the aircraft bounced two additional times. The impact resulted in damage to the aft pressure bulkhead.
During the final 20 seconds of the flight, the MD-11 maintained an average descent rate of 1,380 feet per minute at a speed of 152 knots, with an approach angle of 5.12 degrees.
Findings
The investigation found that while the MD-11 flight manual addressed visual approaches, go-around procedures, and tail or wing clearance issues, the operator lacked formal tailstrike awareness training for its pilots. Following the accident, the operator implemented a new training program focusing on bounced landing recovery and simulator training, which included limiting pitch attitude to 7.5 degrees during recovery.
Additionally, it was noted that the tower controller did not issue any precautions regarding wake turbulence. The Aeronautical Information Manual (AIM) recommends that when landing on a parallel runway behind a larger aircraft at a distance of less than 2,500 feet, pilots should remain above the flight path of the preceding aircraft.