CEN24LA341 · Taylorcraft BC12-D
Taylorcraft BC12-D · Accident: loss of engine power (partial) en route
From Rapid City, SD to Hulett, SD
Event
- NTSB case
- CEN24LA341
- 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
- Event fatalities
- Unknown
- 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
- N95078
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rapid City, SDTo Hulett, SD
- Aircraft age
- About 78 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
- En route · cruise
- 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 engine power (partial)
- 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
No findings designated as a cause are recorded in the NTSB data yet.
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 while enroute the engine sustained a partial loss of power. The pilot attempted to restore engine power by applying carburetor heat, adjusting the mixture, and checking the fuel control valve. The pilot’s troubleshooting efforts were unsuccessful, and the airplane was unable to maintain altitude. The pilot descended into a wooded valley and conducted a forced landing into the treetops. The airplane came to rest inverted and sustained substantial damage to the fuselage and both wings. Postaccident examination of the engine revealed that the hold-down nuts on the right magneto were loose, and the magneto could rotate freely by hand. It is likely that the loose magneto detrimentally affected ignition, which resulted in a partial loss of engine power.
Probable cause
The partial loss of engine power due to a loose magneto and subsequent impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24LA341
- Event ID
- 20240907195074
- Case number
- CEN24LA341
- 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: b4e04fe570a425dace67d6ec73ede16f446609285e9bdd3878d3f375f34f8c9a; retrieved 2026-09-16T19:14:31.412Z.