Cessna 172S accident near Santa Monica, California, October 26, 2014
On October 26, 2014 at about 6:00 pm local time, a 2005 Cessna 172S, registered N353MV, was substantially damaged in an accident during takeoff near Santa Monica, California (Santa Monica Muni airport). It was an instructional flight under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 26, 2014 · about 6:00 pm local time · cases in 2014
- Place
- Santa Monica, California · Santa Monica Muni · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 3 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172S, built 2005 · all 172Ss on the register
- Registration
- N353MV · registry record · serial 172S9908
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Part(s) separation from AC during takeoff defining event
The NTSB's findings
- cause Aircraft › Aircraft propeller/rotor › Propeller system › Propeller blade section › Failure
- cause Aircraft › Aircraft propeller/rotor › Propeller system › Propeller blade section › Fatigue/wear/corrosion
- factor Aircraft › Aircraft handling/service › Maintenance/inspections › Time limits › Not serviced/maintained
- factor Aircraft › Aircraft handling/service › Maintenance/inspections › Scheduled maint checks › Not inspected
- factor Organizational issues › Management › Policy/procedure › (general) › Operator
Flight instructor
- Certificate: airline transport pilot, flight instructor, commercial pilot
- Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
- Flight time: 13,500 hours in all; 3,500 in this make and model; 130 in the last 90 days; 40 in the last 30 days; 13,400 as pilot in command; 10,500 on instruments
- Last flight review: April 14, 2014
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: rgt
- Injury: no injuries
Dual student
- Certificate: private
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 930 hours in all; 300 in this make and model; 30 in the last 90 days; 6 in the last 30 days; 690 as pilot in command
- Last flight review: July 13, 2014
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 3,544 hours
- Last inspection: 100-hour inspection, September 23, 2014; 44 hours since
- Maximum gross weight: 2,299 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming IO-360-L2A (piston); 924 hours total
- Operator: Justice Aviation, Inc.
The flight
- Departed from: SMO Santa Monica CA at 6:00 pm
- Destination: SMO Santa Monica CA
- Flight plan: none
- Runway 21, 4,973 ft by 150 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 100° at 7 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 72°F (22°C), dew point 57°F (14°C)
- Altimeter: 29.98 inHg
- Observation at 5:51 pm from SMO
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
5 documents, released by the NTSB on May 24, 2016. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Materials Laboratory Factual Report 15-030 | PDF, 16 pages | View Download |
| 2 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 3 | Propeller Maintenance History Summary | PDF, 2 pages | View Download |
| 4 | Service Bulletin 240E | PDF, 8 pages | View Download |
| 5 | Statement of Party Representatives to NTSB Investigation | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N353MV on the register today · the tail number may have moved to another aircraft since
- Cessna 172 Skyhawk 20,695 registered today · the model family and its accident history
- Cessna 72,674 aircraft on the register
- Engine: Lycoming IO-360-L2A 2,664 aircraft carry this series today · as the NTSB recorded it
- Santa Monica Municipal · nearest airport
- Accidents and incidents in California 9,080 since 1982 · 1,093 in the last ten years
- California 28,525 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR15LA025.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.