FIELD NOTES / SECOND WORLD WAR

Operation Overlord 1944: The Road to D-Day — Strategy, Planning, Deception & the Atlantic Wall // Log 032

General Dwight D. Eisenhower speaking with 101st Airborne paratroopers in England before D-Day, 5 June 1944

What interests me here is the gap between a strategic instruction and a force that can actually execute it. Infantry sees the beach; communications sees the headquarters and links; technical and quality work sees the dependencies and failure points. Overlord only works when all of those layers line up. That is the professional-service lens through which I read the planning, not a claim of personal experience of 1944.

D-Day was the visible edge of a much larger system. Years of coalition argument, industrial production, intelligence, deception, weather forecasting, naval planning, air superiority, engineering and logistics had to converge on one coastline and one narrow weather window.

Political and strategic context

After the United States entered the war in December 1941, the western Allies agreed that Nazi Germany had to be defeated, but they did not always agree on how quickly a direct cross-Channel assault should be attempted. American planners generally pressed for an early return to north-west Europe. British leaders, carrying the memory of 1940 and years of campaigning on several fronts, were more cautious about committing before landing craft, trained formations, air superiority and a sustainable supply system existed.

North Africa, Sicily and Italy were therefore not simply delays on the road to France. They tied down Axis forces and gave the Allies practical experience of amphibious operations, coalition command, beach logistics and large-scale joint warfare.

At Tehran in late 1943, Roosevelt, Churchill and Stalin confirmed the broad coalition commitment to a 1944 cross-Channel invasion. The Soviet Union had long demanded a major western front. Overlord became part of a wider Allied strategy in which German forces would be pressured from west, east, Italy and the air.

From COSSAC to SHAEF

In 1943 Lieutenant-General Frederick Morgan became Chief of Staff to the Supreme Allied Commander (Designate)—COSSAC. His staff developed the first workable Overlord outline before the supreme commander had even been appointed. Normandy was chosen over the shorter Pas-de-Calais crossing because it offered a combination of beaches, room for expansion, access toward Cherbourg and a German defensive picture judged more manageable than the most obvious invasion route.

When General Dwight D. Eisenhower arrived in London in January 1944, the COSSAC structure expanded into Supreme Headquarters Allied Expeditionary Force—SHAEF. Planning now shifted from a concept produced for a future commander into the operational headquarters that would launch and sustain the campaign.

Allied command structure

  • Supreme Allied Commander: General Dwight D. Eisenhower.
  • Deputy Supreme Commander: Air Chief Marshal Sir Arthur Tedder.
  • Ground forces for the assault phase: General Bernard Montgomery, commanding 21st Army Group.
  • US First Army: Lieutenant-General Omar Bradley.
  • British Second Army: Lieutenant-General Miles Dempsey, including British and Canadian formations and attached Allied troops.
  • Allied Naval Commander-in-Chief: Admiral Sir Bertram Ramsay.
  • Air Commander-in-Chief: Air Chief Marshal Sir Trafford Leigh-Mallory.
  • Strategic air component: British and American bomber commands operating within a wider strategic arrangement, with Eisenhower receiving authority necessary to support the invasion.

The important point is not the list of famous names. It is unity of effort. A five-beach assault with airborne divisions, thousands of ships and an immense air plan could not be run as separate national projects that happened to arrive in Normandy on the same morning.

Key commanders

General Dwight D. Eisenhower — Supreme Allied Commander

Eisenhower’s decisive contribution was coalition command: holding together different national priorities and accepting responsibility for the final launch decision.

General Bernard Montgomery — 21st Army Group

Montgomery expanded and reshaped the ground plan, increasing the assault from the earlier three-division concept to a broader five-beach landing supported by airborne forces on both flanks.

Field Marshal Erwin Rommel — Army Group B

Rommel drove efforts to strengthen the coast and believed Allied air power meant the invasion had to be defeated close to the beaches.

The final assault plan

US Army map of Allied D-Day assault routes into Normandy
US Army historical map showing the Allied assault routes toward Normandy. Public-domain US government work. The arrows are not the battle itself; they are the intended movement of a joint force whose real progress would depend on terrain, defenders, weather and the condition of each landing. Map source and rights information.

From west to east, US forces would land at Utah and Omaha; British forces at Gold and Sword; and Canadian forces at Juno. The US 82nd and 101st Airborne Divisions would operate behind Utah and around the Cotentin approaches. British 6th Airborne Division would secure the eastern flank around the Orne and Caen Canal and attack objectives including Merville Battery.

The immediate requirement was not to achieve every line drawn on the map by nightfall. It was to establish lodgements that could survive German counter-attack, gain exits from the coast and continue receiving troops, vehicles, ammunition and fuel faster than the defenders could mass enough combat power to destroy them.

Operation Neptune: getting the army across the water

Operation Neptune was the assault phase of Overlord. Ramsay’s naval command had to organise minesweeping, bombardment, convoy routes, assault craft, landing ships, command vessels and the follow-on shipping that would turn a beachhead into a campaign.

The fleet included warships, transports and thousands of smaller craft. The invasion could not be understood simply as five infantry divisions stepping out of landing craft. Every initial formation depended on a continuous maritime pipeline behind it.

The air plan

By mid-1944 the Allies possessed overwhelming air strength in western Europe. The air plan had several jobs: reduce the Luftwaffe’s ability to interfere, isolate the Normandy battlefield, attack railways and bridges, strike coastal positions, protect the fleet and support troops after landing.

The Transportation Plan attacked rail and communications networks across France and Belgium to slow German reinforcement. It was militarily important but also caused substantial civilian casualties. That cost belongs inside the account of Overlord rather than being treated as an unrelated tragedy.

Fortitude and Bodyguard: making Calais remain believable

Overlord was protected by the wider Bodyguard deception strategy. Fortitude South reinforced the German expectation that the Pas-de-Calais—the shortest crossing and an obvious strategic target—remained the likely location of the main invasion.

The deception used double agents, controlled radio traffic, dummy formations and the fictitious First US Army Group associated with General George Patton. The aim was more sophisticated than hiding Normandy. Allied planners wanted German commanders to continue believing that Normandy might be a diversion after the landings had begun.

The National Archives preserves messages from double agent Juan Pujol García—GARBO—feeding precisely that interpretation into the German intelligence system after D-Day.

The Atlantic Wall: strong but not one continuous wall

German coastal defences included batteries, bunkers, field positions, beach obstacles, mines and flooded areas. The term Atlantic Wall was powerful propaganda, but the defensive system varied enormously in strength, completion and troop quality from sector to sector.

Rommel accelerated mines and obstacles and wanted the assault defeated near the coast before Allied air power prevented German reserves moving freely. Field Marshal Gerd von Rundstedt, Commander-in-Chief West, favoured a more traditional operational reserve concept. The disagreement was made worse by an awkward command system in which Hitler retained influence over the release of important armoured reserves.

German command structure facing Overlord

  • OB West: Field Marshal Gerd von Rundstedt—overall German ground command in western Europe, but without clean control over every air, naval and security component.
  • Army Group B: Field Marshal Erwin Rommel—responsible for the anti-invasion battle across northern France, Belgium and the Netherlands.
  • Seventh Army: the main German army covering Normandy and Brittany.
  • Fifteenth Army: concentrated farther north around the Pas-de-Calais and Flanders—exactly the force Allied deception wanted kept away from Normandy.
  • Panzer reserves: divided between different command arrangements, with some release decisions requiring higher authority.

The contrast with SHAEF is significant. The Allies certainly had arguments and national friction, but they had built a single supreme headquarters for the operation. The German defence possessed overlapping chains and political interference that could slow reaction at the decisive moment.

Engineering the beachhead

Planners could not assume Cherbourg or another deep-water port would fall immediately or arrive intact. Artificial Mulberry harbours were therefore designed to provide sheltered unloading capacity. Breakwaters, floating roadways and pier systems were prepared in Britain and towed across the Channel.

PLUTO—Pipeline Under The Ocean—has become one of the best-known engineering stories, although its important contribution came later rather than supplying the first hours of D-Day. In the immediate phase, the critical system was less glamorous: landing ships, coasters, beach groups, engineers, trucks, dumps and traffic control.

That mundane infrastructure is what converted a tactical landing into a strategic foothold.

Intelligence and the French Resistance

Allied intelligence combined aerial photography, signals intelligence, agents, hydrographic work and detailed study of the coast. French Resistance networks provided local intelligence and later attacked railway and communications infrastructure when coded instructions activated sabotage plans.

Resistance action could delay German movement, but it carried enormous personal risk. Captured resistance members and civilians faced torture, execution and reprisals.

Weather, tide, moon and the 24-hour decision

Landing craft, engineers, airborne troops, aircraft and naval forces did not all want the same conditions. Obstacles needed to be visible at useful states of tide; airborne troops benefited from moonlight; ships and aircraft needed weather inside acceptable limits.

The invasion was planned for 5 June but severe weather forced a postponement. Group Captain James Stagg led the meteorological team advising Eisenhower. The National Archives records the intense uncertainty around forecasts for a short improvement on 6 June.

There was no perfect forecast and no risk-free choice. Postponing into the next suitable tidal period risked secrecy, morale, shipping schedules and the strain of keeping an enormous assembled force ready. Going meant committing thousands of men into weather that was only predicted to be acceptable for a limited window.

5 June: Eisenhower decides

The final decision was Eisenhower’s. He chose to launch on 6 June.

Before the outcome was known, he also wrote a short statement to be used if the invasion failed. In it he made clear that “If any blame or fault attaches”, responsibility was his. The note—mistakenly dated July 5 in his handwriting—is one of the strongest surviving documents of command accountability from the operation.

His public Order of the Day presented confidence to the force. His private failure note shows the other half of command: he understood that confidence did not remove the possibility of disaster.

Chronology: building Overlord

  • 1942: US entry into the European coalition intensifies planning for an eventual cross-Channel return.
  • 1943: COSSAC under Frederick Morgan develops the first Overlord outline; Normandy is selected.
  • Late 1943: Tehran confirms the 1944 coalition commitment.
  • January 1944: Eisenhower arrives in Britain and SHAEF takes shape.
  • Early 1944: Montgomery expands the assault plan; detailed Neptune, air, engineering and logistics planning accelerates.
  • Spring 1944: bombing and sabotage increasingly isolate the intended battlefield while Fortitude reinforces the Calais threat.
  • May 1944: troops concentrate, rehearse, waterproof vehicles, load shipping and receive sealed operational information.
  • 4 June: deteriorating weather forces the 5 June assault to be postponed.
  • 5 June: Stagg’s forecast identifies a short improvement. Eisenhower gives the final order to proceed.
  • Night 5–6 June: airborne forces depart and the invasion fleet crosses the Channel.
  • 6 June: planning hands the battle to the assault forces. Continue to Log 033 →

A service perspective: plans are systems, not slides

The temptation with Overlord is to admire the finished map. What matters more is the dependency chain behind it. If minesweepers do not clear the lanes, shipping cannot move safely. If communications fail, headquarters loses control. If beach exits stay blocked, vehicles pile up. If air interdiction fails, German reserves arrive faster. If supply stops, a successful landing becomes a stranded force.

Good planning therefore is not predicting exactly what will happen. It is identifying what must keep working when the prediction starts to fail.

Related Field Notes and products

Sources and further reading

One terminology point I keep explicit throughout: Overlord was the wider Normandy operation, Neptune was its assault phase, and D-Day was 6 June 1944.

Browse topics

    Share this