Aircraft impacts terrain and residence during GPS approach

Casualties unknown • Glenwood, MN, US

An aircraft sustained substantial damage after colliding with a fence, terrain, and a residence while performing an instrument approach to its destination.

What happened

The aircraft was operating under instrument flight rules (IFR) at a cruise altitude of 10,000 feet mean sea level (msl). Prior to the approach, air traffic control authorized a descent from 6,000 feet msl to 4,000 feet msl at the pilot's discretion. The pilot initially requested to remain at 6,000 feet to avoid potential icing conditions. Following a request and clearance to climb to 7,000 feet msl, the aircraft encountered light rime and mixed icing.

The flight was cleared for a GPS instrument approach to runway 33. Radar track data showed the aircraft began its descent from 7,000 feet approximately 9 nautical miles southeast of the destination, intercepting the published approach course. The aircraft crossed the GPS runway 33 approach final approach fix (FAF), located 5 nautical miles south-southeast of the runway threshold, at 6,000 feet msl; however, the published procedure required a minimum altitude crossing the FAF of 3,000 feet msl. Final radar contact occurred at 4,000 feet msl about 2 nautical miles south-southeast of the airport.

The aircraft subsequently impacted terrain approximately 1 nautical mile north-northwest of the airport. The debris path was oriented on a 150-degree magnetic bearing toward the airport, while the inbound course for the GPS approach was 338 degrees magnetic. The collision involved a fence, terrain, and a residence, resulting in substantial damage to the aircraft.

At the time of the accident, terminal weather forecasts for an airport 14 nautical miles north of the destination indicated ceilings of 300 feet above ground level (agl) overcast with 2 statute mile visibility in light snow and mist. An airport ceiling of 200 feet agl was recorded 15 minutes prior to the accident. While preflight weather briefings had been provided for two previous flights that day, no weather briefing was obtained by the pilot for the accident flight.

The investigation

A post-accident examination of the aircraft revealed no airframe or engine anomalies that would indicate a malfunction occurred prior to the accident.

Probable cause

The investigation did not explicitly state a single probable cause, but noted the pilot failed to obtain a weather briefing and was operating in icing conditions and low visibility.

Frequently asked questions

What happened in the 2004-12-09 Piper PA-32R-301T accident near Glenwood, MN?

An aircraft sustained substantial damage after colliding with a fence, terrain, and a residence while performing an instrument approach to its destination.

What aircraft was involved and where did it happen?

The accident on 2004-12-09 involved a Piper PA-32R-301T, registration N587C, at Glenwood, MN.

What was the probable cause of the accident?

The investigation did not explicitly state a single probable cause, but noted the pilot failed to obtain a weather briefing and was operating in icing conditions and low visibility.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20050104X00009. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.

Loading the flight search…