Amphibious buildup

Why is an amphibious landing decided less by the size of the fleet than by the width of the beach?

Picture the fleet: hundreds of ships, a whole army embarked, more combat power in one place than the defender has anywhere. Now ask the awkward question. On the morning of the landing, how much of that army is ashore?

Almost none of it. That gap between what is committed and what is present is where amphibious operations are decided — which is why planners argue about hydrography and beach exits rather than about how many divisions are on the ships.

Begin with what the fleet can and cannot do. It can deliver a total. It cannot deliver a rate beyond what the shore will absorb, because everything must pass through a small number of landing points, each discharging so many tons an hour, for whatever hours tide, light and weather allow. Ships waiting offshore contribute exactly nothing to the fight until they are discharged. So adding ships past the shore's capacity adds congestion, not combat power — the shore is a fixed-capacity node with a queue behind it.

And it is worse than the beach itself. The narrowest point is often the exit: the roads and tracks leading inland off the sand. A beach that can land a great deal onto a strip with two exits will simply fill up, because stores and vehicles accumulate faster than they can be cleared, and a jammed beach discharges slower than an empty one.

Now the other side. The defender is also building up at the lodgement, over roads and railways — which move formations far faster than landing craft, work at night, and start closer.

So the operation is not "can we get ashore". It is a race between two rates. The attacker wins if, at every hour, what he has ashore exceeds what the defender has managed to bring against it. Lose that inequality once and the lodgement can be crushed while most of the army is still afloat, watching.

Put illustrative numbers on it to see how tight the arithmetic is. Suppose the beaches pass the equivalent of one battalion an hour, and the defender's road network can deliver one every twenty minutes — three times as fast. Then the attacker must keep the defender's movement suppressed for two hours in every three merely to hold level, before he gains an inch. Those figures are invented to show the shape, not measured. But the shape is the point: the attacker's problem is not force but rate, and the rate is set by geography he cannot change.

Which tells us exactly what the levers must be, and there are only two kinds.

Raise your own rate: capture a working port, or bring a harbour with you, as the artificial harbours towed to Normandy show. Land across more beaches at once — which is why frontage, not fleet size, is the planning currency.

Or suppress the defender's rate. Cut the bridges and rail junctions so his movement takes days instead of hours; make daylight movement costly so he only travels at night; land troops inland to hold the crossings his reserves must use. And — the subtlest one — make him uncertain where the main effort is, so his operational reserves are held rather than committed. Its neighbour Strategic deception is usually discussed as fooling an intelligence staff; its operational payoff here is measured in hours of delayed reserve release. Deception is a rate-suppression instrument.

Here is the falsification test. If a landing is decided by the ratio of build-up rates rather than the ratio of committed forces, then outcomes should track throughput and interdiction, and a lodgement should be containable even where the attacker holds overwhelming total superiority — as at Anzio, where getting ashore was easy and the lodgement was then sealed off, because the defender's build-up beat the beachhead's. The refuting observation would be a lodgement lost while leading the build-up race at every hour, or held while losing it.

Two refinements are worth making explicit.

The first is a boundary with its neighbour. Military logistics is about a supply radius: transport consumes what it carries, so past a certain distance a convoy arrives empty and more convoys do not help. This piece is about throughput at a fixed node: distance is short, but capacity per hour is capped, and more shipping does not help. Both are limits that more effort cannot buy off, and they are different limits — one set by distance, one set by geography at a point. An amphibious force meets the second on the beach and the first as soon as it moves inland.

The second is that the race does not end when the lodgement is secure. It ends when the attacker can supply an advance, which usually needs a port — which is why the operational objective of a landing is so often a harbour, why defenders demolish them, and why a follow-on stalls even after the landing succeeded.

The honest limits: this is a framework, not an equation. Real discharge rates depend on sea state, tidal range, gradient, soil bearing strength and the state of the defences, and weather can shut a beach entirely, which the tidy arithmetic above hides. Published figures for how much a given beach passed in a given day come mostly from post-hoc official histories written by the services whose planning is being assessed, so I have used no real ones. And the build-up race is a rationalisation applied afterwards more often than a calculation made beforehand; how consciously any particular commander was optimising it is a fair historical argument.

• Why capturing a port intact is so rarely achieved, and what that implies for planning to do without one.
• How airborne landings inland are best understood not as an attack but as an instrument for slowing the defender's clock.

Every term the collection defines is gathered in the glossary.