# Incident 19940921046379I: Mooney M20K, Bremerton, WA, September 21, 1994

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: September 21, 1994, 13:45 local time
- Place: Bremerton, WA
- Airport: Bremerton National
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 47.4902° N, 122.7650° W: Placed by OpenAirDocs at Bremerton National Airport (PWT), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=47.4902&lon=-122.7650&mi=10
- Aircraft: N1157K, registered now (https://openairdocs.org/aircraft/N1157K) (OpenAirDocs)
- Registry model: Mooney M20K (registry code 5870220, https://openairdocs.org/model/mooney-m20k) (OpenAirDocs)
- Registry engine: Continental TSIO-360 series (registry code 17019, https://openairdocs.org/engine/continental-tsio-360-series) (OpenAirDocs)
- Reported make and model: MOONEY M20K
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 425 total, 325 in this make and model, 10 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19940921046379I

## Narrative

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

STEEP ANGLE TO RUNWAY ON LANDING. PROP STRUCK RUNWAY THEN STEP. APPEARS GEAR NOT DOWN. WENT AROUND. PUT GEAR DOWN.

## Other reports on N1157K (2)

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

- [Accident 20080911854729A](https://openairdocs.org/incident/20080911854729A), Sep 11, 2008: Mooney M20K (N1157K), Weaverville, CA, Substantial damage. At an undetermined point in time, the bracket that supported the fuel flow transducer for the airplane’s fuel monitoring system failed. This allowed the…
- [Incident 20041120029349I](https://openairdocs.org/incident/20041120029349I), Nov 20, 2004: Mooney M20K (N1157K), Baker, OR, Minor damage. (-23) Pilot was operating on an instrument flight plan in visual weather conditions. Did not allow for the high wind aloft and ended up very high at the final…

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.