NTSB CAROL · Event
Event WPR18LA039
Registry · N2103T
FAA Aircraft Registry record.
Make / Model
CESSNA 172R
Year of manufacture
2004 · 13 years old at event
Engine
LYCOMING IO-360-L2A (180 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
20040322
ADS-B equipped
Yes — Mode-S A1BC55
Registrant of record
IASCO FLIGHT TRAINING INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The fatigue separation of the crankshaft due to a fatigue fracture, which resulted in a total loss of engine power and a subsequent off-airport landing and impact with a fence.
Factual narrative
On November 2, 2017, about 0930 Pacific daylight time, a Cessna 172R airplane, N2103T, was substantially damaged when it was involved in an accident near Redding, California. The flight instructor and two students were not injured. The airplane was being operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. The flight instructor reported that he told the student pilot who was flying to climb the airplane to 3,500 ft. As it approached 3,100 ft, the student began leaning the mixture. Subsequently, the engine began to sputter, followed by a loss of all power. The instructor then saw sparks emanating from the propeller area, took the flight controls, and turned back toward the departure airport. The instructor added that the student conducted the “emergency checklist” while he contacted the tower controller and maintained 100 knots. Due to fire near the propeller area and the smell of smoke in the cockpit, during short final, the instructor turned the airplane 360° to try to lose altitude; however, the airplane was still too high to safely land on the runway. Subsequently, he conducted a forced landing to a field just past the runway, during which the airplane struck a fence, which resulted in substantial damage to the left wing and firewall. Examination of the engine revealed that the crankshaft had separated at the propeller hub assembly with a portion of the crankshaft remaining in the assembly. No holes were found in the engine case. After the connecting rods were disassembled, examination revealed that the No. 1 connecting rod bearing exhibited metal smearing on its face. The No. 4 connecting rod and bearing assembly had metal shavings on it and exhibited thermal discoloration and some deformation. The other two connecting rods and bearings exhibited some thermal discoloration. Metallurgical examination further revealed that the crankshaft had fractured into two halves at the main bearing journal’s forward side. The fracture consisted of two primary mating crack faces, one of which was a circumferential crack and the other of which was a spiral through a lubrication hole to the inside of the crankshaft journal. The mating fracture surfaces of the circumferential fracture exhibited crack arrest marks, which had propagated from the spiral facture, consistent with progressive crack growth. The areas outside of the circumferential fracture exhibited features consistent with subsequent overstress fracture. The mating fracture surfaces of the spiral fracture also exhibited crack arrest marks, which originated from the inside portion of the hole wall, consistent with progressive crack growth. The lubrication hole exhibited witness marks consistent with rotational wear and crack arrest marks that originated from the inside portion of the hole wall. Maintenance records revealed that On March 15, 2016, the engine was signed off as overhauled and maintenance personnel performed a final inspection of the engine with no discrepancies identified. According to a logbook entry made the next day, the engine was overhauled to zero-time and had a previous total time of 2,754 hours. At the time of the accident the engine had accumulated a total time of 3,907.1 hours and 1,153.7 hours since the major overhaul. Two student pilots and the flight instructor were conducting a cross-country instructional flight. The instructor reported that he told the student who was flying to climb to 3,500 ft above ground level (agl). As the airplane approached 3,100 ft agl, the student began leaning the mixture. Subsequently, the engine began to sputter, followed by a loss of all power. The instructor then saw sparks near the propeller area, took the flight controls, and turned back toward the departure airport. During short final, due to fire near the propeller area and the smell of smoke in the cockpit, the instructor turned the airplane 360° to try to lose altitude; however, the airplane was still too high to safely land on the runway. Subsequently, he conducted a forced landing to a field just past the runway, during which the airplane struck a fence, which resulted in substantial damage to the wing and firewall. Examination of the engine revealed that the crankshaft had separated at the propeller hub assembly and that a portion of it remained in the assembly. No holes were found in the engine case. Metallurgical examination revealed that the crankshaft had fractured into two halves at the main bearing journal’s forward side. The fracture consisted of two primary mating crack faces, one of which was circumferential and the other of which was a spiral through a lubrication hole to the inside of the crankshaft journal. The lubrication hole exhibited crack arrest marks that originated from the inside portion of the hole wall. The mating fracture surfaces of the circumferential and spiral fractures exhibited crack arrest marks consistent with progressive crack growth due to fatigue. The areas outside of the circumferential fracture exhibited features consistent with subsequent overstress fracture. Maintenance records revealed that at the time of the accident the engine had accumulated a total time of 3,907.1 hours and 1,153.7 hours since major overhaul. Based on the evidence, it is likely that the crankshaft fractured due to a fatigue crack that had initiated at a lubrication hole on the main bearing journal and then progressed in an outward spiral direction toward the inside surface of the crankshaft journal. The fatigue crack then progressed circumferentially until the crankshaft fractured into two halves due to overstress, which resulted in a subsequent total loss of engine power and off-airport landing. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- — Aircraft-Aircraft power plant-Engine (reciprocating)-(general)-Fatigue/wear/corrosion
- — Environmental issues-Physical environment-Object/animal/substance-Fence/fence post-Not specified
Verbatim from NTSB's published report. Source file
NTSB_2017_WPR18LA039.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Just Culture in Aviation: A Metaphorical Study on Aircraft Maintenance Students
Just Culture, a sub-dimension of safety culture, has been a prominent and debated topic in aviation safety in recent years.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Performance PRISM: A Comprehensive Framework For Performance Measurement In Aircraft Maintenance
Aircraft maintenance is governed by rigorous safety requirements and high operational complexity, demanding robust performance measurement frameworks to ensure optimal maintenance practices.
Browse the full corpus — academia portal ↗