ERA21LA223 · Zenith Zodiac 601 XL
Zenith Zodiac 601 XL · Accident: part(s) separation from aircraft during initial climb
From Carroll County Airport (HZD) to an unrecorded destination
Event
- NTSB case
- ERA21LA223
- 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
Zenith Zodiac 601 XL
- Aircraft type
- Zenith ZODIAC 601
- 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
- N493TG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Carroll County Airport (HZD), McKenzie, TNTo not recorded
- Aircraft age
- About 16 years (built 2005)
- 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
- Initial climb
- 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
- Part(s) separation from aircraft
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot reported the initial takeoff was normal. About 300 ft above the runway, the airplane shook violently and the propeller separated from the engine. The airplane banked to the right and the student pilot lowered the nose of the airplane and landed on a grass berm. The airplane traveled off of the berm, dropped into a 3-to-4-ft depression, struck a fence, and was substantially damaged. The propeller was found about halfway between the takeoff point and where the airplane touched down on the berm. About 9 years earlier, the airplane had incurred a propeller strike that was severe enough to destroy the blades of the propeller. A replacement propeller was installed by the owner of the airplane. The airplane owner, who was not the original builder, did not hold either a mechanic certificate or repairman certificate for the airplane. About 7 months before the accident, a propeller strike test was performed, and the cap screws were replaced in the propeller flange and flywheel. The mechanic who performed the work noted that the manufacturer’s recommended bolts did not fit, so he installed cap screws that were longer. The bolts that were installed could result in the threads bottoming out and the bolts not being able to be torqued correctly. Postaccident examination of the cap screws indicated they fractured from fatigue cracking that initiated along the thread roots where the nuts were threaded. This fatigue initiated at multiple sites along the thread roots, where there were no indications of material or mechanical defects. This also suggested that the cap screws were able to flex or move, allowing fatigue crack propagation. Once the fatigue crack had progressed about halfway through a cap screw cross section, the remainder of the material would fracture from overstress (likely in bending). Without the cap screws to affix the propeller assembly to the engine, the hub would be able to separate. Examination also revealed that no thread locking adhesive was present on the cap screw threads as required by the manufacturer. The lack of a thread locking adhesive alone did not necessarily account for the lack of torque or clamping force on the cap screws. The fatigue pattern suggested a lack of preload, which may have developed during service as the nut backed off slightly or an indication of over-torquing at installation. If properly installed, the application of a thread locking adhesive to the cap screws would have helped keep the parts in place, reducing the chance of this type of fatigue cracking occurring (assuming the bolts had been torqued to an acceptable preload).
Probable cause
The improper installation and inspection of the propeller, which resulted in an in-flight separation of the propeller assembly.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA21LA223
- Event ID
- 20210521103124
- Case number
- ERA21LA223
- 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: 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: 6d69378dbd72ac572c0b3d14132c440a6e3bfa91aeb2ae168341cc897fe0529d; retrieved 2026-09-16T14:04:29.387Z.