Which ship was sunk at Kentish Knock?
Only one Dutch ship was clearly destroyed in the battle itself: Wapen van Alkmaar, which blew up during the action.
Complete directory
Explore every watch point in reverse video-date order, then in timestamp order within each video.
Only one Dutch ship was clearly destroyed in the battle itself: Wapen van Alkmaar, which blew up during the action.
Kentish Knock began with a substantial Commonwealth advantage in ships, guns, sailors, and the ability to choose the terms of engagement from windward.
The battle came during a transition from bronze to iron cannon, with the wartime Commonwealth holding a practical advantage in guns and experienced crews.
On the eve of battle, De With's attempt to take Tromp's former flagship exposed how badly his authority had failed inside his own fleet.
Blake sought to split the Dutch formation because isolated ships could be boarded, captured, and denied mutual support.
The Commonwealth's heavier ships inflicted severe damage, and the Dutch position deteriorated further after darkness as ships and captains left the force.
When the wind again favoured the Commonwealth, De Ruyter and Cornelis Evertsen helped persuade De With to withdraw and covered the retreat.
Kentish Knock removed De With, recalled Tromp, prompted a Dutch heavy-ship building programme, and encouraged the Commonwealth to overestimate its strategic margin.
Tromp, De Ruyter, and Blake needed enough self-confidence to decide for thousands of sailors, but the same trait is praised after victory and mocked after defeat.
Two months after Kentish Knock, Tromp defeated Blake's reduced fleet and exposed indiscipline that pushed the Commonwealth toward stronger fighting instructions.
The famous story that Tromp hoisted a broom to show he had swept the seas lacks contemporary evidence and conflicts with period symbolism.
The squadron detached after Kentish Knock failed to unite with the ships trapped at Leghorn, allowing the Dutch to seize command of Mediterranean trade routes.
At the Gabbard, Commonwealth line tactics and ammunition depth punished Dutch attempts to board and enabled a blockade of the Dutch coast.
Portland cost the Dutch twelve ships and restored Commonwealth momentum before the Gabbard.
The Dutch attempt to break the blockade cost Tromp his life and many ships, yet damage to the Commonwealth fleet ended the blockade and pushed both states toward peace.
The Dutch remained a significant maritime state after the later Anglo-Dutch wars, but no longer occupied the very top rank among European powers.
A late question looks beyond Kentish Knock to the large ships planned as the Napoleonic Wars ended but never completed.
Violet Friend may have been technically viable with enough time and money, especially against intermediate-range missiles, but Britain chose Polaris over a land-based deterrent system.
Although HMS Blake was no longer fit for reactivation, her guns, command spaces, helicopters, and flight deck illustrate capabilities that would have been useful at San Carlos.
A modern-warship comparison shows why secondary weapons would normally be ample against wooden sailing vessels.
With the necessary fitting work, the Type 22 frigates and Type 82 destroyer were plausible platforms for the proposed surface-launched Sea Gull anti-ship missile.
A proposed British surface-to-surface missile with a very large nuclear warhead illustrates how uncertainty about enemy capabilities could justify extraordinary Cold War systems.
Kentish Knock's North Sea geography and the ten-day difference between Gregorian and Julian dating explain why the battle appears under two dates.
Commercial rivalry escalated because Dutch merchant elites preferred negotiation while England's postwar rulers were accustomed to pursuing political aims by force.
The provinces, the States General, and five regional admiralties formed an effective but difficult naval command system.
A rejected political union, Dutch convoy expansion, and a disputed flag salute carried Anglo-Dutch diplomacy into gunfire in 1652.
The war crossed the dismissal of the Rump Parliament, Cromwell's restructuring of government, and the proposed union of England and Scotland.
Replacing Tromp with the more aggressive Witte de With exposed the difficulty of commanding a fleet assembled from competing Dutch interests.
Conflicting calendars and battle names leave the action associated with Tromp's removal uncertain in the surviving accounts.
Robert Blake's short naval career and popularity with sailors explain both his later reputation and his fleet's loyalty at Kentish Knock.
De With's struggle to retain senior officers and secure a flagship made the Dutch command crisis visible before the fleets met.
De With rejected de Ruyter's advice to wait for better circumstances and committed an already divided fleet to decisive action.
The English order of battle depends partly on an obscure digitized source reached through references attached to a modern summary.
The orders of battle show a fight dominated by smaller ships and a Dutch force whose larger vessels often retained merchant-hull limitations.
A gale scattered the Dutch before Blake approached with the wind advantage against an opponent still trying to concentrate.
Light winds and dangerous shoals combined with English gunnery, disabled flagships, and sharply different responses to commanders in danger.
Darkness, ship losses, and the departure of Zeeland captains reduced the Dutch fleet, but de With and de Ruyter still covered an orderly withdrawal.
England treated a limited victory as decisive, dispersed ships toward the Mediterranean, and gave the restored Tromp room to reverse the naval balance.
The Dutch broke the English blockade at Scheveningen but lost enough ships and men to help drive the war toward peace.
The Erebus-class monitors were rapidly built at Harland and Wolff in 1915-16 as inexpensive, heavily armed ships for coastal operations.
From Erebus Class: Naval Fire Support of the WWI Western Front Long Patrol Part 8 ·
The class traded speed for two 15-inch guns whose range made it a dedicated platform for shore bombardment.
From Erebus Class: Naval Fire Support of the WWI Western Front Long Patrol Part 8 ·
Erebus combined unusually wide torpedo bulges with heavy armour, then moved from First World War bombardment into intervention and gunnery duties.
From Erebus Class: Naval Fire Support of the WWI Western Front Long Patrol Part 8 ·
Erebus's changing Second World War assignments show how a slow monitor could guard a harbour, carry supplies, and support major amphibious operations.
From Erebus Class: Naval Fire Support of the WWI Western Front Long Patrol Part 8 ·
The often-repeated claim that one of Erebus's guns armed HMS Vanguard remains uncertain, and a spare barrel is more plausible than a complete-gun transfer.
From Erebus Class: Naval Fire Support of the WWI Western Front Long Patrol Part 8 ·
German FL boats show that remotely controlled explosive craft were already being developed to attack British monitors in the First World War.
From Erebus Class: Naval Fire Support of the WWI Western Front Long Patrol Part 8 ·
At Walcheren in November 1944, Erebus helped the Anglo-Canadian force clear the approaches to Antwerp with concentrated naval gunfire support.
From Erebus Class: Naval Fire Support of the WWI Western Front Long Patrol Part 8 ·
Terror's secondary battery was repeatedly altered, showing how a 15-inch-gun monitor had to adapt to changing anti-surface and anti-aircraft demands.
From Erebus Class: Naval Fire Support of the WWI Western Front Long Patrol Part 8 ·
Erebus and Terror supported the Zeebrugge Raid, an effort to limit U-boat operations by striking the harbour infrastructure rather than submarines at sea.
From Erebus Class: Naval Fire Support of the WWI Western Front Long Patrol Part 8 ·