CEN14CA132 · Taylorcraft BC12 D
Taylorcraft BC12 D · Accident: collision during takeoff/landing
From HFX · Hartford, WI to Wittman Regional Airport (OSH)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN14CA132
- 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
- N43955
- Operator
- Hoagland Carri Eve
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From HFX · Hartford, WITo Wittman Regional Airport (OSH), Oshkosh, WI
- Aircraft age
- About 68 years (built 1946)
- 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
- 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
- Environmental issues › Physical environment
- 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 he was departing to the north from a snow covered grass runway in a ski-equipped tail-wheel airplane. A plowed asphalt runway intersected the snow covered runway, and snowbanks were located on the north and south side of the plowed runway. The pilot reported that during takeoff, the airplane impacted the snowbank on the south side of the asphalt runway and nosed over. The airplane sustained substantial damage to the fuselage, wings, and empennage. The pilot reported that there was no malfunction or system failure of the airplane before the accident.
Probable cause
The pilot's inadequate preflight planning and failure to inspect the runway before departure.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14CA132
- Event ID
- 20140210X90922
- Case number
- CEN14CA132
- 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: 8056efe66093e31f17174fde7431c31675fc7dbe2cee60db03168dc81265f648; retrieved 2026-09-15T23:18:39.579Z.