No fatalities

2001-03-22: Piper PA-31-350 Navajo Chieftain (PH-ABD) — Tulip Air — Orléans-Loiret (Saint-Denis-de-l'Hôtel), France

Orléans-Loiret (Saint-Denis-de-l'Hôtel), FranceTakeoff (climb)

On March 22, 2001, a Piper PA-31-350 Navajo Chieftain (registration PH-ABD) operated by Tulip Air was involved in an aviation accident near Orléans-Loiret (Saint-Denis-de-l'Hôtel), France during takeoff. No fatalities were reported. Investigators recorded the probable cause as: The accident resulted from the crew failing to remove a flight control locking device and neglecting essential pre-flight inspections. This summary draws on records from the Bureau of Aircraft Accidents Archives (B3A).

Sourcesthe Bureau of Aircraft Accidents Archives (B3A)Primary reportUpdated 1781202816Data APIEditorial standards
Aircraft registered PH-ABD
Aircraft registered PH-ABD. Photo: Rob Hodgkins / CC BY-SA 2.0, via Wikimedia Commons

A passenger charter flight aborted its takeoff at Orléans-Saint Denis de l’Hôtel on 22 March 2001, resulting in a runway excursion and nose gear failure.

What happened

On the afternoon of 22 March 2001, a PA-31-350 Chieftain, operating under call sign Tulip 2B with registration PH-ABD, was attempting an instrument flight rules departure from Orléans-Saint Denis de l’Hôtel. The aircraft, performing a passenger charter service, was utilizing runway 23 for its takeoff toward Paris-Le Bourget.

During the takeoff roll, the co-pilot, acting as the pilot flying, encountered difficulties attempting to rotate the aircraft. This prompted an immediate aborted takeoff. However, due to the wet condition of the runway surface, the aircraft's braking systems were unable to decelerate the plane sufficiently before the end of the paved surface. Tire marks indicated that the aircraft had traveled approximately one hundred meters along the runway without successful deceleration.

Following the end of the runway, the aircraft entered a water-soaked grass area. The impact with the terrain caused the nose landing gear to collapse. The sequence ended when the aircraft came to a complete stop roughly one hundred and eighty meters beyond the runway threshold. There were no fatalities reported in this incident.

Findings

Investigations into the accident revealed that a flight control locking device had been left installed on the aircraft. The primary contributing factor was the crew's failure to remove the control lock during pre-flight procedures, which prevented the necessary movement of flight control surfaces required for rotation. Additionally, the lack of rigorous Crew Resource Management (CRM) protocols contributed to the oversight during the pre-flight checks.

Probable cause

The accident resulted from the crew failing to remove a flight control locking device and neglecting essential pre-flight inspections.