# Incident 20150703011119I: Cessna 172P, Marlboro, MA, July 3, 2015

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 3, 2015, 14:10 local time
- Place: Marlboro, MA
- Airport: Marlboro
- Damage: Minor damage
- Phase of flight: Landing: Rollout
- Operating rules: General operating rules (Part 91)
- Location: 42.3432° N, 71.5090° W: Placed by OpenAirDocs at Marlboro Airport, closed, within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=42.3432&lon=-71.5090&mi=10
- Aircraft: N5212K, registered now (https://openairdocs.org/aircraft/N5212K) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 3
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 145 total, 145 in this make and model, 80 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20150703011119I

## Narrative

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

^PRIVACY DATA OMITTED^ WAS ENROUTE FROM SIMSBURY, CT TO MARLBORO, MA TO DROP OFF FRIENDS. ^PRIVACY DATA OMITTED^ HAD MISMANAGED THE CONTROLS OF THE AIRCRAFT RESULTING IN OVERSHOOTING THE RUNWAY UPON LANDING. THE AIRCRAFT WAS AT LOW POWER SETTING WHEN IT CONTACT THE AIRPORT BOUNDARY FENCE.

## Other reports on N5212K (1)

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

- [Incident 20130221003999I](https://openairdocs.org/incident/20130221003999I), Feb 21, 2013: Cessna 172P (N5212K), Portland, ME, Minor damage. On Thursday February 21, 2013 [privacy data omitted] , pilot in command of N5212K, was doing touch-n-go practice at the Portland International Jetport (pwm) on…

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.