FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI05FA042 · Piper PA-32R-301T

9 Dec 2004 · Glenwood, MN, United States

Piper PA-32R-301T · Accident: in flight encounter with weather on approach

From Mount Vernon Outland Airport (MVN) to Glenwood Municipal Airport (GHW)

Report a problem

Event

NTSB case
CHI05FA042
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Piper PA-32R-301T

Aircraft type
Piper PA-32
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N587C
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mount Vernon Outland Airport (MVN), Mount Vernon, ILTo Glenwood Municipal Airport (GHW), Glenwood, MN
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
In flight encounter with weather
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command › Altitude/clearance, not maintained
  • Pilot in command › Missed approach, not performed

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

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

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI05FA042
Event ID
20050104X00009
Case number
CHI05FA042
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: c337142ac5258e4f86bc7fdd1d3d6f8d7fdaa4d75e8a881d38445ae83935ad67; retrieved 2026-09-20T18:10:54.685Z.