# Incident 20040915033929I: Mooney M20K, Asheville, NC, September 15, 2004

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: September 15, 2004, 21:04 local time
- Place: Asheville, NC
- Airport: Asheville Regional
- Damage: Substantial damage
- Phase of flight: Forced/Precautionary Landing
- Operating rules: General operating rules (Part 91)
- Location: 35.4361° N, 82.5420° W: Placed by OpenAirDocs at ASHEVILLE RGNL (AVL), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=35.4361&lon=-82.5420&mi=10
- Aircraft: N57232, registered now (https://openairdocs.org/aircraft/N57232) (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
- Reported engine: CONT TSIO360*
- People aboard: 3
- Fatal injuries: 0
- Pilot flight hours: 800 total, 500 in this make and model, 35 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20040915033929I

## Narrative

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

(-23) AT APPROXIMATELY 5:00 PM ON SEPTEMBER 15, 2004, AIRCRAFT (N57232) HAD A GEAR UP LANDING AFTER LOSING POWER ON TAKEOFF. THE PILOT STATED THAT THE AIRCRAFT RUN UP WAS NORMAL BEFORE TAKEOFF.

## Other reports on N57232 (2)

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

- [Incident 20060602012419I](https://openairdocs.org/incident/20060602012419I), Jun 2, 2006: Mooney M20K (N57232), Richmond, KY. (-23) At FL200 engine quit running. Engine restarted at 13,000 MSL. Landed at Richmond KY (I39) without incident. Mechanic statement indicates that…
- [Incident 19861015077539I](https://openairdocs.org/incident/19861015077539I), Oct 15, 1986: Mooney M20K (N57232), Chino, CA, Minor damage. Propeller struck runway after porposing on landing.

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.