SEA05CA116 · Taylorcraft BC12-D
Taylorcraft BC12-D · Accident: in flight collision with object on approach
From Big Creek Airport (U60) to Johnson Creek Airport (3U2)
Event
- NTSB case
- SEA05CA116
- 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
Taylorcraft BC12-D
- Aircraft type
- Taylorcraft BC12
- 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
- N96156
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Big Creek Airport (U60), Big Creek, IDTo Johnson Creek Airport (3U2), Yellow Pine, ID
- 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 › Altitude/clearance, not obtained
- Pilot in command › Go-around, delayed
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 he made an approach to runway 17. He was "slightly high" on final approach, slipped the airplane, and his airspeed increased by "a few miles an hour." When the airplane was 3 to 5 feet above the ground, at an airspeed of 50 miles per hour, with 300 feet of runway remaining, the pilot executed a go around. After completing 90 degrees of left turn, the airplane impacted trees and descended to the ground. Both wings and the fuselage sustained structural damage.
Probable cause
The pilot's delay in executing a go-around which resulted in his failure to obtain altitude/clearance with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA05CA116
- Event ID
- 20050628X00890
- Case number
- SEA05CA116
- 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: 050db04b9373e42b1a7760de49ccf2b830d1da6d30b31a9bc379b69d7dd2f9d9; retrieved 2026-09-22T05:47:56.199Z.