High-speed landing leads to runway excursion at Rotterdam Airport

Casualties unknown • Runway overrun during landing, Fairchild SA227-AC Metro III, Rotterdam Airport, NL

A ferry flight involving a Fairchild SA227-AC Metro III veered off the runway at Rotterdam after an unstabilized approach and excessive touchdown speed.

What happened

On December 9, 2005, a Fairchild SA227-AC Metro III, registration EC-HHS, was performing a ferry flight from Odense to Rotterdam Airport. The aircraft, operated by Aeronova, was configured for cargo but was empty of all freight, carrying only the two-person flight crew.

During the approach to runway 24, the aircraft was flying at an altitude higher than prescribed for the localizer intercept. Although the air traffic controller questioned the crew's ability to manage the approach, the crew confirmed they could proceed. The captain took control of the aircraft near the outer marker. The aircraft subsequently touched down at approximately one-third of the available runway length with a significantly high speed. During the braking phase, the pilot struggled to maintain the centerline. The aircraft eventually veered to the right and exited the runway, coming to rest in the grass near the threshold of runway 06. There were no injuries to the crew, and the aircraft sustained no structural damage.

The investigation

The Dutch Safety Board (DSB) focused its investigation on the final approach parameters and the condition of the braking system. Investigators analyzed flight data from the flight data recorder (FDR), which provided critical information regarding airspeed and altitude, though the cockpit voice recorder (CVR) was unusable as it contained data from a previous flight.

Technical examinations of the aircraft's braking units were conducted by the National Aerospace Laboratory (NLR). While the nose wheel steering and engine thrust systems were found to be functioning normally, the brake units showed signs of significant overheating. Additionally, two of the four brake units were found to be worn slightly beyond the allowable inspection limits.

Findings

  • The approach was not stabilized, as the aircraft was flying at an excessive altitude and required a nose-down maneuver to descend.
  • The touchdown speed was approximately 171 knots, which represented a 34% increase over the average touchdown speed of 127 knots recorded on the previous twelve flights.
  • The aircraft touched down with a groundspeed of approximately 177 knots, aided by a 6-knot tailwind.
  • The difficulty in maintaining the runway centerline was likely caused by uneven braking forces resulting from the overheating of the brake units during deceleration.

Safety action

The Dutch Safety Board emphasized that flight crews must perform a go-around whenever the criteria for a stabilized approach cannot be met by the designated minimum stabilization height.

Probable cause

The runway excursion was caused by an unstabilized approach characterized by excessive touchdown speed and a late touchdown point, compounded by uneven braking forces due to overheated brake units.

Frequently asked questions

What happened in the null aircraft accident near Runway overrun during landing, Fairchild SA227-AC Metro III, Rotterdam Airport, NL?

A ferry flight involving a Fairchild SA227-AC Metro III veered off the runway at Rotterdam after an unstabilized approach and excessive touchdown speed.

What aircraft was involved and where did it happen?

The accident on null involved a aircraft, at Runway overrun during landing, Fairchild SA227-AC Metro III, Rotterdam Airport, NL.

What was the probable cause of the accident?

The runway excursion was caused by an unstabilized approach characterized by excessive touchdown speed and a late touchdown point, compounded by uneven braking forces due to overheated brake units.

Loading the flight search…