- Date
- August 25, 2010, 12:00 local (16:00 UTC)
- Place
- Frederick, MD
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N387AFCessna 172S
- Defining event
- Landing-flare/touchdown: Hard landing
- Weather
- Visual (VMC) · Not reported
- Status
- Completed · report March 16, 2011
- Report
- Approved by Office Director
- NTSB office
- Eastern Region Aviation
- FAA report
- 20100825043429A
- Case key
- 77199
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
Undetermined.
Findings · 2
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
During a Phase III inspection of the airplane, the Director of Maintenance for the operator noticed that the airplane's firewall was damaged. The damage was reported to the nearest Federal Aviation Administration (FAA) Flight Standards District Office, and verified by the FAA. The damage occurred between the Phase II and Phase III inspection. The airplane had flown 48.2 hours since the Phase II inspection. According to the FAA, the damage was a result of a hard landing. The purpose of the flight and composition of the flight crew was not determined. In addition, the date, actual location, and time of the accident were not determined.
Factual narrative
During a Phase III inspection of the airplane, the Director of Maintenance for the operator noticed the firewall was damaged. The damage was reported to the nearest Federal Aviation Administration (FAA) Flight Standards District Office, and verified by the FAA. The damage occurred between the Phase II and Phase III inspection. The airplane had flown 48.2 hours since the Phase II inspection. According to the FAA, the damage was a result of a hard landing. The purpose of the flight and composition of the flight crew was not determined. In addition, the date, actual location, and time of the accident were not determined.
Aircraft
- Registration
- N387AF
- Reported as
- Cessna 172S
- Category
- Airplane
- Serial number
- 172S10387
- Engine
- Lycoming IO-360-L2A, 180 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Part 91
- Operator
- Frederick Flight Center
- Registered owner
- Kaufman Air Inc
- Airworthiness certificate
- Standard, Normal
- Departed
- Unknown, MD
- Destination
- Unknown, MD
- Flight plan
- Unknown
- Airport
- FDK · Freerick Municipal Airport, runway 05, 5,220 × 100 ft
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew · 2
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 1
- Flight hours
- 0 total · 0 in this make and model
- Role
- Student pilot
- Age
- 1
Weather
- Conditions
- Visual (VMC) · Not reported
Docket · 3
The files NTSB released with the investigation on October 3, 2010, on NTSB’s docket system: statements, records, photos and specialists’ reports. 517 KB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.
Other investigations on N387AF · 2
Matched to the same aircraft by N-number and date.