Alligator cracking vs block cracking: how to tell them apart

If you've stood in a lane closure trying to decide whether what's under your boots is alligator cracking or block cracking, you're not alone. Both show up as a web of cracks breaking the surface into cells, and from the window of a truck doing 40 mph they can look like the same distress. They're not, and mixing them up on a condition survey sends the wrong fix to the wrong location.
Alligator cracking is a structural problem concentrated in the wheel path. Block cracking is a surface problem that doesn't care where your tires land, and the test for telling them apart happens on the ground, not from a truck window.
Pattern, size, and location
Alligator cracking (also called fatigue cracking) forms tight, interconnected polygons, often under 2 feet across, that genuinely look like reptile skin or chicken wire. It almost always sits inside the wheel paths, because it's caused by repeated traffic loading flexing the pavement until the asphalt layer fatigues from the bottom up. Walk a travel lane with alligator cracking and you'll usually find a clean strip down the centerline and shoulder that's barely touched, with the damage stacked up right where the axles track.
Block cracking is the opposite layout. The cracks form larger, roughly rectangular blocks, commonly a foot or more on a side and sometimes several feet, and they run the full width of the lane, shoulder to shoulder, including areas that never see a wheel. That full-width pattern is the single fastest tell in the field: if the cracking doesn't respect the wheel path at all, you're looking at block cracking, not alligator cracking.
Severity matters too. Low-severity alligator cracking can look like a loose network of hairline cracks that's easy to dismiss, but it tightens fast under continued loading, and high severity means the cells are rocking and spalling, which is one step from a pothole. Block cracking tends to stay stable in shape longer. The risk there is water getting into the joints and oxidizing the binder at the edges, not the pavement losing its structure outright.
What's causing each one, and why it changes the fix
This is where fatigue cracking vs thermal cracking gets confused with block cracking, because transverse cracking is a third distress that quick visual surveys often lump in with the other two. Transverse cracks run roughly perpendicular to the centerline, show up at fairly regular intervals, and come from the asphalt binder shrinking in cold weather: a single event, not a network of cells. Block distress is closer kin to that one than to the fatigue pattern. It comes from binder aging and shrinkage over repeated thermal cycles, not from axle loads, so an old, oxidized mix with almost no traffic can still break into blocks.
Alligator cracking has nothing to do with temperature cycling. It's fatigue, plain and simple, and it tells you something about the structure underneath: either the original design was thin for the loading it's carrying, or the base has lost support, maybe from drainage that's failed. That's why alligator cracking usually points toward reconstruction, a structural overlay, or at minimum a deeper mill-and-fill, while block cracking often responds to a crack seal program, a fog seal, or a thin surface treatment that keeps water out without needing to rebuild anything.
Getting that distinction right matters more at budget time than it does on any single segment. A crew can misclassify one mile and it's a rounding error. Misclassify the pattern across a windshield survey of a whole network and you end up sending structural dollars to blocks that just needed sealing, and sealing budget to wheel paths that are already failing underneath. That's the gap a yearly, segment-by-segment read of the whole network is built to close, which is the idea behind what we're building at Road Surface Condition.
If cracking type is the detail your current survey keeps getting wrong at scale, it might be worth seeing what a network-wide pass looks like before next budget season.