FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14IA301 · Cirrus Design Corp SR22

11 Jun 2014 · Burlington, MA, United States

East Coast Aeroclub Cirrus Design Corp SR22 · Incident: loss of engine power (total) on approach

From Laurence G Hanscom Field (BED) to Laurence G Hanscom Field (BED)

Report a problem

Event

NTSB case
ERA14IA301
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
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
N813JE
Onboard fatalities
Unknown
Route
From Laurence G Hanscom Field (BED), Bedford, MATo Laurence G Hanscom Field (BED), Bedford, MA
Aircraft age
About 6 years (built 2008)
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
Approach
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
Minor

Cause areas

  • Aircraft › Aircraft handling/service
  • Aircraft › Aircraft power plant
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The flight instructor reported that he and the pilot receiving instruction had completed a local instructional flight and were returning to the departure airport. While the airplane was about 1,700 ft mean sea level, the engine began running roughly and subsequently lost all power. The pilot receiving instruction immediately handed over the flight controls to the flight instructor. The flight instructor attempted to maneuver the airplane to a field for a forced landing but realized that the airplane would not be able to reach the field, so the pilots activated the ballistic parachute system. After the parachute deployed, the airplane touched down in an area of dense vegetation.

Postincident examination of the engine revealed that the crankshaft had fractured at the No. 2 main journal and that the camshaft had fractured between the Nos. 2 and 3 main bearing supports. The No. 2 main bearing had shifted, and fretting was present on the main bearing supports, consistent with a loss of clamping load on the crankcase, which resulted in movement of the No. 2 bearing and excessive loading on, and the ultimate failure of, the crankshaft. The nuts securing the No. 5 cylinder to its two crankcase through bolts had less torque than that specified by the engine manufacturer's installation guidance, and it is possible that the loss of clamping load on the crankcase was due to a loss of torque to the adjacent No. 5 cylinder crankcase through bolts. According to maintenance records, the No. 5 cylinder had been removed and replaced about 4 months, or 27 flight hours, before the accident. Although the logbook entry indicated that the through bolts were torqued "from each side to [the engine manufacturer's] specifications," it is likely that, while replacing the No. 5 cylinder, maintenance personnel did not properly torque the cylinder crankcase through bolts, which resulted in displacement of the No. 2 bearing and the catastrophic failure of the engine.

Probable cause

A loss of clamping load of the No. 5 cylinder crankcase through bolts due to maintenance personnel’s failure to properly torque the through bolts during recent maintenance, which resulted in displacement of the No. 2 bearing and the subsequent catastrophic engine failure.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14IA301
Event ID
20140619X25754
Case number
ERA14IA301
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. 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: 525405f73e45e4cfccf1b558499ae6d391353fde0a15e591b5979d1ed13063e8; retrieved 2026-09-16T00:06:38.223Z.