The Vietnam Airlines 787 Munich Overrun, Brake Inputs During the Takeoff Roll, and the Discipline of the Most Dangerous Ten Seconds in Aviation

A Vietnam Airlines Boeing 787-9 overran the runway at Munich International Airport during the takeoff roll, and investigators have identified a finding with implications for every pilot: brake inputs were recorded multiple times during the roll, with no clean rejected takeoff command. The investigation is being led by Germany’s BFU (Bundesstelle für Flugunfalluntersuchung), with participation from American and Vietnamese aviation authorities. The preliminary findings, reported by AeroTime, are already generating a conversation the industry needs to have.

What the Munich Overrun Investigation Found

The aircraft involved was a Boeing 787-9, one of the newer widebody long-haul jets in commercial service. During the takeoff roll at Munich, something went wrong before the aircraft could rotate and lift off. When investigators reviewed the flight data, they found repeated brake inputs during the roll itself - not a single decisive rejected takeoff command, but multiple inputs spread across the ground roll.

That distinction matters enormously. A clean rejected takeoff (RTO) is a defined procedure. The crew recognizes a condition, calls the rejection, closes the thrust levers, and applies maximum braking. The aircraft decelerates along a performance profile that was calculated before the flight. Everything that follows is planned.

What the Munich data shows is different. Braking occurred without a commanded rejection - which means the aircraft was simultaneously being asked to accelerate and being slowed down, without the crew committing to either outcome.

Why Braking During the Takeoff Roll Is So Dangerous

The physics of a takeoff roll make partial braking particularly hazardous. As speed builds, the energy of the aircraft in motion grows with it. Below V1 - the published decision speed for transport category aircraft - a crew can reject the takeoff and stop with the runway remaining. Above V1, stopping is no longer viable. The only safe path is into the air.

That decision boundary is binary by design. The entire framework of airline RTO training, crew briefings, and certification data is built around the discipline of committing cleanly to one side of V1 or the other.

When brake inputs occur during the roll without a formal rejection, the airplane loses the performance it was counting on. Thrust output is calculated on the assumption of no brake drag. Any braking extends the ground roll, generates heat in the brakes and tires, and introduces asymmetric forces if the inputs are uneven side to side. The runway that was sized for the planned performance profile begins to run out faster than expected - and the crew may not be in a position to recognize how much faster until it is too late.

Why the 787’s Systems Made This Detectable

The Boeing 787 uses an electromechanical braking system rather than the hydraulic brakes found on older platforms like the 767 or 747. Each brake is driven by electric motors, with no hydraulic fluid in the braking circuit. The system is newer technology and has a strong service record, but one of its characteristics is high-fidelity input detection.

Modern flight data recorders and quick access recorders on 787-series aircraft can capture brake pedal pressure in granular detail that older analog systems could not resolve. This is, in part, why the investigation has the data it has. The inputs were there to find because the aircraft was built to record them.

This is precisely the value of Flight Operational Quality Assurance (FOQA) programs, which the FAA has pushed hard to expand across U.S. carriers. Airlines that analyze their flight data routinely can identify patterns - brake drag on takeoff roll, unstabilized approaches, speed deviations on final - before those patterns produce accidents. The data exists in every modern airliner. The question is whether operators are reading it systematically.

What This Means for the Takeoff Roll Decision

The Munich report raises the question of what caused the brake inputs in the first place. The investigation is ongoing and the full narrative of what happened in the cockpit is still being assembled. Three possibilities are worth understanding:

Crew indecision at a critical moment. If the inputs represent a crew that was uncertain whether to continue or reject, the result is the worst of both outcomes - the airplane slowed without stopping, and continued without full acceleration.

Inadvertent pedal contact. On most modern aircraft, the rudder pedals and toe brakes are physically linked. A pilot whose foot position places the toes in contact with the brake surface during the roll can produce brake drag without intending to. This is a known human factors issue, particularly when pilots transition to higher-performance aircraft from types where foot position habits were never explicitly addressed.

An underlying mechanical issue. The investigation has not ruled out a system fault that either caused the braking or influenced the crew’s decision-making. The final report will address this.

Regardless of cause, the finding of repeated inputs without a committed RTO reflects a breakdown in the discipline that the takeoff roll demands.

The GA Parallel: Your Abort Point Is Your V1

The commercial RTO framework doesn’t map directly onto general aviation, but the underlying principle does. Light aircraft pilots don’t receive a V1 callout from a first officer. Most fly solo or with non-pilot passengers. The go/no-go decision on takeoff happens entirely between the pilot and the airplane.

The equivalent tool is an abort point - a specific location on the runway designated before the roll begins. If the aircraft is not flying by that point, the takeoff stops. It is not published in the AFM the way V1 is certified for transport category aircraft, but it serves the same disciplinary function: it converts the takeoff roll from a reactive moment into a planned one.

The space between a clean stop and a clean takeoff is where overruns live. A takeoff continued past the point where stopping was possible, and rejected before the aircraft had enough energy to fly, produces an outcome the runway was never sized to handle.

What the BFU Investigation Will Determine

The primary investigation falls under the BFU, Germany’s federal aviation accident investigation body, whose work on previous high-profile events has contributed materially to international safety practices. Boeing’s involvement as manufacturer and the international scope of the operator means U.S. and Vietnamese aviation authorities are also participating.

Multi-party investigations of this nature take time. The final report will be substantially more detailed than the preliminary findings currently available. But the core finding - repeated brake inputs during the takeoff roll of a widebody aircraft at a major European hub - is already sufficient to frame the conversation.

It is also worth noting that takeoff overruns are not geographically concentrated. The Flight Safety Foundation’s Runway Excursion Reference Guide documents events across multiple decades and all regions of the world. The common threads are human factors: decision latency at critical moments, ambiguous crew communication about the go/no-go question, interrupted procedures. The Munich event fits that pattern. The lessons from it belong to everyone who flies.

Pre-Takeoff Briefing: The Fifteen-Second Discipline

For airline crews, the pre-takeoff briefing covering the RTO procedure is mandatory and standardized. For general aviation pilots, it is optional - and essential.

Before rolling, brief your abort point. Identify what you’re looking for in the first seconds of the roll: engine instruments in the green, airspeed alive, acceleration normal. Know what condition will make you stop, and say it out loud if you have a passenger aboard. The briefing takes roughly fifteen seconds. It converts the most dangerous ten seconds in aviation from a reactive scramble into a committed plan.

Once rolling, keep feet light on the pedals. Rudder input on the takeoff roll is necessary - particularly in crosswind conditions or in higher-performance aircraft. Brake contact should be intentional, not accidental. Pilots who habitually rest their toes high on the rudder pedals, where the toe brake surfaces are, can introduce drag without realizing it. If your initial training didn’t address foot position explicitly during the takeoff roll, it is worth raising with a flight instructor at your next flight review.

Key Takeaways

• A Vietnam Airlines Boeing 787-9 overran the runway at Munich International Airport after investigators found repeated brake inputs recorded during the takeoff roll - without a clean rejected takeoff procedure being executed.
• Braking during the roll without commanding an RTO degrades performance against the planned numbers, extends the ground roll, and can place the crew in the gap between a clean stop and a clean takeoff - where runway excursions happen.
• The 787’s electromechanical braking system records pedal inputs with high fidelity, making this finding visible in the data in ways that older aircraft systems may not have captured.
• The investigation by Germany’s BFU, with U.S. and Vietnamese authority participation, is ongoing. Final findings will be more complete, but the preliminary data is already instructive.
• For every pilot: brief your abort point before every takeoff, monitor for go/no-go cues in the first seconds of the roll, and keep brake contact intentional. The discipline of commitment at the decision point is the same whether you’re flying a 787 or a Cessna 172.