ATL98LA084 · Bellanca 17-31A
Bellanca 17-31A · Accident: partial loss of engine power (mechanical failure) en route
From DeKalb Peachtree Airport (PDK) to Corpus Christi International Airport (CRP)
Event
- NTSB case
- ATL98LA084
- 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
- 0
- 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
Bellanca 17-31A
- Aircraft type
- Bellanca 17
- 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
- N39853
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From DeKalb Peachtree Airport (PDK), Atlanta, GATo Corpus Christi International Airport (CRP), Corpus Christi, TX
- 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
- En route · cruise
- 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
- Partial loss of engine power (mechanical 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
- Engine assembly, connecting rod › Fractured
- Engine assembly, piston › Jammed
- Engine assembly, push rod › Bent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While in cruise flight, the airplane engine's #2 cylinder connecting rod suffered a fracture. This resulted in the #2 piston becoming jammed in the cylinder and bending of the #2 cylinder intake valve pushrod. These events resulted in partial loss of engine power and a forced reduction in power setting. The pilot performed an emergency landing whereon the landing roll, the airplane skidded and turned in efforts to avoid a collision with a tree/fence row. The turn resulted in a collapse of the right main landing gear and right wing collision with the terrain. The landing gear broke off the aircraft, punctured the right main fuel cell, broke the main right wing wood spar and bent the right fuselage stringers. The outboard 36' of main right wing was severed from the airframe.
Probable cause
The fracture of the #2 cylinder connecting rod which resulted in partial loss of engine power and subsequent forced landing. A factor in the accident was the rough terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL98LA084
- Event ID
- 20001211X10231
- Case number
- ATL98LA084
- 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. 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: 752637e306207ad3dde8aa296c0a6590000efa99e958ae3d5eaec08a2287a9b0; retrieved 2026-09-22T17:40:21.863Z.