CEN13LA524 · Stemme Gmbh & Co S10-VT
512 Horses Stemme Gmbh & Co S10-VT · Accident: system/component malfunction/failure (non-power) on approach
From Waukegan National Airport (UGN) to Albert J Lindberg Airport (5Y1)
Event
- NTSB case
- CEN13LA524
- 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
Stemme Gmbh & Co S10-VT
- Aircraft type
- Stemme S10
- Category
- Glider
- 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
- N389BD
- Operator
- 512 Horses
- Onboard fatalities
- Unknown
- Route
- From Waukegan National Airport (UGN), Waukegan, ILTo Albert J Lindberg Airport (5Y1), Hessel, MI
- Aircraft age
- About 12 years (built 2001)
- 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
- Approach · VFR pattern final
- Defining eventThe 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
- System/component malfunction/failure (non-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
- Aircraft › Aircraft propeller/rotor
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that the motor-glider was on a long, straight-in visual approach to land when he heard a very loud "bang" in the front of the motor-glider followed by a severe vibration. The pilot shut down the engine and made a forced landing to a field. A postaccident examination of the aircraft revealed that the flexible disk on the front of the driveshaft had disconnected. Only one of the three bolts that connected the disk to the driveshaft remained partially installed. No evidence of Loctite or torque paint was found on the bolt. The bolt's threads were rusted, and the bolt's head was digging into the gearbox housing. The second bolt was sheared off, and the third bolt was missing.
A review of maintenance records revealed that the motor-glider's most recent annual inspection was completed about 1 month before the accident. According to the manufacturer's maintenance manual, a mechanic was required to check the tightness of the bolt connections of the flexible disk on the front side of the drive shaft. It is likely that the mechanic improperly inspected the bolts that connected the flexible joint to the front side of the driveshaft during the last annual inspection, which resulted in the ultimate failure of these components.
The maintenance records also revealed that, during the last annual inspection, Federal Aviation Administration Airworthiness Directive (AD) 2006-19-08, which required inspection for deformations and cracks in the exhaust pipes and the replacement of any damaged exhaust pipes found, had not been properly complied with when a weld repair was made to the No. 1 exhaust pipe. The mechanic's failure to not properly comply with the AD and the operator's failure to ensure that the AD was complied with were not causal to the accident; however, because the AD was not complied with, the motor-glider was not considered airworthy.
Probable cause
The mechanic’s failure to inspect the tightness of the bolts that connected the flexible disk to the driveshaft, which resulted in the failure of these components.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13LA524
- Event ID
- 20130904X62649
- Case number
- CEN13LA524
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2013-08-31.
- API snapshot SHA-256: 288ac54869d548791337515f7560e41bf002fb0452eaf722517b71120a037266; retrieved 2026-09-15T22:44:06.725Z.