Incident Overview

Date: Monday 24 January 2005
Aircraft Type: Boeing 747-212B (SF)
Owner/operator: Atlas Air
Registration Number: N808MC
Location: Dsseldorf International Airport (DUS/EDDL) – ÿ Germany
Phase of Flight: Landing
Status: Substantial, written off
Casualties: Fatalities: 0 / Occupants: 3
Component Affected: Boeing 747 Aircraft System ? Specifically, the braking system, weather data transmission system, and the pilot’s braking control.Boeing 747 Aircraft System ? Specifically, the braking system, weather data transmission system, and the pilot’s braking control.
Investigating Agency: BFUBFU
Category: Accident
On October 26, 2006, a Boeing 747 experienced a significant incident at Dsseldorf Airport due to a sudden and unexpected change in weather conditions. The flight, operating cargo, encountered runway 23L in use following an initial unexceptional part of the flight. The crew immediately initiated braking action, but the snowstorm conditions rapidly deteriorated, leading to a loss of visibility and a critical failure in the braking coefficient measurement. The pilot then applied manual braking, resulting in the aircraft overrunning the runway end and colliding with ILS aerials, causing a fire in engines 2 and 3. The incident highlights a critical failure in communication and reliance on weather data during challenging conditions.On October 26, 2006, a Boeing 747 experienced a significant incident at Dsseldorf Airport due to a sudden and unexpected change in weather conditions. The flight, operating cargo, encountered runway 23L in use following an initial unexceptional part of the flight. The crew immediately initiated braking action, but the snowstorm conditions rapidly deteriorated, leading to a loss of visibility and a critical failure in the braking coefficient measurement. The pilot then applied manual braking, resulting in the aircraft overrunning the runway end and colliding with ILS aerials, causing a fire in engines 2 and 3. The incident highlights a critical failure in communication and reliance on weather data during challenging conditions.

Description

The Boeing 747 operated on a cargo flight from Dubai to Dsseldorf on behalf of Emirates. The en route part of the flight was uneventful. The flight crew established radio contact with Dsseldorf Radar at 05:43. The crew were told that runway 23L was in use. Two minutes later the radar controller contacted flight 8995: “I just talked to the tower and ah for the time being braking action on all parts of the runway is supposed to be good. They are measuring again right now because it started to snow again and I’ll keep you advised.” The flight was then cleared to descend to FL80. The flight crew decided to set the autobrakes for landing on Medium, to account for the snow. At 05:50 the radar controller again contacted the flight about the current weather circumstances: “…latest update on the weather situation ahm the friction tester has reported braking action to be good for the moment however as its continuing to snow they are ah afraid that it might worsen, so they are going to do another friction test right before you land.” In the following minutes the flight was given descent instructions and vectors for an approach to runway 23L. At 05:54 the controller radioed: “weather update we now have a surface wind of three four zero degrees eleven knots, that’s slight tail wind component by two knots. Visibility is down to one thousand five hundred meters, still in snow showers and ah cloud base is now five hundred feet only.” The flight was subsequently cleared for the approach. At 05:57 the radar controller instructed the crew to contact Dsseldorf Tower. The Tower controller stated: “Good morning,… we are just waiting for the braking action values from the friction tester stand by a second. The surface wind is actually three three zero degrees one two knots.” Two minutes later the controller radioed: “… the braking action was measured to be medium at all parts. And ah the visibility dropped right now due to the heavy snow showers at the field ah. The RVR value at the touch down zone is presently nine hundred meters, at the mid-point one thousand one hundred meters and ah stop end one thousand one hundred meters.” At that moment the flight was 3,5 nautical miles out. The flight was subsequently cleared to land. The airplane touched down about 1700 ft (518 m) past the runway threshold. Ground spoilers and thrust reversers deployed and the autobrakes activated. Still the airplane did not decelerate as expected and the pilot applied manual braking. The airplane failed to stop and overran the runway end. It collided with ILS aerials, which caused a fire in engines no. 2 and no. 3. The aircraft was withdrawn from use at Dsseldorf until being scrapped there in April 2006. Causes: The accident is attributable to the fact that the braking values transmitted to the crew did not meet the conditions that had arisen as a result of heavy snowfall since the last measurement on the runway. Contributing factors: – Fast changing weather – The lack of an in all weather conditions reliable measurement method for the determination of braking coefficient.

Primary Cause

The braking values transmitted to the flight crew did not adequately account for the rapidly changing snow conditions, leading to a loss of braking effectiveness despite the crew’s immediate action.The braking values transmitted to the flight crew did not adequately account for the rapidly changing snow conditions, leading to a loss of braking effectiveness despite the crew’s immediate action.

Share on:

Leave a Reply

Your email address will not be published. Required fields are marked *