# Accident 20150718011159A: Piper PA-32-300, Greensboro, NC, July 18, 2015

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 18, 2015, 15:30 local time
- Place: Greensboro, NC
- Airport: Air Harbor
- Damage: Substantial damage
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 36.1736° N, 79.8031° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=36.1736&lon=-79.8031&mi=10
- Aircraft: N96ML, registered now (https://openairdocs.org/aircraft/N96ML) (OpenAirDocs)
- Registry model: Piper PA-32-300 (registry code 7103212, https://openairdocs.org/model/piper-pa-32-300) (OpenAirDocs)
- Registry engine: Lycoming IO-540 series (registry code 41530, https://openairdocs.org/engine/lycoming-io-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA-32-300
- Reported engine: LYCOMING IO-540 SER
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 150 total, 49 in this make and model, 5 in the last 90 days
- NTSB investigation: [NTSB GAA15CA190](https://openairdocs.org/ntsb/GAA15CA190) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20150718011159A

## Narrative

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

THE PILOT FLEW FROM DILLON, SC (DLC AIRPORT) TO AIR HARBOR (W88).  ON HIS FIRST APPROACH, HE SAID HE CAME IN HIGH, AND DID A GO-AROUND.  ON HIS SECOND APPROACH, HE STATED TO ME THAT HE HAD TOO MUCH AIRSPEED AND DID NOT TOUCHDOWN SOON ENOUGH ON RUNWAY 9.  HE DIDN'T HIT HARD ON THE RUNWAY, BUT HE HAD EXTRA AIRSPEED AND FLOATED DOWN A SIGNIFICANT PORTION OF THE RUNWAY BEFORE TOUCHING DOWN.  WHEN HE TOUCHED DOWN, HE REALIZED HE DID NOT HAVE ENOUGH RUNWAY TO STOP, LEAVING HIM WITH TWO OPTIONS: TO ATTEMPT A GO-AROUND (THERE ARE TREES AT THE END OF RUNWAY 9) OR TRY TO BRAKE BUT RUN OFF THE END OF THE RUNWAY.  HE CHOSE THE LATTER.  THE AIRCRAFT RAN OFF THE END OF THE RUNWAY AND COLLIDED WITH THE BASE OF THE TREES THERE.  THE PILOT WAS UNINJURED BUT THE AIRCRAFT SUSTAINED SUBSTANTIAL DAMAGE.

## 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 GAA15CA190](https://openairdocs.org/ntsb/GAA15CA190), Jul 18, 2015: Piper PA 32-300 (N96ML), Greensboro, NC, substantial damage. Probable cause: The pilot's decision to continue the approach after realizing the intended parameters were not attainable, resulting in a runway over-shoot, a loss of control on the ground and the consequent…

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.