SEA05FA072 · Stinson 10-A
Stinson 10-A · Accident: in flight collision with object on approach
From Oak Harbor, WA to an unrecorded destination
Event
- NTSB case
- SEA05FA072
- 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
- 2 · 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 10-A
- Aircraft type
- Stinson 10
- 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
- N39482
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Oak Harbor, WATo not recorded
- 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
- Approach · VFR go-around
- First occurrenceThe 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
- In flight collision with object
- 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
- Pilot in command › Clearance, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
A pilot and his passenger flying a Cessna 170 reported that they observed a small airplane on approach, to the east, to a small airstrip. The passenger watched the aircraft on final approach to the point where a go-around was initiated. She was not sure if the aircraft actually touched down or not. She watched it as it pulled up over the trees and continued to the east. She momentarily lost sight of the aircraft due to interference with the frame of the door of the aircraft she was in. When she tried to find the aircraft again, she spotted a plume of smoke. Witnesses near the accident site reported that the aircraft was seen traveling in an easterly direction, very low and near the tree line just before the collision with several trees. The witnesses reported that the engine was running, but seemed like it was strained or not at full power. The local area Paramedic who tended to the pilot before he was airlifted to a hospital reported that he asked the pilot if he had a medical condition, which the pilot responded that he did not. The pilot was also able to recall the day and date and further reported to the paramedic that he "overshot his landing," and that either the "winds or wing flipped him over." At the time of the accident, the winds were from the west at ten knots. During the post-accident inspection of the airframe and engine, no evidence of a mechanical failure or malfunction was found.
Probable cause
The pilot's failure to adequately plan the approach for landing and maintain clearance from trees during the go-around. A tailwind and trees were factors.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA05FA072
- Event ID
- 20050412X00444
- Case number
- SEA05FA072
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 77b6c5c00c080fe2695aa31370b02aa24f4b703c26cfe5aba32420f09557016d; retrieved 2026-09-20T18:05:02.367Z.