Crash of a Learjet C-21A at Maxwell AFB: 2 killed

Date & Time: Jan 14, 1987
Type of aircraft:
Operator:
Registration:
84-0121
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Maxwell AFB - Maxwell AFB
MSN:
35-567
YOM:
1985
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
The aircraft was engaged in a local training flight at Maxwell AFB, carrying three pilots. At liftoff, it went out of control and crashed near the runway. Two occupants were killed and a third pilot was injured.

Crash of a NAMC YS-11A-213 in Remington

Date & Time: Jan 13, 1987 at 1354 LT
Type of aircraft:
Operator:
Registration:
N906TC
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Indianapolis - West Lafayette
MSN:
2154
YOM:
1970
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3913
Captain / Total hours on type:
1381.00
Circumstances:
The flight crew failed to adhere to appropriate procedures and directives when they failed to select the hp cock levers to the hswl (lock out) position while performing an approach to landing stall during a training/test flight. When stall recovery was initiated, both propellers 'hung up' when the high (cruise pitch) stops of each propeller failed to withdraw. As the power levers were advanced, turbine gas temperatures (tgt's) exceeded limitations; the left propeller auto-feathered, the right propeller was later feathered by the captain. Restart procedures were attempted without success, and a forced landing in a plowed cornfield ensued. Examination of the engines revealed that the turbines had been 'subjected to severe (and destructive) thermal degradation during operation' as a result of the propellers being constrained during low speed operations. Testing of the relays revealed that the high stop withdrawal relay for the right propeller functioned intermittently. All three crew members escaped uninjured.
Probable cause:
Occurrence #1: airframe/component/system failure/malfunction
Phase of operation: maneuvering
Findings
1. (c) procedures/directives - not followed - pilot in command
2. (f) inattentive - pilot in command
3. (c) powerplant controls - improper use of - pilot in command
----------
Occurrence #2: loss of engine power (total) - mech failure/malf
Phase of operation: descent - emergency
Findings
4. Turbine assembly - overtemperature
5. Emergency procedure - attempted - pilot in command
6. Propeller system/accessories, feathering system - engaged
7. Propeller feathering - performed - pilot in command
----------
Occurrence #3: forced landing
Phase of operation: descent - emergency
----------
Occurrence #4: gear not extended
Phase of operation: landing - flare/touchdown
Findings
8. Terrain condition - open field
9. (c) wheels up landing - intentional - pilot in command
10. Terrain condition - rough/uneven
Final Report:

Crash of a Rockwell Grand Commander 690A in Miles City

Date & Time: Jan 7, 1987 at 1359 LT
Operator:
Registration:
N57133
Survivors:
Yes
Schedule:
Billings – Miles City
MSN:
690-11133
YOM:
1973
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2398
Captain / Total hours on type:
45.00
Aircraft flight hours:
6216
Circumstances:
The pilot of the nonscheduled domestic passenger air taxi flight was flying the VOR/DME runway 22 approach to Wiley Field, Miles City, MT. The pilot said he turned on the autopilot and after turning inbound from the procedure turn towards the faf he engaged the approach mode. After crossing the faf the pilot descended to MDA and engaged the altitude hold mode. When he reached the map the pilot started to make a missed approach but a passenger, seated next to him in the copilot's seat, reported the runway in sight. The pilot said he saw the runway and retarded the throttles in order to descend for landing. The aircraft nose pitched up abruptly, the aircraft stalled, and mushed to the ground. The aircraft hit hard and skidded off the runway. Two occupants were injured and four others escaped uninjured.
Probable cause:
Occurrence #1: abrupt maneuver
Phase of operation: approach - faf/outer marker to threshold (ifr)
Findings
1. Weather condition - low ceiling
2. (c) autopilot - improper use of - pilot in command
3. Weather condition - obscuration
4. (c) throttle/power control - reduced - pilot in command
5. Weather condition - fog
----------
Occurrence #2: loss of control - in flight
Phase of operation: approach - faf/outer marker to threshold (ifr)
Findings
6. (c) stall/mush - inadvertent - pilot in command
----------
Occurrence #3: in flight collision with terrain/water
Phase of operation: descent - uncontrolled
Findings
7. Terrain condition - runway
Final Report:

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

Date & Time: Dec 30, 1986 at 0254 LT
Type of aircraft:
Registration:
N74NL
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Louisville - Chicago
MSN:
31-7720010
YOM:
1977
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2170
Captain / Total hours on type:
140.00
Aircraft flight hours:
6888
Circumstances:
The aircraft was enroute to the Chicago Midway Airport. While letting down to 16,000 feet the pilot reported he was shutting down the right engine. ARTCC cleared the aircraft to 5,000 feet. Ten minutes later ARTCC lost radio transponder and mode C contact. 15 minutes later the aircraft descended out of the 1,800 feet overcast and struck a 170 feet utility tower at the 150 feet level. The aircraft then ground impacted and burned. Investigation revealed that the right engine had a bearing failure due to lack of lubrication. The pilot, sole on board, was killed.
Probable cause:
Occurrence #1: loss of engine power (partial) - mech failure/malf
Phase of operation: descent - normal
Findings
1. (f) engine assembly, bearing - distorted
2. (f) engine assembly, bearing - binding (mechanical)
3. Emergency procedure - inadequate - pilot in command
----------
Occurrence #2: airframe/component/system failure/malfunction
Phase of operation: descent - normal
Findings
4. (f) electrical system - failure, total
5. (f) lack of familiarity with aircraft - pilot in command
----------
Occurrence #3: in flight collision with object
Phase of operation: unknown
Findings
6. (c) proper altitude - not maintained - pilot in command
7. (f) flight/nav instruments - failure, partial
8. (f) minimum descent altitude - not maintained - pilot in command
9. Anxiety/apprehension - pilot in command
10. (f) light condition - dark night
11. (c) descent - misjudged - pilot in command
----------
Occurrence #4: in flight collision with terrain/water
Phase of operation: descent - uncontrolled
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 Rockwell Aero Commander 500 in Hagerstown

Date & Time: Dec 12, 1986 at 0324 LT
Registration:
N116CA
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Akron - Mount Vernon
MSN:
500-1133-75
YOM:
1961
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3150
Captain / Total hours on type:
200.00
Aircraft flight hours:
11034
Circumstances:
The pilot was on the fourth leg of a night cargo flight cruising at approximately 500 feet agl enroute to Mt Vernon, IL, when the aircraft struck some trees and subsequently collided with the ground. The engines and propellers were both torn down and tested and no evidence of malfunction was discovered. The pilot stated he did not recall the crash sequence at all. The pilot was wearing a 'walkman' radio at the time of the accident. He stated it was to help keep him awake, because he had fallen asleep at times in the past while flying night cargo.
Probable cause:
Occurrence #1: in flight collision with object
Phase of operation: cruise
Findings
1. Object - tree(s)
2. (c) altitude - not maintained - pilot in command
3. Fatigue (flight schedule) - pilot in command
4. (f) light condition - night
5. (c) judgment - poor - pilot in command
----------
Occurrence #2: in flight collision with terrain/water
Phase of operation: descent - uncontrolled
Final Report:

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 Cessna 414A Chancellor in Sun Valley

Date & Time: Dec 6, 1986 at 1900 LT
Type of aircraft:
Registration:
N37561
Flight Type:
Survivors:
Yes
Schedule:
Van Nuys - Sun Valley
MSN:
414A-0007
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3680
Captain / Total hours on type:
618.00
Aircraft flight hours:
1487
Circumstances:
During the transition from a DME arc to the ILS final approach course, the pilot allowed the aircraft to prematurely descend into the ground. The reason for the descent could not be determined. However, no preimpact mechanical malfunction with the aircraft was found nor was there any evidence supporting pilot incapacitation. Dark night conditions in fog and low ceilings prevailed during the approach. All three occupants were injured, two seriously.
Probable cause:
Occurrence #1: in flight collision with terrain/water
Phase of operation: approach - iaf to faf/outer marker (ifr)
Findings
1. (c) reason for occurrence undetermined
2. (c) descent - premature - pilot in command
3. (f) light condition - dark night
4. (f) weather condition - fog
5. (f) weather condition - low ceiling
Final Report:

Crash of a Cessna 441 Conquest in Erie

Date & Time: Nov 30, 1986 at 1345 LT
Type of aircraft:
Registration:
N117EA
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
441-0191
YOM:
1981
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1600
Captain / Total hours on type:
31.00
Aircraft flight hours:
2200
Circumstances:
Reason for the Cessna to veer in a semi-circle and collide with another aircraft is undetermined. Examination of the start lock assemblies could not be completed due to the extensive impact and fire damage. The aircraft was being prepared for a flight. During a manual speed governor check on the left engine the aircraft veered in a semi-circle. An attempt to examine the aircraft start locks was negated by the fire damage from the collision. Both occupants escaped uninjured.
Probable cause:
Occurrence #1: miscellaneous/other
Phase of operation: standing - engine(s) operating
Findings
1. (c) reason for occurrence undetermined
----------
Occurrence #2: on ground/water collision with object
Phase of operation: taxi
Findings
2. (f) brakes (normal) - delayed - pilot in command
3. Object - aircraft parked/standing
----------
Occurrence #3: fire
Phase of operation: taxi
Final Report: