A Vietnam Airlines Boeing 787-9 left Munich Airport for Hanoi on Saturday with a late, hard takeoff that kicked up dust near the end of a long runway, then returned for an emergency landing that shredded tires and closed a runway while investigators collect evidence.
Specialist reporting and the Aviation Safety Network entry for registration VN-A867 place Vietnam Airlines flight VN34 on runway 26L at about 11:57 UTC on August 15, 2026. Video and ADS-B records show a full-length takeoff roll on the 4,000-meter runway, a late rotation, a dust plume near the threshold, a holding pattern, low approaches, and a return landing about two hours later with substantial underside damage and no reported fatalities.
- Flight: Vietnam Airlines VN34, Munich (MUC) to Hanoi (HAN).
- Aircraft: Boeing 787-9, registration VN-A867, built 2016.
- When: Saturday, August 15, 2026, takeoff about 11:57 UTC.
- What happened: Late takeoff, tail strike damage, emergency return.
- Outcome: No fatalities reported; runway 26R closed after landing.
What investigators and specialists have confirmed so far
The Aviation Safety Network summary, still labeled as drawing from news and unofficial sources, records a passenger scheduled flight from Munich-Franz Josef Strauss Airport to Hanoi-Noi Bai. It lists zero fatalities, substantial aircraft damage, and a takeoff-phase event on runway 26L, which has a take-off run available of 4,000 meters.
One Mile at a Time matches that sequence with independent specialist reporting. The jet accelerated far along 26L, became airborne late with a visible dust cloud, declared an emergency, held near Munich for roughly 90 minutes, made low approaches so ground crews could look for damage, then landed on runway 26R about two hours after the original takeoff time.
After landing, multiple tires on the left main gear were shredded. The aircraft became immobilized after leaving the runway onto a taxiway.
Post-landing photos circulating in aviation channels show scrape and puncture damage under the rear fuselage consistent with a tail strike. Those photos are secondary evidence rather than a finished investigation report.
The formal cause is not yet published by German investigators or the airline in the sources opened for this report.
What Munich and connecting passengers should do today
If you are flying through Munich on Saturday or Sunday, treat runway capacity as reduced until the airport says otherwise. A disabled widebody and a closed runway can cascade into longer taxi times, gate holds, and rebooked short-haul connections even for airlines that never flew VN34.
Check your live itinerary in the airline app and the Munich Airport flight board before you leave for the terminal. Build extra time for security and transfer buses if your connection already looked tight.
If your flight is canceled or delayed past three hours on an EU itinerary, keep boarding passes, delay notices, and receipts for meals or hotels. Use the passenger-rights path described in Deep Arrival’s guide to flight cancellation rules, refunds, and rebooking.
Passengers who were ticketed on VN34 should contact Vietnam Airlines through the booking channel that issued the ticket, not only through social media. Ask for written rebooking or refund options plus care while stranded.
If you booked a package, start with the tour operator or travel agency that holds the contract so hotel and transfer pieces move with the air ticket.
What is known versus still unknown
Confirmed in the opened specialist and safety-database reporting: the date, flight number, aircraft type and registration, Munich-to-Hanoi routing, long takeoff roll on 26L, emergency return, tire damage on landing, and zero fatalities in initial summaries. Also confirmed is that the aircraft did not continue to Hanoi on that service after the event.
Not confirmed in those sources: an official airline press statement with passenger counts, the exact mechanical or performance factor that produced the late rotation, whether runway lights were damaged in a way that keeps 26L restricted, or how long VN-A867 will remain grounded.
Do not treat social speculation about brake actuators or takeoff-data entry as fact until investigators or Vietnam Airlines publish it.
Weather around the METAR window cited in the safety database was warm and clear rather than stormy. This is not being framed here as a thunderstorm diversion story.
Clear weather does not by itself prove a crew or systems cause. It only means travelers should not invent a weather waiver that the airline has not posted.
How this changes planning for Europe to Vietnam trips
Long-haul Asia departures from Munich are limited. When one 787 is immobilized after a substantial event, Vietnam Airlines may need days or weeks to recover the airframe.
Schedule recovery can touch later Hanoi or Ho Chi Minh City banks that use the same aircraft rotation. Travelers booked on upcoming Vietnam Airlines services from Germany should watch the app for equipment swaps and protect same-day rail or short-haul backups into other European gateways if their ticket allows.
If you still need to move east this week, compare alternate carriers and hubs rather than assuming a same-day VN repair. Lufthansa and other Munich-based networks remain useful planning companions for Europe-side recovery.
The Deep Arrival Lufthansa airline guide helps map connections when a single long-haul aircraft is taken out of the board.
For travelers already in Munich without a hotel, ask the operating airline first about care obligations before you self-book an expensive airport hotel. Keep itemized receipts.
If you self-rebook another airline without written authority, you may struggle to recover the fare even when EU care rules would have covered a hotel night.
Practical checks before you rebook or claim
Write down the flight number, scheduled times, actual takeoff and landing times if you have them, and the registration if cabin crew or the app showed it. Photograph gate screens and delay messages.
Those records matter more than screenshots of social video when you later ask for a refund, reroute, or compensation assessment.
EU261 style compensation can apply to cancellations and long delays on flights departing the EU, but it is not automatic for every irregular operation. Extraordinary-circumstance arguments depend on the final investigation.
File with the airline first, keep the case number, and use a national enforcement body only if the airline stonewalls. Deep Arrival’s cancellation guide covers the practical sequence without turning this post into a legal opinion.
Do not board a substitute aircraft if you are not fit to fly after a stressful diversion day. Tell the airline if anyone in your party needs medical attention, special assistance, or longer connection times.
Stress and dehydration after a multi-hour hold are common. Water and a quiet seat matter as much as the next ticket number.
| If you… | What to do |
|---|---|
| Were booked on VN34 today | Contact Vietnam Airlines now for rebooking or refund and written care instructions. |
| Connect through Munich today | Recheck live status, add buffer, and protect tight same-day connections. |
| Hold later Vietnam Airlines MUC flights | Watch the app for equipment changes and build a backup Europe hub plan. |
| Need hotels after a long delay | Ask the airline for care first; keep every meal and hotel receipt. |
| See viral cause theories online | Ignore them until investigators or the airline publish primary findings. |
- Today: Expect Munich runway and taxi delays while 26R recovery continues.
- VN34 passengers: Secure rebooking, care, and written case numbers before leaving the airport.
- Documents: Save boarding passes, delay notices, and expense receipts.
- Next Vietnam trips: Reconfirm equipment and departure bank 48 hours before travel.
- Unknown: Final cause and VN-A867 return-to-service date remain open.
A serious takeoff event that ends with everyone alive is still a day that rewrites itineraries. Use official airline and airport status tools, keep proof of what you spent, and wait for primary investigation results before treating any single mechanical theory as settled fact.
What flight was involved at Munich on August 15, 2026?
Vietnam Airlines flight VN34 from Munich to Hanoi, operated by Boeing 787-9 registration VN-A867, according to specialist and safety-database summaries.
Were there fatalities?
Initial Aviation Safety Network and specialist reports list zero fatalities. Always recheck airline and airport notices for any update.
Did the aircraft continue to Hanoi?
No. After the late takeoff and emergency, the jet returned to Munich, landed with tire damage, and became immobilized on a taxiway in the opened reporting.
Is the cause of the late takeoff known?
The cause is not established in the primary sources used for this report. Investigators will examine performance data, systems, and crew actions while social theories remain unconfirmed.
What should Munich passengers do right now?
Check live flight status, add connection buffer, keep receipts if delayed, and follow airline rebooking instructions if your flight is canceled or severely delayed.
