# Incident 19820404017809I: Mooney M20C, Fallbrook, CA, April 4, 1982

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: April 4, 1982, 17:15 local time
- Place: Fallbrook, CA
- Airport: Fallbrook
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 33.3747° N, 117.2183° W: Placed by OpenAirDocs: center of Fallbrook, CA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.3747&lon=-117.2183&mi=10
- Aircraft: N6833N, a cancelled registration (https://openairdocs.org/deregistered/N6833N-2019-05-04) (OpenAirDocs)
- Registry model: Mooney M20C (registry code 5870208, https://openairdocs.org/model/mooney-m20c) (OpenAirDocs)
- Registry engine: Lycoming O&VO-360 series (registry code 41514, https://openairdocs.org/engine/lycoming-o-vo-360-series) (OpenAirDocs)
- Reported make and model: MOONEY M20C
- Fatal injuries: 0
- Pilot flight hours: 3,538 total, 3,488 in this make and model, 42 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19820404017809I

## Narrative

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

LANDED GEAR UP. DID NOT HEAR GEAR HORN. WAS USING HEADPHONE THAT EXCLUDED COCKPIT SOUNDS.

## Other reports on N6833N (2)

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

- [Accident 20170820011379A](https://openairdocs.org/incident/20170820011379A), Aug 20, 2017: Mooney M20C (N6833N), Palm Coast, FL, Substantial damage. On August 20, 2017, about 2055 eastern daylight time, a Mooney M20C, N6833N, was substantially damaged (fire damage to the complete cockpit)during a forced…
- [Incident 20001104021269I](https://openairdocs.org/incident/20001104021269I), Nov 4, 2000: Mooney M20C (N6833N), Deland, FL, Minor damage. (-23) Left tallahassee on 11-04-00 at approx. 10:00 am bound for embry riddle parents fly-in weekend. He became intimidated by the amount of traffic in daytona…

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.