Cessna 172H accident near El Monte, California, January 6, 2020
On January 6, 2020 at about 9:09 pm local time, a 1966 Cessna 172H, registered N1658F, was substantially damaged in an accident during maneuvering near El Monte, California (San Gabriel Valley airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The inflight separation of a section of a propeller blade due to a fatigue crack which resulted in a forced landing.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- January 6, 2020 · about 9:09 pm local time · cases in 2020
- Place
- El Monte, California · San Gabriel Valley · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172H, built 1966 · all 172Hs on the register
- Registration
- N1658F · registry record · serial 17255053
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that during the flight, the airplane suddenly vibrated severely followed by a sudden loss of engine power and the appearance of oil on the windscreen. The pilot noticed that the propeller was not rotating along with visible damage to the engine cowling. The pilot initiated a forced landing to a nearby airport and landed uneventfully. Postaccident examination of the airplane revealed that the engine mount was bent, and a portion of one propeller blade had separated in flight. Examination of the propeller revealed that it exhibited a fracture chordwise across the propeller approximately 12 inches outboard of the center of the propeller hub. The leading-edge area of the fracture exhibited an area of darker coloration and smoother surface texture along with fracture features consistent with progressive crack growth on the fracture surface in the area. The signatures were consistent with a fatigue fracture originating at the leading edge of the propeller
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 maneuvering defining event
The NTSB's findings
- Aircraft › Aircraft propeller/rotor › Propeller system › Propeller blade section › Fatigue/wear/corrosion
- Aircraft › Aircraft propeller/rotor › Propeller system › Propeller blade section › Failure
Pilot
- Certificate: 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: 5,208.7 hours in all; 1,258.4 in this make and model; 159.5 in the last 90 days; 44.2 in the last 30 days; 5,064.4 as pilot in command; 4,363.8 on instruments
- Last flight review: January 30, 2018
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 9,794 hours
- Last inspection: 100-hour inspection, December 4, 2019; 33 hours since
- Maximum gross weight: 2,299 lb
- Seats: 4
- Landing gear: fixed
- Engine: Continental O-360-A4M (piston); 0 hours total
The flight
- Flight plan: none
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 77°F (25°C), dew point 25°F (-4°C)
- Altimeter: 30.23 inHg
- Observation at 9:47 pm from KEMT
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Photographs from the investigation 3 pictures from the NTSB's docket, as the NTSB released them
Photo 1 – View of the airplane and propeller.
Photo 2 - View of the propeller fracture area.
Photo 3 - View of the airplane and propeller assembly.The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
4 documents, released by the NTSB on March 21, 2022. 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 | NTSB Materials Laboratory Report | PDF, 5 pages | View Download |
| 2 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 10 pages | View Download |
| 3 | Evidence Control Form | PDF, 1 page | View Download |
| 4 | Photo Array | PDF, 3 pages · our copy | 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
- N1658F on the register today · the tail number may have moved to another aircraft since
- Cessna 172 Skyhawk 20,691 registered today · the model family and its accident history
- Cessna 72,672 aircraft on the register
- Engine: Continental O-360-A4M · as the NTSB recorded it
- San Gabriel Valley Airport · nearest airport
- Accidents and incidents in California 9,080 since 1982 · 1,094 in the last ten years
- California 28,500 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR20LA062.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.
