SEA98FA089 · Mooney M20A
Mooney M20A · Accident: airframe, component or system failure while maneuvering
From Lewiston Nez Perce County Airport (LWS) to Great Falls International Airport (GTF)
Event
- NTSB case
- SEA98FA089
- 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
- 1 · 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 M20A
- 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
- N1048B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lewiston Nez Perce County Airport (LWS), Lewiston, IDTo Great Falls International Airport (GTF), Great Falls, MT
- 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
- Maneuvering
- 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
- Airframe, component or system failure
- 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 › Design stress limits of aircraft, exceeded
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Prior to takeoff, the pilot received a weather briefing for his proposed route of flight. The specialist reported low ceilings and mountain obscuration along the route, and suggested a route of flight away from the mountains and poor weather conditions. The pilot filed a visual flight rules flight plan for his original route. Approaching his destination, the pilot contacted air traffic and advised that he needed assistance in locating an airport that was clear of the weather, as he was on top of an overcast layer and could not see the ground. The controller informed the pilot of the multiple cloud layers in the area and to remain in visual conditions. With the aid of other pilots in the area who were reporting actual weather conditions, the controller was maneuvering the aircraft to an area where he might be able to get below the overcast layer. While en route, the pilot notified the controller that he saw a hole and was going to try and punch through it. Shortly after this time, the aircraft dropped off radar contact and there was no further communication from the pilot. Evidence found at the accident site indicated that the aircraft broke-up in flight. The low-time, non-instrument rated pilot had just purchased the airplane and had not received the complex aircraft sign-off for solo operation.
Probable cause
The design stress limits of the aircraft was exceeded. The pilot's inadequate preflight planning/preparation, lack of an instrument rating, poor weather evaluation and low ceilings and mountain obscuration were factors.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA98FA089
- Event ID
- 20001211X10414
- Case number
- SEA98FA089
- 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: b1b861727b8996de2b352347df9b27840224a0efd64ca5a312f9023c20919a5d; retrieved 2026-09-20T22:33:18.346Z.