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

Piper PA-32R-301T accident near Glenwood, Minnesota, December 9, 2004

On December 9, 2004 at about 11:10 pm local time, a Piper PA-32R-301T, registered N587C, was substantially damaged in an accident near Glenwood, Minnesota (Glenwood Municipal airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The pilot's failure to execute a missed approach and his failure to maintain sufficient altitude and clearance from terrain and obstructions. Contributing factors were the pilot's failure to obtain a preflight weather briefing, his decision to delay descent for approach (icing concerns), cloud ceilings below the minimum descent altitude, in-flight icing conditions, dark night lighting conditions, and the fence and residence.

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

What the record shows

Date
December 9, 2004 · about 11:10 pm local time
Place
Glenwood, Minnesota · Glenwood Municipal · map
Type
Accident
Injuries
2 people were killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Piper PA-32R-301T · all PA-32R-301Ts on the register
Registration
N587C · no longer on the register · serial 3257324
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The airplane was substantially damaged when it collided with a fence, terrain and a residence during an instrument approach to the intended destination. The accident flight was operating on an instrument flight rules (IFR) flight plan at a cruise altitude of 10,000 feet mean sea level (msl) prior to descent for the approach. After descent to 6,000 feet msl, further descent to 4,000 feet msl at pilot's discretion was authorized by air traffic control (ATC). The pilot requested to remain at 6,000 feet in order to stay "out of the clouds here [until] the last minute [due to] possible icing." Shortly afterward the pilot requested and was cleared by ATC to climb to 7,000 feet msl when the aircraft encountered "light" rime and mixed icing conditions. The flight was subsequently cleared for the global positioning system (GPS) instrument approach to runway 33. Radar track data indicated that the aircraft began a descent from 7,000 feet about 9 nautical miles (nm) southeast of the destination and intercepted the published approach course. The radar track data plot depicted the airplane crossing the GPS runway 33 approach final approach fix (FAF), located 5 nm south-southeast of the runway threshold, at 6,000 feet msl. The minimum altitude crossing the FAF was 3,000 feet msl, according to the published procedure. Final radar contact was at 4,000 feet msl about 2 nm south-southeast of the airport. The normal floor of radar coverage in the area was 4,000 feet msl. The airplane subsequently impacted terrain about 1 nm north-northwest of the airport. The debris path was oriented on a 150-degree magnetic bearing toward the airport. The inbound course for the GPS approach to runway 33 was 338-degrees magnetic. The published minimum descent altitude (MDA) for the straight-in GPS runway 33 approach was 1,760 feet msl, or 372 feet above ground level (agl). An overcast ceiling at 200 feet agl was recorded at the airport about 15 minutes prior to the accident. Terminal weather forecasts issued for an airport located 14 nm north of the intended destination called for ceilings of 300 feet agl overcast and 2 sm visibility in light snow and mist about the time of the accident. Preflight weather briefings for two previous flights that day had been provided, however, no weather briefing for the accident flight was obtained by the pilot. A post-accident examination did not reveal any airframe or engine anomalies associated with a pre-accident malfunction. FAA regulations required a pilot to execute a missed approach when operating below the MDA if the aircraft is not "continuously in a position from which a descent to a landing on the intended runway can be made a normal rate of descent using normal maneuvers."

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; instrument: airplane
  • Flight time: 711 hours in all; 685 in this make and model; 25 in the last 90 days; 9 in the last 30 days; 661 as pilot in command
  • Last flight review: August 22, 2003
  • Medical certificate: Class 3 (valid medical--no waivers/lim.)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 359.7 hours
  • Last inspection: annual inspection, October 4, 2004; 42.6 hours since
  • Maximum gross weight: 3,600 lb
  • Seats: 7
  • Landing gear: retractable
  • Engine: Lycoming TIO-540-AH1A (piston); 0 hours total

The flight

  • Departed from: MVN Mount Vernon IL at 7:40 pm
  • Destination: GHW Glenwood MN
  • Flight plan: IFR
  • Runway 33, 4,500 ft by 75 ft

Weather at the time

  • Light: night
  • Wind: from 050° at 8 knots
  • Visibility: 1.2 statute miles
  • Sky: overcast at 200 ft
  • Temperature: 36°F (2°C), dew point 36°F (2°C)
  • Altimeter: 29.68 inHg
  • Observation at 10:55 pm from GHW, 1 miles away

Injuries

FatalSeriousMinorNone
Crew1
Passengers1

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.