Incident Cessna 172S Skyhawk SP N427CP,
ASN logo
ASN Wikibase Occurrence # 142213
 
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:Saturday 28 January 2012
Time:17:05
Type:Silhouette image of generic C172 model; specific model in this crash may look slightly different    
Cessna 172S Skyhawk SP
Owner/operator:Civil Air Patrol
Registration: N427CP
MSN: 172S-8689
Total airframe hrs:1807 hours
Engine model:Lycoming IO-360 SER
Fatalities:Fatalities: 0 / Occupants: 1
Aircraft damage: None
Category:Incident
Location:Jackson-Evers Airport, Jackson, MS -   United States of America
Phase: En route
Nature:Unknown
Departure airport:Jackson, MS (JAN/KJAN)
Destination airport:Jackson-Hawkins Field, MS (HKS/KHKS)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
According to the pilot, he conducted a thorough preflight inspection of the airplane with no anomalies noted. Then, when the airplane was at an altitude of 7,000 feet mean sea level, an extreme vibration began. The pilot reduced engine power, verified the airplane’s flight controls were still operational, and declared an emergency with the air traffic controller that he was in contact with. As the vibration continued, the pilot elected to shut down the engine and, as the propeller was windmilling, the vibration continued. The pilot reduced the airspeed in order to stop the propeller rotation, then immediately obtained best glide airspeed once the propeller stopped. As soon as the propeller stopped windmilling, the vibration ceased. The pilot landed the airplane without incident and it was towed to the fixed base operator. A postincident engine teardown revealed that there were no anomalies that would have precluded normal operation. Examination of a fracture surface on one of the propeller blades revealed that the blade tip failed as a result of fatigue cracking that initiated at the leading edge of the blade. The propeller blade was inspected about 72 operating hours before the incident, as part of the airplane’s 100-hour annual inspection, and no discrepancies were noted at that time.
Probable Cause: The separation of the propeller blade tip due to fatigue cracking that initiated at the blade’s leading edge.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: ERA12IA169
Status: Investigation completed
Duration: 1 year and 2 months
Download report: Final report

Sources:

NTSB
FAA register: https://www.faa.gov/data_research/accident_incident/preliminary_data/events03/media/14_427CP.txt
http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=427CP&x=0&y=0
https://www.ntsb.gov/aviationquery/brief.aspx?ev_id=20120202X81145&key=1

Location

Revision history:

Date/timeContributorUpdates
01-Feb-2012 11:39 Geno Added
03-Feb-2012 11:23 Alpine Flight Updated [Aircraft type]
09-Feb-2012 13:02 Geno Updated [Time, Total occupants, Location, Nature, Departure airport, Destination airport, Source, Damage, Narrative]
21-Dec-2016 19:26 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
28-Nov-2017 20:17 ASN Update Bot Updated [Other fatalities, Nature, Departure airport, Destination airport, Source, Narrative]
31-May-2023 13:11 Ron Averes Updated [[Other fatalities, Nature, Departure airport, Destination airport, Source, Narrative]]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org