# Incident 19971220045969I: Mooney M20J, Sioux Falls, SD, December 20, 1997

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: December 20, 1997, 12:45 local time
- Place: Sioux Falls, SD
- Airport: Great Planes Airport
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 43.5500° N, 96.7003° W: Placed by OpenAirDocs: center of Sioux Falls, SD, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=43.5500&lon=-96.7003&mi=10
- Aircraft: N57651, registered now (https://openairdocs.org/aircraft/N57651) (OpenAirDocs)
- Registry model: Mooney M20J (registry code 5870219, https://openairdocs.org/model/mooney-m20j) (OpenAirDocs)
- Registry engine: Lycoming AEIO-360 series (registry code 41522, https://openairdocs.org/engine/lycoming-aeio-360-series) (OpenAirDocs)
- Reported make and model: MOONEY M20J
- People aboard: 3
- Fatal injuries: 0
- Pilot flight hours: 345 total, 130 in this make and model
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19971220045969I

## Narrative

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

(-23) LANDED AIRCRAFT WITH GEAR UP. LANDING GEAR CHECKED OUT FINE WITH NO MECHANICAL PROBLEMS AFTER THE INCIDENT.

## Other reports on N57651 (2)

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

- [Incident 20100106025819I](https://openairdocs.org/incident/20100106025819I), Jan 6, 2010: Mooney M20J (N57651), Glencoe, MN, No damage. While conducting a proficiency check, (pc) the aircraft throttle cable became jammed. The throttle could not be moved forward or aft. This was noticed during a…
- [Incident 19960607027099I](https://openairdocs.org/incident/19960607027099I), Jun 7, 1996: Mooney M20J (N57651), Duluth, MN, Minor damage. Narrative: pilot was landing on rwy 32 at sky Harbor with wind coming over trees at approximately 020. Made a bad landing and porpoised. Decided not to go…

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.