FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR15LA025 · Cessna 172S

26 Oct 2014 · Santa Monica, CA, United States

Justice Aviation Cessna 172S · Accident: part(s) separation from aircraft during takeoff

From Santa Monica Municipal Airport (SMO) to Santa Monica Municipal Airport (SMO)

Report a problem

Event

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

Cessna 172S

Aircraft type
Cessna 172
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
N353MV
Onboard fatalities
Unknown
Route
From Santa Monica Municipal Airport (SMO), Santa Monica, CATo Santa Monica Municipal Airport (SMO), Santa Monica, CA
Aircraft age
About 9 years (built 2005)
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
Takeoff
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
Part(s) separation from aircraft
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 propeller/rotor

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The flight instructor was conducting a local instructional flight with a pilot-receiving-instruction and one passenger on board. The flight instructor stated that, after completing a normal engine run-up and upon applying full throttle, he heard a loud "bang," followed by a violent vibration. He retarded the throttle back to idle, and the engine stopped producing power. After exiting the airplane, he found that a section of a propeller blade was missing.

Examination of the remainder of the propeller blade revealed that it had failed due to fatigue cracking that had initiated from a preexisting discontinuity (defect) in the blade material. Although the defect was probably related to the blade's initial forging, this could not be confirmed.

The propeller manufacturer had issued a service bulletin (SB) for the accident propeller model and serial number, which recommended additional inspection requirements for propellers installed in aircraft, such as the accident airplane, that are used in flight schools. The SB advised that the propeller should be inspected for cracks and surface discontinuities in the area that the failure occurred every 1,000 hours. A review of the maintenance records revealed that, at the time of the accident, the propeller was about 1,630 hours past the SB-recommended inspection interval.

The propeller owner/operator's information manual required that the entire propeller be checked for corrosion cracks and other damage at each 100-hour and annual inspection and that the propeller be overhauled every 2,000 hours. The maintenance records showed that the airplane's most recent 100-hour inspection occurred slightly more than a month before the blade separation; the surface corrosion should have been visible on the blades at that time; therefore, it is likely that the propeller was not inspected as part of this inspection. Further, at the time of the accident, the propeller was 630 hours past the 2,000-hour time between overhaul interval. If the operator had complied with the manufacturer's maintenance and inspection instructions, the fatigue cracking likely would have been detected before the propeller failure.

Probable cause

The separation of a section of a propeller blade due to fatigue cracking. Contributing to the accident was the operator’s failure to comply with the manufacturer’s maintenance and inspection instructions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR15LA025
Event ID
20141028X14906
Case number
WPR15LA025
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, coordinates. 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: 0c87cdf58b6476076fdccc991b5eb7beef654c122350d1c1a841d61181bf0921; retrieved 2026-09-16T01:53:19.902Z.