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

Piper PA-22-150 accident near Plymouth, Indiana, January 23, 2000

On January 23, 2000 at about 2:00 pm local time, a Piper PA-22-150, registered N3814P, was substantially damaged in an accident near Plymouth, Indiana (Plymouth Municipal airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

the pilot's disregard of the unsafe runway condition, his decision to operate the airplane on unsuitable terrain, and the failure to maintain runway centerline alignment which resulted in the landing gear contacting deeper snow. Factors associated with the accident were the snow covered runway and the snow bank which the airplane contacted.

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

What the record shows

Date
January 23, 2000 · about 2:00 pm local time
Place
Plymouth, Indiana · Plymouth Municipal · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-22-150 · all PA-22-150s on the register
Registration
N3814P · registry record · serial 22-3504
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot reported the runway was covered with approximately 2 inches of snow near the center and deeper snow on the left (north) side. He reported that as he was back taxiing, the left main gear contacted the deeper snow and the airplane veered to the left. The airplane then nosed over when it encountered a two to three foot deep snow bank on the left side of the runway. The pilot reported the local winds were from the south/southwest at 12 to 15 knots at the time of the accident. The Plymouth Municipal airport manager reported the runway had not been plowed. He stated the airport was NOTAMed closed and the accident pilot knew about the NOTAM.

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: 29 in the last 90 days; 15 in the last 30 days
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 3,136 hours
  • Last inspection: annual inspection, June 1, 1999; 90 hours since
  • Maximum gross weight: 2,000 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320 (piston); 0 hours total

The flight

  • Departed from: C65 Plymouth MI
  • Flight plan: none
  • Runway 28, 4,400 ft by 60 ft

Weather at the time

  • Light: daylight
  • Wind: from 260° at 13 knots
  • Visibility: 9 statute miles
  • Sky: overcast at 10,000 ft; not recorded
  • Temperature: 21°F (-6°C), dew point 10°F (-12°C)
  • Altimeter: 29.00 inHg
  • Observation at 1:53 pm from GSH, 29 miles away

Injuries

FatalSeriousMinorNone
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.