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

Piper PA-32R-300 accident near Medford, Minnesota, August 26, 1996

On August 26, 1996 at about 3:32 pm local time, a Piper PA-32R-300, registered N7133C, was destroyed in an accident near Medford, Minnesota. It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

failure of the pilot to maintain control of the airplane, due to spatial disorientation. Factors relating to the accident were: failure of the (primary) vacuum system and a restriction in the (standby) vacuum system.

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

What the record shows

Date
August 26, 1996 · about 3:32 pm local time
Place
Medford, Minnesota · map
Type
Accident
Injuries
1 person was killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Piper PA-32R-300 · all PA-32R-300s on the register
Registration
N7133C · no longer on the register · serial 36R-7680039
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

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

While flying in instrument meteorological conditions (IMC), the pilot reported to approach control that the airplane had suffered a loss of its vacuum system. He requested a lower altitude in an attempt to descend into visual meteorological conditions (VMC). The pilot reported being unable to locate visual conditions. The airplane departed controlled flight and impacted the terrain. The primary vacuum pump was found inoperative with fractures of the rotor and vanes. The standby system was found not capable of operation due to a restriction in the system from the migration of sealing material or a gasket, blocking a hole drilled for the installation and operation of the standby system.

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: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 1,789 hours in all; 111 in this make and model; 56 in the last 90 days; 27 in the last 30 days; 1,628 as pilot in command
  • Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 2,543 hours
  • Last inspection: annual inspection, November 13, 1995; 133 hours since
  • Maximum gross weight: 3,600 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Lycoming IO-540-1A5D (piston); 0 hours total
  • Fire on the ground

The flight

  • Departed from: FCM Eden Prairie MN at 3:05 pm
  • Destination: DVN Davenport IA
  • Flight plan: IFR
  • Runway 0

Weather at the time

  • Light: daylight
  • Wind: from 300° at 6 knots
  • Visibility: 10 statute miles
  • Sky: overcast at 600 ft; not recorded
  • Temperature: 63°F (17°C), dew point 63°F (17°C)
  • Altimeter: 30.00 inHg
  • Observation at 2:55 pm from KFB, 10 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.