Crash of a Piper PA-31T Cheyenne II in Madison

Date & Time: Aug 31, 2007 at 1218 LT
Type of aircraft:
Operator:
Registration:
N199MA
Flight Type:
Survivors:
Yes
MSN:
31-8104005
YOM:
1981
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On approach to Madison-Dane County-Truax Field, the pilot encountered technical problems with the right main gear that remained stuck in its wheel well. He decided to retract the gear and to complete a wheels-up landing. The twin engine aircraft belly landed and slid for few dozen metres before coming to rest. Both occupants escaped uninjured and the aircraft was damaged beyond repair.

Crash of a Piper PA-31T Cheyenne II in Zweibrücken: 1 killed

Date & Time: Feb 12, 2007 at 1020 LT
Type of aircraft:
Operator:
Registration:
N160TR
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Zweibrücken – Split – Athens
MSN:
31-7920036
YOM:
1979
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The pilot departed Zweibrücken Airport on a flight to Athens with an intermediate stop in Split as the aircraft should be delivered to its new owner based in Greece. After takeoff from runway 21 at Zweibrücken Airport, while in initial climb, the aircraft deviated to the left while the standard departure route was a straight climb until 7 nm. The pilot was contacted by ATC and reported problems. Shortly later, the altitude of the aircraft fluctuated from 1,500 to 3,200 feet and again, the pilot was contacted by ATC to check the situation. Few seconds later, the aircraft entered an uncontrolled descent and crashed in an open field located in Rieschweiler, about 6 km northeast of the airport. The aircraft was totally destroyed upon impact and the pilot, sole on board, was killed. It was reported that, prior to departure, the pilot encountered difficulties to close the main cabin door and had to be shown how to operate it. A member of the FBO staff then asked the pilot if he should explain the aircraft's avionics and, after the pilot replied yes, went on to describe how to operate the RNAV system. The pilot then had difficulty in starting the right engine and was directed to the 'ignition switch' on the overhead panel.

Crash of a Piper PA-31T Cheyenne in Quetzaltenango

Date & Time: Nov 22, 2006
Type of aircraft:
Operator:
Registration:
TG-NCN
Flight Type:
Survivors:
Yes
Schedule:
Guatemala City - Quetzaltenango
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Quetzaltenango-Los Altos Airport, the pilot encountered engine problems. He completed a belly landing in a wheatfield located few km from the airport. The pilot escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Piper PA-31T Cheyenne I in Cassano di Centenaro: 2 killed

Date & Time: Nov 6, 2006 at 0322 LT
Type of aircraft:
Operator:
Registration:
I-POMO
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Valetta - Milan
MSN:
31-7904030
YOM:
1979
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
3169
Captain / Total hours on type:
2540.00
Aircraft flight hours:
3122
Circumstances:
The twin engine aircraft departed Valetta Airport, Malta, on a night flight to Milan-Linate Airport, carrying one passenger and one pilot. After passing Elba Island at an altitude of 21,000 feet, over the Gulf of Genoa, the aircraft deviated from the prescribed route to the east while it was supposed to pass over Genoa before descending to Milan. Few minutes later, the aircraft entered an uncontrolled descent and crashed in a wooded and hilly terrain located in Cassano di Centenaro, about 43 km southwest of Piacenza. The aircraft disintegrated on impact and both occupants were killed.
Probable cause:
The pilot lost control of the aircraft, resulting in a collision with the ground. For reasons that investigations have not been able to determine with precision, the twin engine aircraft deviated from its intended course to the east. The lack of visibility caused by night could remain a contributing factor in that the pilot was not able to distinguish the ground and determine his position accurately. The analysis of the flight path and the debris of the aircraft did not make it possible to provide convincing and objective evidence on the possibility of an in-flight structural failure, of a technical failure of the flight controls or any alteration in the psychic or physical abilities of the pilot.
Final Report:

Crash of a Piper PA-31T Cheyenne II near Benalla: 6 killed

Date & Time: Jul 28, 2004 at 1048 LT
Type of aircraft:
Registration:
VH-TNP
Survivors:
No
Site:
Schedule:
Bankstown – Benalla
MSN:
31-7920026
YOM:
1979
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
14017
Captain / Total hours on type:
3100.00
Aircraft flight hours:
5496
Circumstances:
At 0906 Eastern Standard Time on 28 July 2004, a Piper Aircraft Corporation PA31T Cheyenne aircraft, registered VH-TNP, with one pilot and five passengers, departed Bankstown, New South Wales on a private, instrument flight rules (IFR) flight to Benalla, Victoria. Instrument meteorological conditions at the destination necessitated an instrument approach and the pilot reported commencing a Global Positioning System (GPS) non-precision approach (NPA) to Benalla. When the pilot had not reported landing at Benalla as expected, a search for the aircraft was commenced. Late that afternoon the crew of a search helicopter located the burning wreckage on the eastern slope of a tree covered ridge, approximately 34 km southeast of Benalla. All occupants were fatally injured and the aircraft was destroyed by impact forces and a post-impact fire.
Probable cause:
Significant factors:
1. The pilot was not aware that the aircraft had diverged from the intended track.
2. The route flown did not pass over any ground-based navigation aids.
3. The sector controller did not advise the pilot of the divergence from the cleared track.
4. The sector controller twice cancelled the route adherence monitoring alerts without confirming the pilot’s tracking intentions.
5. Cloud precluded the pilot from detecting, by external visual cues, that the aircraft was not flying the intended track.
6. The pilot commenced the approach at an incorrect location.
7. The aircraft’s radio altimeter did not provide the pilot with an adequate defence to avoid collision with terrain.
8. The aircraft was not fitted with a terrain awareness warning system (TAWS).
Final Report: