Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

April 29, 2020 · Cessna 177 Undesignat · N3386T

Lodi, CA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
April 29, 2020
Injury Outcomes
1 injury (1 minor injury)
Location
Lodi, CA
Aircraft
Cessna 177 Undesignat (1968)
Tail Number
N3386T
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
WPR20LA133

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.

NTSB Probable Cause

The fatigue failure of the no. 4 cylinder connecting rod, which resulted in a total loss of engine power.

Full Narrative

On April 28, 2020, about 1752 Pacific daylight time, a Cessna 177, N3386T, was substantially damaged when it was involved in an accident near Lodi, California. The pilot sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The student pilot reported that about 15 minutes after takeoff, at an altitude of 1,400 ft, the engine suddenly began to run rough and make metallic noises along with oil on the windscreen, which was followed by a total loss of engine power. The pilot attempted to restart the engine unsuccessfully and initiated a forced landing to a nearby field. Subsequently, the airplane landed hard and came to rest upright. Examination of the engine revealed that the engine remained attached to the airframe, with all accessories attached. A hole in the crankcase was observed above cylinder No. 4 and 3. No loose oil lines were found with the exception of the oil pressure line, which was separated from the crankcase, consistent with impact damage. The No. 4 cylinder exhibited extensive damage to the piston skirt area and cylinder wall. The No. 4 connecting rod remained attached to the crankshaft, however, the web was separated from just outboard of the crankshaft to about 1 inch inboard from the piston pin. The area of separation near the piston pin was flat, with no apparent mechanical damage. The separation near the crankshaft exhibited extensive mechanical damage. The middle portion of the connecting rod web was found within the oil sump and exhibited mechanical damage. See figure 1. Figure 1: View of the No. 4 connecting rod. The middle web section exhibited multiple areas of locally deformed material, mostly along the protruding flange surfaces. These features were consistent with this remnant having been impacted by adjacent components in multiple locations. The fracture surface between this remnant and the crankshaft bore surfaces exhibited a general rounded but perpendicular orientation, with localized buckling on the flanges. The rough orientation and texture suggested overstress fracture, however, the mating surfaces were damaged from post-fracture impact, with no discernible fracture features present. The other fracture surface of the connecting rod, toward the piston pin side, was relatively flat and oriented perpendicular to the rod longitudinal direction. The fracture on the pin side remnant was relatively smooth, exhibiting few elevated features. Most of the fracture surface, which was generally flat in orientation, exhibited crack arrest marks, indicative of progressive crack growth, consistent with fatigue. The remaining fracture surface exhibited a rougher, more undulating surface texture consistent with subsequent overstress fracture, as seen in figure 2. Therefore, the fatigue crack covered about 95% of the rod flange-to-flange cross section, measured as approximately 1.086 inches. Figure 2: The no. 4 connecting rod fracture surface (piston pin side) The lack of ratchet marks suggested a single initiation site. This site was located at the inside corner of a flange edge. The river patterns and crack arrest marks were consistent with having emanated from this feature. When viewed at an angle, the feature was collocated with an area of local plastic deformation and wear. As shown in figure 3, the outer flange surface had been smoothed, and deformed over the side of the inner flange surface. Figure 3: Angled view of the crack initiation site (arrow), showing inward deformation of the flange side. The engine was overhauled on November 10, 1986 and had accumulated 887.86 hours at the time of the accident. No maintenance entries regarding the No. 4 connecting rod were found throughout the engine logbook.

Flight

Event TypeAccident
Event Time17:52 PDT
Nearest Airport0nm
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 177 Undesignat
Tail NumberN3386T
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-360-A1A · Reciprocating · 180
Seats4

People & Injuries

Injury Summary1 injury (1 minor injury)
Fatal0
Serious0
Minor1
Uninjured0
Total1
Crew 1Age 64 · Third Class · Minor

Conditions

ConditionsVMC
LightDaylight
Wind310° @ 4 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point54
Altimeter29.94 inHg
Observation Time00:55
Weather SourceWFAC

Appendix: Source Data