# Accident 20200728008349A: Piper PA-28-235, Indian Trail, NC, July 28, 2020

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 28, 2020, 17:00 local time
- Place: Indian Trail, NC
- Airport: Goose Creek
- Damage: Substantial damage
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 35.1236° N, 80.5833° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=35.1236&lon=-80.5833&mi=10
- Aircraft: N33JM, registered now (https://openairdocs.org/aircraft/N33JM) (OpenAirDocs)
- Registry model: Piper PA-28-235 (registry code 7102810, https://openairdocs.org/model/piper-pa-28-235) (OpenAirDocs)
- Registry engine: Lycoming 0-540 series (registry code 41532, https://openairdocs.org/engine/lycoming-0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA-28-235
- Reported engine: LYCOMING 0-540 SERIES
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor, private pilot, student
- Pilot flight hours: 320 total, 64 in this make and model, 14 in the last 90 days
- NTSB investigation: [NTSB ERA20CA267](https://openairdocs.org/ntsb/ERA20CA267) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20200728008349A

## Narrative

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

THIS AIRMEN WAS ON A FLIGHT TO THE GOOSE CREEK AIRPORT (28A) FROM THE MONROE EXECUTIVE AIRPORT (KEQY) WITH HIS SON.

HE OVER FLEW THE GOOSE CREEK AIRPORT TO CHECK THE WINDS AND DECIDED TO LAND ON RUNWAY 4.  HE ENTERED THE PATTERN AND NOTED TREES THAT APPEARED TO HIM TO BE TALL AND CLOSE TO THE DISPLACED THRESHOLD.  HE HAD ONLY BEEN TO THIS AIRPORT 2 OTHER TIMES.  THE AIRMEN STATED THAT HE WAS HIGHER WITH HIS APPROACH SPEED ON THIS APPROACH.  AFTER HE CLEARED THE TREES HE PROCEEDED TO LAND.  HE STATED THAT HIS LAST CHECK OF AIRSPEED WAS APPROXIMATELY 85 TO 90.   WITH THE NOSE OF THE AIRCRAFT STILL POINTED DOWN THE EXTRA AIRSPEED CAUSED THE AIRCRAFT TO FLOAT.  THE AIRCRAFT DID NOT TOUCH DOWN UNTIL APPROXIMATELY THE HALFWAY POINT OF THE 2300 FOOT RUNWAY.  THE AIRMEN IMMEDIATELY APPLIED HEAVY BRAKING ACTION WHICH LEFT MARKINGS THAT WERE APPROXIMATELY 990 FEET IN LENGTH.  THE AIRCRAFT CONTINUED TO SLIDE IN THE GRASS TURNING TO THE LEFT AND THEN DOWN A SHALLOW HILL COMING TO REST IN THE BRUSH AND TREES OFF THE DEPARTURE END OF THE RUNWAY.

## 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 ERA20CA267](https://openairdocs.org/ntsb/ERA20CA267), Jul 29, 2020: Piper PA28 (N33JM), Indian Trail, NC, substantial damage. Probable cause: The pilot's failure to attain the proper landing approach speed and touchdown point, which resulted in a runway overrun.

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.