ATL06CA002 · Piper PA-28-181
Long Aviation Piper PA-28-181 · Accident: loss of control in flight on approach
From Goose Creek Airport (28A) to Pageland Airport (PYG)
Event
- NTSB case
- ATL06CA002
- 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-28-181
- Aircraft type
- Piper PA-28
- 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
- N6922T
- Operator
- Long Aviation
- Onboard fatalities
- Unknown
- Route
- From Goose Creek Airport (28A), Indian Trail, NCTo Pageland Airport (PYG), Pageland, SC
- 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
- Approach · VFR go-around
- 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; 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, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The student pilot was making an approach to land on runway 05 and elected to go-around. As the student pilot initiated the go-around, he made a left 90 degrees turn, the airplane stalled and collided with trees west of the airport. The witness stated that the winds were coming from the right of runway 05, at approximately 13 knots, gusting to 22 to 26 knots. The airplane rested about 250 yards west of the runway in a nose low attitude. The examination of the accident site revealed that there was a narrow vertical swath through the trees to where the airplane rested. Post-accident examination of the airplane revealed that both wings were separated from the airplane and the empennage was damaged. The carburetor heat lever was found in the off position, the throttle control lever was half open, the mixture control lever was retracted 1/2 inch, and the flaps were extended. The pilot did not report a mechanical problem with the airplane.
Probable cause
The pilots failure to maintain flying speed during the go-around, which resulted in a stall and the subsequent collision with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL06CA002
- Event ID
- 20051101X01760
- Case number
- ATL06CA002
- 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: dbc7eab919e7b9c06b4125be7d40f37871a2d6e8cecac01e855cb78a17b7df03; retrieved 2026-09-21T09:02:36.774Z.