The Vietnam Airlines VN34 incident at Munich on 15 August 2026 was more than a tail strike. The Boeing 787-9 used almost the entire 4,000-metre Runway 26L before rotating very late, striking its tail and reportedly becoming airborne at or beyond the runway end. The key issue isn’t just the tail strike but why the aircraft couldn't accelerate normally and why the crew recognised the performance problem so late.
The crew was highly experienced, comprising three captains and one first officer, with a combined total of over 60,000 flying hours. This makes it a significant human-factors case. Experience alone doesn’t ensure effective monitoring, and having three captains may have created complex CRM dynamics, such as authority gradients or role confusion.
According to the crew, acceleration stalled around mid-runway, briefly resumed, then worsened again. By then, they believed there wasn’t enough runway left for a safe rejected take-off and decided to continue with maximum thrust.
This unusual acceleration pattern is critical. A simple error—such as incorrect weight, temperature, flap setting, or V-speeds—would usually cause consistently poor acceleration, not a pattern of loss, recovery, and then slowdown. This suggests possible intermittent retarding forces, such as unintended brake application, wheel resistance, or a brake-system fault.
Photographs and videos reportedly show brake or tyre marks near the runway end, but it’s unclear what they signify—whether they caused the acceleration loss or resulted from the aircraft departing the paved surface. Only flight recorder data can clarify the sequence.
The BFU recovered both the flight data and cockpit voice recorders. Analysing them should involve correlating engine thrust, acceleration, brake pressure, wheel speed, pilot inputs, flap settings, V-speeds, pitch, and control inputs over time.
If thrust was normal but acceleration dropped suddenly, the cause was likely due to external drag; if brake pressure increased at the same time, it suggests either crew input or a brake malfunction.
Until the data is available, attributing the event to pilot error, data errors, or aircraft failure is premature. What is clear is that the incident didn’t begin with the tail strike but earlier, when the Boeing 787 failed to accelerate properly during high-speed take-off. That’s the anomaly the BFU must explain.
If confirmed, the acceleration pattern warrants detailed scrutiny. A simple performance error would typically cause consistently poor acceleration, not an intermittent loss and recovery, which points to an external force such as brake or wheel resistance.
The technical cause is only part of the story. With a 240-tonne aircraft, rotation should normally occur well within the available runway—roughly 8,000 feet—depending on conditions. The actual roll-out was abnormally long. So why did four experienced pilots not recognise earlier that the aircraft was using too much runway?
This may reveal weaknesses in current take-off monitoring practices. Pilots are well trained for clear emergencies, such as engine failure or tyre blowouts, but less so for subtle issues where the engines appear normal, airspeed increases, yet acceleration is inadequate.
Unlike approaches, take-offs lack a clear performance checkpoint to confirm that a specific speed has been reached at a particular point on the runway. Modern aircraft can compare actual performance with calculations, but this isn’t usually flagged explicitly.
Hence, VN34 raises questions about procedures and training. Simulator exercises might need to include scenarios involving low or silent acceleration issues to help crews recognise problems early. Greater focus on runway position, expected acceleration, and active performance monitoring could improve safety.
The BFU should be able to resolve much of the technical uncertainty by analysing engine thrust, acceleration, brake pressures, wheel speeds, configuration, V-speeds, and runway position. The CVR will show when and how the crew first noticed the problem, what they discussed, and whether CRM influenced their decisions.
While the visible event was the tail strike, the real issue began earlier—when a heavily loaded Boeing 787 failed to accelerate as expected. The BFU must determine why this happened. But the industry should also consider another crucial question. Why did an exceptionally experienced crew apparently fail to recognise the developing performance deficit when there was still sufficient runway to act?
The lesson may extend well beyond VN34.
For now, assigning blame would be premature. The BFU has not published the recorder-derived sequence, and there is insufficient evidence to determine whether the cause was technical, procedural or human.
If the recorder evidence confirms that the reduced acceleration was detectable well before V1, VN34 should prompt a wider examination of take-off monitoring philosophy, CRM within augmented crews, and low-acceleration recognition and simulator training.
Commercial aviation has become highly proficient at teaching pilots what to do once an emergency has been identified.
VN34 may ultimately remind us that the harder challenge is recognising an emergency developing before the aircraft announces it. That may ultimately prove to be VN34's most important safety lesson.
No comments:
Post a Comment