The U.S. aircraft register, updated daily
Accidents · NTSB ERA15CA107 · Final report

Piper PA-28-161 accident near Alexander City, Alabama, January 19, 2015

On January 19, 2015, a 1979 Piper PA-28-161, registered N104SA, was substantially damaged in an accident during standing (engine(s) start-up) near Alexander City, Alabama (Thomas C. Russell Field). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to properly secure the airplane before hand-propping the engine for startup.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
January 19, 2015
Place
Alexander City, Alabama · Thomas C. Russell Field · map
Type
Accident
Injuries
1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Piper PA-28-161, built 1979 · all PA-28-161s on the register
Registration
N104SA · registry record · serial 28-8016165
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

On the day of the accident, the pilot had to get the airplane jumpstarted as the battery was low on energy. Later during his flight home, he landed at an airport to refuel. After refueling, he attempted to start the engine. The battery however, was too weak to start the engine. The pilot then checked the parking brake was engaged and got out to look for his portable jump starter pack in the storage compartment. It was not however onboard. He then proceeded to look for someone to assist in starting. Not finding anyone, he went back to the airplane and set the mixture to full rich, opened the throttle about 10 percent, primed the engine about 8 to 10 times, turned the magneto switch to "BOTH", checked the parking brake, and attempted to hand-prop the engine twice without success. He then checked these items again and once again attempted to hand-prop the engine. The engine still failed to start. He assumed the engine was flooded. Therefore, he set the mixture to idle cutoff, turned off the magnetos, and checked the parking brake once again. He then got out of the aircraft and prior to touching the propeller, visually looked in the cabin to check that the key for the magneto switch wasn't in the "BOTH" position. He then hand-propped it. A puff of smoke came out of the exhaust, and the engine suddenly accelerated to maximum rpm. He immediately moved from in front of the propeller. He then thought "the brakes are on, don't worry", then noticed that the airplane was moving and picking up speed. At this point, he was in front of the right wing. He then attempted to grab hold of the door, hop on wing and get into the airplane. He could not however get a grip on door as the slipstream from the propeller pushed it shut. He was then dragged and run over by the airplane. The airplane then made contact with a ditch and was substantially damaged. The pilot advised that he had been having problems with the battery holding a charge, and that he should have replaced it. He also advised that apparently one magneto was still on; he should have used chocks, and should not have attempted to hand-prop it by himself.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Aircraft maintenance event
  2. Loss of control on ground during standing (engine(s) start-up) defining event
  3. Attempted remediation/recovery during standing (engine(s) operating)
  4. Collision with terrain or object (not controlled flight into terrain) during taxi

The NTSB's findings

  • Aircraft › Aircraft systems › Electrical power system › Battery/charger › Incorrect service/maintenance
  • Aircraft › Aircraft systems › Electrical power system › Battery/charger › Failure
  • cause Personnel issues › Action/decision › Action › Lack of action › Pilot
  • cause Aircraft › Aircraft handling/service › Parking/securing › Tie › down/mooring › Incorrect use/operation
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot

Pilot

  • Certificate: flight instructor, commercial pilot, private
  • Ratings: single-engine land; instructor: helicopter; instrument: helicopter; rotorcraft: helicopter
  • Flight time: 1,043 hours in all; 283 in this make and model; 330 as pilot in command
  • Last flight review: May 2, 2014
  • Medical certificate: Class 2
  • Seat: left
  • Injury: minor injuries

The aircraft

  • Airframe total time: 5,137.2 hours
  • Last inspection: annual inspection, September 1, 2014; 135 hours since
  • Maximum gross weight: 2,325 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming 0-320-D3G (piston); 1,371 hours total

The flight

  • Departed from: ALX Alexander City AL
  • Destination: 71J Ozark AL
  • Flight plan: none

Weather at the time

  • Light: night, dark
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 45°F (7°C), dew point 25°F (-4°C)
  • Altimeter: 30.14 inHg

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

11 documents, released by the NTSB on June 29, 2015. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.