Piper PA28 N8957W
2 September 2020 · Walker, Minnesota, United States · Fatal
Summary
On 2 September 2020 at about 01:07 local time, a Piper PA28 registered N8957W was involved in an accident near Walker, Minnesota, United States. One person was on board and one 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 01:07
- Classification
- Accident
- Location
- Walker, Minnesota, United States
- Nearest airport
- Walker Muni (Y49)
- Coordinates
- 47.2056, -94.4226
- Aircraft
- Piper PA28
- Registration
- N8957W
- Category
- Airplane
- Year built
- 1964
- Engines
- 1
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- St. Cloud → Bemidji
- Aircraft damage
- Substantial
- Weather
- VMC
- Light
- Dusk
- NTSB number
- CEN20LA374
People
1 person died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 1 | 1 | 0 | 0 | 0 |
Probable cause
The pilot’s impairment from the effects of an undiagnosed brain tumor.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
The pilot was on the final leg of a cross-country flight at the time of the accident. A representative of the fixed base operator (FBO) reported that, during a fuel stop after the initial flight leg, the pilot landed without announcing his intentions over the radio. The pilot subsequently requested the airplane be fueled but remained in the airplane and stared straight ahead as it was being fueled. Afterward, the pilot exited the airplane and ate his lunch in the FBO conference room. He was offered a bottle of water but did not acknowledge. During the second flight leg, air traffic controllers observed altitude and course deviations and noted slow radio responses that caused them to be concerned that the pilot was hypoxic or disoriented. They diverted the pilot to an intermediate airport and subsequently declared an emergency on the pilot’s behalf. He was met by emergency medical personnel but refused treatment. The pilot subsequently departed for the intended destination airport without refueling. During the final flight leg, position data depicted the pilot altering course as the airplane approached a line of storms. He proceeded about 15 miles away from the storms but then abruptly reversed course toward the intended destination airport and again approached the line of storms. About 4 minutes before the accident and as the airplane continued to approach the line of storms, the pilot entered a descent from 7,000 ft, which appeared to continue until impact with the surface of a lake. The airplane came to rest in about 12 ft of water. Post-recovery airframe and engine examinations did not reveal any anomalies consistent with a preimpact failure or malfunction. Based on the available information, the airplane flew about 4.5 hours since being fully fueled. However, due to submersion in the lake, no estimate could be made concerning the remaining fuel onboard at the time of the accident. Without additional data, whether fuel exhaustion occurred could not be determined. The pilot was reportedly slow to respond during conversations, sleeping excessively, and seemed to have significant difficulty focusing in the weeks before the accident, which was noted to be unusual for the pilot. His autopsy revealed a previously undiagnosed brain tumor that had a compressive effect on his brain. Based on the autopsy findings and information about the pilot’s behavior on the day of the accident and during the preceding weeks, the pilot was likely impaired by effects of his brain tumor at the time of the accident. The autopsy also identified two peripheral blood clots in the pilot’s left lung and blood clots in the deep veins of his left lower leg. Blood clots in deep leg veins may develop for a variety of reasons, including from slowed blood flow during prolonged sitting and from pro-clotting effects of cancer. However, whether symptoms from the blood clots contributed to the accident could not be determined from available information.
Quoted verbatim from the NTSB record.
Other Piper PA28 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 30 Jan 2020 | Piper PA28 | Naples, Florida, United States | Apflight Llc | No injuries | - |
| 30 Sep 2020 | Piper PA28 | Oregon City, Oregon, United States | - | No injuries | - |
| 21 Aug 2020 | Piper PA28 | Corsicana, Texas, United States | Private Individual | No injuries | - |
| 4 Oct 2020 | Piper PA28 | Fulton, New York, United States | - | Minor injuries | - |
| 16 Feb 2020 | Piper PA28 | Sparta, Michigan, United States | P T Arts LLC | No injuries | - |
| 2 Jul 2020 | Piper PA28 | Bridgeport, Texas, United States | - | No injuries | - |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 30 Apr 2020 | Cessna A185 | Anoka, Minnesota, United States | C Y Transport Llc | Minor injuries | - |
| 21 Aug 2020 | Lancair LANCAIR SUPER ES | Ely, Minnesota, United States | - | Fatal | 1 |
| 3 Oct 2020 | Cessna 172 | Hinckley, Minnesota, United States | - | No injuries | - |
| 25 Jun 2020 | Hatz HATZ CB 1 | Red Wing, Minnesota, United States | - | No injuries | - |
| 2 Oct 2020 | Piper PA46 | Lake Elmo, Minnesota, United States | - | Serious injuries | - |
| 25 Jun 2020 | Sonex ONEX | Minneapolis, Minnesota, United States | - | No injuries | - |