A reported tailstrike involving a Vietnam Airlines Boeing 787-9 Dreamliner (registration VN-A867) at Munich Airport (EDDM) is circulating via social media, with the sole source being a brief Reddit post and accompanying video rather than an official statement from Vietnam Airlines, Munich Airport, the German BFU (Bundesstelle für Flugunfalluntersuchung), or EASA. The post indicates the aircraft was seen dumping fuel in the vicinity of Munich shortly after the event, which is consistent with an aircraft preparing to return for an overweight landing after a tailstrike shortly following takeoff, or alternatively burning down fuel prior to a precautionary landing after a rejected departure or in-flight abnormality. At this stage, no altitude, phase of flight, runway, or damage assessment has been confirmed, and pilots should treat the report as unverified until corroborated by NOTAMs, ATC recordings, FlightRadar24 track data, or an official carrier/regulatory release.
Tailstrikes remain one of the more common ground-contact events on wide-body jets, particularly on rotation during takeoff or during a hard/mishandled landing flare, and they carry real operational significance even when no injuries occur. On the 787 specifically, the aft fuselage geometry and the aircraft's relatively long body combined with a full-flight-envelope, fly-by-wire control law mean tailstrikes are usually associated with excessive pitch rate or over-rotation near VR, often exacerbated by aft CG loading, high gross weight, or a mis-set stabilizer trim/derate takeoff performance calculation. Airbus and Boeing wide-body fleets alike have tailstrike protection logic and audible/visual cues, but crew technique — particularly rotation rate discipline and avoiding "pulling through" the flight director command — remains the primary defense. When a tailstrike is suspected or confirmed, standard operating procedure typically calls for a precautionary return, structural inspection focusing on the aft pressure bulkhead and lower fuselage skin, and in many cases fuel jettison to get below max landing weight before landing, which aligns with the fuel-dumping activity described in the post.
For working pilots, incidents like this reinforce several recurring themes: the criticality of accurate weight-and-balance and takeoff performance data entry (a factor in several high-profile tailstrike events over the past decade, including notable cases with Emirates, Etihad, and Cathay Pacific aircraft), the importance of adhering to briefed rotation rates (typically 2-3 degrees per second) rather than reacting to a "sluggish" feel during heavy-weight departures, and the operational discipline required when executing an air turnback — coordinating with ATC for fuel dumping in controlled airspace, managing an overweight or near-max-landing-weight arrival, and ensuring emergency services are positioned for inspection upon landing. Munich, as a major European hub with significant long-haul wide-body traffic, has established procedures for exactly this kind of contingency, and the relatively fast response (fuel dumping observed within roughly 90 minutes of the reported event) suggests the crew followed a standard non-normal checklist flow rather than declaring a prolonged emergency.
More broadly, this event — however it is ultimately characterized once official data emerges — fits into a pattern the industry has been tracking closely: a modest but persistent rate of tailstrike occurrences across the global wide-body fleet, prompting renewed emphasis in recurrent training on rotation technique, go-around and rejected-takeoff decision-making, and rigorous cross-checking of load sheets and takeoff performance calculations, especially at airports with runway length or obstacle constraints. Operators and training departments will likely watch for the eventual incident report to determine whether this was a performance-data, technique, or environmental (e.g., gusting crosswind) factor, since each carries different fleet-wide corrective actions. Until Vietnam Airlines, EDDM, or German investigators release confirmed details, crews and dispatchers should treat this report as an early, unofficial account and await the formal safety bulletin or preliminary investigation summary before drawing operational conclusions.