Accident Cirrus SR22 GTS N223SS,
ASN logo
ASN Wikibase Occurrence # 157702
 
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 20 July 2013
Time:20:03
Type:Silhouette image of generic SR22 model; specific model in this crash may look slightly different    
Cirrus SR22 GTS
Owner/operator:Appendix R Solutions Inc
Registration: N223SS
MSN: 1819
Year of manufacture:2006
Total airframe hrs:1664 hours
Engine model:Continental IO-550-N
Fatalities:Fatalities: 0 / Occupants: 4
Aircraft damage: Substantial
Category:Accident
Location:Near Rollins Lane, Tappahannock, VA -   United States of America
Phase: En route
Nature:Private
Departure airport:Salisbury, MD (SBY)
Destination airport:Hanover, VA (OFP)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The pilot reported that the airplane was in cruise flight when he heard a “loud noise” come from the engine, followed by a loss of engine power. The pilot established the airplane’s best glide speed and declared an emergency with air traffic control, and an air traffic controller then provided vectors toward the nearest airport. While approaching the airport, the pilot heard another loud noise come from the engine, and oil then covered the windscreen. The pilot chose to deploy the airplane’s parachute system, and the airplane descended under the canopy until it came to rest among trees.
Examination of the engine revealed that the crankshaft top rear trailing forward counterweight retaining plate was fractured; the counterweight pin and portions of the plate were found in the crankcase and oil sump. The No. 2 connecting rod was fractured, and the crankcase exhibited significant damage concentrated at the No. 2 cylinder. A material analysis of the fractured counterweight pin revealed failure signatures consistent with overload. The hardness of the plate met manufacturer specifications, and microstructure analysis of the plate appeared normal.
About 4 years before the accident, the engine manufacturer issued a critical service bulletin (SB) “to inform operators of the possible long term effects of low engine RPM in cruise conditions.” Models affected included the accident engine make and model. The SB described two instances of sudden engine stoppage as a result of a crankshaft counterweight release. These instances were found to have been associated with engine operation at a sustained cruise rpm of less than 2,300 rpm. As a result, the manufacturer recommended that engine cruise rpm settings be no lower than 2,300 rpm. Although the engine operating manual cautioned that the minimum cruise rpm setting was 2,300 rpm, the airplane manufacturer did not include this information in the Pilot’s Operating Handbook. A review of recorded data from the accident airplane revealed that nine flights were flown in the 6 months before the accident and that, during these flights, the accident airplane was operated at or below 2,300 rpm for 20 minutes or longer. However, the investigation could not determine if the top rear trailing forward counterweight retaining plate failed due to these operations.

Probable Cause: A failure of the engine crankshaft top rear trailing forward counterweight retaining plate, which resulted in a total loss of engine power. The reason for the retaining plate’s failure could not be determined during postaccident examination.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: ERA13LA328
Status: Investigation completed
Duration:
Download report: Final report

Sources:

NTSB
https://flightaware.com/live/flight/N223SS

Location

Revision history:

Date/timeContributorUpdates
21-Jul-2013 04:30 Geno Added
21-Jul-2013 13:09 RobertMB Updated [Aircraft type, Phase, Nature, Damage, Narrative]
21-Jul-2013 13:12 RobertMB Updated [Narrative]
03-Aug-2013 11:38 RobertNB Updated [Narrative]
21-Dec-2016 19:28 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
29-Nov-2017 08:48 ASN Update Bot Updated [Operator, Other fatalities, 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