A Cathay Pacific Airbus A330-300 suffered a tailstrike while conducting a go-around at Hong Kong International Airport, with photographic evidence of the damage surfacing in the days following the incident. While detailed specifics of the flight number, registration, and exact circumstances remain limited in initial reporting, the visible damage to the aft fuselage and tail skid area confirms that the aircraft made hard contact with the runway during the abnormal maneuver. Tailstrikes during go-arounds are less common than those occurring during landing or takeoff rotation, making this event notable from a training and human-factors perspective, as it suggests a possible mishandling of pitch attitude during the transition from a landing configuration back to a climb profile.
Go-around tailstrikes typically occur when a crew, often already configured with a high angle of attack for landing, applies aggressive nose-up input during the go-around initiation, particularly if power application and pitch control inputs are not properly sequenced. The A330's geometry, with its long fuselage and tail-mounted skid, leaves relatively little margin between normal landing pitch attitudes and the angle at which tail contact occurs. This margin shrinks further if the go-around is initiated late, if the aircraft is heavier than expected, if trim settings are not adjusted for the change in thrust, or if there is any element of surprise or rushed decision-making involved, such as a late runway incursion, a wind shear alert, or an unstable approach criteria breach prompting the go-around call.
For working pilots, this incident serves as a reminder of the criticality of disciplined go-around technique, particularly the initial pitch and power inputs immediately following the decision to abort a landing. Airlines have increasingly emphasized go-around training in recurrent simulator sessions following a string of industry incidents, including several high-profile tailstrikes and even the 2016 Emirates 777 crash in Dubai, where a mismanaged go-around after a bounced landing proved fatal. Cathay Pacific, like most major carriers, trains this maneuver as a memory item with strict pitch and thrust lever sequencing, and any deviation, whether from muscle memory under stress or ambiguity in crew coordination, can produce exactly this kind of outcome. The fact that the strike occurred at a major international hub with an experienced widebody operator underscores that tailstrikes are not solely a function of inexperience but can occur even within mature, well-trained crews, particularly under compressed decision timelines.
From a broader industry perspective, this event will likely feed into ongoing discussions about go-around monitoring and automation. Modern flight data monitoring (FDM) programs are specifically designed to flag exceedances such as this, and Cathay Pacific will almost certainly conduct a thorough investigation examining flight data recorder traces, pitch rates, and crew callouts to determine root cause. Airbus, too, may review whether existing alpha-floor and pitch-limiting protections functioned as intended or whether there are opportunities for enhanced tailstrike protection logic, an area some manufacturers have already begun addressing through software-based pitch attitude alerting systems. For operators, the incident also carries real financial and operational weight, as tailstrike damage typically requires borescope inspections, structural assessments, and potentially extended aircraft-on-ground time, reinforcing why prevention through rigorous training remains far cheaper than post-incident repair and investigation.