ERA22LA202 · Piper PA32 300
Piper PA32 300 · Accident: runway excursion during landing
From Pickens County Airport (LQK) to an unrecorded destination
Event
- NTSB case
- ERA22LA202
- 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
- Event fatalities
- Unknown
- 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 PA32 300
- Aircraft type
- Piper PA32
- 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
- N9583C
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Pickens County Airport (LQK), Liberty, SCTo not recorded
- Aircraft age
- About 44 years (built 1978)
- 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, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was attempting to land on a 2,250-ft long uphill turf runway with a 7 knot tailwind. He reported that during the landing flare, his groundspeed was higher than expected for a normal touchdown point. The pilot did not perform a go-around as he was concerned about clearing power lines at the end of the runway. The airplane subsequently touched down, overran the departure end of the runway, and collided with a fence, which resulted in substantial damage to the left wing. The pilot added that there were no preimpact mechanical malfunctions with the airplane.
Probable cause
The pilot’s failure to obtain the proper touchdown point during landing, which resulted in a runway overrun and collision with a fence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22LA202
- Event ID
- 20220425104997
- Case number
- ERA22LA202
- 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, coordinates, cause areas. 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: aca10fa21d1c70bd4268f9061435c11cbd9d1fc8edb714cfbd7f7c540e269dc0; retrieved 2026-09-16T15:10:19.675Z.