FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14FA167 · SOCATA TBM 700

22 Mar 2014 · Ridgway, CO, United States

SOCATA TBM 700 · Accident: loss of control in flight on approach

From Bartlesville Municipal Airport (BVO) to Montrose Regional Airport (MTJ)

Report a problem

Event

NTSB case
CEN14FA167
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
5 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

SOCATA TBM 700

Aircraft type
Socata TBM-700
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N702H
Operator
Unknown
Onboard fatalities
Unknown
Route
From Bartlesville Municipal Airport (BVO), Bartlesville, OKTo Montrose Regional Airport (MTJ), Montrose, CO
Aircraft age
About 18 years (built 1996)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · IFR initial approach
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

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.

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14FA167
Event ID
20140322X03239
Case number
CEN14FA167
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: f8884d23048709f53d40e66063a7f6b1e6a32ae1c1dbf5abf8047c848b5306a2; retrieved 2026-09-14T16:11:55.998Z.