Dropping the Central Trilithon: a physics toy for Stonehenge's oldest cold case
Update: the model now shows stone 56 leaning, with a slider for its inclination at the moment of the fall. Gowland's 1901–02 record has the "leaning-stone" declining from 77° above horizontal in 1650 to a dangerous 61° by 1901 — that is, from 13° to 29° off vertical — while the collapse itself predates 1574, so a small lean at the fall (the default is 5°) is the sensible back-extrapolation. Two honesty notes. First, the lean is entered as scenery — 56 settling in its own deep socket — not produced by the fall: experiments with fully physical tenon joints showed the collapse transmits almost no overturning force to its partner. Second, the model quietly endorses the back-extrapolation: 56's lean moves the lintel's perch, and if you set the full 1901 angle of 29° the simulation hurls 156 about three metres past where it actually lies. The lintel's resting place prefers a nearly-upright 56 at the moment of collapse — which is just what the documentary decline implies. The stones and the archive agree, which is always worth a small celebration.
Update the second — the plan view, and the lintel's pirouette: looking at where the stones actually lie in plan, lintel 156 rests in front of stone 56, not out along 55's line of fall — which suggested it twisted as it went. Measuring Gowland's 1902 General Plan confirms it, precisely: 156's centre lies 4.5 m out along the fall direction but only 0.4 m west of 56's own centreline — dead in front of it — and its long axis bears about N27°W, roughly 72° (or, equivalently for a symmetrical slab, 108°) twisted from how it was bedded across the trilithon. Even 55b lies twisted the same sense, at about N21°W.
The mechanics of that twist fall straight out of the joint geometry. The lintel's two mortises sat about 2.4 m apart. When 55's top departed along the axis, the lintel could not keep both engagements: it had to swing like a gate, pivoting in plan on 56's tenon while 55 hauled its far end forward. That gate-swing has a hard geometric ceiling — once 55's top has travelled the full 2.4 m, the far mortise must have slipped off — which caps how long the tenons can possibly have dragged the lintel, at about 31° of 55's rotation. The model now enforces that ceiling, shows the whole thing in a small plan-view inset (drawn after Gowland's plan, with his measured position as a dashed ghost), and scores every run against the plan as well as the section: final twist against the measured 72–108°, and lateral position against "dead in front of 56."
Two consequences worth savouring. The tenon-grip knob is now over-constrained — it must satisfy the landing distance in section and the twist in plan simultaneously — and a sweet spot duly emerges: joints that slip too easily deliver the lintel untwisted; joints that grip to the geometric ceiling overspin it; only the middle of the range does both, which is the difference between a knob and a measurement. And one small prediction came free: for a gate-swing, the lintel centre's sideways offset is simply half the mortise spacing times the cosine of the twist — at the measured twist that gives 0.38 m west of 56's line. Gowland drew 0.4 m. The hypothesis didn't just accommodate the plan observation; it predicted its second coordinate.
Nobody recorded the tallest stones at Stonehenge coming down. Stone 55 of the Central Trilithon — the pair that once framed the winter-solstice sunset, and which most books will insist on calling the "Great" Trilithon (a friend who knows these stones far better than I do assures me the name properly belongs elsewhere, and I've learned not to argue with him) — fell and snapped in two at some unrecorded moment in antiquity, taking lintel 156 with it. By the time anyone drew the monument reliably, the wreckage was already lying where it lies today: 55a, 55b and the lintel sprawled across the recumbent Altar Stone, pinning it to the ground. Its partner, stone 56, leaned on alone until it was hauled upright and set in concrete in 1901.
That wreckage poses a question archaeologists still argue about: was the Altar Stone standing when the trilithon fell on it — or was it already lying flat? The Altar Stone has never been fully excavated, partly because the fallen sarsen pieces sit on top of it. So the resting positions of four stones are nearly all the evidence there is.
Which makes it a perfect problem for a physics sandbox. If every hypothesis has to end with the stones where they actually are, you can throw hypotheses at a rigid-body simulator all day and see which ones survive.
The toy
The simulation below (or [here], if the embed misbehaves) is a 2D cross-section along the solstice axis, built on the Matter.js physics engine at true scale — the uprights are 6.7 m proud of the ground, the lintel a metre-thick slab perched at over 7 m. Stone 56 doesn't fall but leans, how much is a variable to play with, as the evidence demands. Everything about stone 55 is a slider:
- how far it leaned before letting go, and how sharp the subsidence "kick" was;
- how deep its socket was — 56's was measured at a famous 2.4 m in 1901; 55's is thought to have been embarrassingly shallow, which is presumably why it's the one that fell;
- how strong the sarsen was (how hard an impact snaps it in two);
- how tenaciously the mortise-and-tenon joints dragged the lintel along before letting go;
- and, in the standing scenario, how firmly the Altar Stone was bedded.
Dashed outlines mark where the pieces lie today. After every run, a verdict card checks the outcome against them, and a "trench notebook" narrates the collapse: the base kicking out of its socket, the tenons shearing, the fracture, the strike. Three preset buttons reproduce the runs discussed below, so you don't have to take my word for any of it.
What the model says
The lazy expectation is that one scenario matches and the other doesn't. That's not what happens, and the way it fails is the interesting part.
Fall onto an already-recumbent Altar Stone, and everything works on nearly the first try. With middle-of-the-road parameters, stone 55 tips, its upper end strikes the raised edge of the flat slab at around 4 m/s, and it snaps over that edge like a bar over a fulcrum — the butt end flat at about 2 m, the upper half flat at about 5 m across the altar, the lintel coming to rest on top of the pile. That is, uncannily, the arrangement in the ground.
Fall onto a standing Altar Stone, and the knock-over itself is easy — almost too easy. A ~30-tonne slab sweeping through its arc fells a half-metre-thick pillar without much argument. But here's the result I didn't see coming: the collision absorbs so much of the fall's energy that stone 55 tends to land in one piece. The standing altar acts as a crumple zone. And an unbroken 55 contradicts the most solid fact we have — the real stone broke. To get the full observed sequence in the standing scenario (altar felled flat and 55 snapped), I have to dial the sarsen strength down to a conveniently flawed stone. Push the other way — bed the altar firmly — and you get a third outcome the ground flatly rules out: a permanent stalemate, with 55 propped against a still-standing Altar Stone like a failed game of dominoes.
So the model can't prove which history happened; with enough slider-turning, both scenarios reproduce today's arrangement, and that underdetermination is honestly the deepest lesson in it. But the two scenarios are not on equal footing:
Falling onto a recumbent Altar Stone breaks stone 55 for free — the slab's edge is exactly the anvil the fracture needs. Felling a standing Altar Stone instead cushions the fall, and the break has to be bought with an extra assumption about a weak stone.
Call it an argument from parsimony, delivered by a physics engine. It lines up with where much of the archaeology has been drifting anyway: many researchers suspect the Altar Stone was placed recumbent by design, a threshold rather than a pillar. The simulation adds a small, mechanical voice to that side of the debate: the flat-altar story needs nothing special to be true.
The Tenon Problem and an Insight
A real difficulty is that the mortise-and-tenon joints at Stonehenge were remarkably tenacious. Elsewhere on the monument we can see the evidence: stones 6 and 7 of the outer circle, one leaning out and the other in, still carried their twisted lintel until a scaffold was put up in 1881; observers at the time noted that without the joints that section would have collapsed long before. Stone 56 of the Central Trilithon itself stood for centuries at a lean of something like 12–15° after its partner and lintel had already fallen. A simple model that treats the joints as springs, or even as a clean kinematic coupling that releases after a few degrees of lean, cannot reproduce this. The joints were “sticky”; they held under conditions that look precarious to us.
What made the Central Trilithon different was almost certainly not a sudden failure of the tenons at the top, but the progressive failure of the shallow socket at the base of stone 55 — the heel being pushed or washed out. Once that footing gave way, the upright was free to rotate past the point of no return while the still-engaged joints dragged the lintel with it. Our 2-D simulations are limited because they cannot properly separate those two mechanisms: a base that can soften and release, and an upper joint that remains tenacious until the geometry finally forces it apart.
Even so, the simplified model yields two clear archaeological implications. First, trilithons fail from the base, not from the top; it is the heel coming out that allows the structure to fall. Second, the observed breakage of stone 55 is far more consistent with an already-recumbent Altar Stone acting as an impact surface than with a still-standing one. More elaborate modelling of the joints can wait; these two results are already visible.
Caveats, cheerfully admitted
This is a toy, and it wears its assumptions on its sleeve. It's 2D, so both uprights live in the same cross-section and the lintel's three-dimensional tumble is collapsed onto a plane. Fracture is a threshold on impact velocity at the contact point, not real crack mechanics; the tenon coupling — genuinely unknowable — is a parametrized "how long did the joints hang on" knob rather than simulated joinery. The stones are rigid rectangles on level ground. None of the slider ranges pretend to precision; they pretend to span the plausible, which is all a hypothesis machine needs.
The right way to read it: not "this is how it happened," but "here is the space of ways it could have happened, and notice which corner of that space doesn't need a coincidence."
Go push the stones over yourself. Start with the "already recumbent" preset, then try to make the standing scenario work without weakening the stone. That failure is the most informative thing in the whole toy.
Built with Matter.js. The trilithon geometry follows the standard published dimensions; socket depths per Gowland's 1901 excavation of stone 56. Nomenclature corrected under expert duress. All remaining errors of physics and prehistory are mine.