WPR10CA436 · Cessna TU206F
Cessna TU206F · Accident: loss of control in flight during takeoff
From Inshallah International Airport (7OR8) to Portland Hillsboro Airport (HIO)
Event
- NTSB case
- WPR10CA436
- 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
Cessna TU206F
- Aircraft type
- Cessna 206
- 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
- N1406Q
- Operator
- Fancho F. Stubblefield · private individual
- Onboard fatalities
- Unknown
- Route
- From Inshallah International Airport (7OR8), Seneca, ORTo Portland Hillsboro Airport (HIO), Portland, OR
- 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
- 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
- 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
- Personnel issues › Task performance
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 reported that all airplane systems were operating normally during his preflight inspection and attempted takeoff. The pilot stated that, because of the rocky runway condition, he made a combination soft- and short-field takeoff with the wing flaps extended to the 20-degree position. The pilot reported that the engine produced full power during the takeoff roll and that initially the airplane rolled straight down the runway's centerline. He also reported that it was his standard procedure to lift the airplane off the ground upon accelerating to 55 mph. Thereafter, he relaxes the back pressure on the yoke to accelerate to 90 mph, and then he begins climbing. The pilot reported that, during the accident flight, he immediately felt the nose raise and the airplane started tracking left toward the left side of the runway. Although he attempted to maintain directional control, the airplane veered left, and a wing broke upon impacting a juniper tree and terrain.
Probable cause
The pilot's failure to maintain directional control after takeoff, resulting in a collision with a tree.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10CA436
- Event ID
- 20100830X00534
- Case number
- WPR10CA436
- 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: b5704b919e657566fe354e70814a5ae0561074ab60fbe1e835fbb47dbee9be6e; retrieved 2026-09-15T15:00:31.669Z.