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

Piper PA-28-181 accident near Sandusky, Ohio, July 20, 2003

On July 20, 2003 at about 2:50 pm local time, a Piper PA-28-181, registered N8199D, was substantially damaged in an accident near Sandusky, Ohio (Griffing Sandusky airport). It was a personal flight under general aviation rules (Part 91). 4 people were seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to maintain the engine mixture control during the go-around, which resulted in a loss of power, and in-flight collision with trees.

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

What the record shows

Date
July 20, 2003 · about 2:50 pm local time
Place
Sandusky, Ohio · Griffing Sandusky · map
Type
Accident
Injuries
4 people were seriously injured.
Weather
visual conditions (good weather)
Aircraft
Piper PA-28-181 · all PA-28-181s on the register
Registration
N8199D · registry record · serial 28-8290115
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The airplane was on final approach to a 3,559-foot-long, 60-foot-wide, asphalt runway, when the pilot observed a twin-engine airplane on a taxiway near the runway. The pilot was not certain if the airplane was going to utilize the runway, and elected to go-around. The pilot pushed the throttle full-forward and kept his right hand on the power quadrant. During the climb out, the engine began to sputter and lose power. The pilot looked down at the power quadrant and noticed that the engine mixture control was pulled back. He pushed mixture control in and lowered the airplane's nose to avoid a stall; however, the airplane struck trees about 1/2 mile beyond the departure end of the runway. Examination of the engine and associated controls did not reveal any pre-impact mechanical malfunctions.

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

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 338 hours in all; 67 in this make and model; 4 in the last 90 days; 3 in the last 30 days; 285 as pilot in command
  • Last flight review: June 15, 2003
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: left
  • Injury: serious injuries

The aircraft

  • Airframe total time: 8,461 hours
  • Last inspection: annual inspection, December 9, 2003; 152 hours since
  • Maximum gross weight: 2,550 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-360-A4M (piston); 0 hours total

The flight

  • Departed from: FWA Fort Wayne IN at 1:30 pm
  • Destination: SKY Sandusky OH
  • Flight plan: none
  • Runway 27, 3,559 ft by 60 ft

Weather at the time

  • Light: daylight
  • Wind: from 230° at 9 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 77°F (25°C), dew point 63°F (17°C)
  • Altimeter: 30.01 inHg
  • Observation at 3:53 pm from LPR, 22 miles away

Injuries

FatalSeriousMinorNone
Crew1
Passengers3

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.