# NTSB ERA10CA468: Cessna 172S, N387AF, Frederick, MD, August 25, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: August 25, 2010, 12:00 local (16:00 UTC) - Place: Frederick, MD - Coordinates: 39.417499, -77.374168 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.4175&lon=-77.3742&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) - Highest injury: No injuries - Status: Completed, report March 16, 2011 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - NTSB case key (mKey): 77199 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA10CA468 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/77199/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=77199 - Page: https://openairdocs.org/ntsb/ERA10CA468 ## Probable cause Undetermined. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Not specified (probable cause); cases with it: [Cessna 172S, 32 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=2072439), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md) - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Cessna 172S, 99 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072439), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); cases with it: [Cessna 172S, 102 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072439), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) ## 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](https://openairdocs.org/aircraft/N387AF), registered now, S/N 172S10387, built 2006 (OpenAirDocs) - Reported make and model: CESSNA 172S - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S10387 - Engines: 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 ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 1; flight hours: 0 total, 0 in this make and model - Student pilot; age 1 ## Weather - Conditions: Visual (VMC), Not reported ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20100825043429A](https://openairdocs.org/incident/20100825043429A), Aug 25, 2010: Cessna 172S, Frederick, MD, Substantial damage. Received phone call from school maintenance mechanic concerning a damaged firewall on this aircraft. Went to school on 09/01/10 to inspect damage. Firewall was… ## Other investigations on N387AF (2) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB WPR26FA232](https://openairdocs.org/ntsb/WPR26FA232), Jun 24, 2026: Cessna 172 (N387AF), Willard, UT, destroyed, 1 fatal, investigation ongoing - [NTSB ERA12CA439](https://openairdocs.org/ntsb/ERA12CA439), Jun 17, 2012: Cessna 172S (N387AF), Frederick, MD, substantial damage. Probable cause: The pilot's inadequate landing flare, which resulted in a hard landing. ## Docket (3 files) The files NTSB released with the investigation on October 3, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=77199. 517 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 453 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40336030&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Statement Director of Maintenance (item 2, .PDF, 23 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40336031&FileExtension=.PDF&FileName=Statement%20Director%20of%20Maintenance-Redacted.PDF - FAA Inspector Statement (item 3, .PDF, 40 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40336032&FileExtension=.PDF&FileName=FAA%20Inspector%20Statement-Redacted.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.