ATL04LA072 · Piper PA-22-135
Piper PA-22-135 · Accident: loss of control in flight during landing
From Florence Regional Airport (FLO) to Goose Creek Airport (28A)
Event
- NTSB case
- ATL04LA072
- 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-22-135
- Aircraft type
- Piper PA-22
- 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
- N1107C
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Florence Regional Airport (FLO), Florence, SCTo Goose Creek Airport (28A), Indian Trail, NC
- 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 · aborted
- 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
- Loss of control in flight
- 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
- Stall/mush; 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
- Pilot in command › Airspeed, inadequate
- Pilot in command › Compensation for wind conditions, inadequate
- Pilot in command › Directional control, not maintained
- Pilot in command › Lift-off, premature
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 stated while touching down, a strong crosswind caused the airplane to "weathervane to the right". The airplane bounced. As the pilot tried to recover from the bounced landing, he stated that he "overcorrected and the airplane started to run off the right side" of the runway. At this point the pilot decided to execute a climb out, but the airplane did not have enough airspeed to climb and only got approximately three feet in the air. The airplane collided with a tree and landed partially in a pond 1300 feet from the approach end and 30 feet to the right of runway 22. The wind conditions at the time of the accident were from a heading of 280-degrees, wind speed 11 knots with a wind gust to 19 knots. The pilot did not report any mechanical malfunctions with the airplane prior to the accident. Examination of the airplane revealed damage to wings, the right door panel and the propeller. Post examination did not reveal any mechanical problems with the airplane.
Probable cause
The pilot's attempted lift off without adequate airspeed resulting in a stall/mush and collision with trees while transitioning from an aborted landing to takeoff climb. A factor was the crosswind condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL04LA072
- Event ID
- 20040206X00170
- Case number
- ATL04LA072
- 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, coordinates. 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: ba61d75c035fa606ac58da0c8d08de4b21d81e44cb2e760ee83f79ecb93da74f; retrieved 2026-09-22T07:59:53.924Z.