FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL04LA074 · Piper PA-28-161

7 Feb 2004 · Summerville, SC, United States

Piper PA-28-161 · Accident while standing

From Summerville Airport (KDYB) to Columbia Metropolitan Airport (KCAE)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ATL04LA074
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-28-161 Possible conflict

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
N21266
Operator
Unknown
Onboard fatalities
Unknown
Route
From Summerville Airport (KDYB), Summerville, SCTo Columbia Metropolitan Airport (KCAE), Columbia, 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
Standing · engine(s) start-up
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
Miscellaneous/other
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 › Starting procedure, inadequate

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 set the parking brake and attempted to start the airplane by rotating the propeller by hand. The airplane started and moved forward, and the pilot climbed up on the right wing to enter the cockpit but slipped and fell to the ground. The pilot grabbed onto the cabin step and was dragged as he attempted to gain access to the cockpit. When the pilot realized a collision with a parked airplane was imminent, he released his hold on the cabin step. The airplane taxied unmanned and collided with a parked airplane. The pilot reported no mechanical malfunction with the airplane.

Probable cause

The pilot's inadequate start procedure, which resulted in a run-away airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL04LA074
Event ID
20040210X00176
Case number
ATL04LA074
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: ad3d80469afb481154d884c30cc399e83bb8dc04a704b38297cea9a616663937; retrieved 2026-09-21T19:17:44.928Z.