A desperate Allied naval force, cobbled together from five nations, faces a Japanese invasion fleet. Their only hope for Java's survival is a combined strike, but a critical communication bottleneck threatens to doom the mission before it begins.

The Bottleneck That Slowed Every Command

This episode explores the Battle of the Java Sea, a pivotal naval engagement in World War II where a hastily assembled Allied fleet confronted the Japanese. It delves into the challenges faced by the Allied command and the factors that contributed to the battle's outcome.

Event: Battle of the Java Sea
Date: February 27-28, 1942
Location: Java Sea
Commander: Rear Admiral Karel Doorman
Allied Force: Combined Striking Force (Netherlands, US, Great Britain, Australia)

- The Dutch cruiser Java exploded from within, marking the second ship lost in minutes during the battle.
- Rear Admiral Karel Doorman commanded a multinational fleet with no shared language or unified doctrine.
- Japan's rapid advance in the Pacific had already led to the fall of Malaya, Singapore, Borneo, and Sumatra.
- The Combined Striking Force was formed to protect Java, a vital oil-producing region, from Japanese invasion.
- Allied ships like HMS Exeter and USS Houston entered the battle with significant damage or missing critical equipment like radar.

To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com.

© 2026 OBOMEDIA. All rights reserved.
This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.