Socata TBM 700 N702H
22 March 2014 · Ridgway, Colorado, United States · Fatal
Summary
On 22 March 2014 at about 20:00 local time, a Socata TBM 700 registered N702H was involved in an accident near Ridgway, Colorado, United States. 5 people were on board and 5 died. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 20:00
- Classification
- Accident
- Location
- Ridgway, Colorado, United States
- Nearest airport
- Montrose Regional (MTJ)
- Coordinates
- 38.2181, -107.7453
- Aircraft
- Socata TBM 700
- Registration
- N702H
- Category
- Airplane
- Year built
- 1996
- Engines
- 1
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Bartlesville → Montrose
- Aircraft damage
- Substantial
- Weather
- VMC
- Light
- Day
- NTSB number
- CEN14FA167
People
5 people died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 5 | 5 | 0 | 0 | 0 |
Probable cause
The pilot's loss of airplane control during an instrument approach procedure, which resulted in the airplane exceeding its critical angle of attack and entering an inadvertent aerodynamic stall and spin.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
About 3 months before the accident, the pilot received about 9 hours of flight instruction, including completion of an instrument proficiency check, in the airplane. The accident flight was a personal cross-country flight operated under instrument flight rules (IFR). Radar track data depicted the flight proceeding on a west-southwest course at 15,800 ft mean sea level (msl) as it approached the destination airport. The flight was cleared by the air traffic controller for a GPS approach, passed the initial approach fix, and, shortly afterward, began a descent as permitted by the approach procedure. The track data indicated that the flight became established on the initial approach segment and remained above the designated minimum altitude of 12,000 ft msl. Average descent rates based on the available altitude data ranged from 500 feet per minute (fpm) to 1,000 fpm during this portion of the flight. At the intermediate navigation fix, the approach procedure required pilots to turn right and track a north-northwest course toward the airport. The track data indicated that the flight entered a right turn about 1 mile before reaching the intermediate fix. As the airplane entered the right turn, its average descent rate reached 4,000 fpm. The flight subsequently tracked northbound for nearly 1-1/2 miles. During this portion of the flight, the airplane initially descended at an average rate of 3,500 fpm then climbed at a rate of 1,800 fpm. The airplane subsequently entered a second right turn. The final three radar data points were each located within 505 ft laterally of each other and near the approximate accident site location. The average descent rate between the final two data points (altitudes of 10,100 ft msl and 8,700 ft msl) was 7,000 fpm. About the time that the final data point was recorded, the pilot informed the air traffic controller that the airplane was in a spin and that he was attempting to recover. No further communications were received from the pilot. The airplane subsequently impacted the surface of a reservoir at an elevation of about 6,780 ft and came to rest in 60 ft of water. A detailed postaccident examination of the airframe, engine and propeller assembly did not reveal any anomalies consistent with a preimpact failure or malfunction. The available meteorological data suggested that the airplane encountered clouds (tops about 16,000 ft msl or higher and bases about 10,000 ft msl) and was likely operating in IFR conditions during the final 15 minutes of the flight; however, no determination could be made regarding whether the clouds that the airplane descended through were solid or layered. In addition, the data suggested the possibility of both light icing and light turbulence between 12,000 ft msl and 16,000 ft msl along the flight path. Although the pilot appeared to be managing the flight appropriately during the initial descent, it could not be determined why he was unable to navigate to the approach fixes and maintain control of the airplane as he turned toward the airport and continued the descent.
Quoted verbatim from the NTSB record.
Other Socata TBM-700 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 6 Aug 2014 | Socata TBM 700 | Saint Jean les Deux Jumeaux, France | - | Fatal | 2 |
| 5 Oct 2014 | Socata TBM 700 | Fayetteville, Georgia, United States | - | Serious injuries | - |
| 5 Sep 2014 | Socata TBM 700 | Caribbean Sea, Unknown | - | Fatal | 2 |
| 29 Jul 2015 | Socata TBM 700 | Milwaukee, Wisconsin, United States | Trustey Management Corporation | Fatal | 2 |
| 19 Nov 2013 | Socata TBM 700 | Mouffy, France | Fabry Air Corp Trustee | Fatal | 6 |
| 8 Aug 2013 | Socata TBM-700 | Vertaizon, France | - | Fatal | 3 |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 29 Jan 2014 | Diamond DA20-C1 | Fort Carson, Colorado, United States | Doss Aviation Inc | Minor injuries | - |
| 19 Apr 2014 | Firefly 8B-15 | Security, Colorado, United States | Howes Skip | Serious injuries | - |
| 27 Jul 2014 | Beechcraft 35-C33A | Pueblo, Colorado, United States | Henke Petroleum Corp | Serious injuries | - |
| 21 Apr 2014 | American AA 1 | Peyton, Colorado, United States | - | No injuries | - |
| 14 Feb 2014 | Cirrus SR22 | Gunnison, Colorado, United States | - | No injuries | - |
| 16 Feb 2014 | Beechcraft 35/33 | Telluride, Colorado, United States | Arizona Cloudbusters Inc | Fatal | 3 |