Midway · Chapter 10 of 12Choose a chapter

4–7 June 1942 · Pursuit and salvage · Chapter 10 of 12

Beyond the Carrier Battle

The Japanese carrier strike had been broken, but the battle was not over. There were enemy ships still at sea, aircraft still being sent out, and a damaged American carrier that might yet be saved.

Article · Updated 19 October 2026 · Sources for this page

On the night after the carrier attacks, Rear-Admiral Raymond Spruance still had decisions to make with incomplete information. Japanese surface ships remained a threat, and reports had not settled whether another carrier was nearby. He could not plan as though he already possessed the later historian’s inventory of the enemy fleet. M43

His force moved east before turning west again. The intention was to avoid a night encounter with potentially superior surface forces while remaining able to defend Midway or pursue a withdrawal. The American carriers had won a great advantage. Keeping them intact was part of exploiting it. M43

Finding the retreating ships

The following day brought a pursuit through uncertain reports. Nimitz’s account records a submarine sighting that initially raised concern about an approach to Midway, followed by information suggesting retirement. Search aircraft were sent far out, but a reported carrier force was not found. M01

Enterprise’s squadron reports describe a late strike on 5 June expecting a much more valuable target than the vessel it eventually attacked. The aircraft found no carrier; their report recorded near misses against a ship identified as a light cruiser. Some pilots then had to land on a carrier at night for the first time. A fruitless search could still demand considerable flying skill and expose crews to danger. M17

For some Japanese ships, the withdrawal had already become a struggle. In postwar interrogation, officers from the cruiser force described an emergency turn after a submarine sighting. Mogami collided with Mikuma, badly damaging Mogami’s bow. Their account places the collision before the air attacks on the retreating cruisers. It is later testimony, rather than a surviving contemporary damage log inspected for this chapter. M46

The attacks on the cruisers

American aircraft from Midway attacked on 5 June. Their reports included hit claims that cannot simply be carried into a final account of Japanese damage. Carrier aircraft attacked again on 6 June, in a sequence Nimitz’s report records as strikes from Hornet, Enterprise and Hornet. M01

The Enterprise squadron record shows how uncertainty persisted even during the attack. Aircraft searched beyond the cruisers for a reported battleship before turning back to attack the ships actually found. A report of a battleship was not proof that one was there. The search, the target finally attacked and the damage subsequently claimed are separate pieces of evidence. M17

Mikuma was lost. Mogami, although damaged, survived to reach a Japanese base and later return to Japan. That distinction is important because Nimitz’s June report credited the Americans with sinking both cruisers. Comparing it with the Japanese officers’ later account changes the result: the contemporary American summary overstated the ships destroyed. M01 M46

The pursuit also had practical limits. Worsening weather complicated operations, while destroyers were running short of fuel. The American force could not keep steaming west indefinitely without regard to the ships protecting its carriers. M01

A carrier still worth saving

Elsewhere, Yorktown remained afloat after the attacks of 4 June. Abandonment had been an emergency response to an increasing list and the loss of power. It did not mean that the crew had given up every possibility of recovering her.

The technical damage report records the tug Vireo taking the carrier in tow on 5 June. The tow made only about two knots. On 6 June a salvage party returned to a ship still leaning heavily to port, with material smouldering in the forward rag stowage. This was a damaged ship being worked on, not an empty wreck awaiting its inevitable end. M18

The destroyer Hammann came alongside to supply power and assistance. Men removed weight from the low side, pumped water and admitted water to selected spaces on the opposite side. That last measure, counterflooding, could reduce the lean by changing the balance of weight. It also added water to the ship, so a smaller list was not by itself proof that she was safer. M18

The second disaster

On 6 June, a Japanese submarine’s torpedoes reached the salvage operation. Hammann was hit and sank rapidly. Two torpedoes struck Yorktown’s starboard side. A heavy underwater explosion followed the destroyer’s sinking; the technical report tentatively attributed it to depth charges. M18

Yorktown did not immediately disappear. Her list actually decreased, but she settled deeper in the water. This is one of the clearest warnings against judging a damaged ship by her angle alone: flooding could make her look more upright while worsening her overall condition. M18

The salvage party left before dark, closing watertight openings as it withdrew. The carrier survived another night. On the morning of 7 June the list increased, and Yorktown capsized and sank. Her loss came after a separate submarine attack had interrupted a real attempt to save her. M18

Midway’s outcome therefore cannot be reduced to the few minutes in which three Japanese carriers were set on fire. Withdrawal, searching, further bombing and salvage continued to change the losses. For the men on damaged ships, in aircraft overdue to return, or waiting in the water, those later days were still part of the battle.

Evidence within reach

Sources for this page

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

M43Task Force 16 action report

Contemporary command report · modern web transcription

Passage: Serial 0144-A · paragraphs 4(h), 5 and 6: overnight movements, pursuit and fuel; modern transcription

The decision to launch, expected Japanese movement, the time required to launch and Spruance’s incomplete knowledge of carrier strength.

Checked: Heading and selected operational passages read in HyperWar and Midway 1942 transcriptions on 18 October 2026. Original page images not inspected. Later movement, search and fuel passages reread in the HyperWar transcription for Beyond the Carrier Battle. Paragraphs 4(a), 4(f), 9(k) and 9(m) reread for aircraft operation and fighter-equipment profiles.

Limits: Both web copies transmit the same report. Uses Zone plus 10, two hours ahead of Midway’s Zone plus 12. Expectations of Japanese movement are not observed tracks; retrospective statements about Japanese flight decks and a seaplane tender are not adopted as established facts.

View full source record →
M01Nimitz’s Midway action report

Contemporary command report · selected scan pages checked; earlier passages read in transcription

Passage: PDF / printed pp.17–21, paragraphs 48–63: pursuit, cruiser attacks and salvage

The broad course of the battle and the report’s explicit clock convention. Later pursuit, cruiser attacks and rescue from Yorktown.

Checked: Earlier preparation, timing and attack passages read in modern transcriptions; paragraphs 13–18, 19–25 and 27–36 rechecked on 18 October 2026. For the aftermath chapters, a 28-page scan of serial 01849 was retained and PDF / printed pp.1 and 17–21 rendered and visually inspected. Earlier chapter passages have not all been compared with these images. The report date is taken from the transcription; it is not legible on the inspected first-page image. PDF / printed p.25 visually inspected for fighter assessment, replacement groups and training. Aircraft expansion: PDF / printed pp.6–12, 23 and 25 visually inspected on 18 October 2026; night attack, scout reports, TBF/TBD operations, fighter allocations and equipment assessments. Supporting-ship update: PDF/printed pp.21–22 visually inspected for paragraphs 62–65, including the continuation of paragraph 63. Cruiser-profile review, 18–19 October 2026: PDF / printed pp.20–21 visually rechecked for 6 June attacks and the erroneous two-cruiser sinking claim.

Limits: Preliminary enemy identifications and loss estimates are not final accounting. The report uses Zone plus 12; task-force reports can use a different clock. Both web copies transmit the same report. The apparent 126 B-17 transcription error is not adopted. Early hit claims and a possible fifth carrier are not accepted as established facts. Early warning times differ from M31. The statement implying deliberately spared runways is not adopted; M32 records actual runway damage and repairs. Torpedo hits, early Sōryū damage, additional ships claimed hit and precise deck conditions are not adopted as confirmed facts. Aircraft losses are distinct from personnel losses. Its retrospective sacrifice explanation is not treated as a deliberate attack plan. Its claim that both Mogami and Mikuma sank is rejected; its preliminary personnel total is not a final casualty roll. The scan does not include the separately listed enclosures. Paragraph 74’s claimed fighter exchange ratio is not treated as a verified loss total or controlled performance comparison. Early damage and hit claims on these pages are not adopted as confirmed results. The retrospective sacrifice explanation is not an order for a planned diversion. The reported two hits on Hammann differ from the captain’s account; post-sinking explosion explanations remain tentative. Ships dispatched to assist are not all treated as having arrived.

View full source record →
M17Enterprise’s dive-bomber squadron reports

Contemporary squadron reports · third-party hosted scan extract

Passage: PDF p.6 / VB-6 printed p.6 and PDF pp.13–14 / VS-6 printed pp.5–6: attacks on 5–6 June and night recovery

Reported bomb loads, oxygen difficulties, target-allocation confusion, fighter opposition, aircraft returns and Stuart Mason’s actions. Afternoon opposition, attacking squadrons and observations of a burning carrier still underway.

Checked: PDF pp.2–4 and 10 rendered and visually inspected on 18 October 2026. Forwarding heading previously inspected; full 15-page research copy retained. PDF p.5 rendered and visually inspected for the afternoon attack and withdrawal. PDF pp.6 and 13–15 rendered and visually inspected for 5–6 June operations and personnel accounting. PDF pp.2 and 9 re-rendered and visually inspected for aircraft variants, in-commission counts and morning loads. Cruiser-profile review, 18–19 October 2026: PDF pp.13–14 visually rechecked; p.13 supplies 5 June context, while p.14 / VS-6 printed p.6 supplies the 6 June afternoon sortie used in the profile.

Limits: VB-6 printed page 3 is absent between printed pp.2 and 4. Carrier identities, hit estimates and aircraft identifications are contemporary claims, not confirmed results. Aircraft returning, crews rescued and crews unaccounted for are distinct report-date categories. Times are not silently combined with the island or Japanese clocks. Not the separate Enterprise ship action report. The roster headed 2 June contains later loss/rescue annotations, not pre-battle knowledge; a missing entry is not proof of the circumstances of death. The 5 June cruiser in the VS-6 narrative is not identified here as Mogami or Mikuma. The 6 June target classifications and hit claims are not individually mapped to confirmed ships.

View full source record →
M46Japanese cruiser officers on the Midway withdrawal

Postwar interrogation · modern transcription

Passage: NAV 66 / USSBS 295 · collision, retirement and cruiser-loss passages; postwar interrogation transcription

The collision of Mogami and Mikuma and their different eventual fates.

Checked: Relevant questions and answers read on 18 October 2026. Original interrogation pages not inspected. Cruiser-profile review, 18–19 October 2026: Shibata and Nishikawa passages reread through the transcription. An NDL/Commons scan catalogue was located, but no original page inspection is claimed.

Limits: Postwar recollection, not a contemporary damage log. Exact bomb counts, aircraft-crash claims, casualty estimates and fine chronology are not adopted. Shibata was navigator of Suzuya, not aboard Mogami; Nishikawa was Mogami’s gunnery officer. The witnesses’ different positions and later recollection are retained. Original damage records remain outstanding.

View full source record →
M18Yorktown’s damage report

Technical report · third-party scan extract

Passage: PDF p.6 / printed p.3, paragraphs 13–16: towing, salvage, submarine attack and sinking

The sequence of damage, recovery, interrupted salvage and loss of Yorktown. Fuel precautions, flight-deck repair, boiler recovery, loss of power and abandonment.

Checked: PDF pages 4 and 17 visually inspected; other text selectively examined. PDF pp.4–5 rendered and visually rechecked on 18 October 2026 for Hiryū Fights Back. PDF p.6 / printed p.3 visually inspected for towing, salvage, the submarine attack and final loss. Supporting-ship update: PDF p.6 visually rechecked for Vireo’s tow and Hammann’s salvage assistance.

Limits: Relies on officers’ reconstructed recollections after records were lost. Cover publication date and complete plate set are absent from the retained extract. Draws on the captain’s submissions, so is not independent corroboration of M04. Its 1645 torpedo-hit time differs from M04’s approximately 1620, and its 23-degree abandonment list differs from M04’s 26 degrees. The paragraph 10 elapsed-time arithmetic is inconsistent; no exact repair duration is inferred from it. The post-Hammann underwater explosion is tentatively attributed to depth charges, whereas M44 leaves the cause unresolved. The smaller list after the later attack did not mean improved overall buoyancy.

View full source record →

Photograph

Enlarged historical photograph

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