Country

Crash of a Socata TBM-700 in Brasília

Date & Time: Jan 31, 2022 at 0930 LT
Type of aircraft:
Operator:
Registration:
PP-INQ
Flight Type:
Survivors:
Yes
Schedule:
Bahia - Brasília
MSN:
558
YOM:
2010
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing at Brasília-Nelson Piquet Airport, the single engine airplane went out of control and veered off runway. It went down into a ravine and came to rest into trees. All five occupants evacuated safely while the aircraft was destroyed. The pilot reported he encountered strong winds upon landing.

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
Circumstances:
On August 20, 2021, about 1440 eastern daylight time, a Socata TBM 700A airplane, N700DT, was destroyed when it was involved in an accident near Urbana, Ohio. The pilot sustained fatal injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Preliminary air traffic control information revealed the airplane was en route from the Erie Ottawa Airport (PCW), Port Clinton, Ohio, to the Cincinnati Municipal Airport (LUK), Cincinnati, Ohio. The airplane departed runway 9 at PCW and climbed to flight level 200 before beginning to descend. The airplane was southbound, descending to 12,000 ft mean sea level (msl), and established communications with the assigned terminal radar approach control controller. The controller cleared the pilot to descent to 10,000 ft msl and proceed direct to LUK. While descending through 12,100 ft msl, the airplane entered a left turn. The controller observed the left turn and asked the pilot if everything was alright; there was no response from the pilot. Radar contact was subsequently lost with the airplane. The controller’s further attempts to establish communications were unsuccessful. A witness, located about 2 miles south of the accident location, stated that he observed the airplane at a high altitude in a nose-dive descent toward the terrain. He reported the airplane was not turning or spinning; it was headed straight down. The witness observed no signs of distress, such as smoke, fire, or parts coming off the airplane, and he stated the airplane’s engine was at full throttle. The witness lost sight of the airplane as it descended behind some trees. The accident site was located 1.3 miles northwest of the last radar contact. The accident site showed the airplane impacted trees, two powerlines, and the terrain in a left-wing low attitude. The initial ground scar, located in a residential yard, contained separated components of the left wing. The airplane crossed a highway, struck trees and a ditch, and then continued into mature potato and soybean fields. The airplane wreckage was scattered at a distance of about 2,050 ft along a measured magnetic heading of 275°. According to acquaintances of the pilot, the pilot purchased the airplane about 9 days before the accident. Following the purchase, the pilot and a flight instructor completed several hours of ground school and 15.5 hours of dual instruction in the airplane.

Crash of a Socata TBM-700 in Lansing: 5 killed

Date & Time: Oct 3, 2019 at 0858 LT
Type of aircraft:
Operator:
Registration:
N700AQ
Flight Type:
Survivors:
Yes
Schedule:
Indianapolis - Lansing
MSN:
252
YOM:
2003
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
1404
Captain / Total hours on type:
76.00
Aircraft flight hours:
3550
Circumstances:
The pilot was conducting an instrument approach at the conclusion of a cross-country flight when the airplane entered a shallow climb and left turn away from the runway heading about 0.5-mile from the intended runway. According to airspeeds calculated from automatic dependent surveillance-broadcast position data, the airplane’s calibrated airspeed was 166 knots when it crossed over the final approach fix inbound toward the runway and was about 84 knots when it was on a 0.5-mile final approach. The airplane continued to decelerate to 74 knots while it was in a shallow climb and left turn away from the runway heading. At no point during the approach did the pilot maintain the airframe manufacturer’s specified approach speed of 85 knots. The airplane impacted the ground in an open grass field located to the left of the extended runway centerline. The airplane was substantially damaged when it impacted terrain in a wings level attitude. The postaccident examination did not reveal any anomalies that would have precluded normal operation of the airplane. The altitude and airspeed trends during the final moments of the flight were consistent with the airplane entering an aerodynamic stall at a low altitude. Based on the configuration of the airplane at the accident site, the pilot likely was retracting the landing gear and flaps for a go around when the airplane entered the aerodynamic stall. The airplane was operating above the maximum landing weight, and past the aft center-of-gravity limit at the time of the accident which can render the airplane unstable and difficult to recover from an aerodynamic stall. Additionally, without a timely corrective rudder input, the airplane tends to roll left after a rapid application of thrust at airspeeds less than 70 knots, including during aerodynamic stalls. Although an increase in thrust is required for a go around, the investigation was unable to determine how rapidly the pilot increased thrust, or if a torque-roll occurred during the aerodynamic stall.
Probable cause:
The pilot’s failure to maintain airspeed during final approach, which resulted in a loss of control and an aerodynamic stall at a low altitude, and his decision to operate the airplane outside of the approved weight and balance envelope.
Final Report:

Crash of a Socata TBM-700 in Evanston: 2 killed

Date & Time: Feb 18, 2018 at 1505 LT
Type of aircraft:
Registration:
N700VX
Flight Type:
Survivors:
No
Schedule:
Tulsa – Evanston
MSN:
118
YOM:
1997
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
4154
Captain / Total hours on type:
100.00
Aircraft flight hours:
3966
Circumstances:
The commercial pilot was conducting an instrument approach following a 3.5-hour cross-country instrument flight rules (IFR) flight in a single-engine turboprop airplane. About 1.6 miles from the runway threshold, the airplane began a climb consistent with the published missed approach procedure; however, rather than completing the slight left climbing turn toward the designated holding point, the airplane continued in an approximate 270° left turn, during which the airplane's altitude varied, before entering a descending right turn and impacting terrain. Tree and ground impact signatures were consistent with a 60° nose-low attitude at the time of impact. No distress calls were received or recorded from the accident flight. A postimpact fire consumed a majority of the cockpit and fuselage. Weather information for the time of the accident revealed that the pilot was operating in IFR to low IFR conditions with gusting surface winds, light to heavy snow, mist, cloud ceilings between 700 and 1,400 ft above ground level with clouds extending through 18,500 ft, and the potential for low-level wind shear and clear air turbulence. The area of the accident site was under AIRMETs for IFR conditions, mountain obscuration, moderate icing below 20,000 ft, and moderate turbulence below 18,000 ft. In addition, a winter storm warning was issued about 6 hours before the flight departed. Although the pilot received a weather briefing about 17 hours before the accident, there was no indication that he obtained updated weather information before departure or during the accident flight. Examination of the airframe and engine did not reveal any preimpact anomalies that would have precluded normal operation; however, the extent of the fire damage precluded examination of the avionics system. The airplane was equipped with standby flight instruments. An acquaintance of the pilot reported that the pilot had experienced an avionics malfunction several months before the accident during which the airplane's flight display went blank while flying an instrument approach. During that occurrence, the pilot used ForeFlight on his iPad to maneuver back to the northeast and fly the approach again using his own navigation. During the accident flight, the airplane appeared to go missed approach, but rather than fly the published missed approach procedure, the airplane also turned left towards to northeast. However, it could not be determined if the pilot's actions were an attempt to fly the approach using his own navigation or if he was experiencing spatial disorientation. The restricted visibility and turbulence present at the time of the accident provided conditions conducive to the development of spatial disorientation. Additionally, the airplane's turning flight track and steep descent profile are consistent with the known effects of spatial disorientation.
Probable cause:
The pilot's loss of control due to spatial disorientation.
Final Report: