A connected ship profile

USS Enterprise

Enterprise’s weapons reached far beyond the ship, but her aircraft still had to be launched, recovered, fuelled, armed and flown by people who could endure the next sortie.

Profile · Evidence and limits

26 May 1942

Enterprise entering Pearl Harbor shortly before the Midway operation.

U.S. Navy / NHHC, 80-G-66121 · Source · Public domain (source statement)

More than one kind of aircraft

Enterprise’s air striking force combined aircraft with different tasks. Fighters protected ships and escorted attacks; scout/dive bombers searched and delivered bombs; torpedo aircraft approached to release underwater weapons. Spruance’s report records the different groups launching in sequence, a process that took time before the attack could reach the enemy. M43

The squadron reports make the inventory more precise. Bombing Six reported eighteen SBD-2 and SBD-3 aircraft assigned and in commission on 4 June. Scouting Six reported eighteen SBD-3s. These are two squadron returns, not a total for the carrier’s complete air group or a claim that all thirty-six aircraft joined the same attack. M17

The loads actually flown

The recorded morning formation included fifteen VB-6 aircraft with a 1,000-pound bomb each, sixteen VS-6 aircraft with a 500-pound bomb and two 100-pound bombs each, and the air-group commander’s aircraft carrying the latter load. Those differences matter when reading a general description of “the Dauntless attack”. M17

A carrier had to support the aircraft that returned as well as those originally assigned to her. Spruance records Yorktown aircraft landing aboard Enterprise and Hornet and contributing to subsequent attacks. The air groups in action became less tidy than the pre-battle organisation chart. M43

Sustaining the effort

Enterprise’s squadron records follow attacks through 6 June, including the unsuccessful late search on 5 June and the night landings that followed. They also record a photographic mission. Flying after the first victory served several purposes: attacking, locating targets, bringing crews home and establishing what damage had actually been done. M17

An intact flight deck did not mean an untouched fighting force. Nimitz called for complete replacement air groups trained ashore so that depleted groups could leave their carriers, rest and rebuild. Aircraft, skilled crews and training capacity were all parts of carrier strength. M01

This profile concentrates on CV-6 at Midway; it does not borrow dimensions or equipment from later ships named Enterprise. Full machinery and dated shipboard armament tables remain to be checked.

Read The Morning Strikes and Beyond the Carrier Battle.

Photographs

Circa May 1942

A VT-6 Devastator launches from Enterprise. The catalogue places the scene around May; it is not presented as a confirmed Midway launch.

U.S. Navy / Library of Congress · Source · Public domain (source statement)

Exact date and aircraft serial are not established here.

4 June 1942

Clifton R. Bassett of VB-3 is carried from Enterprise’s flight deck after returning wounded from the attack on Hiryū, as identified in the naval photograph catalogue.

U.S. Navy / National Museum of the U.S. Navy, 80-G-7745 · Source · Public domain (source statement)

Follow the connections

Across the stories

Akagi
Nagumo’s flagship, her aircraft contribution and the fires that forced command to move to another ship.
Bombs and torpedoes at Midway
The weapons recorded in American and Japanese carrier sorties, and what their expenditure can tell us.
Douglas SBD Dauntless
The scout and dive bomber, its two-person crew and the bomb loads actually flown from Enterprise.
Douglas TBD Devastator
The American carrier torpedo bomber and the failures of protection and coordination that exposed it at Midway.
USS Hornet
The carrier whose separated morning strike brought disaster to Torpedo Eight, and whose surviving air group kept fighting.
Kaga
A major part of Japan’s opening air attack, followed by the destruction of her bridge and a desperate fight against fire.
Mark 13 aerial torpedo
The American aerial torpedo’s early water-entry problems, its role at Midway and the improvements that came later.
Mikuma
The Japanese cruiser lost during the withdrawal from Midway, whose survivors connect the air battle to the days spent searching the sea.
Mogami
The Japanese cruiser that survived collision and air attack during the withdrawal from Midway, despite an early American claim that she had sunk.
Tone
The Japanese cruiser whose No. 4 reconnaissance aircraft reported American ships during the critical morning at Midway.
USS Vireo
The small tug that tried to bring Yorktown home, and the practical limits of towing a damaged carrier.
Grumman F4F-4 Wildcat
Folding wings, six machine guns and the trade-offs faced by American carrier fighters at Midway.
USS Yorktown
Fighting damage, restoring capability and attempting salvage after Midway.

Appears in

Examine the sources ↓

Evidence within reach

Sources for this page

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

M17Enterprise’s dive-bomber squadron reports

Contemporary squadron reports · third-party hosted scan extract

Passage: PDF pp.2–3, 6, 9 and 13–15: squadron strength, loads, later missions and personnel

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 →

M43Task Force 16 action report

Contemporary command report · modern web transcription

Passage: Paragraphs 4(a), 4(f), 5(e), 6 and 9(m): operations and aircraft from Yorktown; 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 p.25, paragraph 76: replacement groups and recovery

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 →