Midway · Chapter 1 of 12Choose a chapter

May 1942 · Before the battle · Chapter 01 of 12

Why Midway?

Midway was an outpost to defend, a base to capture, and a place where rival fleets might be brought to battle.

Article · Updated 18 October 2026 · Sources for this page

The struggle for Midway involved more than possession of an island. The Japanese First Air Fleet’s report, compiled after the battle, describes it as an American forward outpost protecting Hawaii, with added importance after the loss of Wake. The American defence plan expected an assault intended to capture the island and turn it into a base for operations against the Hawaiian area. M14 M26

Those records describe a Japanese assessment and an American expectation. Together they explain why a small place in a wide ocean could draw so much naval strength towards it. Air facilities, reconnaissance and the possibility of an enemy base gave the island a significance far beyond its size.

An island—and the fleet beyond it

The Japanese carrier force expected to attack Midway’s aircraft and support a landing. It also expected to be able to defeat an American carrier force that intervened. These were connected tasks: the island’s defences had to be suppressed, while the carriers retained the ability to fight at sea. M14 M06

The confidence behind that expectation is visible in the First Air Fleet report. Its account of the commander’s estimate says that a powerful American force centred on carriers was not believed to be operating nearby. It records an assumption that the operation had remained undiscovered. This is a report compiled after the battle, describing the force’s earlier assessment; it is not a surviving real-time view from every Japanese bridge. M14 M06

The plan therefore depended on more than striking power. It depended on assumptions about where the Americans were, what they knew and when they might react. An island attack and a fleet action could demand attention at the same time.

The American answer

Admiral Chester Nimitz’s Operation Plan 29-42, dated 27 May, prepared for an attack on Midway. It anticipated carrier strikes followed by a landing, and warned that American carriers discovered early might become the enemy’s principal target. Its predictions were estimates, not a transcript of Japanese orders. M26

The instructions to the American striking forces were nevertheless specific. They were to operate initially north-east of Midway and seek an advantage against Japanese carriers while those carriers’ aircraft were attacking the island. The Americans were preparing to exploit the very operation the Japanese intended to conduct. M26

Warning did not remove the need to search. Nor did knowing an attack was coming guarantee that American aircraft would find the enemy in time. Information could make an opportunity possible; ships and aircrews still had to turn it into one.

What could Nimitz afford to lose?

The plan ordered the defence of Midway and the infliction of maximum damage on the enemy. Alongside those aims it placed a restriction: the striking forces were to avoid an engagement likely to produce heavy losses among American carriers and cruisers. Preserving the fleet was part of the mission. M26

Even the force available was not yet entirely settled. The same document made Task Force 17’s availability as a unit dependent on the condition of USS Yorktown, and allowed for fresh instructions if she could not take part. A ship on a fleet list was not necessarily a ship ready to fight. M26

The headquarters record supplies the wider pressure. On 27 May, the CINCPAC running estimate described the strain of strategic defence with limited resources: Task Force 16 had rushed back from the South Pacific to meet the Midway threat and might soon be needed in the Coral Sea area again. More carriers and destroyers were needed to ease that burden. M19

Losing the American carriers would therefore have affected much more than the defence of one island. It would have reduced the forces available for the next emergency, wherever that came.

Before the outcome was known

Midway brought several questions together. Could the island hold? Could the Japanese carrier force defeat an American response? Could Nimitz damage that force without sacrificing the ships he needed for the wider war?

The answers would emerge from searches, attacks, damage control and decisions made with incomplete reports. To understand the victory—and what a Japanese victory might have meant—we first need to keep those different stakes in view.

Evidence within reach

Sources for this page

Open a note for the passage, inspection status and limits. Source records link to the available documents.

M14First Air Fleet detailed battle report

Contemporary Japanese command report · archival scan

Passage: JACAR C08030023800, PDF pp.10–11 and 14–15: Midway’s role and the commander’s estimate; selected Japanese passages

The carrier command’s reported assumptions, force organisation and the division of air attack, reconnaissance, support and supply tasks. The opening island strike, request for another attack and changing armament preparations. Hiryū’s counterattack aircraft, remaining strength and later fire emergency. Akagi, Kaga and Sōryū damage and evacuation; opening island-strike allocations.

Checked: Selected Japanese passages on PDF pp.10–11 and 14–15 visually checked for chapter 1. For chapter 4, pp.16–20 visually inspected and compared with M06’s English organisation tables; pp.21–22 inspected for context on 18 October 2026. For Midway Under Attack, PDF pp.29–33 / stamped 0031–0035 visually inspected and selected passages compared with M06; pp.23–26 sampled for context. For Search and Decision, PDF pp.32–33 / stamped 0034–0035 rechecked against M39’s chronological table. PDF pp.34–35 / stamped 0036–0037 visually inspected for The Morning Strikes; p.34 supports command transfer and Hiryū’s continued ability to attack. PDF pp.35–43 rendered and visually inspected for Hiryū Fights Back: pp.35–38 cover counterattack strength, claims and Hiryū’s bombing; pp.42–43 cover fire, propulsion failure and abandonment preparations. Intervening Akagi/Kaga passages inspected for context. PDF p.44 / stamped 0046 visually inspected for the continuation of Hiryū’s evacuation to destroyers. PDF p.18 / stamped 0020 re-rendered and visually inspected for Hiryū counterattack organisation. Ship-profile expansion: PDF pp.17, 39–42 and 44–46 rendered and visually inspected; selected damage passages compared with M06. Cruiser-profile review, 18–19 October 2026: PDF pp.32–33 / stamped 0034–0035 visually rechecked for the successive Tone No.4 reports and decisions. PDF p.45 / stamped 0047 visually rechecked on 21 October 2026 for the Isokaze profile: rescue, treatment and transfer to Hamakaze and Isokaze. The already retained scan was used; a fresh JACAR viewer request returned HTTP 403.

Limits: Working readings, not a certified full translation. The report was compiled after the battle and some tables include actual results, not just pre-battle plans. The English table’s Haruna aircraft type differs from the Japanese image; no type is assigned here. M06 transmits the same report family. Opening narrative compresses later attacks into the same paragraph. Its dates and times are not silently merged with the American chronology; message timing and flight-deck readiness require further records. Initial-contact timing differs between the narrative and M39’s chronological table; no fixed message delay is inferred. Predicted aircraft readiness is not a completed launch. Japanese counterattack target identities and claimed damage on these pages are not confirmed outcomes. Evacuation entries are not a complete personnel roll; scuttling orders and final sinking times remain distinct. Exact bomb-hit counts and the compressed Kaga/Sōryū terminal sinking passages do not settle scuttling contributions. Akagi command-transfer times differ within the report; no single minute is adopted. Sōryū evacuation: M14 PDF p.45 / stamped 0047 names Hamakaze and Isokaze (磯風); M06 renders the second as Isonami. The profile follows the original Japanese name.

View full source record →
M06The Japanese Story of the Battle of Midway

Contemporary Japanese report · postwar English translation in modern web transcription

Passage: Part I, sections 2–3: Midway-area assessment and Mobile Force commander’s estimate, English pp.2–3

The Japanese carrier command’s reported assessment of Midway and its expectation of an American response.

Checked: Selected opening passages compared with M14. Force, attack and reconnaissance tables compared with Japanese images on 18 October 2026; Haruna aircraft-type discrepancy recorded in the chapter-four audit. Opening strike and second-attack preparation passages compared with M14 PDF pp.29–33 on 18 October 2026. Part III section 1 contact and recovery passages rechecked for Search and Decision. Akagi fire and Hiryū response passages compared with selected M39 and M14 images for The Morning Strikes. HIRYU damage subsection reread for evacuation; selected fire passages compared with M14 PDF pp.42–43. AKAGI, KAGA and SORYU damage subsections reread for the ship profiles and compared with selected M14 images; this is the same report family.

Limits: The translation and Japanese scan transmit the same report, not independent accounts. Cover numbering differs: English No.6-38, Japanese No.6-37. A retrospective command account; enemy estimates and editorial additions are not accepted as established facts. Sōryū evacuation: M14 PDF p.45 / stamped 0047 names Hamakaze and Isokaze (磯風); M06 renders the second as Isonami. The profile follows the original Japanese name.

View full source record →
M26Operation Plan 29-42

Contemporary operational plan · scan and transcription

Passage: PDF pp.3–6: expected attack, Yorktown’s conditional availability, island defences and striking-force instructions

Dated force organisation and availability, anticipated attack, island defence and striking-force instructions that limited carrier risk.

Checked: PDF pp.1–6 and 9 previously inspected. For chapter 4, pp.1–6 visually rechecked on 18 October 2026, including task organisation and the distinction between Saratoga’s listing and projected availability.

Limits: Original printed page 2 is absent. Task-organisation entries and registration number differ between copies; do not silently merge them.

View full source record →
M19The CINCPAC Gray Book

Contemporary running estimate · digitised loose-page copy

Passage: 27 May entry, printed p.544 / PDF p.550: pressure on personnel, ships and competing commitments

The developing warning, first-contact reporting, incomplete intelligence, searches, competing commitments and carrier recovery after the battle.

Checked: Selected digitised pages inspected, including PDF pp.502, 505, 546, 549–550, 578, 581, 590 and 600. May warning and preparation passages visually checked on 18 October 2026. For First Contacts, PDF pp.575–577 / printed pp.569–571 visually checked; the chapter uses the 2–3 June entries on pp.569–570. PDF pp.579–583 / printed pp.573–577 visually inspected for aftermath context; the people chapter uses printed p.574. Cruiser-profile review, 18–19 October 2026: PDF p.580 / printed p.574 visually rechecked for Trout’s recovery of two prisoners on 9 June.

Limits: Not Nimitz’s personal diary. Early combat claims and estimates reflect the information then available. The entire 874-page volume has not been read. The brief prisoner entry and M45 come from the same headquarters record environment; they are not two independent survivor testimonies. The 9 June entry does not itself identify the prisoners as Mikuma survivors; that identification comes from M45.

View full source record →

Photograph

Enlarged historical photograph

Web copy resized and compressed; original framing retained. Open image file ↗