ATL90DKJ04 · 67 Flying Dutchman D1/LFD-13
67 Flying Dutchman D1/LFD-13 · Accident: airframe, component or system failure en route
From Tuscaloosa National Airport (TCL) to an unrecorded destination
Event
- NTSB case
- ATL90DKJ04
- 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
67 Flying Dutchman D1/LFD-13
- Aircraft type
- 67 Flying Dutchman D1
- 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
- N1113D
- Operator
- Richard L. Chaffin · private individual
- Onboard fatalities
- Unknown
- Route
- From Tuscaloosa National Airport (TCL), TuscaloosaTo 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
- 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
- Substantial
Cause areas
- Other maintenance personnel › Maintenance, modification, improper
Approximate · Estimated position: the centre of Tuscaloosa, AL, the place the record names. Not the accident site.
NTSB narrative
THE PILOT REPORTED THAT HE WAS AT 2000 FEET WHEN A PROPELLER BLADE SEPARATED FROM THE AIRCRAFT. A FORCED LANDING WAS MADE AFTER THE ENGINE WAS SHUT DOWN USING THE MAGNETO SWITCH. SUBSEQUENT EXAMINATION OF THE PROPELLER REVEALED THAT THE BLADES HAD BEEN SHORTENED FROM THE TYPE CERTIFICATE DATA SHEET MINIMUM OF 71.5 IN TO 65 IN. ADDITIONALLY THE PROPELLER WAS NOT RATED FOR THE 125 HP ENGINE. ITS MAXIMUM RATED HP WAS 115. THE MODIFICATION WAS DONE BY UNKNOWN MAINTENANCE PERSONNEL.
Probable cause
MAINTENANCE PERSONNEL WHO PERFORMED AN IMPROPER MODIFICATION OF THE PROPELLER BLADE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL90DKJ04
- Event ID
- 20001212X23056
- Case number
- ATL90DKJ04
- 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: 1bc594b395040430ebf2b8dc2e96175d4bcba9600cd7311a39d8407a6bccc07b; retrieved 2026-09-23T06:08:38.219Z.