Aviation Crash Map

Piper PA-32R-301T N587C

9 December 2004 · Glenwood, Minnesota, United States · Fatal

Summary

On 9 December 2004 at about 23:10 local time, a Piper PA-32R-301T registered N587C was involved in an accident near Glenwood, Minnesota, United States. 2 people were on board and 2 died. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 23:10
Classification
Accident
Location
Glenwood, Minnesota, United States
Nearest airport
Glenwood Municipal (GHW)
Coordinates
45.6514, -95.3397
Aircraft
Piper PA-32R-301T
Registration
N587C
Category
Airplane
Engines
1
Operator
Not recorded
Operating rule
Part 91: General Aviation
Purpose of flight
Personal
Phase of flight
Not recorded
Route
Mount Vernon → Glenwood
Aircraft damage
Substantial
Weather
IMC
Light
Night
NTSB number
CHI05FA042

People

2 people died.

On board Died Serious Minor Uninjured
2 2 0 0 0

Probable cause

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.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

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

Quoted verbatim from the NTSB record.

Other Piper PA-32R accidents

Date Aircraft Location Operator Outcome Died
5 Sep 2004 Piper PA-32R-301T
N880SC
Picabo, Idaho, United States Bob Cullen No injuries -
25 Jun 2004 Piper PA-32R-300
N49KG
Dalhart, Texas, United States Kenneth Green No injuries -
9 Sep 2004 Piper PA-32R-300
N6209J
Rachel, Texas, United States - Fatal 1
21 Jan 2004 Piper PA-32R-300
N8701E
Big Pine, California, United States - Fatal 1
22 Mar 2004 Piper PA-32R-301
N8173U
Harlan, Kentucky, United States - Fatal 6
8 Aug 2004 Piper PA-32R-301
N4171D
Pittstown, New Jersey, United States George Tarantino Minor injuries -

All 525 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
19 Jan 2004 Piper PA-46-500TP
N1968W
Minneapolis, Minnesota, United States - No injuries -
23 Aug 2004 Enstrom F-28A
N9573
Leroy, Minnesota, United States P & N Corporation Serious injuries -
25 Sep 2004 Johnson TITAN TORNADO I
UNREG
Carlton, Minnesota, United States - No injuries -
19 May 2004 Cessna 180J
GNQK
South St. Paul, Minnesota, United States - No injuries -
12 May 2004 Robinson R22 BETA
N2301F
Winsted, Minnesota, United States - Minor injuries -
23 Aug 2004 Champion 7ECA
N11083
Angle Inlet, Minnesota, United States Daniel N. Carlson Fatal 2

All 170,864 records in United States