* Flight CX509 involved 203 passengers and 12 crew.
* The incident occurred on July 3 at Tokyo's Narita airport.
* During an aborted landing in adverse weather, the tail section of the Airbus A330-343's fuselage contacted the surface of the south runway at Hong Kong International Airport.
* The aircraft landed safely with no reports of injuries.
* The investigation classified the case as an "abnormal runway contact" accident.
* Post-flight inspection showed abrasion on the lower fuselage skin and damage to the potable water service door, waste service door, and aft water drain mast.
* The aft cargo compartment was deformed, showing cracks in floor beam webs, floor beam supports, slope panel supports, and frame beams.
* A floor crossbeam support strut was broken, and a 10-inch crack was found on the bottom section of the aft pressure bulkhead.

An incident occurred on July 3 involving flight CX509 from Tokyo at Narita airport, which involved an aborted landing known as a go-around in adverse weather conditions. During this event, the tail section of the Airbus A330-343's fuselage made contact with the surface of the south runway at Hong Kong International Airport. The aircraft subsequently landed safely without any reports of injury to passengers or crew.
Following the incident, an investigation was conducted by the Air Accident Investigation Authority. This authority classified the event as an "abnormal runway contact" accident. Post-flight inspection revealed damage, including abrasion on the lower fuselage skin and damage to the potable water service door, waste service door, and aft water drain mast. Furthermore, deformation was noted in the aft cargo compartment, with cracks found in several floor beam webs, floor beam supports, slope panel supports, and frame beams. A floor crossbeam support strut was broken, and a 10-inch crack was found on the bottom section of the aft pressure bulkhead.

The shift from an operational event to an official classification as an "abnormal runway contact" suggests a necessary recognition that standard operating parameters were exceeded, prompting a formal inquiry into deviations that occurred during critical phases of flight. The documentation details physical damage to both the external structure and internal load-bearing components of the aircraft following the contact. This sequence—event, impact, inspection revealing structural compromise—establishes a pattern where operational anomalies lead directly to forensic analysis of material integrity.
The focus on specific structural elements like floor beam webs, frame beams, and pressure bulkheads implies that safety assessments in aviation must account not just for flight control and airframe integrity during normal operations but also for the resilience of the structure under extreme or erroneous physical stresses. The implication is that identifying anomalous runway contact necessitates a comprehensive evaluation of structural tolerances to understand why specific components sustained damage beyond normal wear. The missing element is the broader systemic context: what procedural failures allowed the go-around, and how does this material evidence inform future regulatory standards on airframe stress tolerance?
Bridge Questions: What were the environmental conditions precisely when the aborted landing occurred that contributed to the deviation? How do these specific findings regarding fuselage and floor beam damage correlate with existing aviation standards for post-impact structural fatigue analysis? What institutional checks need to be established to ensure that anomalous runway contacts trigger proactive, rather than reactive, reviews of airframe design tolerances?