FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12IA459 · SOCATA TB10

15 Jul 2012 · Pawtucket, RI, United States

Pacca Club SOCATA TB10 · Incident: powerplant system/component malfunction/failure during initial climb

From North Central State Airport (SFZ) to North Central State Airport (SFZ)

Report a problem

Event

NTSB case
ERA12IA459
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

SOCATA TB10

Aircraft type
Socata TB10
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
N189TB
Operator
Pacca Club
Onboard fatalities
Unknown
Route
From North Central State Airport (SFZ), Pawtucket, RITo North Central State Airport (SFZ), Pawtucket, RI
Aircraft age
Not recorded
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
Initial climb
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
Powerplant system/component malfunction/failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Aircraft › Aircraft propeller/rotor

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

NTSB narrative

During departure, as the airplane reached an altitude of about 800 feet above ground level, the tip of one propeller blade separated. The flight instructor returned the airplane to the runway and landed without incident. The separated blade tip was not located; however, the remaining section of propeller blade was examined, and a fracture analysis was performed. The results of the analysis revealed fatigue crack propagation, followed by a final overstress fracture. The fatigue crack origin could not be accurately determined because the pertinent portion of blade’s leading edge suffered from postfracture damage, which likely occurred during removal or shipment. This postfracture damage also precluded determination of fatigue crack growthe timing or propagation. However, the fatigue and overstress fractures were consistent with other blade tip fractures that have occurred as a result of excessive vibrations within the propeller blade, typically as a result of a propeller ground strike.

The incident airplane’s propeller blades were manufactured 32 years before the incident, and the manufacturer imposed no life limits on the blades as long as they passed the required overhaul inspections. The incident propeller blades were overhauled twice in the 3 years before the incident. The first overhaul was performed as a result of a propeller strike, and the reason for the second overhaul was not documented. At the time of the incident, the blades had accumulated 852 hours since the most recent overhaul, which occurred 18 months before the incident.

Probable cause

The in-flight separation of the propeller blade tip due to a fatigue fracture.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12IA459
Event ID
20120717X03630
Case number
ERA12IA459
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, damage. 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: fa1bba7fafb9f93dc21b2a9f81189884df6df85adf29a9a464bfc78a7e1b40dd; retrieved 2026-09-15T18:55:31.198Z.