Probable cause
The pilot’s failure to attain a proper glidepath on approach for landing, which resulted in impact with trees. Contributing to the accident was a partial, temporary loss of engine power for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation.
NTSB analysis
The commercial pilot reported that he entered the downwind leg of the airport traffic pattern higher than pattern altitude to avoid a traffic conflict. While on downwind, he switched the fuel selector and turned on the electric fuel pump. As he turned from downwind onto the base leg of the traffic pattern, he reduced engine power to idle and initiated a glide toward the runway. On final approach, the pilot realized that the airplane was too low; he added engine power, but the engine "failed to respond." He cycled the fuel pump, the engine surged, and the airplane impacted treetops and landed short of the runway. The pilot further reported that, after landing, he taxied the airplane to the ramp, thus it is unlikely there was a fuel issue.
A postaccident engine examination and test run revealed no anomalies that would have precluded normal operation.
Text from the NTSB. Open the NTSB docket for GAA17LA090 for the full record.
Event
- Date
- Nov 5, 2016
- Type
- Accident
- Place
- Watertown, Wisconsin
- Nearest airport
- Watertown Muni (RYV)
- Highest injury
- None
- Weather
- Visual (VMC)
- Light
- Day
Piper PA28R
- N-number
- N300KR
- Category
- Airplane
- Year built
- 1976
- Damage
- Substantial
- Operating rule
- Part 91 (general aviation)
- Purpose of flight
- Personal
Other records under this N-number
From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.