# Incident 19860108003049I: Mooney M20J, Danbury, CT, January 8, 1986

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 8, 1986, 14:31 local time
- Place: Danbury, CT
- Airport: Danbury Municipal
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 41.3715° N, 73.4822° W: Placed by OpenAirDocs at DANBURY MUNI (DXR), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=41.3715&lon=-73.4822&mi=10
- Aircraft: N4101H, a cancelled registration (https://openairdocs.org/deregistered/N4101H-2003-10-28) (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
- Reported engine: LYC IO360A3B6
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 7,000 total, 5,000 in this make and model, 100 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19860108003049I

## Narrative

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

AT ALTITUDE OIL APPEARED ON WINDSHIELD. ENGINE SHUTDOWN ON FINAL. CRANKSHAFT SEAL LEAKING DUE TO FROZEN BREATHER.

## Other reports on N4101H (2)

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

- [Accident 20001205025259A](https://openairdocs.org/incident/20001205025259A), Dec 5, 2000: Mooney M20J (N4101H), Danbury, CT, Substantial damage. (-23) The a/c performed a normal runup and takeoff as reported by the pilot. Shortly after takeoff the pilot reported to the dxr tower that he had an engine…
- [Incident 19920929045429I](https://openairdocs.org/incident/19920929045429I), Sep 29, 1992: Mooney M20J (N4101H), Wadsworth, OH, Minor damage. Pilot lost directional control on a soft field takeoff. Veered off runway and struck a tree.

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.