The Battle Of Leyte Gulf

Reconstructing the Battle Of Leyte Gulf: A Practical Guide to Using Combined Fleet

The main way most people study this battle is through the Combined Fleet project and its accompanying books. You get access to translated Japanese orders, movement logs, and signal documents that aren't available anywhere else in any useful form. The site itself is a mess of outdated design, but the primary sources inside it are genuinely unmatched. I spent years cross-referencing these documents against American records before I could trust any single narrative about what actually happened. You need two things: the Combined Fleet website (combinedfleet.com) for the Japanese side and Denny's work on the American operational records. Download the PDF transcriptions of the Japanese war diaries first. They're organized by task force and date. The Leyte materials are in the October 1944 section. Start with Operations I Go 1, which is the overall plan for the Leyte operation, then move to the individual fleet action reports filed after the fact. Here is where people usually hit a wall. The Japanese documents use a mix of old and new date formats, and several key entries are missing or fragmented. I ran into this constantly when trying to trace the exact timing of Nishimura's approach through Surigao Strait. The official records say one thing, the radio intercepts say another, and the post-action reports backfill gaps with stuff that wasn't written in real time. My workaround was simple but tedious: I stopped trusting the chronologies and started building my own timeline from the raw signal intercepts instead, using NARA microfilm copies of the SIGINT reports. It added maybe six hours of work per engagement but it resolved nearly every contradiction I found.

What Beginners Miss About the Battle Of Leyte Gulf

Most casual treatments of this battle treat it as five separate engagements that happened to occur around the same time. That's wrong, and it's a fundamental misunderstanding. It was one coherent operational plan executed by multiple forces with poor communications. The Japanese high command designed it as a single trap. You can see that clearly once you stop reading American after-action reports and actually look at Operation Shō 1 from the Japanese perspective. The second thing people miss is the intelligence picture. The US had broken most Japanese naval codes by this point. However, they were not reading everything in real time, and some intercepts were simply ignored or misfiled. There was a real gap between what US intelligence knew and what fleet commanders acted on. Take the case of Kurita's Center Force. American submarines and aircraft spotted it entering the Sibuyan Sea on October 24th, but the information took hours to filter down to Halsey, and even then it was presented with varying degrees of certainty. This isn't a failure of intelligence collection. It's a failure of translation, prioritization, and chain-of-command latency. Nobody in the system understood how large that force actually was until it was nearly too late. On the Japanese side, communication breakdowns were catastrophic in a different way. Ozawa's carrier task force was ordered to run a diversionary strike that would draw Halsey north. It worked. But the signal to begin the attack was ambiguous, and several subordinate commanders interpreted their orders differently. The result was a piecemeal attack rather than a coordinated one, which is why Soemba and others have argued the diversion could have been executed more effectively if radio silence had been maintained longer.

Primary Sources and Where to Find Them

Combined Fleet remains the single best starting point for the Japanese side. The site offers scanned originals alongside typed translations for most documents. Read both. The translations sometimes smooth over terminology that matters, like the difference between shutsudō (sortie) and shuppatsu (departure), which changes how you interpret when a force actually moved versus when it was ordered to move. For American records, the National Archives holds the microfilmed copies of the Pacific Fleet war diaries and the operational reports from each task group. These are not digitized in a searchable format, so you'll need to request specific reel numbers. The Naval History and Heritage Command also has the action reports posted online, but they're incomplete. The Third Fleet war diary for October 1944 is particularly sparse around the 24th through the 26th, which coincides with exactly when the most critical decisions were being made. That gap matters. Tom Spector's site and the Dening transcription of the Imbrie reports round out the major sources. Spector's battle diagrams are the best single-visual reference you'll find for the Leyte Gulf area, though you should verify his timing data against the original logbooks. He occasionally misreads the ship logs, especially on turn times and speed changes during the Sibuyan Sea engagement.

Common Interpretive Pitfalls

The biggest one is assuming that Halsey's decision to pursue Ozawa was simply a mistake or overreach. The historical record shows he had reasonable cause to believe the carrier force was the primary threat. Japanese radio traffic suggested multiple carriers were involved, and signals intelligence pointed to a northern deployment. What Halsey did not know was that the decoy carriers were largely empty of effective air power and that Kurita's battleships were still in the Sibuyan Sea. Without that context, his move looks reckless. With it, it looks like a commander making the best decision available with incomplete information. Another frequent error is conflating the Battle of Leyte Gulf with the Battle of the Java Sea or other Pacific engagements in the narrative treatment. The scope is different. This was an operational-level engagement involving roughly 284 ships on both sides combined, over an area spanning hundreds of miles of open ocean and confined straits. The command relationships were messy. Three separate American fleet commanders were operating under vague orders from Nimitz, and the Japanese forces were divided into four task groups with limited coordination between them. The lack of a unified command structure on both sides is one reason the battle produced such contradictory accounts. There is also a persistent myth about the Yamato's gunnery performance during the battle that deserves correction. The battleship's main battery missed nearly every target it engaged during the Sibuyan Sea sortie, and not because of poor ammunition or maintenance. The firing solutions were degraded by the ship's unstable platform during high-speed maneuvering, and the range estimation methods available to her fire control teams were inadequate against fast-moving aircraft at extreme ranges. This is well-documented in the post-war US Naval Technical Mission to Japan reports, which interviewed the Yamato's fire control officers directly. The guns were fine. The system around them was not.

A Practical Research Approach

If you are trying to build your own understanding of this battle rather than reading a single narrative, here is a method that works. Start with the American operational narrative from the Third and Seventh Fleet war diaries. Then pull the Japanese action reports from Combined Fleet. Overlay them on a timeline. Mark where they agree and where they diverge. The disagreements are usually where the truth is. Japanese records tend to minimize failures and obscure intelligence losses. American records tend to overstate their own awareness and underreport confusion. Neither side is lying deliberately, but both sides are editing reality in predictable ways. The edge case that trips up most people is the timeline around the morning of October 25th at Samar. The American destroyers and escort carriers engaged the entire Center Force in what became known as the Battle off Cape Engaño's companion action. The Japanese side claims they were repulsing a massed air attack. The American side describes surface engagement. Both are partially right and partially wrong. The Japanese ships fired at aircraft throughout the morning, but by midday the remaining aircraft had mostly broken off, and the engagement that followed was primarily a surface action initiated by Taffy 3's captains when Kurita's fleet turned toward them. The confusion in the records comes from the fact that many Japanese crews continued to report aircraft contacts even after the skies had cleared, because that was their trained response protocol. I learned this the hard way while cross-referencing the USS Johnston's action report with the Japanese destroyer Amagiri's combat log. The two accounts of the same afternoon clash differ by nearly twenty minutes on timing, and the Johnston's report describes aircraft that simply were not there. The Amagiri log, which was written in the moment, corrects the record. This kind of discrepancy appears in almost every engagement during this battle. Always favor the contemporaneous record over the post-action report whenever you can find both.

Supplementary Materials

Beyond the primary sources, several secondary works are worth reading, but with caveats. Samuel Eliot Morison's history is detailed but occasionally defensive about American performance. John Prados's Combined Fleet Decoded is excellent on the intelligence side but tends to downplay the role of chance and confusion in Japanese decision-making. Mark Stille's Osprey books are solid on ship design and armament but thin on operational analysis. For someone who wants to go deeper, the US Naval War College has published several papers on Leyte that address specific tactical questions. The 2014 paper by Jon Parshall on Japanese torpedo tactics during the battle is particularly useful. It corrects a lot of common misconceptions about Type 93 torpedo performance and deployment. The Battle Of Leyte Gulf remains one of the most documented naval engagements in history, and that is partly its problem. There is more source material than any single person can reasonably process, which means contradictions are abundant and resolution requires patience. The sources exist. They just require you to do the work of putting them together rather than accepting anyone else's synthesis.