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

Piper PA-28R-200 accident near San Diego, California, January 30, 2012

On January 30, 2012 at about 4:30 pm local time, a Piper PA-28R-200, registered N746R, was involved in an accident during standing (engine(s) start-up) near San Diego, California (Gillespie Field Airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to turn the magneto switch to the off position before moving the propeller to start the engine by hand.

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

What the record shows

Date
January 30, 2012 · about 4:30 pm local time
Place
San Diego, California · Gillespie Field Airport · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Piper PA-28R-200 · all PA-28R-200s on the register
Registration
N746R · no longer on the register · serial 28R-7535075
Damage
Not recorded
Flight
Personal flight · general aviation rules (Part 91)

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

The passenger reported that he and the pilot were both seated in the airplane when the pilot made three unsuccessful attempts to start the engine. The pilot told the passenger to “get out, I need to jump it.” The passenger got out of the airplane and was walking away when he heard a noise. When he looked back toward the front of the airplane, he saw the pilot lying on the ground below the propeller. The airplane’s engine was not running. Postaccident examination revealed that the magneto switch was in the both position. It is likely that the pilot moved the propeller, and because the magnetos were in a ready-to-start condition, this resulted in a spark plug firing, which caused the propeller to turn rapidly and strike the pilot.

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. AC/prop/rotor contact w person during standing (engine(s) start-up) defining event

The NTSB's findings

  • cause Aircraft › Aircraft power plant › Ignition system › Switching › Incorrect use/operation
  • cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine sea; instrument: airplane
  • Medical certificate: Class 3 (without waivers/limitations)
  • Injury: fatal

The aircraft

  • Maximum gross weight: 2,600 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Lycoming IO-360 SER (piston); 0 hours total

The flight

  • Departed from: SEE San Diego CA
  • Destination: SEE San Diego CA
  • Flight plan: not recorded

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: scat at 2,000 ft
  • Temperature: 61°F (16°C), dew point 27°F (-3°C)
  • Altimeter: 30.04 inHg
  • Observation at 4:51 pm from SAN, 12 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

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.