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

Date & Time: Jul 4, 1986
Type of aircraft:
Operator:
Registration:
GN-750
Flight Phase:
Survivors:
No
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
6
Circumstances:
While cruising at low height, the twin engine aircraft struck power cables, stalled and crashed in a pasture, bursting into flames. All six occupants were killed.

Crash of a Piper PA-31T Cheyenne II in Southend: 1 killed

Date & Time: Mar 13, 1986 at 0832 LT
Type of aircraft:
Operator:
Registration:
D-IHVI
Flight Type:
Survivors:
Yes
Schedule:
Cologne - Southend
MSN:
31-8020007
YOM:
1980
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3081
Captain / Total hours on type:
311.00
Circumstances:
A flight plan for the flight from Cologne to Southend was filed on the evening of 12 March 1986. The pilot obtained by telephone details of the actual weather conditions at Southend at 0650 hrs on 13 March 1986. He took off from Cologne at 0714 hrs with a company colleague as his sole passenger. The aircraft flew without incident using the airways as FL220 until cleared by ATC to descend towards Southend. At 0820 hrs the pilot established radio communications with the approach controllers. He was passed details of the existing weather conditions and said that he would try the approach. He requested and was given radar guidance to land on runway 24 at Southend. The published operating minimum for an approach using the 3 cm surveillance radar is an Obstacle Clearance Limit (OCL) of 280 feet. radar guidance for the approach terminates at half a nautical mile from touchdown. The recommended Decision Height (DH) and Runway Visual Range (RVR) published in the UK Air PIlot (RAC 4-6-13) is 380 feet and 800 meters respectively. The approach was flown accurately in azimuth, and advisory heights to maintain a 3° glide path were passed to the pilot. The aircraft's flight path was observed on the London Air Traffic Control descent profile. The radar talkdown was terminated at half a mile and the aircraft was cleared to land. when the aircraft was not sighted from the control tower at the expected time of landing the alarm was raised. Members of the airfield fire service were already positioned on the airfield at 'weather standby'. They initiated a search for the aircraft. It was learned that it had crashed close to an industrial estate which lies about half a mile from the threshold of runway 24. The aircraft had been seen on the normal approach path but at a height judged to be lower than normal. Two eye withnesses saw the aircraft bank sharply to the left before it crashed into a small field. There was a minor post-impact fire in the area of the left engine, which was quickly extinguished by those first on the scene using a hand held extinguisher. The passenger was assisted in opening the main cabin door and he was escorted from the wreckage. The pilot was killed on impact. The passenger, who had been seated in a rearwards facing seat behind the copilot's station, stated that he had glimpsed the ground shortly before the accident but could give no information indicating the cause of the accident.
Final Report:

Crash of a Piper PA-31T Cheyenne II in Jacksonville: 2 killed

Date & Time: Jan 9, 1986 at 2126 LT
Type of aircraft:
Registration:
N700CM
Flight Type:
Survivors:
No
Schedule:
Hampton - Jacksonville
MSN:
31-7820007
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1710
Captain / Total hours on type:
100.00
Circumstances:
While being vectored for an ILS runway 07 approach, the pilot was told to maint 3,000 feet and advised he was following a Boeing 727. The minimum approach altitude before intercepting the ILS glide slope at the final approach fix/outer marker was 1,900 feet. As the aircraft was approaching the outer marker, the pilot was cleared for the approach and was handed off to the tower. After contacting the tower, the pilot was told to descend as published. At approximately that time, the tower controller and his supervisor discussed N700CM's altitude and proximity to the 727. The controller was going to discontinue the approach, but his supervisor suggested he wait and see if it would work out. Subsequently, N700CM crashed into trees approximately 5,800 feet short of the runway while descending in a wings level attitude. Radar data showed N700CM was well above the ILS glide slope when cleared for the approach. ATC procedures requested the aircraft to be below the glide slope before being cleared. Also, N700CM was approximately 2.57 miles behind the 727, but stayed well above the 727's flight path (and possible wake turbulence) until moments before impact. N700CM entered an excessive rate of descent before going below the glide slope. Both occupants were killed.
Probable cause:
Occurrence #1: in flight collision with object
Phase of operation: approach - faf/outer marker to threshold (ifr)
Findings
1. (f) weather condition - low ceiling
2. (f) weather condition - fog
3. (f) weather condition - rain
4. Radar separation - inadequate - atc personnel (dep/apch)
5. (f) instructions, written/verbal - improper - atc personnel (dep/apch)
6. (f) descent - delayed
7. (c) planned approach - improper use of - pilot in command
8. Missed approach - not issued - atc personnel (lcl/gnd/clnc)
9. (f) supervision - inadequate - atc personnel (supervisor)
10. (f) proper glidepath - not attained - pilot in command
11. (c) missed approach - not performed - pilot in command
12. (c) descent - excessive - pilot in command
13. (f) object - tree(s)
14. (c) decision height - improper use of - pilot in command
----------
Occurrence #2: in flight collision with terrain/water
Phase of operation: descent - uncontrolled
Final Report:

Crash of a Piper PA-31P-350 Mojave in Norco: 2 killed

Date & Time: Jan 4, 1986 at 1814 LT
Type of aircraft:
Registration:
N9253Y
Survivors:
No
Schedule:
Greer - Norco
MSN:
31-8414030
YOM:
1984
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1085
Captain / Total hours on type:
140.00
Circumstances:
The pilot initiated an ILS approach in below minimum weather conditions shortly after night fall. He was given a low altitude alert, but continued the approach. He announced a missed approach, and indicated problems climbing to altitude. He then declared an unspecified emergency, and requested vectors to a larger airport, in spite of worsening weather conditions. He reached an altitude of 2,100 feet, but commenced another ILS approach despite previous difficulties. Radar data indicates excessive maneuvering to intercept the inbound course, with wide variations in ground speed and altitude. Following a steep climb at a low groundspeed, the aircraft disappeared below radar coverage. Witnesses indicated irregular engine sounds as the aircraft made a tight level turn at low altitude prior to impacting trees in a near level attitude. On-scene evidence shows power was being produced from both engines upon impact. Post-impact fire consumed the wreckage. Both occupants were killed.
Probable cause:
Occurrence #1: miscellaneous/other
Phase of operation: missed approach (ifr)
Findings
1. (f) aircraft performance, climb capability - loss,partial
2. (c) reason for occurrence undetermined
3. Not performed - other maintenance personnel
----------
Occurrence #2: loss of control - in flight
Phase of operation: approach - iaf to faf/outer marker (ifr)
Findings
4. (c) weather condition - below approach/landing minimums
5. In-flight planning/decision - improper - pilot in command
6. Flight into known adverse weather - intentional - pilot in command
7. (c) maneuver - excessive - pilot in command
8. (c) airspeed - improper - pilot in command
9. (c) proper altitude - not maintained - pilot in command
----------
Occurrence #3: in flight collision with object
Phase of operation: maneuvering
Findings
10. Object - tree(s)
Final Report:

Crash of a Piper PA-31P-350 Mojave in Denver

Date & Time: Dec 1, 1985 at 1808 LT
Type of aircraft:
Registration:
N9250Y
Flight Type:
Survivors:
Yes
Schedule:
El Paso – Denver
MSN:
31-8414029
YOM:
1984
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1050
Captain / Total hours on type:
212.00
Aircraft flight hours:
296
Circumstances:
The pilot had been flying approximately 7 hours and was completing the flight at night when the accident occurred. He was using visual cues (the airport environment) to position the aircraft at a proper altitude for a visual approach and landing. The terrain south of the airport rises several hundred feet above the airport elevation. The terrain is sparsely lit. The aircraft touched down two miles short of runway 34R in an open pasture at an elevation of approximately 400 feet higher than the airport. The pilot had flown approximately one hour of night time in the last 90 days, according to his logbook. All three occupants were injured, two seriously.
Probable cause:
Occurrence #1: in flight collision with terrain/water
Phase of operation: approach
Findings
1. (f) light condition - dark night
2. (c) became lost/disoriented - inadvertent - pilot in command
3. (f) visual/aural perception - pilot in command
4. (f) fatigue - pilot in command
5. (f) lack of familiarity with geographic area - pilot in command
6. (f) lack of recent experience in type operation - pilot in command
7. (c) altitude - misjudged - pilot in command
8. Terrain condition - rising
9. (c) clearance - not maintained - pilot in command
Final Report:

Crash of a Piper PA-31T Cheyenne II near Flat Rock: 5 killed

Date & Time: Aug 23, 1985 at 2155 LT
Type of aircraft:
Registration:
N600CM
Flight Phase:
Survivors:
No
Site:
Schedule:
Louisville - Greer
MSN:
31-7720024
YOM:
1977
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
1700
Aircraft flight hours:
4077
Circumstances:
Aircraft hit northwest side of ridge in level attitude, cruise speed, heading southeast. Conditions were dark night and the cloud ceiling was about 40 feet above the ridge. Pilot received weather brief before take off and en route which reported a ceiling of 10,000 feet at destination. Aircraft was flown at 17,500 feet en route. Pilot-in-command radioed GSP approach control, said he was VFR for landing, passing 6,000 feet. Two way communication not established but discrete tx code assigned. Controller saw tx code change northwest of crash site then radar target disappeared at accident site. All five occupants were killed.
Probable cause:
Occurrence #1: in flight collision with terrain/water
Phase of operation: cruise
Findings
1. (c) ifr procedure - disregarded - pilot in command
2. (c) descent - premature - pilot in command
Final Report:

Crash of a Piper PA-31T Cheyenne II in Utica: 2 killed

Date & Time: Feb 22, 1985 at 2000 LT
Type of aircraft:
Operator:
Registration:
N100RN
Survivors:
No
Schedule:
Montgomery - Utica
MSN:
31-7820091
YOM:
1978
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
11000
Captain / Total hours on type:
800.00
Aircraft flight hours:
1516
Circumstances:
The pilot attempted a VOR approach and missed. He advised ATC he was going to attempt the NDB and if he could not see the runway he would go to metro at Detroit or Pontiac. On the NDB approach the aircraft struck trees 960 feet below the MDA. The aircraft flipped over landing on the nose and top of the fuselage. Both occupants were killed.
Probable cause:
Occurrence #1: in flight collision with object
Phase of operation: approach - faf/outer marker to threshold (ifr)
Findings
1. (f) in-flight planning/decision - not corrected - pilot in command
2. (f) ifr procedure - not followed - pilot in command
3. (f) judgment - poor - pilot in command
4. (c) minimum descent altitude - not used - pilot in command
5. (c) decision height - not maintained - pilot in command
----------
Occurrence #2: in flight collision with terrain/water
Phase of operation: descent - uncontrolled
Final Report:

Crash of a Piper PA-31T Cheyenne in Paris: 7 killed

Date & Time: Dec 12, 1984 at 2200 LT
Type of aircraft:
Registration:
F-GDPJ
Survivors:
No
Site:
Schedule:
Torino - Paris
MSN:
31-7620006
YOM:
1976
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
The twin engine aircraft was returning to Paris following a charter flight from Torino-Caselle Airport, carrying four journalists, a member of the AFP Agency and two pilots. On final approach to Paris-Le Bourget runway 07 by night, the crew encountered limited visibility due to foggy conditions. Apparently in an attempt to establish a visual contact with the approach lights, the crew failed to realize his altitude was too low when the aircraft struck the roof of a warehouse and crashed in Garges-lès-Gonesse, less than 2 km short of runway 07 threshold. The aircraft was destroyed by a post crash fire and all seven occupants were killed.

Crash of a Piper PA-31T Cheyenne II in Toronto: 3 killed

Date & Time: Oct 17, 1984
Type of aircraft:
Registration:
C-GAPT
Survivors:
No
MSN:
31-7620004
YOM:
1976
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
On approach to Toronto-Lester Bowles Pearson Airport, the twin engine airplane struck the ground and crashed about 11 km short of runway threshold. All three occupants were killed.

Crash of a Piper PA-31T3-T1040 Cheyenne in Atlanta

Date & Time: Sep 24, 1984 at 1609 LT
Type of aircraft:
Registration:
N9193Y
Survivors:
Yes
Schedule:
Florence - Atlanta
MSN:
31T-8275010
YOM:
1982
Crew on board:
2
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3309
Captain / Total hours on type:
439.00
Aircraft flight hours:
1857
Circumstances:
The normal fuel load for the flight was 1,500 lbs, but with a forecast tail wind and an estimated flight time for only 1+10, the crew accepted the lower indicated (950 lb) fuel load. The flight was uneventful until an indication of 250 lbs per side, then the fuel 'seemed to dissipate faster.' With an indication of 150 lbs on downwind, the copilot recommended declaring an emergency. The captain's response was to ask ATC for the anticipated length of the downwind leg. He was told 20 miles. Priority handling was requested, but was only available for a declared emergency. The approach was continued with normal handling for approximately 10 minutes. At 1608:39, the crew declared an emergency, then reported the aircraft was out of fuel. It crash landed on rough terrain, short of runway 08. An exam revealed fuel sensors had been improperly installed (interchanged between the inboard and outboard tanks). Thus the gages indicated about 180 lbs more than the approximately 763 lbs that was actually aboard at takeoff. A special 500 hour inspection of the entire fuel system was made on 7/8/84 using the 'wet' method, but only the capacitance method checks each individual sensor. All 11 occupants were injured and the aircraft was destroyed.
Probable cause:
Occurrence #1: loss of engine power (total) - nonmechanical
Phase of operation: approach - faf/outer marker to threshold (ifr)
Findings
1. (f) fuel system - incorrect
2. (f) maintenance, installation - improper
3. (f) engine instruments, fuel quantity gage - false indication
4. Maintenance, inspection - inadequate
5. (f) procedure inadequate - manufacturer
6. (f) fluid, fuel - low level
7. (c) in-flight planning/decision - improper - pilot in command
8. (c) remedial action - delayed - pilot in command
9. (c) fluid, fuel - exhaustion
10. Fuel supply - inadequate
----------
Occurrence #2: forced landing
Phase of operation: approach - faf/outer marker to threshold (ifr)
----------
Occurrence #3: in flight collision with terrain/water
Phase of operation: landing - flare/touchdown
Findings
11. (f) terrain condition - rough/uneven
Final Report: