Cessna 172S accident near Chesapeake, Virginia, June 30, 2010
On June 30, 2010 at about 4:00 pm local time, a Cessna 172S, registered N6064R, was substantially damaged in an accident during landing (flare/touchdown) near Chesapeake, Virginia (Chesapeake Regional Airport). It was a flight of an unrecorded kind under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A hard landing by person(s)unknown.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 30, 2010 · about 4:00 pm local time
- Place
- Chesapeake, Virginia · Chesapeake Regional Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172S · all 172Ss on the register
- Registration
- N6064R · registry record · serial 172S10246
- Damage
- Substantial damage
- Flight
- Flight of an unrecorded kind · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Hard landing during landing (flare/touchdown) defining event
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Not specified
Other crew
- Flight time: 0 hours in all; 0 in this make and model
- Medical certificate: Unknown
The aircraft
- Airframe total time: 969 hours
- Last inspection: approved inspection programme, June 28, 2010
- Maximum gross weight: 2,550 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming IO-360-L2A (piston); 0 hours total
The flight
- Departed from: CPK Chesapeake VA
- Destination: CPK Chesapeake VA
- Flight plan: not recorded
- Runway 05
Weather at the time
- Light: daylight
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Other NTSB records under N6064R the same tail number, which may have belonged to a different aircraft at the time
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.