Crash of a Rockwell Turbo Commander 681 in Mansfield: 1 killed

Date & Time: Nov 30, 1996 at 1030 LT
Operator:
Registration:
N9129N
Flight Type:
Survivors:
No
Schedule:
Dayton - Mansfield
MSN:
680-6056
YOM:
1971
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
587
Captain / Total hours on type:
64.00
Aircraft flight hours:
5688
Circumstances:
After 2 previous attempts, the pilot was cleared for a third VOR Runway 14 Approach. He was issued landing information, and he reported the airport in sight. The minimum descent altitude (MDA) for the approach was 1,620 ft msl. The airport elevation was 1297 ft. The airplane was observed by an ATC controller to descend, and the controller's Brite scope (radar) displayed 1,400 ft. The controller observed the airplane's landing light bob up and down, followed by the nose pitching up. At about the same time, a ground witness in the area saw the airplane at low altitude; according to this witness, the pilot tried to 'pull the plane up' just before it collided with the static cable of a power line. The cable was about 85 feet above ground level (1,382 feet MSL) and approximately 2 miles from the approach end of the runway. No preimpact malfunction of the airplane, engine, or VOR was found.
Probable cause:
The pilot's early descent below the minimum descent altitude (MDA), while preparing to land from an instrument approach, and his failure to maintain adequate altitude and clearance from
obstruction(s).
Final Report:

Crash of a Beechcraft A100 King Air in San Jose

Date & Time: Nov 28, 1996
Type of aircraft:
Operator:
Registration:
RP-C710
Survivors:
Yes
MSN:
B-15
YOM:
1970
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After touchdown at San Jose Airport, the aircraft collided with a dog. On impact, the right main gear collapsed and the aircraft came to rest on its belly. The right engine struck the ground and caught fire. All three occupants escaped uninjured while the aircraft was damaged beyond repair. The dog was killed.

Crash of a Cessna 208B Grand Caravan in Bethel: 1 killed

Date & Time: Nov 26, 1996 at 1101 LT
Type of aircraft:
Registration:
N4704B
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Bethel - Kwigillingok
MSN:
208B-0199
YOM:
1989
Flight number:
ATS1604
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3623
Captain / Total hours on type:
474.00
Aircraft flight hours:
3711
Circumstances:
The pilot was departing on a cargo flight. Just after takeoff, a company dispatcher attempted to contact the pilot by radio. The pilot replied, 'stand by.' No further communication was received from the pilot. The airplane was observed by ATC personnel in a left turn back toward the airport at an estimated altitude of 200 feet above the ground. The angle of bank during the turn increased, and the nose of the airplane suddenly dropped toward the ground. The airplane struck the ground in a nose and left wing low attitude about 1 mile west of the airport. The terrain around the airport was relatively flat, snow covered tundra. The airplane was destroyed. A postaccident examination of the engine did not reveal any mechanical malfunction. Power signatures in the engine indicated it was developing power. A postaccident examination of the propeller assembly revealed one of three composite blades had rotated in its blade clamp 17/32 inch; however, the propeller manufacturer indicated blade contact with the ground would try to drive the propeller from a high blade angle toward a low blade angle. Movement toward a low blade angle would compress the propeller feathering springs, while movement toward a high blade angle would result in a hydraulic lock condition as oil in the system is compressed. The propeller manufacturer indicated they had no reports of composite blade slippage in the blade clamps.
Probable cause:
Failure of the pilot to maintain control of the airplane, while maneuvering to reverse direction after takeoff, after encountering an undetermined anomaly. The undetermined anomaly was a related factor.
Final Report:

Crash of an Antonov AN-32A in Baykit

Date & Time: Nov 22, 1996 at 1306 LT
Type of aircraft:
Registration:
RA-48104
Survivors:
Yes
Schedule:
Tura – Vanavara – Baykit – Yeniseysk
MSN:
16 02
YOM:
1988
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
22
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft was damaged beyond repair when it veered off runway and the crew tried to get back on the runway without help. The aircraft went out of control, crossed the runway and hit the mast of a powerline and a parapet with more than 3.5 g, suffering structural damage. All 5 crew members and 22 passengers (19 of them illegal ones) escaped unhurt.

Crash of a Beechcraft 65-A90 King Air in Quincy: 2 killed

Date & Time: Nov 19, 1996 at 1701 LT
Type of aircraft:
Registration:
N1127D
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Quincy - Quincy
MSN:
LJ-223
YOM:
1967
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
25647
Captain / Total hours on type:
22.00
Aircraft flight hours:
11391
Circumstances:
The Beechcraft 1900C, N87GL, was in its landing roll on runway 13, and the Beechcraft A90, N1127D, was in its takeoff roll on runway 04. The collision occurred at the intersection of the two runways. The flight crew of the Beechcraft 1900C had made appropriate efforts to coordinate the approach and landing through radio communications and visual monitoring; however they mistook a Cherokee pilot's transmission (that he was holding for departure on runway 04) as a response from the Beechcraft A90 to their request for the Beechcraft A90's intentions, and therefore mistakenly believed that the Beechcraft A90 was not planning to take off until after the Beechcraft 1900C had cleared the runway. The failure of the Beechcraft A90 pilot to announce over the common traffic advisory frequency his intention to take off created a potential for collision between the two airplanes.
Probable cause:
The failure of the pilots in the King Air A90 to effectively monitor the common traffic advisory frequency or to properly scan for traffic, resulting in their commencing a takeoff roll when the Beechcraft 1900C (United Express flight 5925) was landing on an intersecting runway. Contributing to the cause of the accident was the Cherokee pilot's interrupted radio transmission, which led to the Beechcraft 1900C pilot's misunderstanding of the transmission as an indication from the King Air that it would not take off until after flight 5925 had cleared the runway. Contributing to the severity of the accident and the loss of life were the lack of adequate aircraft rescue and firefighting services and the failure of the air stair door on the Beechcraft 1900C to be opened.
Final Report:

Crash of a Beechcraft 1900C-1 in Quincy: 12 killed

Date & Time: Nov 19, 1996 at 1701 LT
Type of aircraft:
Operator:
Registration:
N87GL
Survivors:
No
Schedule:
Chicago – Burlington – Quincy
MSN:
UC-087
YOM:
1989
Flight number:
UA5925
Crew on board:
2
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
12
Captain / Total flying hours:
4000
Captain / Total hours on type:
700.00
Copilot / Total flying hours:
1950
Copilot / Total hours on type:
800
Aircraft flight hours:
18446
Aircraft flight cycles:
26797
Circumstances:
The Beechcraft 1900C, N87GL, was in its landing roll on runway 13, and the Beechcraft A90, N1127D, was in its takeoff roll on runway 04. The collision occurred at the intersection of the two runways. The flight crew of the Beechcraft 1900C had made appropriate efforts to coordinate the approach and landing through radio communications and visual monitoring; however they mistook a Cherokee pilot's transmission (that he was holding for departure on runway 04) as a response from the Beechcraft A90 to their request for the Beechcraft A90's intentions, and therefore mistakenly believed that the Beechcraft A90 was not planning to take off until after the Beechcraft 1900C had cleared the runway. The failure of the Beechcraft A90 pilot to announce over the common traffic advisory frequency his intention to take off created a potential for collision between the two airplanes.
Probable cause:
The failure of the pilots in the King Air A90 to effectively monitor the common traffic advisory frequency or to properly scan for traffic, resulting in their commencing a takeoff roll when the Beechcraft 1900C (United Express flight 5925) was landing on an intersecting runway. Contributing to the cause of the accident was the Cherokee pilot's interrupted radio transmission, which led to the Beechcraft 1900C pilot's misunderstanding of the transmission as an indication from the King Air that it would not take off until after flight 5925 had cleared the runway. Contributing to the severity of the accident and the loss of life were the lack of adequate aircraft rescue and firefighting services and the failure of the air stair door on the Beechcraft 1900C to be opened.
Final Report:

Crash of a Lockheed PV-1 Ventura in Richmond

Date & Time: Nov 18, 1996 at 1335 LT
Type of aircraft:
Operator:
Registration:
VH-SFF
Flight Type:
Survivors:
Yes
Schedule:
Richmond - Richmond
MSN:
5378
YOM:
1943
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11444
Captain / Total hours on type:
25.00
Circumstances:
The aircraft was approaching to land after completing a handling display during an Open Day at RAAF Richmond. At an altitude of about 800 feet, on the base leg for runway 28, both engines stopped simultaneously and without warning. As there was insufficient altitude to reach the field for a power off landing, the flaps and landing gear were retracted and a successful forced landing carried out into a cleared field short of the airfield. The crew evacuated the aircraft without injury.
Probable cause:
A subsequent investigation failed to positively determine the cause of the simultaneous stoppage of both engines. A large quantity of fuel remained in the tanks and no defects were found with either of the engine fuel systems. The engine ignition systems were tested and functioned normally after the accident. The design of this aircraft, as with other ex-military multi-reciprocating engine types, includes a master ignition switch. The switch is guarded, and when turned off results in the termination of ignition to all engines simultaneously. The switch was removed from the aircraft after the accident and subjected to extensive testing, including vibration tests, but could not be faulted. It was noted however that ignition isolation resulted with only a small movement of the switch from the ON position. The most likely reason for the sudden stoppage of both engines was movement of the master ignition switch from the ON position, possibly as the result of vibration or by a crew member inadvertently bumping the switch prior to landing.
Final Report:

Crash of a Piper PA-61-601P (Ted Smith 601) in Eagle County: 5 killed

Date & Time: Nov 17, 1996 at 1505 LT
Operator:
Registration:
N251B
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Eagle County – Minneapolis
MSN:
61-0812-8063422
YOM:
1980
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
752
Captain / Total hours on type:
16.00
Circumstances:
The non instrument-rated pilot filed an IFR flight plan, but did not request nor was given a weather briefing. Shortly after taking off into low instrument meteorological conditions, he reported he was returning to the airport, but did not give a reason why. He never declared an emergency. The last transmission was when the pilot said he had 'the problem resolved,' and was continuing on to his destination. Various witnesses said the engines were 'revvying' and 'unsynchronized,' and that the propellers were being 'cycled.' One witness said brownish-black smoke trailed from the right engine. The airplane struck one ridge, then catapulted approximately 1,000 feet before striking another ridge. There was post impact fire. Both propellers bore high rotational damage. Disassembly of the engines, propellers, turbochargers, and various components failed to disclose what may have prompted the pilot to want to return to the airport. Internal components of the right engine, however, were black and, according to a Textron Lycoming representative, were indicative of 'an excessively rich mixture.' A psychiatrist had recently treated the pilot for depression, attention deficit and bipolar disorders. The pilot also had a history of alcohol and drug abuse. Postmortem toxicology protocol disclose the presence of Fluoxetine (an antidepressant), Norfluoxetine (its metabolite), and Hydrocodone (the most commonly prescribed opiate).
Probable cause:
The pilot initiating flight into known adverse weather conditions without proper certification. Factors were the meteorological conditions that existed --- low ceiling, low visibility, and falling
snow --- and his use of contraindicated drugs.
Final Report:

Crash of a Beechcraft 65-A90 King Air in Orange

Date & Time: Nov 16, 1996 at 1500 LT
Type of aircraft:
Operator:
Registration:
N814SW
Flight Phase:
Survivors:
Yes
Schedule:
Orange - Orange
MSN:
LJ-186
YOM:
1967
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1170
Captain / Total hours on type:
40.00
Circumstances:
The pilot was taking off with 10 jumpers onboard. At the rotation speed of 100 knots, he used elevator trim to rotate the airplane, but it did not lift off the runway. He continued moving the trim wheel violently to pitch the nose up, and attempted to pull back on the yoke, but the airplane collided with rising terrain off the end of the runway. A witness did not see any of the flight controls move during the pilot preflight inspection, and during the takeoff roll, he did not observe a nose up rotation of the airplane. The pilot reported that he removed a single pin control lock from the yoke during preflight. The Beech control lock consisted of two pins, two chains, and a U-shaped engine control lock. The pilot walked away from the wreckage after the accident. No control locks were found in the wreckage. However, the control column shaft exhibited distress signatures on the periphery of the hole where the control lock is installed. No other evidence was found of any other form of mechanical jamming, interference, or discontinuity with the flight controls. Investigators were unable to identify any potential source of interference, other than a control lock, that could have simultaneously jammed both pitch and roll control. According to the airplane's manufacturer, about 3 to 6 degree of trim would have been normal for the airplane's takeoff conditions.
Probable cause:
The pilot's inadequate preflight inspection and his failure to complete the pre-takeoff checklist which resulted in a takeoff roll with the control lock in place.
Final Report:

Crash of a Tupolev TU-134B-3 in Đà Nẵng

Date & Time: Nov 16, 1996
Type of aircraft:
Operator:
Registration:
VN-A114
Flight Phase:
Survivors:
Yes
MSN:
66220
YOM:
1984
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While taxiing at Đà Nẵng Airport, the nose gear collapsed and apparently punctured the cockpit, injuring a crew member. The aircraft was considered as damaged beyond repair.