ERA24LA303 · Jones LONG-EZ
Jones LONG-EZ · Accident: part(s) separation from aircraft en route
From Houma Terrebonne Airport (KHUM) to Thomasville Regional Airport (KTVI)
Event
- NTSB case
- ERA24LA303
- 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
Jones LONG-EZ
- Aircraft type
- Jones LONG-EZ
- 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
- N4JZ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Houma Terrebonne Airport (KHUM), Houma, LATo Thomasville Regional Airport (KTVI), Thomasville, GA
- 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
- 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
- Aircraft › Aircraft propeller/rotor
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that he was maneuvering around weather at 11,500 ft mean sea level (msl) when he made a rapid descent to 3,500 ft msl to remain clear of clouds. He reported that he did not exceed the airplane’s maneuvering speed during the descent, and that when the airplane reached 3,500 msl, it began to “violently shake,” followed by a total loss of engine power. The pilot made a successful forced landing to a field; however, after he landed, he noticed about three-quarters of one of the wooden propeller blades was missing and two of the engine mounts were sheared from the firewall. The pilot stated the wooden P-prop had been overhauled and had accrued about 50-60 hours since overhaul. The pilot provided photographs of the fractured propeller blade; however, the detail observed in the photographs was insufficient to determine the reason the blade failed. Additional photographs were requested; however, they were not provided by the pilot. Therefore, the reason for the blade failure could not be determined.
Probable cause
The in-flight separation of one of the wooden propeller blades for unknown reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA303
- Event ID
- 20240712194679
- Case number
- ERA24LA303
- 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, coordinates, cause areas. 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: 125d31fdcb5f13b244c4cb97f896a51dcbb93fde4c1f1574015d9cd5266a327c; retrieved 2026-09-16T19:02:06.302Z.