ERA13LA328 · Cirrus Design Corp SR22
Appendix R Solutions Cirrus Design Corp SR22 · Accident: loss of engine power (total) en route
From Salisbury Ocean City Wicomico Regional Airport (SBY) to Hanover County Municipal Airport (OFP)
Event
- NTSB case
- ERA13LA328
- 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
- Unknown
- 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
Cirrus Design Corp SR22
- Aircraft type
- Cirrus SR22
- 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
- N223SS
- Operator
- Appendix R Solutions
- Onboard fatalities
- Unknown
- Route
- From Salisbury Ocean City Wicomico Regional Airport (SBY), Salisbury, MDTo Hanover County Municipal Airport (OFP), Hanover, VA
- Aircraft age
- About 7 years (built 2006)
- 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
- Loss of engine power (total)
- 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 power plant
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB 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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13LA328
- Event ID
- 20130721X92450
- Case number
- ERA13LA328
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2013-07-21.
- API snapshot SHA-256: d973b180120cf50a1aaf4241b469d6e72f34ac5b62131974dda49facb908b412; retrieved 2026-09-15T22:16:01.524Z.