ERA20CA267 · Piper PA28 235
Kingdom Air Corps Piper PA28 235 · Accident: runway excursion during landing
From Charlotte-Monroe Executive Airport (EQY) to Goose Creek Airport (28A)
Event
- NTSB case
- ERA20CA267
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA28 235
- Aircraft type
- Piper PA28
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N33JM
- Operator
- Kingdom Air Corps
- Onboard fatalities
- Unknown
- Route
- From Charlotte-Monroe Executive Airport (EQY), Monroe, NCTo Goose Creek Airport (28A), Indian Trail, NC
- Aircraft age
- About 56 years (built 1964)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · landing roll
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Runway excursion
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
As the pilot approached 2,350-ft-long runway for landing at the destination airport, he flew the airplane higher than normal to avoid trees. The pilot noted that during the final approach the airplane’s speed was also higher than normal, and that the airplane touched down near the mid-point of the runway. The pilot attempted to stop the airplane on the remaining runway, but the airplane overran the departure end before it struck dense vegetation and a ditch. The airplane’s wings and the forward portion of the fuselage were substantially damaged. The pilot reported that there were no mechanical malfunctions or failures of the airplane that would have precluded normal operation prior to the accident.
Probable cause
The pilot's failure to attain the proper landing approach speed and touchdown point, which resulted in a runway overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20CA267
- Event ID
- 20200730X70921
- Case number
- ERA20CA267
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2020-07-29.
- API snapshot SHA-256: e8e5358e6abf4aedf57bbcbd31bec5f630c56d63d2b1d61b638aab5ce19f51e7; retrieved 2026-09-16T12:19:14.375Z.