ASN Wikibase Occurrence # 351336
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Wednesday 8 June 2022 |
| Time: | 11:00 |
| Type: |  Beechcraft 58 Baron |
| Owner/operator: | Nea Industrial LLC |
| Registration: | N78KL |
| MSN: | TH-1578 |
| Year of manufacture: | 1990 |
| Total airframe hrs: | 2969 hours |
| Engine model: | Continental IO-550 Series |
| Fatalities: | Fatalities: 0 / Occupants: 5 |
| Aircraft damage: | Minor |
| Category: | Serious incident |
| Location: | Evansville, IN -
 United States of America
|
| Phase: | En route |
| Nature: | Private |
| Departure airport: | Paragould-Kirk Field, AR (PGR/KPGR) |
| Dayton-James Cox Dayton International Airport, OH (DAY/KDAY) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
On June 8, 2022, about 1100 central daylight time, a Beech 58 airplane, N78KL, sustained minor damage when it was involved in an incident near Evansville, Indiana. The pilot and four passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.
The airplane was about 1 hour into the cross-country flight when the pilot heard a 'boom' noise. The airframe began vibrating, and the airplane yawed to the left. The pilot contacted approach control and stated that he needed to land the airplane immediately. The pilot was directed to divert, and he landed the airplane without incident. After exiting the airplane, the pilot noticed that one of the aluminum propeller blades on the left engine had separated about midspan, resulting in minor damage. The 'boom' that the pilot heard was likely the blade separating in flight.
Examination of the fracture surface revealed signatures consistent with high-cycle fatigue failure. The fatigue origin area was coincident with an area of damage that was covered with a thick black paint. The paint had a slightly different composition than the thinner layer of black paint on the rest of the blade. No evidence indicated any repair in the area of the damage and investigators were unable to determine when the damage was painted.
Although the investigation could not determine, based on the available evidence for this incident, when the damage that led to the fracture occurred, or when the damage was painted, it is likely the damaged area was present at the airplane's most recent 100-hour inspection, which occurred 28 hours before the incident. The presence of the black paint could have made it difficult to detect the damage during the mechanic's visual inspection of the blade surface during the airplane's most recent 100-hour inspection. Had the damage been detected during the 100-hr inspection it should have triggered maintenance of the propeller blade.
The damage was also hidden but detectable during the preflight inspection conducted by the pilot before the accident flight. Had the damage been detected by the pilot, it should have triggered further examination and maintenance of the propeller blade.
Probable Cause: The failure of the propeller blade due to high-cycle fatigue that originated from damage that occurred at an unknown time. Contributing to the accident was the failure to identify the damage before the accident flight.
Accident investigation:
 |
|
Sources:
NTSB CEN22LA250
https://data.ntsb.gov/Docket?ProjectID=105266
Location
Images:
Photo: NTSB
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 01-Feb-2024 11:03 | ASN Update Bot | Added |
| 01-Feb-2024 11:08 | harro | Updated [Aircraft type, Other fatalities, Narrative] |
| 07-Feb-2024 09:42 | Captain Adam | Updated [Time, Location, Source, Narrative, Photo] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation