GAA15CA190 · Piper PA 32-300
Piper PA 32-300 · Accident: landing area overshoot
From Dillon County Airport (KDLC) to Air Harbor Airport (W88)
Event
- NTSB case
- GAA15CA190
- 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 PA 32-300
- Aircraft type
- Piper PA-32
- 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
- N96ML
- Operator
- Scott D. Warner · private individual
- Onboard fatalities
- Unknown
- Route
- From Dillon County Airport (KDLC), Dillion, SCTo Air Harbor Airport (W88), Greensboro, NC
- Aircraft age
- About 36 years (built 1979)
- 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
- Landing area overshoot
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that after initiating a go-around on the previous approach, "I made a second attempt and was set up for the asphalt runway but was pushed off slightly so I adjusted for the grass strip." He stated that during the landing flare, the airplane "floated" and "by the time I touched I was going too slow to abort or do a missed approach", and the airplane ran off the end of the runway. The airplane impacted trees, and sustained substantial damage to both wings.
The pilot reported that there were no pre-impact mechanical failures or malfunctions that would have precluded normal operation.
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 collision with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA15CA190
- Event ID
- 20150721X35454
- Case number
- GAA15CA190
- 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: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 5d6e8f54d92535d0353dd9f481ffc144112f4c2c3b7717b7f9acd1cd5a1a813c; retrieved 2026-09-16T02:33:10.322Z.