Zone

Crash of a Cessna 421B Golden Eagle II in Delaware: 1 killed

Date & Time: Mar 17, 2019 at 1745 LT
Registration:
N424TW
Flight Type:
Survivors:
No
Schedule:
Dayton - Delaware
MSN:
421B-0816
YOM:
1974
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3000
Captain / Total hours on type:
48.00
Aircraft flight hours:
8339
Circumstances:
The pilot departed on a short cross-country flight in the twin-engine airplane. Instrument meteorological conditions (IMC) were present at the time. While en route at an altitude of 3,000 ft mean sea level, the pilot reported that the airplane was "picking up icing" and that he needed to "pick up speed." The controller then cleared the pilot to descend, then to climb, in order to exit the icing conditions; shortly thereafter, the controller issued a low altitude alert. The pilot indicated that he was climbing; radar and radio contact with the airplane were lost shortly thereafter. The airplane impacted a field about 7 miles short of the destination airport. Examination of the airplane was limited due to the fragmentation of the wreckage; however, no pre-impact anomalies were noted during the airframe and engine examinations. Extensive damage to the pitot static and deicing systems precluded functional testing of the two systems. A review of data recorded from onboard avionics units indicated that, about the time the pilot reported to the controller that the airplane was accumulating ice, the airplane's indicated airspeed had begun to diverge from its ground speed as calculated by position data. However, several minutes later, the indicated airspeed was zero while the ground speed remained fairly constant. It is likely that this airspeed indication was the result of icing of the airplane's pitot probe. During the final 2 minutes of flight, the airplane was in a left turn and the pilot received several "SINK RATE" and "PULL UP PULL UP" annunciations as the airplane conducted a series of climbs and descents during which its ground speed (and likely, airspeed) reached and/or exceeded the airplane's maneuvering and maximum structural cruising speeds. It is likely that the pilot became distracted by the erroneous airspeed indication due to icing of the pitot probe and subsequently lost control while maneuvering.
Probable cause:
A loss of airspeed indication due to icing of the airplane's pitot probe, and the pilot's loss of control while maneuvering.
Final Report:

Crash of a Beechcraft C90B King Air in Georgetown

Date & Time: Aug 1, 2015 at 2100 LT
Type of aircraft:
Operator:
Registration:
N257CQ
Flight Type:
Survivors:
Yes
Schedule:
Dayton – Somerset
MSN:
LJ-1419
YOM:
1995
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3182
Captain / Total hours on type:
1122.00
Aircraft flight hours:
2324
Circumstances:
The airplane was fueled with 140 gallons of fuel before the second of three flight segments. The pilot reported that, while en route on the third segment, a fuel crossfeed light illuminated. He reset the indicator and decided to land the airplane to troubleshoot. He requested to divert to the nearest airport, which was directly beneath the airplane. Subsequently, the right engine lost power, and the autofeather system feathered the right engine propeller. He reduced power on the left engine, lowered the nose, and extended the landing gear while entering the traffic pattern. The pilot indicated that, after the landing gear was extended, the electrical system "failed," and shortly after, the left engine would not respond to power lever inputs. As the flight was on a base leg approach, the airplane was below the intended flightpath to reach the runway. The pilot stated that he pulled "gently on the control wheel"; however, the airplane impacted an embankment and came to rest on airport property, which resulted in substantial damage to both wings and the fuselage. Postaccident examination of the engines and airframe revealed no evidence of mechanical malfunctions or abnormalities that would have precluded normal operation. Signatures on the left propeller indicated that the engine was likely producing power at the time of impact; however, actual power settings could not be conclusively determined. Signatures on the right propeller indicated that little or no power was being produced. The quantity of fuel in the airplane's fuel system, as well as the configuration of the fuel system at the time of the accident, could not be determined based on the available evidence. Although the position of the master switch (which includes the battery, generator 1, and generator 2) was found in the OFF position, the airplane had been operating for about 30 minutes when the electrical power was lost; thus, it is likely that the airplane had been operating on battery power throughout the flight. This could have been the result of the pilot's failure to activate, or his inadvertent deactivation of, the generator 1 and 2 switch. If the flight were operating on battery power, it would explain what the pilot described as an electrical system failure after the landing gear extension due to the exhaustion of the airplane's battery. The postaccident examination of the left engine and propeller revealed that the engine was likely producing some power at the time of impact, and an explanation for why the engine reportedly did not respond to the pilot's throttle movements could not be determined. Additionally, given the available evidence, the reason for the loss of power to the right engine could not be determined.
Probable cause:
Undetermined based on the available evidence.
Final Report:

Crash of a Swearingen SA226TC Metro II in Paris: 1 killed

Date & Time: Feb 8, 2006 at 1210 LT
Type of aircraft:
Operator:
Registration:
N629EK
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Dayton - Harlingen
MSN:
TC-396
YOM:
1980
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
5237
Captain / Total hours on type:
164.00
Aircraft flight hours:
15883
Circumstances:
While in cruise flight at 16,000 feet, the pilot requested from ATC and was cleared to make a 360-degree turn to the left. Shortly after this, the pilot requested a 360-degree turn to the right. The pilot then requested radar vectors to the closest airport and was given this. ATC asked the pilot if he had an emergency and the pilot reported he had an asymmetric fuel condition. The pilot then asked for a lower altitude and was cleared by ATC to 4,000 feet. About a minute later the pilot transmitted "Mayday" six times and shortly after this radar and radio contact with the flight was lost. Recorded radar data showed that at 1803:13 the accident airplane was proceeding on a southerly heading at 16,100 feet mean sea level (MSL). At 1803:53 the airplane turned left to a southeasterly heading. At 1804:13 the airplane turned right returning to its original southerly heading. At 1805:14 the accident airplane turned to the right on a southwesterly heading, and maintained that heading until 1809:04 at which time the airplane turned due west and was at an altitude of 15,400 feet. The last radar contact was at 1810:06 at an altitude of 13,800 feet. The airplane wreckage was located due north from this last recorded radar contact. Witnesses observed the airplane descend in a near vertical attitude, collide with the ground, and then explode. Components from all areas of the aircraft structure and flight control surfaces were located at the crash site along with components from both engines and propellers. Impact and post crash fire damage precluded the examination of the airplanes fuel system and components.
Probable cause:
The pilot's inflight loss of control following a reported fuel asymmetry condition for undetermined reasons.
Final Report:

Crash of a Beechcraft B200 Super King Air in Piqua: 1 killed

Date & Time: Aug 24, 2001 at 0640 LT
Registration:
N18260
Flight Type:
Survivors:
No
Schedule:
Dayton – Piqua
MSN:
BB-900
YOM:
1981
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
7100
Captain / Total hours on type:
2400.00
Aircraft flight hours:
10821
Circumstances:
The airline transport rated pilot was attempting to land under visual flight rules for a scheduled passenger pick-up and subsequent charter flight. The pilot was communicating with a pilot at the airport, who was utilizing a hand held radio. The accident pilot reported he was not able to see the runway lights due to ground fog and continued to circle the airport for about 20 minutes. The pilot on the ground stated the airplane appeared to be about 1,500 feet above the ground when it circled, and then entered a downwind for runway 26. He was not able to hear or see the airplane as it flew away from the airport. He then began to hear the airplane during its final approach. The airplane's engines sounded normal. He then heard a "terrible sound of impact," followed by silence. When he arrived at the accident site, the airplane was fully engulfed in flames. The airplane impacted trees about 80-feet tall, located about 2,000 feet from, and on a 240 degree course to the approach end of runway 26. Several freshly broken tree limbs and trunks, up to 15-inches in diameter, were observed strewn along a debris path, which measured 370 feet. Examination of the wreckage did not reveal any pre-impact malfunctions. The weather reported at an airport about 19 miles south-southeast of the accident site, included a visibility of 1 3/4 miles, in mist, with clear skies and a temperature and dew point of 17 degrees Celsius. Witnesses in the area of the accident site generally described conditions of "thick fog" and a resident who lived across from the accident site stated visibility was "near zero" and he could barely see across the road.
Probable cause:
The pilot's improper decision to attempt a visual landing under instrument meteorological conditions and his failure to maintain adequate altitude/clearance, which resulted in an inflight collision with trees. A factor in this accident was the ground fog.
Final Report:

Crash of a Douglas DC-8-71F in Sacramento: 3 killed

Date & Time: Feb 16, 2000 at 1952 LT
Type of aircraft:
Operator:
Registration:
N8079U
Flight Type:
Survivors:
No
Schedule:
Sacramento - Dayton
MSN:
45947
YOM:
1968
Flight number:
EB017
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
13329
Captain / Total hours on type:
2128.00
Copilot / Total flying hours:
4511
Copilot / Total hours on type:
2080
Aircraft flight hours:
84447
Aircraft flight cycles:
33395
Circumstances:
On February 16, 2000, about 1951 Pacific standard time, Emery Worldwide Airlines, Inc., (Emery) flight 17, a McDonnell Douglas DC-8-71F (DC-8), N8079U, crashed in an automobile salvage yard shortly after takeoff, while attempting to return to Sacramento Mather Airport (MHR), Rancho Cordova, California, for an emergency landing. Emery flight 17 was operating under the provisions of 14 Code of Federal Regulations (CFR) Part 121 as a cargo flight from MHR to James M. Cox Dayton International Airport (DAY), Dayton, Ohio. The flight departed MHR about 1949, with two pilots and a flight engineer on board. The three flight crew members were killed, and the airplane was destroyed. Night visual meteorological conditions prevailed for the flight, which operated on an instrument flight rules (IFR) flight plan.
Probable cause:
A loss of pitch control resulting from the disconnection of the right elevator control tab. The
disconnection was caused by the failure to properly secure and inspect the attachment bolt.
Final Report:

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 Volpar Turboliner 18 in Baltimore: 1 killed

Date & Time: Dec 10, 1992 at 1535 LT
Type of aircraft:
Operator:
Registration:
N7770B
Flight Type:
Survivors:
No
Schedule:
Dayton - Baltimore
MSN:
AF-320
YOM:
1951
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2658
Captain / Total hours on type:
657.00
Aircraft flight hours:
26436
Circumstances:
The pilot supervised the loading of the airplane. According to info from a person that helped load the plane, the bill of loading, and actual weights and measurements of the cargo after the accident, the plane was loaded to a gross weight of 11,979 lbs with the cg 2.7 inches behind the aft limit. At the destination, the flight was vectored for an ILS runway 10 approach. About 3 miles from the runway, the pilot was told to make a missed approach due to inadequate separation from traffic. The pilot acknowledged, but soon thereafter, radar contact with the plane was lost. Witnesses saw the plane descend from a low cloud layer before it crashed. One witness said its wings were moving from side to side and the plane was falling faster than it was moving forward. There was evidence the plane had impacted in a flat attitude with little forward movement. Four cargo straps were found loose with no sign of tensile overload; 3 others and a restraining board were found loose as if they had not been used. No preimpact mechanical problem was found. The wind was from 090° at 21 gusting 32 kts. The pilot, sole on board, was killed.
Probable cause:
Failure of the pilot to properly secure the cargo, which allowed a shift in the center of gravity during a missed approach maneuver and resulted in subsequent loss of aircraft control and flying speed. A factor related to the accident was failure of the pilot to assure the airplane was loaded within its proper weight and balance limitations.
Final Report:

Crash of a Northrop YC-125B Raider in Tulsa

Date & Time: Jun 29, 1988 at 0625 LT
Type of aircraft:
Registration:
N3756Q
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Tulsa - Dayton
MSN:
2518
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6274
Captain / Total hours on type:
56.00
Circumstances:
The pilot did not hold a type rating or written authorization to act as pilot in command. The copilot did not hold a type rating or written authorization to act as second in command and his medical had expired. The aircraft did not have an airworthiness certificate nor had a special flight permit been issued. The left propeller went into reverse during the initial climb due to corrosion and deterioration of the wiring that controlled the propeller. The aircraft crashed out of control after colliding with power lines during takeoff. It struck the ground and went through a fence then down a slope and over an embankment. The aircraft then bounced across a street while turning around and colliding with a power line pole tail first. The aircraft had traveled about 537 feet from initial ground contact. All 3 engines were still producing power when the aircraft came to rest. Both occupants escaped uninjured.
Probable cause:
Occurrence #1: airframe/component/system failure/malfunction
Phase of operation: takeoff - initial climb
Findings
1. (c) electrical system - corroded
2. (f) inadeq substantiation process, inadequate documentation - company/operator mgmt
3. (c) electrical system - deteriorated
4. (c) propeller system/accessories,reversing system - engaged
5. (c) procedures/directives - disregarded - pilot in command
6. (c) operation with known deficiencies in equipment - attempted - pilot in command
7. (f) lack of total experience in type of aircraft - pilot in command
8. (f) lack of total experience in type of aircraft - copilot/second pilot
----------
Occurrence #2: forced landing
Phase of operation: descent - emergency
----------
Occurrence #3: in flight collision with terrain/water
Phase of operation: descent - uncontrolled
Final Report:

Crash of a BAe 3101 Jetstream 31 in Springfield: 3 killed

Date & Time: Feb 9, 1988 at 1500 LT
Type of aircraft:
Operator:
Registration:
N823JS
Flight Type:
Survivors:
No
Schedule:
Dayton - Springfield
MSN:
623
YOM:
1983
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
8670
Captain / Total hours on type:
1030.00
Aircraft flight hours:
8219
Circumstances:
A company designated instructor and two f/o trainees were conducting a far 135 training flight. The third approach was terminated with a go-around initiated over the runway threshold at about 50 feet. After climbing to about 150 feet, the aircraft was observed to oscillate in yaw, followed by pitch, and then roll to the right. The aircraft impacted in a near-vertical descent attitude. The investigation revealed that the right engine was operating, but at reduced power. The left engine was at full power. There was no indication of aircraft system malfunction or failure. Company pilots indicated that the captain had a history of demeaning cockpit behavior and roughness with students. The f/o, was small in stature and had 100 hours of multi-engine time and no turboprop time. Company pilots reported the f/o trainee was consistently behind the aircraft in prior flights. Examination of the aircraft revealed the flaps in the retracted position contrary to aircraft handbook. Company pilots further indicated the captain had history of requiring low altitude 1-engine go arounds and delaying offers of assistance to students. All three crew members were killed.
Probable cause:
Occurrence #1: loss of control - in flight
Phase of operation: go-around (vfr)
Findings
1. (f) emergency procedure - simulated - pilot in command (cfi)
2. (c) go-around - delayed - pilot in command (cfi)
3. (c) aircraft control - not maintained - dual student
4. (f) lack of total experience in type of aircraft - dual student
5. Lack of familiarity with aircraft - dual student
6. Excessive workload (task overload) - dual student
7. (f) remedial action - delayed - pilot in command (cfi)
8. (c) supervision - inadequate - pilot in command (cfi)
----------
Occurrence #2: in flight collision with terrain/water
Phase of operation: descent - uncontrolled
Final Report:

Crash of a Beechcraft E18S in Plymouth

Date & Time: Oct 1, 1977 at 0456 LT
Type of aircraft:
Operator:
Registration:
N5601D
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Dayton - Chicago
MSN:
BA-297
YOM:
1957
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13676
Captain / Total hours on type:
2355.00
Circumstances:
While cruising by night on a cargo flight from Dayton to Chicago, one or two propeller blades detached. The pilot informed ATC and due to severe vibrations, he was forced to reduce his altitude and to attempt and emergency landing. The twin engine airplane crashed during the forced landing and was destroyed. The pilot, sole on board, was seriously injured.
Probable cause:
Engine propeller tearaway during normal cruise due to nicked blades and fatigue fractures. Separation in flight. Excessive vibrations.
Final Report: