Two Widebodies, One Runway: The Week Munich's 26L Drew Two Investigations

Rajkumar Agarwal23 August 202610 min read2 viewsSafety & Regulation
Two Widebodies, One Runway: The Week Munich's 26L Drew Two Investigations

Weekly safety round-ups usually strain to find a thread. This week, one found us — but only partly, and it is worth being precise about where the pattern ends.

Between Saturday 15 August and Friday 21 August 2026, Germany's Federal Bureau of Aircraft Accident Investigation (Bundesstelle für Flugunfalluntersuchung, or BFU) opened investigations into two separate events involving widebody aircraft on the same runway at Munich Airport, 48 hours apart. Both involved damage to runway lighting. Both had recorders pulled and sent to Braunschweig. That is a genuine cluster, and it is the spine of this briefing.

The rest of the week's notable occurrences — two hydraulic emergencies on long-haul jets, and a fatal midair collision at an uncontrolled airfield in Pennsylvania — are not part of that cluster, and this piece does not pretend otherwise. They are reported here chronologically because they are the week's other significant safety events, not because they share a cause.

Every investigation described below is open. Under ICAO Annex 13, the sole objective of these inquiries is the prevention of accidents and incidents, not the apportioning of blame or liability. Nothing here should be read as a finding.

15 August: Vietnam Airlines VN34 barely gets airborne at Munich

The first event is the more serious of the two. On Saturday 15 August, Vietnam Airlines flight VN34, a Boeing 787-9 registered VN-A867, was departing Munich's runway 26L for Hanoi with 271 passengers and 16 crew aboard.

According to a preliminary account published by the Civil Aviation Authority of Vietnam and reported by Simple Flying and Aerotime, the aircraft's speed stopped increasing for roughly two seconds around the midpoint of the takeoff roll, then resumed accelerating and reached V1 — the decision speed beyond which a takeoff is normally continued. The crew then observed a second decrease in speed. With insufficient runway remaining to reject, the pilots advanced the thrust levers to maximum and continued the takeoff. Rotation began with approximately 300 feet of paved runway left.

The BFU has stated that the aircraft rotated late and that its tail contacted the ground during rotation. The 787 passed beyond the paved surface — reported as roughly 120 metres past the runway end — damaging lighting beyond the runway and several of its own tyres. The crew received a tyre pressure indication shortly after becoming airborne, held to burn or dump fuel, and returned to Munich, landing on runway 26R about two hours after departure. Nobody was hurt. The Aviation Safety Network has logged the occurrence as a serious incident; the aircraft sustained substantial damage.

The flight data and cockpit voice recorders were recovered and taken to the BFU's Braunschweig headquarters. Investigators are expected to concentrate on why the acceleration faltered twice and why the takeoff roll was so much longer than normal. Reporting has raised two working lines of enquiry — takeoff performance data or configuration entered into the flight management computer, and a possible brake or drag issue — but neither has been established, and the BFU has not published a cause. Both should be treated as unverified until the bureau reports.

In Hanoi, the response was institutional as well as technical: Vietnam News reported that a deputy prime minister ordered a comprehensive review of aviation operations in the wake of the incident. That is a regulatory reaction to an event, not a finding about it.

Two events, one runway: a departure that left the paved surface at the far end, and an arrival that touched down ahead of the landing zone at the near end.
Two events, one runway: a departure that left the paved surface at the far end, and an arrival that touched down ahead of the landing zone at the near end.

17 August: a Lufthansa A380 touches down short on the same strip

Forty-eight hours later, on Monday 17 August, Lufthansa flight LH459 from San Francisco — an Airbus A380-800 registered D-AIML, with 351 people aboard — landed on the same runway 26L.

As reported by AIRLIVE, the aircraft touched down short of the designated threshold, its landing gear striking and damaging runway lights in the paved chevron area ahead of the main touchdown zone. The A380 remained under control, there was no evacuation, it taxied to the gate, and nobody was reported injured. The aircraft was subsequently withdrawn from service for technical inspection and landing gear repair.

The BFU opened proceedings here too, recovering the flight data and cockpit voice recorders. Investigators are expected to examine glideslope tracking, airspeeds and control inputs on final approach.

Here is where the honest reading matters. The two Munich events sit at opposite ends of the same strip of concrete and involve opposite phases of flight: one aircraft ran out of runway leaving, the other arrived before the runway properly began. They share a location, a lighting-damage outcome, and an investigating authority. They do not, on anything published so far, share a mechanism. A cluster of two on one runway inside two days is unusual enough to be worth flagging — and unusual events do cluster by chance. Whether anything about 26L's approach environment, markings or operating conditions is common to both is precisely what the BFU is there to determine, and it has not said.

18 and 20 August: two hydraulic emergencies, two days apart

Separately, two long-haul operations declared emergencies for hydraulic problems within 48 hours of one another.

On Tuesday 18 August, British Airways flight BA274, an Airbus A350-1000 registered G-XWBL inbound from Las Vegas, squawked 7700 on approach to London Heathrow. The reported cause was a possible hydraulic failure. The aircraft landed on runway 27R, was met by airport rescue and firefighting services as a precaution, and taxied to a remote stand at Terminal 5. No injuries were reported and no wider disruption to Heathrow followed.

On Thursday 20 August, United Airlines flight UA817, an Airbus A320 registered N495UA operating San Francisco to Mexico City, declared an emergency citing a complete hydraulic failure and diverted to Los Angeles, landing on runway 25L roughly two hours and forty minutes after departure. The aircraft was taken out of service for inspection; passengers were rebooked.

Two hydraulic events on Airbus aircraft in the same week invite a pattern narrative, and it should be resisted. The aircraft are different types with different hydraulic architectures, the operators are different, and no airworthiness authority has linked them. Neither has generated a published investigation report or an airworthiness directive at the time of writing. Both are, on the available record, unconnected occurrences that ended the way the system is designed for them to end.

Why a hydraulic failure is usually a diversion rather than a crisis: transport aircraft carry multiple independent hydraulic systems with overlapping coverage of flight controls, gear and brakes.
Why a hydraulic failure is usually a diversion rather than a crisis: transport aircraft carry multiple independent hydraulic systems with overlapping coverage of flight controls, gear and brakes.

That framing is not complacency. Crews declared formally in both cases — a deliberate act that buys direct routing, priority landing clearance and pre-positioned ground support. The declaration is the safety behaviour, not evidence of a crisis.

19 August: a fatal midair collision at Carlisle Regional

The week's most serious event, measured the way safety work measures things, drew the least aviation-press attention.

On Wednesday 19 August, a Cessna 150 collided in midair with a Pennsylvania State Police Bell 407 helicopter at Carlisle Regional Airport in Cumberland County, Pennsylvania. The pilot of the Cessna, Dr Paul Sokoloski, 57, of Hershey — an emergency room physician at Penn State Health and a certified flight instructor — was killed. Two troopers aboard the helicopter, identified by state authorities as Corporal Bryce Corman and Trooper Jason Mills, survived and were treated at Penn State Health Milton S. Hershey Medical Center.

Reporting by CBS News, ABC News and Pennsylvania outlets indicates the helicopter was conducting a routine training exercise, hovering low over a grassy area beside the runway, when the collision occurred. Carlisle Regional is a non-towered airport, where separation depends on pilots self-announcing on a common traffic advisory frequency and seeing and avoiding one another.

The NTSB has taken the investigation. Investigators have recovered data cards from the wreckage, and are reviewing communications, interviewing witnesses, and examining flight path, altitude, weather — reported as good — and maintenance history. A preliminary report is expected within roughly 30 days of the accident. Preliminary reports state facts, not causes; a final report typically takes considerably longer.

What is actually worth watching

Three things carry forward from this week.

The BFU's two Munich files are the most consequential. If the bureau finds anything common to both — approach lighting configuration, markings, or an operational factor on 26L — that is an airport-level finding with implications well beyond Munich. If it finds two unrelated crew-and-aircraft stories that happened to land on the same runway, that is worth knowing too, and worth saying plainly.

The VN34 takeoff performance question is the single most instructive item. Takeoff performance and configuration remains one of the recurring themes in transport-category safety work, and a preliminary account describing acceleration that faltered twice on the roll is unusual enough that the BFU's findings will be read carefully by operators well outside Vietnam.

And Carlisle is a reminder that the fatal risk in aviation still concentrates in general aviation and in the uncontrolled traffic pattern, where the separation system is human eyes and a shared radio frequency. The NTSB preliminary report is due next month.

Sources

#accident investigation#NTSB#BFU#takeoff performance#runway safety
Share:

Comments

Leave a comment

← All posts