WPR11LA307 · Stinson 108-2
Stinson 108-2 · Accident during initial climb
From Columbia Airport (O22) to Redding Municipal Airport (RDD)
Narrative check · The NTSB narrative appears to contradict this record's damage. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR11LA307
- 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
- 0 · 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
Stinson 108-2
- Aircraft type
- Stinson 108
- 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
- N9351K
- Operator
- Nicholas K Riney · private individual
- Onboard fatalities
- Unknown
- Route
- From Columbia Airport (O22), Columbia, CATo Redding Municipal Airport (RDD), Redding, CA
- Aircraft age
- Not recorded
- 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
- Initial climb
- 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
- Unknown or undetermined
- 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 Possible conflict
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The day before the accident flight, the pilot examined the airplane and discovered water in the fuel tanks. He drained the water and filled the fuel tanks in preparation for the upcoming delivery flight to the owner. The pilot and his passenger departed the airport, which is approximately at sea level, and made an uneventful flight to an airport about 270 miles away at an elevation of 2,118 feet. After refueling, the pilot observed other airplanes departing on runway 17 but decided to use runway 35 due to his observation of wind conditions, which indicated very light wind from the north. The pilot's observation of the wind direction was not supported by the recorded meteorological data, which indicated a 3-knot wind from 230 degrees. However, a note for the airport in the FAA Airport/Facilities Directory stated that "Varying wind direction and velocity may be encountered at midpoint of Rwy 17–35 due to terrain features and wind flow patterns"; therefore, the actual wind conditions at the time of the airplane’s departure could not be determined. At the time of the attempted takeoff, the temperature was 34 degrees Celsius, resulting in a density altitude of about 4,860 feet. The pilot reported that the engine runup was normal and that the takeoff seemed normal until the airplane reached the end of the runway, where the climb performance deteriorated. The airplane was unable to clear the obstacles beyond the end of the runway, impacted trees and terrain, and came to rest about 1,600 feet beyond the runway end. A postimpact fire consumed much of the airframe and all of the baggage, which included some of the airplane’s records. After the accident, the pilot reported that the takeoff and climb for the previous flight was normal but that during cruise, the airplane seemed to operate at a higher pitch attitude than expected. The condition of the wreckage precluded any evaluation of the primary factors, such as wing or control surface rigging or the accuracy of the tachometer or airspeed indicator, that could have accounted for the reported phenomenon. According to the data presented in the published airplane performance information, takeoff and continued flight should have been possible. However, the expected takeoff and climb performance could not be accurately determined because it was not possible to account for multiple differences between the performance data baseline conditions and the actual or reported conditions, such as airplane weight, runway slope, flap setting, and speed. The pilot did not report any engine roughness or rpm loss; therefore, the event was not consistent with water ingestion by the engine. Examination of the engine revealed compression deficiencies in some cylinders, but it could not be determined whether those were present before the accident and fire. While examination found no evidence of any definitive preimpact mechanical malfunctions or failures that would have precluded normal climb and continued flight, the postaccident state of the airplane prevented complete evaluation and analysis of all possible scenarios.
Probable cause
The airplane’s failure to climb at a sufficient rate to clear trees and terrain beyond the end of the runway for reasons that could not be determined because postaccident examination did not reveal any mechanical malfunctions or failures that would have precluded normal operation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR11LA307
- Event ID
- 20110705X62537
- Case number
- WPR11LA307
- 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: df849976c89c472b66ad92799537e66c061cbb4191b089a23e8b7856af0061da; retrieved 2026-09-15T16:23:56.673Z.