DEN00IA133 · Diamond Aircraft Industries 20C-1
Diamond Aircraft Industries 20C-1 · Incident: propeller failure/malfunction en route
From Provo Municipal Airport (PVU) to Manti-Ephraim Airport (41U)
Event
- NTSB case
- DEN00IA133
- 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
- Incident
- 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
Diamond Aircraft Industries 20C-1
- Aircraft type
- Diamond 20
- 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
- N991CT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Provo Municipal Airport (PVU), Provo, UTTo Manti-Ephraim Airport (41U), Ephraim, UT
- 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
- Propeller failure/malfunction
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Company maintenance personnel › Maintenance, adjustment, inadequate
- Miscellaneous, bolt/nut/fastener/clamp/spring › Undertorqued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot had just departed on a cross-country flight, and had climbed to 9,500 feet. He said that he began to feel a 'heavy vibration' in the aircraft, and immediately turned towards the closest runway. Soon thereafter the propeller separated from the airplane, and the pilot performed a forced landing without further incident. Postincident examination of the maintenance records indicated that the attachment bolts for the wooden propeller were last torqued 110 hours before the incident. The manufacturer of the propeller recommends that their wooden propellers be torque checked every 50 hours of flight. Examination revealed that the propeller attachment bolts showed signs of fatigue failure. There was also fretting damage on the propeller extension flange and bushing shanks. The above-mentioned signatures are suggestive of the studs being insufficiently torqued by the mechanic during assembly or periodic maintenance procedures not being followed, and subsequently becoming loose during propeller operation.
Probable cause
The company maintenance personnel's inadequate torquing procedures of the propeller attachment bolts which resulted in the fatigue failure of the propeller attachment bolts and the in-flight separation of the propeller.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN00IA133
- Event ID
- 20001212X21430
- Case number
- DEN00IA133
- 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: 4947ef05f39ac03343ecabdca03b30854f57d3af920a34c3dd82d3cedda7621f; retrieved 2026-09-22T12:45:21.695Z.