DEN89LA221 · Mooney M20C
Mooney M20C · Accident: in flight encounter with weather en route
From Hellinger Airport (MT02) to Lewiston Nez Perce County Airport (LWS)
Event
- NTSB case
- DEN89LA221
- 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
- Instrument Meteorological Cond
Mooney M20C
- 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
- N3456X
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hellinger Airport (MT02), Hardin, MTTo Lewiston Nez Perce County Airport (LWS), Lewiston, ID
- 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
- In flight encounter with weather
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Proper altitude, not maintained
- Pilot in command › VFR flight into imc, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE INSTRUMENT RATED COMMERCIAL PILOT REPORTED THAT HE WAS CRUISING AT 14,500 FEET WHEN HE ENCOUNTERED CLOUDS. HE DESCENDED TO 12,500 FEET AND THEN TO 11,000 FEET IN AN EFFORT TO AVOID THE WEATHER. HE STATED 'I DESCENDED DOWN TO ELEVEN THOUSAND AND THE TREES CAME RIGHT UP ON ME. I WAS VFR, DIDN'T FILE A FLIGHT PLAN . . .' ELEVATION OF THE CRASH SITE WAS 9175 FEET.
Probable cause
VFR FLIGHT BY THE PILOT INTO INSTRUMENT METEOROLOGICAL CONDITIONS (IMC) AND HIS FAILURE TO MAINTAIN SUFFICIENT ALTITUDE. RELATED FACTORS WERE: THE HIGH TERRAIN AND ADVERSE WEATHER CONDITIONS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN89LA221
- Event ID
- 20001213X29356
- Case number
- DEN89LA221
- 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: 2eb8c9ea40f44d2859e77ae816c9df0cf9a99fa62b81ceb9ea37a93208557b8e; retrieved 2026-09-21T15:49:11.974Z.