# Incident 20001014019319I: Mooney M20J, Rialto, CA, October 14, 2000

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 14, 2000, 10:45 local time
- Place: Rialto, CA
- Airport: Rialto Municipal/Miro Field Airport
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 34.1293° N, 117.4020° W: Placed by OpenAirDocs at Rialto Municipal Miro Field, closed, within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=34.1293&lon=-117.4020&mi=10
- Aircraft: N4361H, registered now (https://openairdocs.org/aircraft/N4361H) (OpenAirDocs)
- Registry model: Mooney M20J (registry code 5870219, https://openairdocs.org/model/mooney-m20j) (OpenAirDocs)
- Registry engine: Lycoming I0360 series (registry code 41515, https://openairdocs.org/engine/lycoming-i0360-series) (OpenAirDocs)
- Reported make and model: MOONEY M20J
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 940 total, 340 in this make and model, 15 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20001014019319I

## Narrative

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

(-23) ON OCT. 14, 2000 A MOONEY A/C N4361H, MODEL M30-J, SERIAL NUMBER 24-0720, LANDED GEAR UP AT THE RIALTO AIRPORT, LOCATED IN RIALTO, CA. THE PILOT WAS CONTACTED AND HE REPORTED THAT HE WAS GETTING BUMPED AROUND DUE TO HIGH WINDS AND GUSTS JUST BEFORE ENTERING THE DOWN WIND LEG FOR RUNWAY 35, AT RIALTO AIRPORT. HE SAID "I JUST BECAME DISTRACTED AND FORGOT TO LOWER THE LANDING GEAR".

## Other reports on N4361H (1)

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

- [Incident 20060816016709I](https://openairdocs.org/incident/20060816016709I), Aug 16, 2006: Mooney M20J (N4361H), San Luis Obispo, CA, Minor damage. (-23) Pilot's statement: on Wednesday evening, August 16, 2006, I [privacy data omitted] (pilot-in-command) filed an IFR flight plan telephonically with…

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.