Quick summary
A Vietnam Airlines Boeing 787-9 overran the runway at Munich Airport on August 15, 2026, sustaining damage to its landing gear and tail section after repeated brake pedal inputs were recorded during the takeoff roll. All 287 people on board were uninjured. Germany’s Federal Bureau of Aircraft Accident Investigation (BFU) released a status update on September 27–28, 2026, confirming the sequence of events but leaving the underlying cause unresolved. The aircraft remains grounded at Munich.
The BFU has not established whether the braking resulted from a system fault, cockpit action, or another factor. Human, technical, and organizational elements are all still under examination.
Six weeks after a Vietnam Airlines Boeing 787-9 overran the end of runway 26L at Munich Airport, German investigators still cannot say why the aircraft braked repeatedly during its takeoff roll. The BFU‘s latest public update, released in late September 2026, confirms the sequence: the jet departed at 13:57 local time, its tail contacted the runway during a late rotation, and tyre tracks were found at the runway end. The aircraft returned and landed on runway 26R at 15:58 — two hours after the incident began.
The crew released 62 tons of fuel before coming back. Landing gear and the tail section were damaged; runway lighting was also struck. Vietnam Airlines told Reuters that the crew followed required procedures and that passengers and cabin crew landed safely.
The involved aircraft has not returned to service.
For travelers on Europe–Vietnam routes, the immediate consequence is reduced aircraft availability on Vietnam Airlines‘ Munich services. The BFU’s update does not announce a fleet-wide grounding or any route-wide safety directive — this is a single-aircraft investigation, not a 787 operating prohibition.
What the BFU’s preliminary findings actually confirm
The BFU’s public status update draws a careful line between confirmed facts and open questions. On the facts side: repeated brake pedal inputs occurred during the takeoff roll, the aircraft rotated late, the tail contacted the runway surface, and tyre tracks at the runway end were attributed to the aircraft. On the open side: everything else.
The BFU has not determined whether those brake inputs came from a hardware fault in the braking control system, a crew action, or some combination of both. Human, technical, and organizational factors all remain to be assessed before causes can be established. That is standard language for an open investigation — it is not a finding, and it is not an exoneration.
Vietnam Airlines told Reuters that the crew followed required procedures. The airline has not publicly addressed the brake input data.
| Time (local) | Event | Status |
|---|---|---|
| 13:57 | Aircraft departs runway 26L; repeated brake inputs recorded during takeoff roll | Confirmed by BFU |
| During roll | Late rotation; tail contacts runway surface; tyre tracks at runway end | Confirmed by BFU |
| Post-departure | Crew releases 62 tons of fuel; declares emergency return to Munich | Confirmed |
| 15:58 | Aircraft lands on runway 26R; landing gear and tail section damaged | Confirmed by BFU |
| Post-incident | Aircraft grounded at Munich; investigation ongoing | Confirmed; cause unresolved |
No EASA or FAA airworthiness directive linked to this occurrence has been publicly reported. The BFU’s work continues.
Flight deals
most people never see
Our AI monitors 150+ airlines for pricing anomalies that traditional search engines miss. Air Traveler Club members save $650 per trip per person on average: see how it works.
Each deal saves 40–80% vs. regular fares:
Why the cause still matters — and what it doesn’t yet tell us
Takeoff runway overruns are rare enough that each one draws sustained regulatory attention. The 787-9’s braking architecture involves multiple redundant systems, and an unexplained pattern of brake inputs during a takeoff roll is precisely the kind of anomaly that investigators need to trace to a specific origin before they can close the file.
The distinction between a technical fault and a crew input is not academic. A confirmed hardware defect could trigger a service bulletin or airworthiness directive affecting the broader 787 fleet. A procedural finding would stay within the airline’s training and operations domain. Right now, the BFU has neither — and that gap is why the investigation remains open rather than moving toward a final report.
What the current update does not support is treating this as evidence of a systemic 787 brake problem. The BFU’s language is deliberately neutral: it describes what happened, not why. Tour operator reassurances and airline statements about procedure compliance are both beside the point until the technical analysis is complete.
Steps to take if you’re booked on Munich–Vietnam services
The grounded aircraft reduces Vietnam Airlines‘ available 787-9 capacity on the Munich route, and the BFU timeline for a final report is not yet public — meaning the disruption window is open-ended.
- Check your specific booking now: Log into Vietnam Airlines’ booking management tool and confirm your aircraft assignment and departure time. Equipment substitutions or schedule changes may already be in place without a proactive notification.
- Enable airline notifications: Turn on email and SMS alerts from Vietnam Airlines for your booking reference. The BFU update does not restrict other 787-9 aircraft, but any further investigative development could prompt schedule changes quickly.
- Know your EU261 entitlements: If your flight departs Munich and is cancelled or delayed more than three hours due to equipment unavailability, you are entitled to rebooking or a full refund under EU261/2004. Document any airline communication in writing.
- Build connection flexibility into Munich itineraries: If Munich is a connecting point rather than your final destination, allow extra buffer time. A last-minute equipment change or delay on the Vietnam Airlines service can cascade through onward connections.
- Do not assume fleet-wide impact: The BFU’s update applies to one aircraft. Other Vietnam Airlines 787-9 services — including those from European gateways beyond Munich — are not subject to any published restriction tied to this investigation.
Watch: The BFU’s next public update will indicate whether the investigation has moved from sequence-of-events documentation into causal analysis. If that update names a specific technical component or system, expect EASA to respond with guidance for the broader 787 operator community within weeks.
Questions? Answers.
Is it safe to fly on a Vietnam Airlines 787-9 after this incident?
The BFU’s investigation covers one specific aircraft. No airworthiness directive or fleet-wide operating restriction has been issued by EASA or the FAA in connection with this event. The BFU has not identified a systemic defect — the cause remains undetermined. Other Vietnam Airlines 787-9 aircraft continue to operate normally under existing certification.
How long will the aircraft remain grounded at Munich?
Vietnam Airlines and the BFU have not announced a return-to-service date. The aircraft will remain grounded until the investigation reaches a point where the BFU and the airline are satisfied that the cause is understood and any necessary corrective action has been taken. BFU final reports on complex incidents typically take 12–24 months from the event date.
What compensation am I entitled to if my Munich–Vietnam flight is cancelled because of this?
Passengers on flights departing Munich are covered by EU261/2004. A cancellation or delay of more than three hours due to equipment unavailability entitles you to rebooking on the next available service or a full refund. You can also claim meals and accommodation for delays over two hours. Contact Vietnam Airlines in writing and keep all documentation.
Were any passengers injured in the August 15 incident?
No injuries were reported among the 287 people on board. Vietnam Airlines confirmed to Reuters that passengers and cabin crew landed safely after the aircraft returned to Munich.
