Maule M5 accident near Woodinville, Washington, March 9, 2013
On March 9, 2013 at about 10:45 pm local time, a 1979 Maule M5, registered N17PR, was substantially damaged in an accident during enroute (cruise) near Woodinville, Washington. It was a personal flight under general aviation rules (Part 91). 1 person was killed and 1 person was seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain adequate airspeed following a total loss of engine power due to fuel contamination, which resulted in a stall/spin and subsequent impact with terrain.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 9, 2013 · about 10:45 pm local time
- Place
- Woodinville, Washington · map
- Type
- Accident
- Injuries
- 1 person was killed and 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Maule M5 210C, built 1979 · all M5s on the register
- Registration
- N17PR · no longer on the register · serial 6205C
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The passenger reported that he could not remember if the pilot checked the fuel before the flight, but he remembered that, during the engine start, the engine turned over several times before it started. About 30 minutes into the flight, the engine started to sputter, and then it stopped; the pilot was unable to restart the engine, and the airplane began to lose altitude. The passenger recalled that he observed the stall warning light illuminate and that the airplane was in a turn, but he did not recall the impact. One witness reported that he observed the airplane circle and that it appeared very low. Another witness reported hearing a "pop" sound and then a "puff" or a "sputter" and then seeing that the propeller had stopped. A third witness reported that he saw the airplane in a hard banking turn and that he could tell that the airplane "was going down." The airplane impacted a single-family residence about 16 nautical miles northeast of the departure airport. GPS data revealed that the airplane made several course heading changes at varying altitudes and airspeeds during the flight. During the last 16 seconds of the flight track, the airplane turned left, which was likely indicative of the pilot attempting to make a forced landing to a nearby pond. The last GPS data were recorded when the airplane was at an altitude of 650 feet mean sea level and a groundspeed of 40 knots. The airplane's previous flight occurred 102 days before the accident. During this period of inactivity, the airplane remained parked outside on an airport ramp exposed to inclement weather conditions conducive to the formation of condensation in the airplane's partially filled fuel tanks. No records were found indicating that the airplane had been refueled before the accident flight. Fuel was recovered from the airplane at the accident site. Analysis of a fuel sample revealed the presence of water. The fuel contamination likely resulted in the loss of engine power and the pilot's inability to restart the engine after the power loss. The pilot likely failed to maintain adequate airspeed following the loss of engine power. A postaccident examination of the airframe and engine revealed no evidence of mechanical anomalies that would have precluded normal operation.
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
What happened, in order
- Off-field or emergency landing during emergency descent
- Aerodynamic stall/spin during emergency descent
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
- Fuel contamination during enroute (cruise) defining event
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Attain/maintain not possible
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Aircraft › Fluids/misc hardware › Fluids › Water › Fluid condition
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 946 hours in all; 111 in this make and model; 897 as pilot in command
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 7,948.7 hours
- Last inspection: annual inspection, July 26, 2011; 36.1 hours since
- Maximum gross weight: 2,300 lb
- Seats: 4
- Landing gear: fixed
- Engine: Continental IO360 (piston); 0 hours total
The flight
- Departed from: RNT Renton WA at 10:31 pm
- Destination: RNT Renton WA
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 290° at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 48°F (9°C), dew point 36°F (2°C)
- Altimeter: 30.43 inHg
- Observation at 10:53 pm from PAE, 14 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
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.
