# Accident 20120617013559A: Cessna 172S, Frederick, MD, June 17, 2012

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 17, 2012, 17:30 local time
- Place: Frederick, MD
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 39.4175° N, 77.3744° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=39.4175&lon=-77.3744&mi=10
- Aircraft: N387AF, registered now (https://openairdocs.org/aircraft/N387AF) (OpenAirDocs)
- Registry model: Cessna 172S (registry code 2072439, https://openairdocs.org/model/cessna-172s) (OpenAirDocs)
- Registry engine: Lycoming IO-360-L2A (registry code 41597, https://openairdocs.org/engine/lycoming-io-360-l2a) (OpenAirDocs)
- Reported make and model: CESSNA 172S
- Reported engine: LYCOMING IO-360-L2A
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 119 total, 30 in this make and model, 25 in the last 90 days
- NTSB investigation: [NTSB ERA12CA439](https://openairdocs.org/ntsb/ERA12CA439) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20120617013559A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

PILOT WAS PRACTICING TOUCH AND GO'S AT FDK RWY 23. AIRCRAFT MADE HARD LANDING, CAUSING STRUCTURAL DAMAGE TO THE AIRCRAFT.

## The NTSB's investigation of this event (1)

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 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.

## Other reports on N387AF (2)

Matched to the same aircraft by N-number and date.

- [Accident 20260623009499A](https://openairdocs.org/incident/20260623009499A), Jun 23, 2026: Cessna 172S (N387AF), Willard, UT, Destroyed, 1 fatal. During a VFR cross-country solo flight at night as an incorporation of part 61 training for a commercial pilots certificate, the private and instrument rated…
- [Accident 20100825043429A](https://openairdocs.org/incident/20100825043429A), Aug 25, 2010: Cessna 172S (N387AF), 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…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.