# Accident 20161105023039A: Piper PA-28R-200, Watertown, WI, November 5, 2016

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 5, 2016, 16:00 local time
- Place: Watertown, WI
- Airport: Watertown Municipal
- Damage: Substantial damage
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 43.1706° N, 88.7208° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=43.1706&lon=-88.7208&mi=10
- Aircraft: N300KR, registered now (https://openairdocs.org/aircraft/N300KR) (OpenAirDocs)
- Registry model: Piper PA-28R-200 (registry code 7102811, https://openairdocs.org/model/piper-pa-28r-200) (OpenAirDocs)
- Registry engine: Lycoming I0360 series (registry code 41515, https://openairdocs.org/engine/lycoming-i0360-series) (OpenAirDocs)
- Reported make and model: PIPER PA-28R-200
- Reported engine: LYCOMING I0360 SER
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot
- Pilot flight hours: 4,284 total, 100 in this make and model, 7 in the last 90 days
- NTSB investigation: [NTSB GAA17LA090](https://openairdocs.org/ntsb/GAA17LA090) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20161105023039A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

WHILE ON FINAL APPROACH INTO WATERTOWN MUNICIPAL AIRPORT (KRYV) IN WATERTOWN WISCONSIN ONTO RUNWAY 23 AIRCRAFT N300KR A PA-28R-200 ARROW WITH ONLY THE PILOT ON BOARD STRUCK A TREE TOP OUTSIDE OF THE AIRPORT PERIMETER THEN STRUCK A PERIMETER FENCE POST PRIOR TO A HARD LANDING IN THE GRASS JUST SHORT OF RUNWAY 23 PAVEMENT. THERE WERE NO INJURIES. THE PILOT TAXIED THE AIRCRAFT TO THE RYV FBO. THE WEATHER WAS SUNNY FAIR AND CALM AT THE TIME. THE LOCAL FBO PERFORMED AN ENGINE RUN UP AND ESTABLISHED FLIGHT CONTROL CONTINUITY WITH NO DEFECTS NOTED.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB GAA17LA090](https://openairdocs.org/ntsb/GAA17LA090), Nov 5, 2016: Piper PA28R (N300KR), Watertown, WI, substantial damage. 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…

## Other reports on N300KR (4)

Matched to the same aircraft by N-number and date.

- [Accident 20111017025589A](https://openairdocs.org/incident/20111017025589A), Oct 17, 2011: Piper PA-28R-200 (N300KR), Watertown, WI, Substantial damage. On instructional flight while in cruise, the aircraft experienced an engine failure. Pilot made a successful emergency landing on a city street in Watertown,…
- [Incident 19911109060289I](https://openairdocs.org/incident/19911109060289I), Nov 9, 1991: Piper PA28R200 (N300KR), Paola, KS. Engine failed in flight. Forced landing at airport. Found internal failure on engine.
- [Accident 19850429040069A](https://openairdocs.org/incident/19850429040069A), Apr 29, 1985: Piper PA28R200 (N300KR), Kansas City, MO, Substantial damage. Landed short and bounced onto closed runway. Left gear collapsed. Marginal VFR, pilot not able to use nav radios.
- [Incident 19781218022989I](https://openairdocs.org/incident/19781218022989I), Dec 18, 1978: Piper PA28R200 (N300KR), Fresno, CA, Minor damage. Engine lost power flying in snow and rime ice, pilot landed on highway. No mechanical reason found.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.