Zone

Crash of a Socata TBM-700 near Urbana: 1 killed

Date & Time: Aug 20, 2021 at 1440 LT
Type of aircraft:
Operator:
Registration:
N700DT
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Port Clinton – Cincinnati
MSN:
134
YOM:
1998
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2156
Captain / Total hours on type:
17.00
Aircraft flight hours:
2624
Circumstances:
The pilot was performing a short cross-country flight, which was his third solo flight in the high-performance single-engine airplane. The airplane departed and climbed to 20,000 ft mean sea level (msl) before beginning to descend. About 8 minutes before the accident, the airplane was southbound, descending to 11,000 ft, and the pilot established communications with air traffic control (ATC). About 4 minutes later, the controller cleared the pilot to descend to 10,000 ft msl and proceed direct to his destination; the pilot acknowledged the clearance. While descending through 13,000 ft msl, the airplane entered a descending left turn. The controller observed the left turn and asked the pilot if everything was alright; there was no response from the pilot. The controller’s further attempts to establish communications were unsuccessful. Following the descending left turn, the airplane entered a high speed, nose-down descent toward terrain. A witness observed the airplane at a high altitude in a steep nose-down descent toward the terrain. The witness noted no signs of distress, such as smoke, fire, or parts coming off the airplane, and he heard the airplane’s engine operating at full throttle. The airplane impacted two powerlines, trees, and the terrain in a shallow descent with a slightly left-wing low attitude. Examination of the accident site revealed a long debris field that was consistent with an impact at a high speed and relatively shallow flightpath angle. All major components of the airplane were located in the debris field at the accident site. Examination of the airframe and engine revealed no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. A performance study indicated the airplane entered a left roll and dive during which the airplane exceeded the airspeed, load factor, and bank angle limitations published in the Pilot’s Operating Handbook (POH). An important but unknown factor during these maneuvers was the behavior of the pilot and his activity on the flight controls during the initial roll and dive. The pilot responded normally to ATC communications only 98 seconds before the left roll started. It is difficult to reconcile an alert and attentive pilot with the roll and descent that occurred, but there is insufficient information available to determine whether the pilot was incapacitated or distracted during any part of the roll and dive maneuver. Although all the available toxicological specimens contained ethanol (the alcohol contained in alcoholic drinks such as beer and wine), the levels were very low and below the allowable level for flight (0.04 gm/dl). While it is possible that some of the identified ethanol had been ingested, it is also possible that all or most of the identified ethanol was from sources other than ingestion (such as postmortem production). In either case, the levels were too low to have caused incapacitation. It is therefore unlikely that any effects from ethanol contributed to the circumstances of the accident. There was minimal available autopsy evidence to support any determination of incapacitation. As a result, it could not be determined from the available evidence whether medical incapacitation contributed to the accident.
Probable cause:
The pilot’s failure to arrest the airplane’s left roll and rapid descent for reasons that could not be determined based on the available evidence.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Madeira: 1 killed

Date & Time: Mar 12, 2019 at 1516 LT
Operator:
Registration:
N400JM
Flight Phase:
Survivors:
No
Site:
Schedule:
Cincinnati - Cincinnati
MSN:
31-8152002
YOM:
1981
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
6421
Captain / Total hours on type:
1364.00
Aircraft flight hours:
19094
Circumstances:
The commercial pilot was conducting an aerial observation (surveying) flight in a piston engineequipped multiengine airplane. Several hours into the flight, the pilot advised air traffic control (ATC) that the airplane had a fuel problem and that he needed to return to the departure airport. When the airplane was 8 miles from the airport, and after passing several other airports, the pilot informed ATC that he was unsure if the airplane could reach the airport. The final minutes of radar data depicted the airplane in a descent and tracking toward a golf fairway as the airplane's groundspeed decreased to a speed near the single engine minimum control airspeed. According to witnesses, they heard an engine sputter before making two loud "back-fire" sounds. One witness reported that, after the engine sputtered, the airplane "was on its left side flying crooked." Additional witnesses reported that the airplane turned to the left before it "nose-dived" into a neighborhood, impacting a tree and private residence before coming to rest in the backyard of the residence. A witness approached the wreckage immediately after the accident and observed a small flame rising from the area of the left engine. Video recorded on the witness' mobile phone several minutes later showed the airplane engulfed in flames. Examination of the wreckage revealed no evidence of any preimpact mechanical malfunctions or failures of either engine. The fuel systems feeding both engines were damaged by impact forces but the examined components generally displayed that only trace amounts of fuel remained; with the exception of the left engine nacelle fuel tank. Given the extent of the fire damage to this area of the wreckage, and the witness report that the post impact fire originated in this area, it is likely that this tank contained fuel. By design, this fuel in this tank was not able to supply fuel directly to either engine, but instead relied on an electric pump to transfer fuel into the left main fuel tank. Fire damage precluded a detailed postaccident examination or functional testing of the left nacelle fuel transfer pump. Other pilots who flew similar airplanes for the operator, along with a review of maintenance records for those airplanes, revealed at least three instances of these pumps failing in the months surrounding the accident. The other pilots also reported varying methods of utilizing fuel and monitoring fuel transfers of fuel from the nacelle fuel tanks, since there was no direct indication of the quantity of fuel available in the tank. These methods were not standardized between pilots within the company and relied on their monitoring the quantity of fuel in the main fuel tanks in order to ensure that the fuel transfer was occurring. Had the pilot not activated this pump, or had this pump failed during the flight, it would have rendered the fuel in the tank inaccessible. Given this information it is likely that the fuel supply available to the airplane's left engine was exhausted, and that the engine subsequently lost power due to fuel starvation. The accident pilot, along with another company pilot, identified fuel leaking from the airplane's left wing, about a week before the accident. Maintenance records showed no actions had been completed to the address the fuel leak. Due to damage sustained during the accident, the origin of the fuel leak could not be determined, nor could it be determined whether the fuel leak contributed to the fuel starvation and eventual inflight loss of power to the left engine. Because the left engine stopped producing power, the pilot would have needed to configure the airplane for single-engine flight; however, examination of the left engine's propeller found that it was not feathered. With the propeller in this state, the pilot's ability to maintain control the airplane would have been reduced, and it is likely that the pilot allowed the airplane's airspeed to decrease below the singleengine minimum controllable airspeed, which resulted in a loss of control and led to the airplane's roll to the left and rapid descent toward the terrain. Toxicology results revealed that the pilot had taken doxylamine, an over-the-counter antihistamine that can decrease alertness and impair performance of potentially hazardous tasks. Although the toxicology results indicated that the amount of doxylamine in the pilot's cavity blood was within the lower therapeutic range, review of ATC records revealed that the pilot was alert and that he was making necessary decisions and following instructions. Thus, the pilot's use of doxylamine was not likely a factor in the accident.
Probable cause:
Fuel starvation to the left engine and the resulting loss of engine power to that engine, and a loss of airplane control due to the pilot's failure to maintain the minimum controllable airspeed.
Final Report:

Crash of a Cessna 500 Citation I in Marietta: 1 killed

Date & Time: Mar 24, 2017 at 1924 LT
Type of aircraft:
Registration:
N8DX
Flight Type:
Survivors:
No
Site:
Schedule:
Cincinnati – Atlanta
MSN:
500-0303
YOM:
1976
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
6000
Aircraft flight hours:
9299
Circumstances:
The private pilot departed on an instrument flight rules flight plan in his twin-engine turbojet airplane. The flight was uneventful until the air traffic controller amended the flight plan, which required the pilot to manually enter the new routing information into the GPS. A few minutes later, the pilot told the controller that he was having problems with the GPS and asked for a direct route to his destination. The controller authorized the direct route and instructed the pilot to descend from 22,000 ft to 6,000 ft, during which time the sound of the autopilot disconnect was heard on the cockpit voice recorder (CVR). During the descent, the pilot told the controller that the airplane had a steering problem and was in the clouds. The pilot was instructed to descend the airplane to 4,100 ft, which was the minimum vectoring altitude. The airplane continued to descend, entered visual meteorological conditions, and then descended below the assigned altitude. The controller queried the pilot about the airplane's low altitude and instructed the pilot to maintain 4,100 ft. The pilot responded that he was unsure if he would be able to climb the airplane back to that altitude due to steering issues. The controller issued a low altitude warning and again advised the pilot to climb back to 4,100 ft. The pilot responded that the autopilot was working again and that he was able to climb the airplane to the assigned altitude. The controller then instructed the pilot to change to another radio frequency, but the pilot responded that he was still having a problem with the GPS. The pilot asked the controller to give him direct routing to the airport. A few minutes later, the pilot told the controller that he was barely able to keep the airplane straight and its wings level. The controller asked the pilot if he had the airport in sight, which he did not. The pilot then declared an emergency and expressed concerns related to identifying the landing runway. Afterward, radio contact between the controller and the pilot was lost. Shortly before the airplane impacted the ground, a witness saw the airplane make a complete 360° roll to the left, enter a steep 90° bank to the left, roll inverted, and enter a vertical nose-down dive. Another witness saw the airplane spiral to the ground. The airplane impacted the front lawn of a private residence, and a postcrash fire ensued.The pilot held a type rating for the airplane, but the pilot's personal logbooks were not available for review. As a result, his overall currency and total flight experience in the accident airplane could not be determined. The airplane was originally certified for operations with a pilot and copilot. To obtain an exemption to operate the airplane as a single pilot, a pilot must successfully complete an approved single-pilot exemption training course annually. The accident airplane was modified, and the previous owner was issued a single-pilot conformity certificate by the company that performed the modifications. However, there was no record indicating that the accident pilot received training under this exemption. Several facilities that have single-pilot exemption training for the accident airplane series also had no record of the pilot receiving training for single-pilot operations in the accident airplane. Therefore, unlikely that the pilot was properly certificated to act as a single-pilot. The GPS was installed in the airplane about 3.5 years before the accident. A friend of the pilot trained him on how to use the GPS. The friend said that the pilot generally was confused about how the unit operated and struggled with pulling up pages and correlating data. The friend of the pilot had flown with him several times and indicated that, if an air traffic controller amended a preprogrammed flight plan while en route, the pilot would be confused with the procedure for amending the flight plan. The friend also said the pilot depended heavily on the autopilot, which was integrated with the GPS, and that he would activate the autopilot immediately after takeoff and deactivate it on short final approach to a runway. The pilot would not trim the airplane before turning on the autopilot because he assumed that the autopilot would automatically trim the airplane, which led to the autopilot working against the mis-trimmed airplane. The friend added that the pilot was "constantly complaining" that the airplane was "uncontrollable." A postaccident examination of the airplane and the autopilot system revealed no evidence of any preimpact deficiencies that would have precluded normal operation. This information suggests that pilot historically had difficulty flying the airplane without the aid of the autopilot. When coupled with his performance flying the airplane during the accident flight without the aid of the autopilot, it further suggests that the pilot was consistently unable to manually fly the airplane. Additionally, given the pilot's previous experience with the GPS installed on the airplane, it is likely that during the accident flight the pilot became confused about how to operate the GPS and ultimately was unable to properly control of the airplane without the autopilot engaged. Based on witness information, it is likely that during the final moments of the flight the pilot lost control of the airplane and it entered an aerodynamic stall. The pilot was then unable to regain control of the airplane as it spun 4,000 ft to the ground.
Probable cause:
The pilot's failure to maintain adequate airspeed while manually flying the airplane, which resulted in the airplane exceeding its critical angle of attack and experiencing an aerodynamic stall. Contributing to the accident was the pilot's inability control the airplane without the aid of the autopilot.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Taylor Mill

Date & Time: Feb 16, 2003 at 1520 LT
Registration:
N130CM
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Manhattan – Cincinnati
MSN:
31-7652142
YOM:
1976
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3050
Captain / Total hours on type:
240.00
Aircraft flight hours:
8337
Circumstances:
According to the pilot, he planned the estimated the 726 statute mile flight would take approximately 3 hours and 46 minutes, with one stop to pick up cargo. The available fuel for the flight was 182 gallons, which equaled an approximate 4 hour and 55 minutes endurance, assuming a 40 gallon per hour fuel burn. The flight proceeded uneventfully to the first stop; the airplane was not fueled, and it departed. As the flight neared the destination airport, the pilot began to get nervous because the main tanks were "going fast." He switched to the auxiliary fuel tanks, to "get all of the fuel out of them," and switched back to the main tanks. While executing an approach to the airport, the pilot advised the approach controller that he had lost power to the right engine, and then shortly thereafter, reported losing power to the left engine. The pilot elected to perform a forced landing to a railroad yard. After touching down, the left wing struck a four-foot high dirt mound, and separated from the main fuselage. The airplane came to rest upright on a railroad track. The pilot additionally stated that the loss of power to both engines was due to fuel exhaustion, and poor fuel planning.
Probable cause:
The pilot's inaccurate in-flight planning and fuel consumption calculations, and his improper decision not to land and refuel.
Final Report:

Crash of a Piper PA-60 Aerostar (Ted Smith 600) in Mansfield

Date & Time: Dec 3, 1987 at 2159 LT
Registration:
N500TS
Flight Type:
Survivors:
Yes
Schedule:
Louisville – Cincinnati – Cleveland
MSN:
60-0500-162
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6870
Captain / Total hours on type:
1170.00
Aircraft flight hours:
5176
Circumstances:
The pilot departed Louisville, KY reportedly with a known oil leak in the right engine and was on the second leg of an on-demand air taxi cargo flight. About 14 minutes after entering Mansfield approach control airspace, the pilot requested and received an altitude change from 5,000 to 3,000 ft because he 'was picking up a lot of ice.' After entering Cleveland approach airspace he reported the right engine had failed and requested to return to Mansfield. The pilot was informed of Mansfield weather. He then indicated he wanted to try Cleveland, then reported he could not maintain altitude and wanted to go to Mansfield. The pilot was receiving vectors from Mansfield for an ASR approach to runway 23 and at about 1 1/2 miles from the threshold the pilot reported he was lowering the landing gear. The aircraft then disappeared from the radar scope. Investigation revealed improper weld repairs to the right engine case and separation of the number six cylinder from the case due to fatigue cracking in the through bolts and studs.
Probable cause:
Occurrence #1: loss of engine power (total) - mech failure/malf
Phase of operation: cruise - normal
Findings
1. 1 engine - failure, total
2. Engine assembly, crankcase - cracked
3. (c) maintenance, major repair - improper - other maintenance personnel
4. (c) engine assembly, other - fatigue
5. (c) engine assembly, cylinder - separation
6. (f) operation with known deficiencies in equipment - continued - pilot in command
7. (f) company-induced pressure - pilot in command
----------
Occurrence #2: in flight collision with object
Phase of operation: approach - faf/outer marker to threshold (ifr)
Findings
8. (f) object - tree(s)
9. (f) weather condition - icing conditions
10. (f) weather condition - below approach/landing minimums
11. (f) light condition - dark night
12. (c) in-flight planning/decision - delayed - pilot in command
----------
Occurrence #3: in flight collision with terrain/water
Phase of operation: descent - uncontrolled
Final Report:

Crash of a Cessna 340A in Cincinnati: 4 killed

Date & Time: Jun 20, 1984 at 1217 LT
Type of aircraft:
Registration:
N5345J
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Cincinnati – Williamsburg
MSN:
340A-0418
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
1900
Aircraft flight hours:
1000
Circumstances:
Pilot requested fuel from fbo but failed to make it clear what type he wanted. The fbo personnel misunderstood the pilot's request and refueled the aircraft with 'Jet-A' instead of aviation grade gasoline. The pilot did not monitor the refueling process and failed to recognize the wrong fuel as stated on fuel receipt. The pilot did not realize the improper fuel on his preflight of the aircraft. The aircraft departed and shortly there after the pilot radioed that he was returning to the airport because of a serious problem. Witnesses near the accident site stated that the aircraft was in a left bank (about 45° bank angle) before impact in a densely wooded area. The aircraft was destroyed and all four occupants were killed.
Probable cause:
Occurrence #1: loss of engine power (partial) - nonmechanical
Phase of operation: takeoff - initial climb
Findings
1. (c) fluid,fuel - improper
2. (c) refueling - improper - fbo personnel
3. (f) information unclear (phraseology) - pilot in command
4. (f) fbo personnel
5. (f) refueling - inattentive - pilot in command
6. (c) aircraft preflight - inadequate - pilot in command
----------
Occurrence #2: forced landing
Phase of operation: descent - emergency
----------
Occurrence #3: in flight collision with object
Phase of operation: descent - emergency
Findings
7. Object - tree(s)
----------
Occurrence #4: fire/explosion
Phase of operation: other
Final Report:

Crash of a Beechcraft 65A-80 Queen Air in Cincinnati: 2 killed

Date & Time: Oct 25, 1973 at 0438 LT
Type of aircraft:
Registration:
N6875Q
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Cincinnati - Salina
MSN:
LD-191
YOM:
1964
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1500
Captain / Total hours on type:
40.00
Circumstances:
Shortly after a night takeoff from Cincinnati-Lunken Field Airport, while in initial climb in foggy conditions, the airplane rolled to the left. The pilot elected to regain control when the airplane struck trees and crashed in the Miami River. The pilot and a passenger were killed while a second passenger was seriously injured.
Probable cause:
Loss of control after takeoff due to several errors on part of the pilot. The following factors were reported:
- Premature liftoff,
- Spatial disorientation,
- Failed to maintain directional control,
- Failed to obtain flying speed,
- Low ceiling and fog,
- Limited visibility,
- Drifted left after takeoff then rolled into trees.
Final Report:

Crash of a Beechcraft H18S in Cincinnati

Date & Time: Aug 9, 1964 at 2020 LT
Type of aircraft:
Registration:
N517DC
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
BA-627
YOM:
1962
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4016
Captain / Total hours on type:
600.00
Circumstances:
Shortly after takeoff from Cincinnati-Lunken Field Airport, while in initial climb, the pilot informed ATC about the failure of the left engine. He elected to make an emergency landing in a field when control was lost. The airplane crashed in a field located near the runway end. All four occupants were injured and the aircraft was destroyed.
Probable cause:
Failure of malfunction of the left engine during initial climb and stall due to the failure of the ignition system (spark plug). The loss of control was caused by improper emergency procedures and single engine flight procedures.
Final Report:

Crash of a Ford 5 in Cincinnati: 6 killed

Date & Time: Aug 9, 1931 at 0840 LT
Type of aircraft:
Operator:
Registration:
NC9662
Flight Phase:
Survivors:
No
Schedule:
Cleveland – Cincinnati – Atlanta
MSN:
5-AT-029
YOM:
1929
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
6
Circumstances:
One minute after takeoff from Cincinnati-Lunken Field Airport, while in initial climb, the right engine failed. The pilot attempted to return to the airport when the aircraft stalled and crashed. All six occupants were killed.
Crew:
M. T. Odell, pilot,
William J. Dewald, copilot.
Passengers:
William E. Keith,
W. P. Brimberry,
V. G. Baum,
Wrenna D. Hughes.
Probable cause:
It was determined that prior to the crash, the aircraft’s starboard power plant had torn loose in the air, apparently after the corresponding propeller broke.