DEN00LA143 · Mooney M20J
Mooney M20J · Accident: total loss of engine power (mechanical failure) en route
From Los Alamos Airport (LAM) to Rocky Mountain Metropolitan Airport (BJC)
Event
- NTSB case
- DEN00LA143
- 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 M20J
- Aircraft type
- Mooney M20
- 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
- N201DK
- Operator
- Wings of Denver
- Onboard fatalities
- Unknown
- Route
- From Los Alamos Airport (LAM), Los Alamos, NMTo Rocky Mountain Metropolitan Airport (BJC), Broomfield, CO
- 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 · descent
- 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
- Terrain condition › None suitable
- Terrain condition › Rough/uneven
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During climb following takeoff the engine oil pressure went to 0 and the oil temperature increased. The pilot reduced power, and looked for an emergency landing site in the rough mountainous terrain he was over flying. When the engine began to vibrate, the pilot secured the engine and made an emergency landing in a field with an uneven surface. During landing roll, the nose landing gear collapsed causing damage to the engine firewall. Examination of the engine revealed the number 3 connecting rod bearing had failed due to oil starvation followed by failure of the number 3 connecting rod. The number I connecting rod bearing had also failed due to reduced lubrication. The engine contained 7 quarts of aviation grade lubricating oil and the oil pump and internal oil distribution system were open and functioned in a normal fashion. The correct parts were verified.
Probable cause
The lack of suitable terrain for a forced landing. A factor was a complete loss of power due to mechanical failure.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN00LA143
- Event ID
- 20001212X21447
- Case number
- DEN00LA143
- 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: 2b77975a1bb14f0026f4c315b3a42cc39b71f073dda3c7264d36e025365d1ce6; retrieved 2026-09-22T12:41:35.009Z.