CHI03LA322 · Stinson 108-3
Stinson 108-3 · Accident: loss of engine power en route
From Fremont Municipal Airport (FET) to Lincoln Airport (LNK)
Event
- NTSB case
- CHI03LA322
- 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
- Unknown
- 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-3
- 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
- N6624M
- Operator
- Steven P Becker · private individual
- Onboard fatalities
- Unknown
- Route
- From Fremont Municipal Airport (FET), Fremont, NETo Lincoln Airport (LNK), Lincoln, NE
- 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
- Loss of engine power
- 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, gear › Failure, total
- Engine assembly, gear › Fatigue
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane sustained substantial damage during a forced landing. The pilot reported that the engine failed at 3,000 feet mean sea level during cruise flight. While on his landing roll on a sod field, the airplane struck a concrete marker and the airplane nosed over. The inspection of the airplane revealed the accessory gear drive was fractured in two pieces and had become dislodged from the crankshaft. A metallurgical examination of the accessory gear drive revealed a fatigue fracture at the key way.
Probable cause
The total loss of engine power due to the fatigue fracture of the engine accessory gear drive. A factor was the concrete marker.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI03LA322
- Event ID
- 20030929X01608
- Case number
- CHI03LA322
- 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, coordinates. 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: 392065b6eed960194456c78bef75393f9497f0bfb855146554d4eb15407b2996; retrieved 2026-09-21T19:21:20.897Z.