The thing I like about a fracture surface is that it doesn’t have an opinion. The analysis has opinions, the loads have assumptions, the model has whatever I told it. The broken part just is what it is, and if you can read it, it tells you what actually happened instead of what you predicted.

A fatigue failure and an overload failure look completely different, and you can usually tell them apart by eye. Fatigue leaves a smooth, flat region, often with curved bands sweeping across it, beach marks (clamshell marks, the books call them, and that’s exactly what they look like). Each band is roughly where the crack front sat during one block of loading, left when the load changed or paused. They bow outward from a single point, and that point is the origin. Then the remaining section gets too small to carry the load and the rest goes in one event, rough and fibrous and dull, often on a slant with shear lips if the material’s ductile. That’s the overload zone. The ratio of the two areas is itself information: big fatigue zone, small overload, the part was lightly loaded and the crack ran a long way; tiny fatigue zone, huge overload, it was running near its static limit and didn’t have far to go.

Beach marks you see by eye. Striations are the same idea zoomed right in, one per cycle in the Paris regime (down toward threshold the spacing stops resolving one-to-one, so don’t count there and trust it), and you need an electron microscope, but they’re the real currency, because if you can count them and measure the spacing you read the growth rate straight off the surface and check it against your da/dN. A hand calc never gives you that.

Ductile versus brittle is the other quick read. Ductile necks and tears, shows slant shear lips. Brittle is flat and bright, sometimes chevron marks pointing like little arrows back toward the start, and it went with no plastic warning. Same alloy can do either depending on temperature and constraint, so the morphology tells you about conditions, not just material.

But the origin is the prize. Trace the beach marks back to their common centre, follow the chevrons to their point, and you arrive at where the crack started. Nine times out of ten it started at something: a fastener hole, a sharp fillet, a machining mark, a corrosion pit, an inclusion under the surface. It points straight back at a stress concentration, and it’s almost always one I either knew about and underestimated or one that wasn’t supposed to be there at all.

That’s the part the analysis didn’t give me. The model has the radius I modelled and the finish I assumed. The real part cracked from the radius it actually had, with the actual scratch, the residual stress the actual process left behind. When the origin lands somewhere my analysis said was fine, that’s a gap between my model and the world, and the fracture surface is the only thing that shows me where.

Which is why on a damage tolerance job the broken hardware closes the loop. I picked an initial flaw, a growth curve, an inspection interval, all built on assumptions about where cracks start and how fast they run. The surface checks every one: the origin tells me if my critical location was right, the striation spacing whether my growth rate was right, the final overload area what the critical crack length really was. You don’t always get the part back. When you do, read it.