Skip to content

ERA10CA363

2010-06-30 · Chesapeake, Virginia, United States · None · 1 aircraft · Status: Completed

Airport CPK

Current FAA registration · N6064R

Make / Model
CESSNA 172S
Year of manufacture
2006 · 4 years old at event
Engine
LYCOMING IO-360-L2A (180 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
20060801
ADS-B equipped
Yes — Mode-S A7E07D

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

A hard landing by person(s)unknown.

Factual narrative

During a preflight inspection of the airplane, a certificated flight instructor discovered substantial damage to the underside of the fuselage and reported it to the flight school. Upon further examination, substantial damage to the firewall was also found. Two days before the damage was discovered, the accident airplane underwent a routine phase inspection. The maintenance personnel who examined the airplane for the phase inspection did not report any damage at that time. According to flight school records, there were three flights between the maintenance inspection and the damage report. The first two flights, which occurred later on the same day as the phase inspection, were dual-instructional flights. The third flight, which occurred the next day, and the day before the damage was discovered, was a student pilot solo cross country flight. Interviews conducted by Federal Aviation Administration inspectors with the pilots of those flights failed to reveal who was responsible for the damage, when or where it occurred, or how it was caused. Also unknown, is why the student pilot did not observe the damage prior to his solo flight. During a preflight inspection of the airplane, a certificated flight instructor discovered substantial damage to the underside of the fuselage and reported it to the flight school. Upon further examination, substantial damage to the firewall was also found. Two days before the damage was discovered, the accident airplane underwent a routine phase inspection. The maintenance personnel who examined the airplane for the phase inspection did not report any damage at that time. According to flight school records, there were three flights between the maintenance inspection and the damage report. The first two flights, which occurred later on the same day as the phase inspection, were dual-instructional flights. The third flight, which occurred the next day, and the day before the damage was discovered, was a student pilot solo cross country flight. Interviews conducted by Federal Aviation Administration inspectors with the pilots of those flights failed to reveal who was responsible for the damage, when or where it occurred, or how it was caused. Also unknown, is why the student pilot did not observe the damage prior to his solo flight. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

FAA avdata. C = Cause, F = Factor.

  • C Personnel issues-Action/decision-Action-Incorrect action performance-Not specified - C

Verbatim from NTSB's published report. Source file NTSB_2010_ERA10CA363.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

Matched on aircraft type or causal vocabulary (maintenance). All research papers