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

Date & Time: May 20, 1987 at 1722 LT
Type of aircraft:
Registration:
N2336X
Survivors:
No
Schedule:
Idaho Falls - Cody
MSN:
31-8120002
YOM:
1981
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
6500
Circumstances:
N2336X was on a business flight to Cody, WY. The pilot executed a missed approach on the first attempt of the VOR-A approach. A pilot who landed at Cody minutes before the accident said the visibility had decreased to 3/4 of a mile when N2336X made the first approach and approx 1/2 mile when N2336X crashed. Examination of the wreckage revealed no evidence of a mechanical malfunction or failure of the aircraft prior to accident. The sas servo arm was found in the full up position. The aircraft struck the terrain in a steep nose low attitude on a heading that was opposite to the direction of flight. Approach minimums at Cody are 5,800 feet and 1 mile visibility. All three occupants were killed.
Probable cause:
Occurrence #1: in flight encounter with weather
Phase of operation: circling (ifr)
Findings
1. (f) weather condition - below approach/landing minimums
2. (f) weather condition - low ceiling
3. (f) weather condition - snow
4. (c) in-flight planning/decision - improper - pilot in command
5. (c) ifr procedure - improper - pilot in command
----------
Occurrence #2: loss of control - in flight
Phase of operation: circling (ifr)
Findings
6. (c) airspeed - not maintained - pilot in command
----------
Occurrence #3: in flight collision with terrain/water
Phase of operation: descent - uncontrolled
Final Report:

Crash of a Partenavia P.68B in Rønne

Date & Time: Apr 20, 1987
Type of aircraft:
Operator:
Registration:
SE-GFN
Survivors:
Yes
MSN:
56
YOM:
1975
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Rønne Airport, both engines failed simultaneously. The aircraft stalled and crashed in an open field located few km short of runway. All four occupants escaped with minor injuries while the aircraft was damaged beyond repair.
Probable cause:
Double engine failure on approach caused by a fuel exhaustion.

Crash of a Piper PA-42-720 Cheyenne III in Horseshoe Bay

Date & Time: Feb 7, 1987 at 0840 LT
Type of aircraft:
Registration:
N81SM
Flight Phase:
Survivors:
Yes
Schedule:
Horseshoe Bay – Austin
MSN:
42-8001007
YOM:
1980
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3670
Captain / Total hours on type:
12.00
Aircraft flight hours:
2002
Circumstances:
The pilot made a fairly long taxi from the ramp to the end of the runway and then started his takeoff roll with the parking brake still partially set. The brakes became very hot and the component parts expanded. After rolling almost 3,000 feet the brakes tightened up to the extent that both main gear tires started leaving black skid marks which continued until the aircraft ran off the end of the runway without obtaining flying speed, a distance of 3,168 feet. It was noted, through a design feature of the aircraft, that the parking brake handle could be placed in the released position without the brake being released. However, this would give the appearance that it had been released. The main gear tires were worn almost slick during this attempted takeoff. Both main gear brakes had been overheated during this time to the extent that they were destroyed. The aircraft was destroyed by collision with trees, rocks and a fire hydrant at the bottom of a hill off the end of the runway. The pilot escaped with serious injuries.
Probable cause:
Occurrence #1: loss of control - on ground/water
Phase of operation: takeoff - roll/run
Findings
1. (c) airspeed (vlof) - not obtained - pilot in command
2. (c) aircraft preflight - inadequate - pilot in command
3. (f) procedures/directives - not followed - pilot in command
4. (c) emergency procedure - inadequate - pilot in command
----------
Occurrence #2: overrun
Phase of operation: takeoff
Findings
5. (c) aborted takeoff - delayed - pilot in command
6. (c) powerplant controls - improper use of - pilot in command
----------
Occurrence #3: in flight collision with terrain/water
Phase of operation: takeoff
Findings
7. (f) terrain condition - downhill
8. (f) object - tree(s)
9. (f) terrain condition - rough/uneven
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Independence: 3 killed

Date & Time: Jan 20, 1987 at 1228 LT
Operator:
Registration:
N60SE
Flight Phase:
Survivors:
No
Schedule:
Kansas City - Saint Louis
MSN:
31-8352010
YOM:
1983
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
7418
Captain / Total hours on type:
596.00
Aircraft flight hours:
861
Circumstances:
The two aircraft, a Beech U-21A and a Piper PA-31-350, collided nearly head on at 7,000 feet msl over Independence, MO. In daylight VMC conditions with a visibility of 20 miles. The U-21 was in level cruise and the PA-31 was climbing eastbound to an undisclosed altitude enroute to Saint Louis. Both aircraft were equipped with operating mode-c transponders but the controller in contact with the U-21 did not observe the conflict and traffic advisories were not provided. The PA-31 was operating in accordance with visual flight rules. The U-21 was operating in accordance with instrument flight rules. After the collision both aircraft crashed in uncontrolled descent. There was no indication that either aircraft took any evasive action. The conflict alert subprogram of the ARTS III tracking system was not programmed to alert the controllers to the impending collision and the two controllers did not observe any target in the vicinity of the data block representing the U-21. All six occupants in both aircraft were killed.
Probable cause:
The National Transportation Safety Board determines that the probable cause of the accident was the failure of the radar controllers to detect the conflict and to issue traffic advisories or a safety alert to the flightcrew of the U-21; deficiencies of the see and avoid concept as a primary means of collision avoidance; and the lack of automated redundancy in the air traffic control system to provide conflict detection between participating and nonparticipating aircraft.
Final Report:

Crash of a Cessna 421C Golden Eagle III near Wada: 4 killed

Date & Time: Jan 11, 1987 at 1440 LT
Registration:
JA5273
Flight Phase:
Survivors:
No
Site:
MSN:
421C-1100
YOM:
1981
Location:
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
En route, the right engine failed. The pilot was unable to feather the propeller and the aircraft lost height until it crashed on the slope of a mountain located west of Wada, in the prefecture of Nagano. The aircraft was destroyed and all three occupants were killed.
Probable cause:
Failure of the right engine after the piston head of the second cylinder broke in flight.
Final Report:

Crash of a Cessna 414A Chancellor in Olathe

Date & Time: Dec 24, 1986 at 2249 LT
Type of aircraft:
Registration:
N414LL
Survivors:
Yes
Schedule:
Kirkville - Olathe
MSN:
414A-0627
YOM:
1981
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4117
Captain / Total hours on type:
23.00
Aircraft flight hours:
2403
Circumstances:
The pilot stated that this was not a charter flight and, as such, he decided to attempt the loc 17 approach to Olathe even though the area was forecasting zero-zero conditions. According to the pilot, the last thing he remembers during the flight is bracketing the loc and reading 1,600 feet on the altimeter. Subsequently, the pilot further stated, he remembers being on the ground inside the wreckage, mitigating the injuries suffered and trying to stay warm. A post-accident invest revealed that the aircraft was to the left of the localizer course when it struck two trees 12 feet agl (1,062 feet msl), while in a 30° right bank. The aircraft made a flat 360 right pirouette over some small trees, tearing off the left wing before impacting the ground and sliding approximately 600 feet. A post-crash fire erupted from the right wing tank but it extinguished itself. A dot FAA operational flight test found the localizer to be within limits. A leak check of the aircraft static system and a bench check of both altimeters were satisfactory.
Probable cause:
Occurrence #1: in flight collision with object
Phase of operation: approach - faf/outer marker to threshold (ifr)
Findings
1. (f) weather condition - fog
2. (f) light condition - dark night
3. Object - tree(s)
4. (f) in-flight planning/decision - improper - pilot in command
5. (f) not performed - pilot in command
6. (c) ifr procedure - not followed - pilot in command
7. (c) minimum descent altitude - not maintained - pilot in command
8. (c) missed approach - not performed - pilot in command
----------
Occurrence #2: in flight collision with terrain/water
Phase of operation: approach - faf/outer marker to threshold (ifr)
----------
Occurrence #3: fire
Phase of operation: other
Findings
9. (c) fuel system, tank - burst
Final Report:

Crash of a Cessna 340A in Tomball: 1 killed

Date & Time: Dec 18, 1986 at 0621 LT
Type of aircraft:
Registration:
N8CD
Flight Phase:
Survivors:
No
Schedule:
Tomball - Tulsa
MSN:
340A-0727
YOM:
1979
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2450
Captain / Total hours on type:
200.00
Aircraft flight hours:
2070
Circumstances:
The pilot took off in fog and light rain and climbed into clouds at about 300-400 feet above the ground while both landing lights were extended and illuminated. Also the airport's rotating beacon (located about a mile from the accident site) was flashing on the clouds according to a ground witness. Just after entering the clouds the pilot was issued a left turn from his present heading of 350° to a heading of 270° and told to contact departure control. He did not make this contact and he continued the left turn (now descending) to a heading of 210° at which time the aircraft collided with trees and a large electrical transmission line and then the ground. The engines were operating at a high power setting at the time of impact. All broken flight control cables revealed evidence of overstress separation. No evidence of preimpact mechanical failure or malfunction was found. The pilot, sole on board, was killed.
Probable cause:
Occurrence #1: in flight encounter with weather
Phase of operation: climb - to cruise
Findings
1. (c) directional control - not maintained - pilot in command
2. (f) equipment,other - improper use of - pilot in command
3. (c) proper altitude - not maintained - pilot in command
4. (c) spatial disorientation - pilot in command
5. (f) light condition - dark night
6. (f) weather condition - fog
7. (f) weather condition - rain
----------
Occurrence #2: in flight collision with object
Phase of operation: descent - uncontrolled
Findings
8. (f) object - wire, transmission (marked)
9. (f) object - tree(s)
----------
Occurrence #3: in flight collision with terrain/water
Phase of operation: descent - uncontrolled
----------
Occurrence #4: fire
Phase of operation: other
Final Report:

Crash of a BAe 125-600B in Casablanca: 10 killed

Date & Time: Dec 15, 1986
Type of aircraft:
Registration:
5N-AWS
Survivors:
No
Site:
MSN:
256042
YOM:
1975
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
10
Circumstances:
On approach to Casablanca-Nouasseur Airport, the crew failed to realize his altitude was insufficient when the aircraft crashed into houses located 2 km short of runway. All eight occupants were killed as well as two people on the ground.

Crash of a Beechcraft A100 King Air in Pittsfield: 6 killed

Date & Time: Dec 10, 1986 at 0945 LT
Type of aircraft:
Operator:
Registration:
N65TD
Survivors:
No
Schedule:
Elyria - Pittsfield
MSN:
B-50
YOM:
1970
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
7520
Captain / Total hours on type:
1500.00
Aircraft flight hours:
7710
Circumstances:
During arrival for a LOC runway 26 approach, the pilot was advised the abyss fan marker was notamed out-of-service. With abyss inoperative, the minimum descent altitude (MDA) was 2200 feet. After N65TD was cleared for the approach, radar service was terminated and the flight was cleared to advisory frequency. The crew contacted unicom and obtained airport and weather advisory. The Unicom operator advised winds light and variable, estimated 800 feet overcast, visibility 5 miles, slush and ice reported on runway 1/2 hr earlier. After the crew reported 'procedure turn inbound,' no further transmissions were received from the aircraft. Subsequently, it hit trees on rising terrain at an elevation of approx 2200 feet, approx 7 miles before reaching the final approach fix (FAF, DALTON NDB). Minimum altitude for the approach in that area was 3000 feet. No preimpact part problems were found during the investigation. Airport elevation was 1194 feet. Radio transcripts indicated the crew were getting a weak signal from the DALTON NDB. Although not a required navaid, CHESTER VORTAC was depicted on the approach chart as an additional source to id the FAF, but was notamed as out-of-svc. The pilot did not obtain notams before flight.
Probable cause:
Occurrence #1: in flight collision with object
Phase of operation: approach - iaf to faf/outer marker (ifr)
Findings
1. (f) preflight planning/preparation - inadequate - pilot in command
2. (f) weather condition - low ceiling
3. (f) weather condition - fog
4. (c) ifr procedure - improper - pilot in command
5. (f) terrain condition - rising
6. (f) object - tree(s)
7. (c) proper altitude - not maintained - pilot in command
----------
Occurrence #2: in flight collision with terrain/water
Phase of operation: descent - uncontrolled
Findings
8. (f) terrain condition - mountainous/hilly
Final Report:

Crash of a Beechcraft B200 Super King Air in Fort McMurray

Date & Time: Dec 10, 1986
Operator:
Registration:
C-GKRL
Survivors:
Yes
MSN:
BB-878
YOM:
1981
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While approaching Fort McMurray Airport, the twin engine airplane struck tree tops and crashed in a wooded area located 11 km southeast of the airfield. All four occupants were seriously injured.