WPR15FA143 · Cessna T210M
Cessna T210M · Accident: collision during takeoff/landing
From Upper Loon Creek US Forest Service Airport (U72) to Driggs/Reed Memorial Airport (DIJ)
Event
- NTSB case
- WPR15FA143
- 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
- 4 · 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 T210M
- 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
- N732YQ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Upper Loon Creek US Forest Service Airport (U72), Challis, IDTo Driggs/Reed Memorial Airport (DIJ), Driggs, ID
- Aircraft age
- About 38 years (built 1977)
- 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
- Takeoff
- 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
- Collision during takeoff/landing
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot and three passengers had landed at a remote airstrip earlier in the morning to visit the pilot's ranch. The published guidance for the airstrip noted that the runway was 2,500 ft long and 75 ft wide. After being on the ground about 2 hours 30 minutes, the pilot indicated to ranch personnel that he wanted to depart before the wind increased. Shortly thereafter, the airplane departed with an estimated 4- to 5-kt tailwind. During the initial climb, the nose landing gear and left tire impacted a tree (which was about 50 ft tall) located about 100 ft from the fence that made the perimeter of the runway. The left tire then likely impacted the left horizontal stabilizer and elevator, rendering the airplane uncontrollable. The airplane then descended into a creek and came to rest inverted; a postimpact fire ensued. There was no evidence of any mechanical malfunctions or failures with the airframe or engine that would have precluded normal operation.
The performance data were calculated using the estimated airplane and environmental conditions at the time of the accident. The distance required to clear a 50-ft obstacle for a takeoff with a 5-kt tailwind from a dry grass runway similar to the accident runway was about 2,675 ft. The actual distance from the area where the pilot began the takeoff roll to the first impacted tree was about 2,625 ft, which indicates that the airplane did not have the sufficient performance capability to climb over the tree.
The pilot frequently flew into the airstrip and was familiar with the terrain and departure procedures, and GPS data revealed that the pilot departed from the airstrip on nine prior occasions in the past year. Comparison of these flights to the accident flight revealed that the pilot's flightpath was normally to the right of the accident flightpath. The pilot likely would have not been able to see the tree due to the airplane's nose-high pitch configuration during the takeoff.
Probable cause
The pilot's attempt to depart in conditions that resulted in the airplane having insufficient performance capability, which resulted in a collision with a tree.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR15FA143
- Event ID
- 20150411X00127
- Case number
- WPR15FA143
- 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: 620b7fd328f3dca1a9b65a9ca6866d4e0eac920894c55fcddccc9fb16e9c32bc; retrieved 2026-09-14T17:35:09.171Z.