HardThrasher
Published 25 Dec 2025Hello my little Christmas puddings; today’s film covers the strategic bombing forces in WW2, what they did to support Operation Overlord, the aerial war across France and into Germany during 1944, taking out enemy formations, V1 and V2 sites, and breaking up the Nazi oil fields in the process. But all did not go according to plan … this is the inbetweeny bit from June – December 1944 and the part everyone forgets before the Bulge, Dresden and all that …
00:00:00 – Introduction
00:01:12 – A Word From Our Sponsor
00:03:25 – A Few Notes For New Viewers
00:04:02 – How End A War
00:06:25 – A 90 second (well 6 minutes) Recap of the story so far
00:12:15 – On With The Show
00:18:40 – The Key Players
00:20:10 – Enter Trafford Leigh-Mallory
00:24:05 – Trafford in Charge At the AEAF
00:26:15 – The Strategic Bombers Role In D-Day
00:27:29 – The Bombers As Part Of The Deception Plans
00:28:18 – Cutting Off Normandy
00:29:41 – The V1s, Poison Gas and Biological Warfare
00:37:31 – The One True Raid To End The War
00:41:50 – Self Harm in Normandy (It’s Trafford Time Again)
00:52:04 – Focus On Oil – Why, How and What Happened in 1944
01:05:00 – And on to Dresden
01:05:25 – Survivor’s Club
(more…)
December 26, 2025
Allied Bombing 1944 – Distraction and Destruction before Dresden
November 30, 2025
North Africa Ep. 10: Rommel’s Desert Cannae – The Trap at Mechili
World War Two
Published 29 Nov 2025This episode, Rommel sets up a “Cannae, modern style” at Mechili, a three-pronged encirclement with Wechmar pressing from the west, Schwerin/Ariete and MG 8 driving up from the south, and Olbrich’s panzers meant to close the center. A Ghibli, fuel chaos and delays upset the timing, but Ponath cuts the Derna road and captures Generals Neame and O’Connor. And after failed breakout attempts against Fabris, the Bersaglieri and Streich, Gambier-Parry surrenders about 1,700 men and Mechili falls, opening the road to Tobruk.
(more…)
November 23, 2025
North Africa Ep. 9: Rommel tightens the Noose around Cyrenaica
World War Two
Published 22 Nov 2025April 1941, North Africa. The British forward line at Mersa Brega has collapsed, 2nd Armoured Division is in retreat, and Erwin Rommel’s Afrika Korps is on the move. What was supposed to be a cautious blocking force has turned into a fast-moving desert offensive threatening Benghazi, Mechili, and all of Cyrenaica.
In this episode of our WW2 in Real Time – North Africa miniseries, we follow:
- Rommel as he ignores Hitler’s orders and pushes east after Mersa Brega
- The chaotic British retreat and fuel-starved tanks abandoning the desert
- The fall of Benghazi without a fight
- Wavell’s misjudgements and late reactions from Middle East Command
- The race for Mechili, a vital crossroads and supply dump
- The brutal reality of desert logistics – where sand and distance destroy more vehicles than enemy shells
While Rommel drives his reconnaissance units toward Benghazi and Mechili, British commanders try to trade ground for time and avoid encirclement. At the same time, Italian commanders warn Rommel about overstretch, and German divisional leaders complain about fuel and breakdowns – warnings he largely ignores.
By the end of this week in 1941, the Desert Fox is deep inside Cyrenaica, the British are burning their own supply dumps, and both sides are racing for the next key position. A clash at Mechili is imminent – and so is a showdown at the Er Regima pass with the “Devil’s Own” Australians waiting in ambush.
This is Episode 9 of our North Africa 1941 miniseries – part of our larger effort to cover WW2 week by week, in real time.
If you want to support this work and get deeper into the war in the desert and beyond, join the TimeGhost Army at timeghost.tv or patreon.com.
Excelsior!
November 11, 2025
QotD: Moltke the Younger and the Schlieffen Plan
Helmuth von Moltke the Younger is a difficult character to uncover, but one essential to understanding the panoply of forces that produced WWI.1 Moltke died in 1916, providing him little opportunity to defend his tenure. His widow had intended to publish an exculpatory collection of evidence of the chaos of German war planning before 1914. However, by then it was 1919, and the documents were deemed harmful to Germany’s attempt to avoid the blame for the war and so not published. This would prove fateful; the documents would be destroyed in World War II.
Moltke therefore proved an ideal scapegoat for the “Schlieffen School”. For the Schlieffen School (mostly officers trained by Schlieffen), the Schlieffen Plan was a true recipe for victory bungled by incompetent execution. However, recent scholarship has shown a more nuanced picture. While Schlieffen did not fully approve of his successor, Moltke was a faithful student of Schlieffen’s concepts. The modifications he made to the plan were not because of a difference in opinion, but of circumstance. Following Schlieffen’s retirement, the French army became more aggressive, necessitating a stronger defense of the Rhine. Likewise, Russian strength and mobilization speed increased, necessitating a greater force allocated to the East. Moltke was also more realistic about the logistical limitations of the all-important right wing of the German offensive. While Schlieffen (allegedly with his dying breath) insisted “keep the right wing strong”, there were simply only so many divisions that could practically advance there. Moltke did his best to adapt the Schlieffen Plan to these changing circumstances, though with mounting fear that the strength of the Entente had placed victory beyond Germany’s strength.
Despite awareness of the long odds, officers continued to press for preventative war in succeeding European crises.3 The term “preventative war” did not mean “preempting the attack of hostile powers” but rather to initiate a war while the strategic balance was most favorable for Germany. While, as mentioned, they had their doubts about the surety of victory, they believed the odds would only get worse. The Schlieffen Plan had been designed for a one-front war against France (in 1905, the year of Schlieffen’s retirement, Russia was in the throes of revolution). Though adapted in later years, the plan remained tenable only so long as Germany had the chance to defeat France before Russian mobilization was completed. As the Russian army expanded and its rail system modernized, the General Staff saw the Schlieffen Plan nearing its expiration date.
The General Staff saw no alternative to Schlieffen’s concept because of its axiomatic focus on total victory. The kind of limited victory that the Elder Moltke had settled for in his later war plans had never entered the vocabulary of the General Staff. As such, the General Staff pressed strongly for war (which it believed was inevitable) to break out before the balance of power swung further against Germany.
The only alternative to this would have been to frankly state the perilous situation in which Germany stood militarily and admit that total military victory was out of reach and German diplomacy would need to be reoriented around this fact. Not only would this course of action been antithetical to the proud traditions of the officer corps, but it would also have been viewed as unacceptably political. What’s more, the Kaiser would have likely viewed such behavior as cowardly if not outright insubordinate. Once again, the Kaiser’s power over personnel decisions meant uncomfortable topics were not broached for fear of instant dismissal.
It is not entirely unjust to accuse German leaders of cowardice or careerism in avoiding these conversations. However, they — like so many who serve under capricious or incompetent heads of state — justified their silence and continued service under the logic of harm reduction. If they resigned (or clashed with the Kaiser leading to their dismissal) they knew they would be replaced by someone more compliant. The Kaiser’s power over personnel meant they understood clearly that they had no leverage.
The Chiefs of the General Staff, for all their influence, were incentivized to focus on the areas of their exclusive responsibility. Nevertheless, the younger Moltke was not passive in his efforts for war. He resumed contact with the Austro-Hungarian General Staff, assuring it of German support should Austria choose war in a crisis. As aforementioned, when crises came to Europe (some instigated by the German foreign ministry) he pressed the chancellor and Kaiser for a preventative war. Both, to their credit, while willing to risk war, would not choose it.
Perhaps most decisively, Moltke and his deputy, Erich von Ludendorff,4 made the decision to hinge the operational plan on an attack on the Belgian city of Liège (hosting a critical rail juncture) before the neutral country could mobilize.5 This modification was made because Moltke desired to avoid violating Dutch neutrality (as Schlieffen had called for). He wisely understood Germany could afford no more enemies and that invading the Netherlands would mean increasing the distance the German right wing would have to cover to gain the French flank, decreasing the odds of success. What’s more, Moltke hoped that Dutch neutrality would allow it to act as a “windpipe” in the event of a long war and a British blockade. However, avoiding Dutch territory complicated German logistics, necessitating the swift seizure of Liège to allow the offensive to meet its strict timetables.
This was a strictly operational decision, made on technical grounds. As such, neither the chancellor nor the Kaiser were informed of this detail of the plan (operational plans were kept strictly secret, with the prior year’s being systematically burned). However, as perceptive readers may have noticed, the need for a coup de main against a neutral country before it mobilized severely limited German strategic flexibility. There was only one deployment plan for war in the West (and only one at all after 1913). In a crisis, Germany was therefore bound to attack before the Belgians manned Liège’s fortifications. Yet this all-important point-of-no-return was unknown to the Kaiser, chancellor, and foreign minister. The General Staff had effectively stripped the Kaiser and civilian leaders of their “right to be wrong”.
Thus, the General Staff had drastically increased the likelihood of war in that the point-of-no-return was kept obscured from those who would be responsible for bring Germany to the brink. As would occur in 1914 during the July Crisis, the Kaiser and his minister could not understand why Moltke was pressing so strongly for war. As historian Annika Mombauer puts it, “Only Moltke knew that every hour counted”.6 The General Staff had — intentionally or not — engineered a situation in which political leadership would have to choose war or abandon its only operational plan. While political leadership was reticent to take this step (especially without the details of the plan) contributing to Moltke’s nervous breakdown, the General Staff ultimately got the war it so desired at the next crisis Germany found itself in. If the coup de main on Liège had been devised as a ploy to force political leadership to engage in a preventative war, it had succeeded.
Ultimately, the predominance of the military over German policy — both foreign and domestic — created an environment in which civilian leaders like Bethmann Hollweg were sidelined, and aggressive military strategies took precedence. This imbalance of prestige, coupled with the narrow, fatalistic worldview of military leaders, contributed to Germany’s march toward war, with little room to acknowledge alternative diplomatic or strategic approaches.
Kiran Pfitzner and Secretary of Defense Rock, “The Kaiser and His Men: Civil-Military Relations in Wilhelmine Germany”, Dead Carl and You, 2024-10-02.
- Helmuth von Moltke the Elder was his uncle.
- Mombauer, Moltke, 109.
- Better known for other work.
- Mombauer, 96.
- Mombauer, 219.
- Rosinski, “Scharnhorst to Schlieffen”, 99.
October 19, 2025
North Africa Ep. 4: Quiet Week Before the Desert Storm
World War Two
Published 18 Oct 2025Late Feb–early Mar 1941: convoys from Naples build up 5th Light as MG Battalion 8 and artillery arrive; Rommel wins deployments and edges the line from Nofilia toward Arco dei Fileni. Luftwaffe raids batter Malta, mines choke Suez, RAF assets drain to Greece, and Axis forward probes tighten the noose around El Agheila while Britain improvises under strain.
(more…)
October 9, 2025
Russia’s Great Retreat 1915
The Great War
Published 9 May 2025In May 1915, the Central Powers launched one of the greatest offensive operations of the First World War. The armies of Germany and Austria-Hungary planned to smash their way through Russia lines and tip the strategic balance in their favor. The result was one of the biggest and bloodiest campaigns of the war, known today as the Great Russian Retreat.
(more…)
October 5, 2025
North Africa Episode 2: Rommel Arrives in Africa
World War Two
Published 4 Oct 2025
North Africa, February 1941. Operation Compass has shattered the Italian 10th Army, capturing over 100,000 men and pushing deep into Libya. But just as Britain celebrates its first major land victory of World War II, a new threat arrives: Erwin Rommel. Sent by Hitler to salvage the collapsing Italian front, the “Desert Fox” lands in Tripoli with orders to hold Libya — and immediately begins pushing east.
At the same time, British commanders face tough choices: should they secure North Africa, or divert their best troops to Greece as Churchill demands? With overstretched Commonwealth divisions left behind in the desert and fresh German forces arriving, a new campaign begins — one that will decide the future of the Mediterranean war.
(more…)
September 28, 2025
QotD: Pre-modern armies on friendly territory
Being on territory where the administrative apparatus is the army’s own or friendly to them can vastly simplify the logistics problems of moving through the territory. And we want to keep in mind throughout all of this that the army does not want to be stationary, it is trying to go places. Ideally, the army is attempting to move out of territory we control and into territory the enemy controls, or at least move away from our main administrative centers (cities, castles) to meet an approaching enemy army and by defeating it prohibit a siege. So our concern is not merely victualing our force but doing so while it is moving in a way that facilitates its rapid movement.
But first, we need to talk about the lay of the land. As we’ve discussed, the pre-industrial countryside is not just a uniform blanket of farms; instead settlements are “nucleated” – farms cluster in villages and villages “orbit” (in a sense) towns (which may “orbit” yet larger towns), which usually administer those villages. The road and path system that the locals themselves have created will in turn connect fields to village centers, one village to the next and all of the villages to the town. This makes everything easier on our army which is also using those roads and paths to move – even if the paths are rudimentary, without modern location-finding data, armies use paths and settlements to know where they are. The main body of the army, with its large train of wagons, supplies and troops is going to generally move along major roads (which typically connect towns with other towns) but smaller detachments can move along the pathways between smaller settlements. That means what we have access to is not a vast field of possible maneuver but a spider’s web of pathways which meet and cross at settlements.
Moving through this pathway network, in friendly territory the army can lean on the likely compliance of the local population and the local administrative apparatus, which makes everything easier. Moreover, with control of the area, the army can send out messengers and riders who move faster than the army on its direction of march, making arrangements in advance for what the army needs, drawing supplies from the populace and (maybe) making arrangements to pay them either at the time or in the future. Doing so in hostile territory is much trickier as those messengers would be vulnerable and might reveal the army’s location and direction of march, things it might really rather want to conceal. So assuming the populace and local administration are “friendly”, how do we manage the complexity of getting the food and other supplies they have into the hands of the army?
The simplest method was some form of “billeting”, in use in various forms through antiquity to the early modern, though it seems particularly prominent in the Middle Ages and the first two centuries of the early modern period. Clifford Rogers (Soldiers’ Lives through History: The Middle Ages (2007), 76-78) provides a good “standard practices” overview of the process for a medieval European army. Once drawn up the army was organized into smaller units (often called “banners” because they marched behind a banner); we’ll come back to this again when we talk about marching speeds but it also matters here. Each banner would assign one of its horsemen as a “harbinger” who would ride ahead of the army (supervised by the king or commander’s marshals), ideally a full day ahead. These harbingers (because there might be quite a few of these fellows) also acted as a limited cavalry screen. They would both designate where the army would camp next (with the marshals marking out specific encampments) and make arrangements for food and housing.
In practice “arrangements” here meant frequently that the soldiers, when they arrived the following day were quartered in the homes of the local civilians, often densely packed into small towns or farming villages. If they had the means the locals might try to provide the army a market to buy food and supplies; more often the locals who had soldiers quartered on them were often expected to feed and resupply those soldiers. Notionally this was often supposed the be compensated and notionally kings issued dire warnings against soldiers taking more than they were allowed or abusing the locals. Rogers (op. cit.) is, I think, unusually sanguine in assuming these repeated regulations meant the knights and soldiers were often restrained; in an early modern or Roman context we tend to view the same sort of repeated promulgation of the same laws to mean that abuses were common despite repeated efforts by the central government to stamp them out. In practice reimbursements seem to have often been at best incomplete, where they happened at all and abuses were common.
Certainly as we see these practices more clearly in the early modern period, having soldiers quartered on your village could be economically devastating (see Parker, op. cit. 79-81); having to feed a half-dozen soldiers for a few days plus marching provisions could easily tip a small peasant household into shortage. And we should also be pretty clear-eyed here about what it would mean for a local population to have a large body of armed men (many in the hot-headed years of their youth) functionally turned loose on an unarmed civilian population and told that they could demand to be given whatever they needed; far more disciplined and better controlled armies still left a trail of theft and rape behind them as they moved. Nevertheless, this solution was simple and so for armies with very limited administrative capacity and rulers anxious to shift the burden of military activity away from their own coffers, billeting remained an attractive solution. It was still common enough in the 1700s to have been a major complaint by British colonists in North America, the bulk of whom upon achieving their independence promptly wrote an amendment in their constitution effectively banning the practice (the third amendment for the curious).
A better option for a town or city was instead to establish a market outside the town and arrange for the army to resupply and camp there and not in the town itself, with only small groups of soldiers permitted inside the walls at any given time. Needless to say, it is typically only fortified towns that really have the bargaining power to pull this off. The provision of a market for the gathering mass of crusaders outside of Constantinople in 1097 was a key diplomatic sticking point, with Alexios Komnenos I (the Byzantine Emperor) using his control over both the market and passage over the straits to Asia Minor as bargaining chips to get concessions out of the Crusaders. Likewise towns in Roman provinces seem to have fairly regularly paid exorbitant sums to avoid having armies quartered on them, as Cicero documents in his time in Cilicia (e.g. Cic. Ad Att. 5.21), sometimes in cash and other times in kind (e.g. Plut. Luc. 29.8). It speaks to how destructive billeted soldiers could be that towns that could went to extraordinary lengths to keep even friendly armies outside of the town walls.
Armies might also rely on local contractors to provide supplies, especially if they were going to operate in the region at some length. We’ve already mentioned the Army of Flanders’ pan de munición, provided by contractors. There’s also some evidence for the use of private contractors in supporting Roman armies, though the trend in current scholarship (particularly Erdkamp but also Roth op. cit.) has tended to stress the limited and often marginal role of such contractors. Given the evidence I think Erdkamp has it right here; contractors for supplies existed in the Roman world, but were fairly small supplements to a system (detailed below) that mostly ran on taxation and requisition; most of what we see in the Roman world are just normal sutlers selling luxury foods to soldiers who want to spice up their rations.
As armies grow larger and more complex in the early modern period, we see an effort to move away from destructive “billeting”, often hindered by the weak administrative apparatus of the state and limited financial resources; armies won’t move into permanent barracks on the regular in Europe until the early 1700s. One solution was to take those market towns and their lodgings and turn them from an ad hoc response to a permanent network, as Spain did along the “Spanish Road”, a network of routes taken by Spanish troops traveling overland from the Mediterranean coast in Savoy to the Low Countries during the Eighty Years War.
The way this worked was: To avoid having their reinforcements pillage their way across their own lands or alienate key friends on the way to the Eighty Years War (1568-1648) in the Low Countries, the Spanish government established a standard system for the supply of troops en route – key market towns were designated as étapes or “staples”, standard stop-over and stockpile points. These tended to be key trade towns on the roads (indeed as I understand it étape in this sense originally meant “market town”) which already had some of the infrastructure required. These étapes would then be directed in advance of a movement of troops to stockpile provisions and prepare lodgings for a specific number of advancing soldiers and paid (in theory) in advance. Householders who incurred costs (typically lodgings, sometimes food) could present receipts (billets de logement) to their local tax collector which would count against future liability.
Yet the system here is incomplete and it is striking that when given the opportunity of setting up étapes in Spain itself the crown declined, citing the cost and administrative burden of organization. The greater diplomatic difficulties and consequent stronger bargaining position of communities on the Spanish Road may have a lot to do with the different decisions. The real impetus for the structure of the étapes on the Spanish road was diplomatic: the route was a patchwork, with some territories controlled by the Spanish crown, some by the friendly German Habsburgs and others by the various small statelets of the Holy Roman Empire, any of whom if sufficiently offended might refuse Spanish reinforcements transit (the Holy Roman Emperor could shut the whole route down himself). Consequently the disruption that Spanish troops caused on the route had to be limited for the route to be sustainable at all.
States with a bit more administrative capacity, on the other hand, generally tried to avoid billeting at all, even in regularized form. We’ll see this again when talking about army movement, but control is a key concern in campaigns. Soldiers, after all, are not automatons and so keeping an army together and moving towards a single objective is difficult. Soldiers get bored, wander off, decide to steal or break things (or people) and so on. It is easier to keep an eye on soldiers if they are all in a central camp or barracks and keeping an eye on everyone in turn makes it a lot easier to ensure that everyone shows up promptly to muster in the morning with the minimum of hassle. So if a general can, he really would want to keep everyone out of towns and villages and in a regular marching camp. Doing so demands yet more discipline because of course the soldiers would rather sleep in houses than in tents, but it has substantial advantages.
But an army that can lean on the local administrative capacity can simply demand that local administrative apparatus, whatever its form, coordinate the collection and transport of supplies (over short distances) to the army, enabling the army to camp out in a field and get its grain DoorDashed to it. Thus the Romans, when in friendly territory, for instance first identify the local government – usually a town but it could also be a tribal government in non-state regions – and then requisition food from that government, transmitting their demands in advance and letting that local administration figure out the details of getting the required food to the required place. That lets Roman armies camp in their fortified camps away from civilian centers, with attendant advantages for discipline; and indeed, Roman armies typically avoid permanent or even temporary bases in towns, instead using the threat of billeting to get the supplies they needed to stay in regular camps and later permanent forts.
While the elites who run these local systems of government could provide such requisitions themselves (and might in extremis to avoid retaliation by their superiors; the Romans interpret failure to provide requested supplies as “rebellion” and respond accordingly), in practice they’re going to pass along as much of the costs as they can to the little guy. In some cases, requisition demands are so intense we hear of towns having to buy or import grain to meet the demands of passing armies; Athens had to do this in 171 during the Third Macedonian War to avoid the wrath of Rome (Liv. 43.6.1-4). Caesar likewise relied heavily on food supplies contributed by either allied or recently defeated communities in Gaul (Caesar, BG 1.16, 1.23, 1.40, 1.37, 2.3, 3.7, 5.20, 6.44; he does this a lot) to supplement regular foraging operations. Those sources of supply in turn influence his campaigning, as Caesar is forced to move where the grain is in order to resupply (e.g. Caes. BG 1.23). And I want to be clear even these systems of requisition could mean real hardship on a population as a large army could easily eat all of the surplus grain in a province and then some.
The exact structure of that requisition could vary; in some cases it was a extraordinary tax (which is to say, it was just seized), but in many cases it was organized as a forced sale (often at below market prices) or even rebated against future tax obligations. In the Roman Empire we know that in many provinces, initially ad hoc systems of food requisition from conquered or “allied” (read: subordinated) communities were first regularized so that the demands were set at a steady amount, then monetized as military operations moved further away, until eventually being formalized as a taxation system. Thus the primary Roman tax system of the imperial period grew not out of the tax system the Romans had in Italy (which was mostly dismantled in the second century as the tremendous wealth of the provinces made it unnecessary) but as a regularization of systems of requisition and extortion meant to support armies. The Romans also took advantage of the Mediterranean (where naval transport could break the tyranny of the wagon equation) to ship food from one theater to another (so long as operations were fairly close to coastal ports); this was in the Republic coordinated by the Senate which could direct Roman officials (typically governors of some sort) or non-Italian allies in one region to obtain supplies by whatever means and send them another active military theater (Plb. 1.52.5-8, Liv. 25.15.4-5, 27.3.9, 31.19.2-4, 32.27.2, 36.3-4), in some cases even establishing transit depots which could support operations in a large naval theater (e.g. Chios, Liv. 37.27.1). In particular, grain taxed in Sicily was frequently redirected to support Roman military operations across the Mediterranean.
All of this of course assumes that the army enjoys either the use of the local administrative system or the compliance of the local population. But of course in enemy territory – which is where your army wants to go – you cannot rely on that.
Bret Devereaux, “Collections: Logistics, How Did They Do It, Part II: Foraging”, A Collection of Unmitigated Pedantry, 2022-07-29.
September 22, 2025
Dien Bien Phu: The Battle that Ended French Indochina – W2W 45
TimeGhost History
Published 21 Sept 2025The First Indochina War reaches its climax at Dien Bien Phu. In late 1953 the French parachute into the valley, build a fortress under Christian de Castries, and plan to smash the Viet Minh with artillery and air power. Võ Nguyên Giáp answers with a siege: anti-air guns on the surrounding hills, trenches creeping forward, and relentless assaults on strongpoints Beatrice, Gabrielle, and Isabelle.
After weeks of bombardment and failed resupply, the fortress collapses in May 1954. At Geneva, the great powers draw the ceasefire lines: Vietnam is divided (North–South), and the Indochina War ends.
#DienBienPhu #IndochinaWar #Vietnam #ColdWar #Geneva1954 #VoNguyenGiap #FrenchIndochina
(more…)
September 3, 2025
The Korean War Week 63: The Battle of Bloody Ridge – September 2, 1951
The Korean War by Indy Neidell
Published 2 Sep 2025The South Koreans have won their fight northeast of the Punchbowl, but not that far away the Battle of Bloody Ridge is earning its name, with casualties rising into the thousands for both sides.
Chapters
00:41 Recap
01:11 A ROK Success
01:47 Bloody Ridge
06:17 Soviet Reinforcements
07:08 Operation Strangle
11:06 Summary
11:45 Conclusion
13:37 Call to Action
(more…)
August 17, 2025
August 15, 2025
The Royal Canadian Navy should go for the GLAAM
At True North Strategic Review, Noah returns to a familiar topic when discussing the Royal Canadian Navy’s current and future needs, in this case he recommends that the RCN goes for the GLAAM:
One thing I neglected to fully discuss during that piece, and one that always comes back to me time and time again, is the Global Logistics, Aviation, Amphibious, Medical Support Platform from Davies, aka GLAAM.
This is quite funny, as I have had somewhat of a monopoly on the GLAAM subject, which is probably why it keeps coming back to me. I think I’m one of the few who ever brings it up, and probably the one who does most frequently.
Maybe that’s why it always surprises people when I don’t throw my support behind it. In fact, historically, like most larger vessel proposals, I have been fairly unsupportive of talks of acquisition. As I stated in my Support Ship post, I believe priorities are needed elsewhere, on getting more important things done, and given the River-class, subs, and CDC are a decade out, there is little pressing need for anything beyond the two JSS in the immediate term.
At least not to the point of urgency. I would rather see CPSP fully funded along with CDC before any talks of new vessels like GLAAM. I have always made that clear. That remains my overall position now.
However, in the last few months, I’ve been surprised to see just how much universal support the proposal has, both from the average online reader and those in the navy. There is a fairly broad love for GLAAM, even among those who would rather have JSS — there is always some love to be thrown its way, even as an “if only x and x allowed it” conversation piece.
And let it be known, I don’t dislike GLAAM at all. I think it’s cool. I think it’s unique and has capabilities I like. Even if it didn’t make it into my initial assessment, I focused on vessels a lot smaller like the Vard 7 313, that doesn’t mean we can’t acknowledge GLAAM and its potential.
So. What is GLAAM?
First, what is GLAAM? For those unaware, GLAAM is a proposal from Davies Shipyard for, essentially, a Multi-Functional Support Ship. One could even call it a Joint Support Ship! In fact, looking at GLAAM you can see a lot of what was originally demanded from the Joint Support Ship in its first proposals with the Afloat Logistics Support Capability (ALSC).
Of course, ALSC would evolve into the JSS project and over time drop the amphibious, RO/RO, and vast majority of HADR capabilities. Of course, that’s another conversation for another day, but a lot of GLAAM, at least to me, reminds me of that concept—and then some.
Visually and capability-wise, she is very similar to the HNLMS Karel Doorman. In fact, you could almost call them sisters. They share many design features and capabilities that take a step above the traditional Landing Platform Dock we see in other navies.
August 14, 2025
D-Day’s Flat Pack Ports OR Lord HT Gets Cross with The Fat Electrician
HardThrasher
Published 13 Aug 2025In which we use the @the_fat_electrician as an excuse to talk about the Mulberry Harbours, make a specific threat to a building in the United States and get to oogle at giant bits of floating concrete.
Primary Source – Codename Mulberry – Guy Hartcup, Pen & Sword Military. Kindle Edition 2014 (org. 1977)
(more…)
July 17, 2025
QotD: War elephants in India
… we are going to look at the place war elephants held in society through two lenses: what war elephants meant to the societies that used them and what they often mean in popular culture – as we’ll see, these are connected topics. Previously in this series, we looked at the battlefield advantages and drawbacks of war elephants; now let’s take them off of the battlefield.
This may seem a strange approach to use to end a discussion of war elephants – after all, these are war elephants – but as will soon become apparent, war elephants are almost impossible to fully understand outside of the social and political context in which they are most useful.
First, we are going to look at how elephants fit into the ancient and medieval political systems which used them as weapons of war. I want to stress very strongly here that what I am presenting is essentially the main argument of Trautmann’s Elephants and Kings (2015), not something I dreamed up. For the sake of brevity, I am leaving out a lot of detail here – but you know where to go to find the argument in full.
Last time, we introduced a problem: while awesome, war elephants were very expensive and relatively easy to counter on the battlefield. This answered the question of why the Romans and Chinese mostly ignored the elephant as a weapon-system despite having access to it, but it raised a second question: if the elephant was at best a limited weapon, why did its use persist in India? After all, if the Romans could figure out how to beat these things, surely the Indians could too!
Part of the answer, of course, is that some of the logistical problems that existed for states located at the edges of elephant’s natural range simply don’t apply to states closer to the source. Indian kings could (and did!) deploy elephants in far greater numbers than Seleucid or Roman armies could. In particular, North Indian rulers, rather than relying on long distance trade, could acquire elephants through trade relations with “forest peoples” in their own hinterland. We have reports of armies with not hundreds but thousands of elephants from, for instance, the Nanda or Maurya empires. Nevertheless, while these factors simplified elephant logistics, they hardly made the use of the animals cheap.
What Trautmann instead observes is that the rise of war elephants occurred specifically in the context of kingship in India. Indeed, elephants were associated with kingship through royal elephant hunts and domesticated elephants kept for show even before war elephants were developed. Around 1400 B.C. the chariot arrives in India, bringing with it a military aristocracy where the nobles – and the noblest of all nobles is, of course, the king – rode into battle.
(I keep finding myself recommending it, but I’ll again note – for a good rundown of the value of chariots as royal symbols more than battlefield weapons, check out chapter 2 of Lee, Waging War (2016).)
That was the context the war elephant emerged into. By the fifth century or so, the war elephant seems to be displacing the chariot as the quintessential vehicle of the warrior-aristocrat (and thus the ultimate warrior-aristocrat, the king). Interestingly, the Mahabharata (fourth century B.C., but with components that may date as early as the ninth) preserves some of this shift, with a mix of aristocrats on chariot and aristocrats on elephant. As chariots faded (they were tactically inferior to true cavalry which was arising at this time), elephants progressively became the vehicle for the important warriors.
It’s not hard to see the appeal. For the warrior-aristocrat, battle isn’t just about winning, but is also about social status and position. Put another way: why does anyone put up with warrior-aristocrats, who get to live in luxury and boss everyone around? The implicit reason (sometimes explicit) across cultures is that it is the martial prowess – typically the personal, physical combat skill – that justifies the existence of the military aristocrat. You need Sir-Better-Than-You (to use a European framing) because you need someone who has mastered a difficult combat art (mounted combat) and is very, very good at it.
The warrior-aristocrat needs to be seen being a warrior aristocrat. For this purpose the elephant (much like its chariot forerunner) is perfect. Fighting from the back of an animal is a difficult skill which requires a lot of training the common folk do not have time to do. It also requires being able to afford and maintain a very expensive military asset commoners cannot afford. And not only does it allow the warrior-aristocrat to have an out-sized impact on the battle, but it literally elevates him over his fellow men so he can be seen (and it could not have escaped anyone that this was a physical realization of his actual high status). So long as the elephant remained even moderately militarily valuable, it was a perfect vehicle for a warrior-aristocrat to display his power and prowess.
And even more so for the king. Not only can the king ride his own elephant, but with his vast resources, he can procure elephants for his retainers. What is more impressive than a warrior aristocrat who has his own elephant? A warrior-king who has hundreds or thousands of elephants and his own warrior aristocrats to mount them. The thing is, a king’s actual power derives from the perception of his power – showing off the king’s military might makes him more likely to be obeyed (in ways – like tax collection – which allow him to further enhance his military might). This isn’t just a vanity project for the king (though it is that too) – extravagant displays of royal power are a key component of remaining king (the key big-word idea here is legitimacy).
This pattern in turn becomes self-reinforcing: as kings use elephants to show off (and thus reinforce) their power, elephants become symbols of royal power all on their own. Trautmann (2015) tracks this spread, particularly in South-East Asia – as the Indian model of kingship spreads into that region, war elephants spread with it. Whereas in places where there is plenty of contact, but the institution of Indian-style kingship doesn’t spread, war elephants are used rarely, if at all.
This in turn answers another quandary: why war elephants appealed to Hellenistic (that is, the heirs of Alexander) monarchs. Macedonian monarchy was not a form of Indian kingship – it had grown up in Macedon and been influenced by exposure to the Great Kings of Persia all on its own – but it was very similar in many ways. Compatible, we might say. Macedonian monarchs did not ride elephants (they rode horses), but they did need to be seen demonstrating martial excellence before their armies, just like Indian kings. In that context, the display of wealth and royal power implied by fielding a large elephant corps could be powerful, even if the king himself didn’t ride on an elephant. This is, perhaps most vividly demonstrated with Seleucus I Nicator, who earned himself the nickname “The Elephant King” and even produced coins advertising that fact […] This tie between elephants and kings seems to have been quite strong. Trautmann (2015) notes that even within India, states without kings (oligarchies, independent tribes and cities, etc) only rarely acquired elephants and never in the same sort of numbers as kings. So even when elephants are cheaper – because they are close by – unless you need elephants as physical symbols of the power and legitimacy of the king and his warrior-aristocrats, they are largely not worth the effort to procure.
The one great exception is Carthage – by the time it was using war elephants, Carthage was a mixed republic (much like Rome), and yet employed elephants extensively. Unfortunately, we have no sense of if Carthage – like Rome – would have abandoned elephants given time. The earliest attestation we have of Carthaginian war elephants is 262 B.C. (although they would have encountered them earlier from Pyrrhus of Epirus) and Carthage is completely gone in 146 B.C. It is possible Rome simply caught Carthage in the same “trying them out” phase of elephant use Rome would undergo in the second century B.C. and that Carthage may too have largely abandoned war elephants had it not been destroyed.
Bret Devereaux, “Collections: War Elephants, Part III: Elephant Memories”, A Collection of Unmitigated Pedantry, 2019-08-09.
July 11, 2025
The 1st Canadian Infantry Division in Operation Husky, 10 July 1943
For Project 44, Nathan Kehler describes the role of the 1st Canadian Infantry Division as the western-most part of Montgomery’s 8th Army landings on the southern tip of Sicily:
In the days leading up to Operation Husky, the Canadian contingent suffered two major losses – one in leadership and one in logistics. Though the landings would ultimately succeed, these events cast a shadow over the operation before a single boot touched Sicilian soil.
The Death of General Salmon
On July 2, 1943, Major-General G.G. Salmon, commander-designate of the 1st Canadian Infantry Division for the Sicily campaign, was tragically killed when his Hudson aircraft crashed near Barnstaple, Devonshire, shortly after takeoff from Hendon Airfield. Also on board were several senior officers, including Rear-Admiral P.J. Mack, the Canadian naval force commander, and Lt.-Col. C.J. Finlay, the newly appointed senior logistics officer for the division. All were killed.
General Salmon had been hand-picked to lead Canada’s first major amphibious campaign. His death, just days before the invasion, shook the command structure. With no time to replace him formally, Major-General Guy Simonds was appointed in his place. Simonds was known for his drive, discipline, and tactical focus. The loss of Salmon meant an abrupt shift in leadership style and planning assumptions on the eve of battle.
Sinking of Canadian Troop Ships
Only days later, Canadian forces suffered another blow. Between 4–5 July, as convoys moved across the Mediterranean from North Africa toward Sicily, Axis submarines attacked Allied shipping near the Algerian coast. Three ships were torpedoed: the St. Essylt, City of Venice, and Devis.
While the first two sinkings resulted in relatively few casualties, the loss of the Devis was severe. Carrying 261 Canadian troops, the ship was hit and engulfed in fire. Fifty-two Canadians were killed, with many trapped in the holds below deck. In total, the convoy lost over 500 vehicles and 40 guns, along with critical headquarters and signals equipment. Divisional Headquarters suffered particularly heavy equipment losses, forcing last-minute improvisation in communications and command coordination.
Despite these losses, the Canadian Division adapted quickly, and the operation went forward as planned. These early setbacks, however, underscore the high cost and uncertainty of even reaching the battlefield in the Second World War.
Canadian Beaches
On 10 July 1943, the 1st Canadian Infantry Division landed in southeastern Sicily as part of Operation Husky – the Allied invasion of Europe’s “soft underbelly.” The division’s assault was split across two main beaches: “Roger” Beach to the east and “Sugar” Beach to the west of the village of Le Grotticelle. These beaches formed the right flank of the British Eighth Army’s landings.
General Simonds’ plan for the Canadians was a two-brigade front:
- The 1st Canadian Infantry Brigade would land on Roger Beach and push inland to destroy a coastal battery near Maucini, seize the Pachino airfield, and establish contact with nearby British forces around Pachino town.
- The 2nd Canadian Infantry Brigade would land on Sugar Beach, clear beach defences, support the adjacent British Special Service Brigade landing on the far left, and advance north past the Pantano Longarini marshes.
- The Special Service Brigade (British Commandos) would land west of Punta Castellazzo, eliminate enemy resistance in their zone, and cover the Canadians’ western flank from elevated ground north of the marshes.
The landings were scheduled for 2:45 a.m., with Commandos hitting the shore ten minutes earlier. Objectives were clear: knock out coastal defences, secure strategic positions, and quickly link up with Allied forces to expand the beachhead.
The Landings
Despite rough seas from a storm the day before, the landings went ahead as planned in the early hours of 10 July 1943. Just after 1:00 a.m., British Commandos began landing west of the Canadian sector, encountering only light resistance. By 1:34 a.m., the 2nd Canadian Infantry Brigade – the Seaforth Highlanders of Canada and Princess Patricia’s Canadian Light Infantry – were heading for Sugar Beach under covering fire from naval guns, including the 15-inch guns of HMS Roberts.
Navigation errors caused the Seaforth Highlanders to land to the right of the Patricias, reversing their intended order. But the heavy surf helped carry landing craft over a false beach, and both units came ashore with minimal opposition. They quickly cleared light beach obstacles and scattered Italian machine-gun posts. By 3:00 a.m., both battalions had successfully landed and were advancing inland toward their objectives.
On Roger Beach, however, the 1st Canadian Infantry Brigade faced delays. Their assault relied on DUKWs and landing craft (LCTs) arriving from Malta. When these were delayed, Brigadier Howard Graham initiated a backup plan, switching to Landing Craft Assault (LCAs). Confusion and the heavy swell caused further delay, with some units landing as late as 5:30 a.m. – nearly three hours behind schedule.
Despite the setbacks, the Hastings and Prince Edward Regiment and the Royal Canadian Regiment landed successfully. The Hastings had one reserve company land 5,000 yards off target in the Commando sector but regrouped without major issue. Both units met minimal resistance. The RCR encountered light shelling from the Maucini battery, but naval gunfire quickly silenced it.
By 6:45 a.m., all three lead brigades had secured their assigned beachheads, with support units and armour – including Shermans from the Three Rivers Regiment – beginning to land. The 48th Highlanders of Canada and The Edmonton Regiment followed their respective brigades ashore, some accompanied by pipe bands.
Opposition during the landings was light overall. Many Italian defenders withdrew as the naval bombardment and confusion of the assault overwhelmed them. However, isolated machine-gun fire and limited artillery shelling still resulted in several Canadian casualties, primarily on Roger Beach.
The pre-invasion loss of ships to enemy submarine or air attack was taken fully into account during the weeks before the convoys set out. But as with all military planning, the enemy gets a vote too.







