WPR18FA276 · Cessna T210 M
T And C Aircraft Cessna T210 M · Accident: aerodynamic stall/spin while maneuvering
From Sunrise Skypark Airport (ID40) to Murphy Airport (1U3)
Event
- NTSB case
- WPR18FA276
- 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
- 3 · 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
Cessna T210 M
- Aircraft type
- Cessna 210
- 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
- N732MV
- Operator
- T And C Aircraft
- Onboard fatalities
- Unknown
- Route
- From Sunrise Skypark Airport (ID40), Marsing, IDTo Murphy Airport (1U3), Murphy, ID
- Aircraft age
- About 42 years (built 1976)
- 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
- Maneuvering · low-altitude flying
- 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
- Aerodynamic stall/spin
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot and two passengers departed on a local area flight through mountainous terrain to a nearby airport. A review of primary targets that were consistent with the airplane’s flight track; initially, for a 3 minute period, the airplane was flying between 3,200 and 3,400 ft mean sea level (msl) at an average speed of 131 knots calibrated airspeed (KCAS). Radar data were lost for about the next 4 minutes due to mountainous terrain. Once the radar returns were picked up again, for about the next 4 minutes, the flight track showed the airplane continuing a southerly track, climbing from 4,700 to 6,500 ft msl. The last three radar returns showed that, during the last 36 seconds of flight, the airplane’s altitude above the ground decreased as the terrain rose such that the airplane was about 150 ft above ground level at the last radar return; the airspeed decreased to less than 70 KCAS by the end of the data. The wreckage was located near the bottom of a valley about 1,950 ft west and 15.5 nm east of the wreckage. Postaccident examination of the airplane and engine revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. Using the approximate conditions that existed at the time of the accident, including an estimated airplane gross weight of 3,900 lbs (about 100 lbs over the airplane’s maximum allowable gross weight) and flaps at 10°, the airplane’s stall speed was estimated to be about 68 KCAS. A ground scar at the accident site indicated that the left wing impacted terrain first, and the wreckage lay along a heading of 345°, indicating that the pilot was likely turning the airplane during the accident sequence. Given this evidence and that the airplane was losing speed as it climbed over rising terrain near the accident site and was approaching or at its stall speed by the end of the radar data, it is likely that the pilot did not maintain adequate airspeed while making a left turn in mountainous terrain. The gusting wind and low-level wind shear conditions could also contribute to the airplane exceeding its critical angle of attack, which resulted in an aerodynamic stall with the left wing low. Although the pilot had type 2 diabetes, the accident circumstances are not consistent with incapacitation; therefore, it is unlikely that the pilot's diabetes contributed to the accident. Toxicology testing indicated that the pilot had taken buprenorphine, which can cause somnolence and impaired decision-making, at some point before the accident. However, based on the available information, it could not be determined whether the pilot's use of buprenorphine contributed to the accident.
Probable cause
The pilot's failure to maintain adequate airspeed and his exceedance of the airplane’s critical angle of attack while making a turn in gusting wind conditions while flying through hilly terrain, which resulted in an aerodynamic stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR18FA276
- Event ID
- 20180930X33629
- Case number
- WPR18FA276
- 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, coordinates. 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: 7cd5d760253441b59fda70389f4b3a3b2a9504701db752b88d60e047e768facb; retrieved 2026-09-15T06:48:47.412Z.