# Incident 20111024024309I: Cessna 172S, Frederick, MD, October 24, 2011

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 24, 2011, 19:30 local time
- Place: Frederick, MD
- Damage: Minor damage
- Phase of flight: Taxi
- Operating rules: General operating rules (Part 91)
- Location: 39.4385° N, 77.4117° W: Placed by OpenAirDocs: center of Frederick, MD, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.4385&lon=-77.4117&mi=10
- Aircraft: N2152T, a cancelled registration (https://openairdocs.org/deregistered/N2152T-2018-03-21) (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: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 123 total, 123 in this make and model, 23 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20111024024309I

## Narrative

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

PILOT LANDED AT FDK ON RWY 05 WITHOUT INCIDENT. HE PROCEEDED ON TAXIWAY BRAVO MAKING A LEFT TURN OFF THE TAXIWAY AND ONTO THE GRASS.  WHEN HE REALIZED HE HAD TAXIIED ONTO THE GRASS HE ATTEMPTED TO RETURN TO THE HARD SURFACE AND IN THE PROCESS WENT THROUGH A DIP IN THE GROUND. THE PROPELLOR MADE ENOUGH CONTACT WITH THE GROUND TO RESULT IN MINOR PROP DAMAGE AND WARRANT AN ENGINE TEARDOWN.

## Other reports on N2152T (1)

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

- [Accident 20141108020249A](https://openairdocs.org/incident/20141108020249A), Nov 8, 2014: Cessna 172S (N2152T), Hinton, VA, Destroyed, 1 fatal. Conducted face-to-face interview with surviving student pilot who stated the cause as controlled flight into terrain during a night VFR training flight.…

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.