NYC00LA054 · Mooney 20J
Mooney 20J · Accident: total loss of engine power (mechanical failure) en route
From Danbury Municipal Airport (DXR) to an unrecorded destination
Event
- NTSB case
- NYC00LA054
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Mooney 20J
- Aircraft type
- Mooney 20
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N43TP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Danbury Municipal Airport (DXR), Danbury, CTTo not recorded
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Total loss of engine power (mechanical failure)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Engine assembly, connecting rod › Failure, total
Approximate · Estimated position: the centre of New Milford, CT, the place the record names. Not the accident site.
NTSB narrative
The airplane experienced a propeller strike, and the engine was sent for a teardown inspection. The engine was reinstalled and then run for 0.4 hours. The pilot conducted a preflight, started the engine, and taxiing to the runway. A run-up check was completed, and no abnormalities were identified. The takeoff was uneventful, and the pilot executed closed traffic to a touch-and-go. Afterwards, he departed the traffic pattern, and climbed to 3,000 feet msl. The pilot configured the airplane for cruise flight. After approximately 30 minutes, the pilot proceeded back to the airport. While en route, he heard a loud 'bang,' and white smoke filled the cockpit. Unable to restart the engine the pilot executed a forced landing to a field. A teardown of the engine was preformed. The crankshaft nose seal was partially dislodged. The number 1 connecting rod was still attached. The number 2, 3, and 4 connecting rods had separated from the crankshaft. Damage to the connecting rod bearings was consistent with insufficient lubrication and high temperatures. No engine-oil-system pre-impact failures were identified.
Probable cause
Failure of 3 of the 4 connecting rods for an undetermined reason.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC00LA054
- Event ID
- 20001212X20311
- Case number
- NYC00LA054
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 47f13b6593e14096eb45ff7ed18c91a8f011772692338b7b9309880e63db8854; retrieved 2026-09-22T13:32:12.927Z.