CEN23LA218 · Piper J3C 65
Piper J3C 65 · Incident: part(s) separation from aircraft during initial climb
Event
- NTSB case
- CEN23LA218
- 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
Piper J3C 65
- Aircraft type
- Piper J3
- 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
- N6384H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 77 years (built 1946)
- 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
- Minor
Cause areas
- Aircraft › Aircraft propeller/rotor
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that no anomalies were noted during the preflight inspection of the airplane. During the takeoff, about 650 ft agl, the airplane began to shake “very violently.” The pilot closed the throttle, issued an emergency transmission to the air traffic control tower, and executed a 180° turn to the left to land back on the departure runway. About halfway through turn, the pilot turned off the engine as he felt the airplane could successfully make the landing. The pilot was able to land the airplane on the runway without further incident. After the pilot exited the airplane, he noticed that about 5 inches of the outboard portion of one of the aluminum propeller blades had separated. The airplane sustained minor damage to the propeller. Postincident examination revealed features that were consistent with fatigue cracking initiating at the midpoint of the cambered face of the propeller blade. These initiation sites exhibited corrosion pits consistent with those found on the cambered face of the propeller, which had been present underneath the paint and primer. On closer examination, these pits exhibited higher amounts of chlorine than the rest of the blade surfaces. It is unclear as to the origin of the pitting corrosion, which was likely due to chlorine species. Chlorine is a common element known to cause pitting of aluminum alloys in service. Many chemicals, locales, and substances can impart chlorine (as well as sulfur, phosphorus, and alkali metals) onto metal parts. These constituents can diffuse through a variety of coatings and materials, though their effectiveness resisting potentially aggressive chemicals in this case is unknown. The propeller was overhauled on January 28, 2015, and the total time since new was listed as “unknown.” The propeller was installed on the airplane on August 18, 2015. The maintenance records did not show any overhaul work performed on the propeller since it was installed on the airplane. According to the propeller manufacturer, this propeller is to be overhauled at 2,000 hours or 72 calendar months, whichever occurs first. The Federal Aviation Administration (FAA) does not mandate that propellers be overhauled for Title 14 Code of Federal Regulations (CFR) Part 91 operations. Cracks in propellers can grow to fracture in just a few flights once started. At overhaul, the paint, primer, and any coatings would likely be removed, and the surfaces refinished. These processes would likely remove surface stress concentrators like pitting and other imperfections, along with detecting any visible cracks. With the blade being 2.5 years outside of a recommended overhaul, the chances of cracks initiating would be higher.
Probable cause
The inflight failure of the propeller blade due to fatigue cracking from corrosion pits, initiating at the midpoint of the cambered face.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23LA218
- Event ID
- 20230601192286
- Case number
- CEN23LA218
- 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, 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: c9f0fcc6fd60ef640aaccb4399c539951db47e308f56bbb322834668f203fb78; retrieved 2026-09-16T17:40:34.620Z.