MIA97LA144 · Stinson 108-1
Stinson 108-1 · Accident: total loss of engine power (mechanical failure) en route
Event
- NTSB case
- MIA97LA144
- 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
Stinson 108-1
- Aircraft type
- Stinson 108
- 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
- N9063K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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, crankshaft › Fractured
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While in cruise flight, the pilot noticed that the engine 'became a little rough,' oil pressure was bleeding off, and the tachometer was fluctuating, followed by a complete loss of engine power. The pilot elected to land in a field, touched down, rolled about 240 feet, before 'soft dirt' caused the airplane to nose over. Examination of the engine revealed it would not rotate, but oil and fuel were present. The engine was disassembled, and examination revealed that the crankshaft had cracked completely through at the number one connecting rod journal. The fracture appeared to be clean with no exterior evidence of an existing crack or deterioration of any kind. The fracture did have within it, ridges and valleys and what appeared to be air bubbles near the ridges and valleys.
Probable cause
a fracture in the crankshaft, which resulted in a total loss of engine power, a forced landing, and a nose over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA97LA144
- Event ID
- 20001208X07795
- Case number
- MIA97LA144
- 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: bc37a7383b6e8fa7da26d13e42fe2cb2845a988855c6a171afb40d0b80db141d; retrieved 2026-09-22T19:55:30.995Z.