CEN24LA354 · Cessna 170A
Cessna 170A · Accident: powerplant system/component malfunction/failure en route
From 82I5 · Huntley, IL to Addington Field / Elizabethtown Regional Airport (EKX)
Event
- NTSB case
- CEN24LA354
- 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
Cessna 170A
- Aircraft type
- Cessna 170
- 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
- N1249D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 82I5 · Huntley, ILTo Addington Field / Elizabethtown Regional Airport (EKX), Elizabethtown, KY
- Aircraft age
- About 73 years (built 1951)
- 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
- Powerplant system/component malfunction/failure
- 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 power plant
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that during cruise flight there was a loss of engine power that was preceded by a loud banging sound. The engine oil temperature increased, and oil sprayed onto the windshield. The pilot planned to land the airplane on a short open area but overshot the area because he could not dissipate enough of the airplane’s energy. He then landed the airplane on a corn field where it contacted the corn, nosed over, and impacted the ground. Postaccident examination of the engine revealed a hole in the crankcase above the No. 6 cylinder assembly. The No. 6 connecting rod was fractured near its base. Metallurgical examination of the connecting rod revealed the fracture features were consistent with fatigue cracking that initiated at multiple locations on the outer surface opposite the inner bearing surfaces that mated to the crankshaft.
Probable cause
The fatigue fracture of the No. 6 piston connecting rod, which resulted in a loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24LA354
- Event ID
- 20240912195111
- Case number
- CEN24LA354
- 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, cause areas. 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: 9194012e5292d44474345100d10fd07f78c6175f33a0a61ae1e30bfddbc83d15; retrieved 2026-09-16T19:15:54.666Z.