What happened
On 2 January 2022, an Airbus A350-1041, registration G-XWBC, was completing a commercial passenger flight from Dubai to London Heathrow. During the approach to Runway 27L, the aircraft encountered gusty wind conditions. As the aircraft entered the flare at approximately 50 ft, it began to float along the runway surface. Fearing the aircraft would touch down beyond the runway touchdown zone (TDZ), the commander initiated a go-around in accordance with company policy.
Because the thrust levers had been retarded to idle, the engines required several seconds to spool up to the required takeoff/go-around power. During this period of low energy, the co-pilot applied a significant nose-up control input, reaching nearly full aft movement on the sidestyle. This rapid pitch rate, combined with the aircraft's low airspeed, caused the aircraft to briefly touch the runway. As the aircraft was climbing, the pitch attitude reached a level sufficient to cause the tail to strike the runway surface.
The investigation
The AAIB examined the aircraft's flight data recorder and cockpit voice recorder, which confirmed the sequence of events. The investigation focused on the flight dynamics during the transition from landing to go-around. The investigators noted that while the aircraft had sufficient runway remaining to complete a safe landing, the crew's adherence to the operator's 'Safe Landing Policy' necessitated the rejected landing.
Physical inspections of G-XWBC revealed damage to the lower rear fuselage, including the toilet waste panel and the tailstrike sensor. The investigation also looked into the aircraft's automated systems, specifically the tailstrike pitch limit indicators and the runway overrun protection systems, to determine if any warnings could have mitigated the event.
Findings
- The go-around was initiated at a low altitude and low airspeed.
- The aircraft lacked the immediate performance to climb without touching the runway due to the delay in engine thrust development.
- The co-pilot's high pitch rate input caused the aircraft to reach a nose-up attitude that resulted in the tailstrike.
- The crew acted in accordance with the operator's policy to reject a landing if a touchdown beyond the TDZ is anticipated.