ATL89LA117 · Piper PA-38-112
Piper PA-38-112 · Accident: overrun during landing
From Florence Regional Airport (FLO) to an unrecorded destination
Event
- NTSB case
- ATL89LA117
- 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
- 0
- 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-38-112
- Aircraft type
- Piper PA-38
- 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
- N9451T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Florence Regional Airport (FLO), Florence, SCTo not recorded
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- Overrun
- 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
- Pilot in command › Airspeed, excessive
- Pilot in command › Compensation for wind conditions, inattentive
- Pilot in command › Wrong runway, selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT WAS MAKING TOUCH & GO LANDINGS AT A PRIVATE GRASS STRIP. THE LANDINGS WERE TO RWYS 14 & 32. ON THE 1ST APPROACH THE WIND SOCK INDICATED CALM WIND. THE LAST APPROACH WAS MADE WITH ZERO FLAPS. THE PLT SLIPPED THE ACFT ON FINAL APPROACH & CROSSED RWY THRESHOLD AT 90 KNOTS. THE PILOT STATED THAT A 10 KNOT WIND WAS BLOWING (TAILWIND) WHEN HE TOUCHED DOWN APPROXIMATELY 1/2 TO 3/4 OF THE DISTANCE DOWN THE RUNWAY. THE PILOT WAS UNABLE TO STOP THE ACFT AND IT VEERED TO THE RIGHT, DEPARTED THE RUNWAY AND STRUCK A WOODEN SIGN POST.
Probable cause
THE PILOT'S FAILURE TO REMAIN AWARE OF THE LOCAL WIND CONDITIONS. ADDITIONALLY, HE EXECUTED THE APPROACH AND LANDING WITH EXCESSIVE SPEED, COMBINED WITH A TAILWIND, WHICH RESULTED IN THE RUNWAY OVERRUN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL89LA117
- Event ID
- 20001213X27844
- Case number
- ATL89LA117
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: db85b25b2cecf494c1b9475553fc7b3a7111a505f2e1699fc047ff4c70ea883e; retrieved 2026-09-23T07:46:18.767Z.