WPR20LA133 · Cessna 177 Undesignat
Cessna 177 Undesignat · Accident: loss of engine power (total) en route
From Lodi Airport (1O3) to an unrecorded destination
Event
- NTSB case
- WPR20LA133
- 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
Cessna 177 Undesignat
- Aircraft type
- Cessna 177
- 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
- N3386T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lodi Airport (1O3), Lodi, CATo not recorded
- Aircraft age
- About 52 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 student pilot reported that about 15 minutes after takeoff, he heard a loud noise and observed oil on the windscreen, followed by a total loss of engine power. The pilot attempted to restart the engine but was unsuccessful and initiated a forced landing to a nearby field. Subsequently, the airplane landed hard and came to rest upright, which resulted in substantial damage to the fuselage.
Postaccident examination of the engine revealed that the No. 4 connecting rod had failed. Metallurgical examination of the connecting rod revealed that it had fractured from a fatigue crack, which initiated at an inner flange corner of the rod, about 1.15 inches from the piston pin bore. Once the connecting rod was no longer connected, the lower portion of the connecting rod (closer to the crankshaft) fractured in bending overstress, beginning a cascade of wider damage while the reciprocating engine was running.
Probable cause
The fatigue failure of the no. 4 cylinder connecting rod, which resulted in a total loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR20LA133
- Event ID
- 20200429X05114
- Case number
- WPR20LA133
- 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: local date, investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2020-04-29.
- API snapshot SHA-256: 02d9a0c06fb466ad6861d0f7952cc6957985d6fc8b178253b1358138ac7f40c2; retrieved 2026-09-16T11:32:06.584Z.