CEN16LA249 · Aero Commander 100 180
Aero Commander 100 180 · Accident: loss of engine power (total) en route
From Calhoun County Airport (PKV) to Calhoun County Airport (PKV)
Event
- NTSB case
- CEN16LA249
- 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
Aero Commander 100 180
- Aircraft type
- Aero Commander 100
- 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
- N3718X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Calhoun County Airport (PKV), Port Lavaca, TXTo Calhoun County Airport (PKV), Port Lavaca, TX
- Aircraft age
- About 48 years (built 1968)
- 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
- 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 (total)
- 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 had departed on a local flight. He reported that, about 15 minutes after takeoff and when the airplane was about 1,100 ft above ground level, he felt a vibration and heard a "bang." The engine subsequently began to lose power. The oil pressure dropped to zero, the pilot heard another "bang," and the propeller stopped turning. The pilot executed a forced landing to a pasture, which resulted in substantial damage to the airplane when the nose landing gear collapsed in soft ground.
An engine examination revealed that the No. 4 connecting rod had separated from the crankshaft. However, all fracture surfaces sustained secondary mechanical damage, which precluded further examination. The last engine overhaul was accomplished about 25 years before the accident. The engine manufacturer recommended engine overhauls every 12 years; however, the operator was not required to comply with that recommendation because the airplane was operated under Part 91. Given the available information, the reason for the connecting rod failure could not be determined.
Probable cause
Loss of engine power due to failure of a connecting rod.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16LA249
- Event ID
- 20160706X42954
- Case number
- CEN16LA249
- 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. 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: 79f381c15cd4d408d6be15016cfee0b4d5672079ec696d8a943c86b0faf99557; retrieved 2026-09-16T03:37:38.889Z.