A connected aircraft profile

Grumman F6F Hellcat

The Hellcat’s work did not always involve another aircraft. Against these battleships and their escorts, fighter pilots attacked the guns firing at the bombers.

Profile · Evidence and limits

Hellcat fighters on a carrier flight deck, with other carriers at sea beyond.

April 1944

Hellcats on Emperor’s flight deck, with ships of the Home Fleet involved in Operation Tungsten beyond.

H. A. Mason, Royal Navy official photographer / Imperial War Museums, A 22649 · Source · Public domain (source statement)

The reproduced catalogue dates the image 4 April, after the attack. These are Fleet Air Arm aircraft, not VF-82’s F6F-5s at Yamato.

A fighter in two campaigns

The Admiralty’s Tungsten aircraft table lists a single-seat Hellcat armed with six .50-inch guns. In its account of the first attack on Tirpitz, Hellcats and Wildcats descended to fire on gun positions while Corsairs provided cover above. The summary credits this strafing with disrupting the defences; that is the British attacking force’s assessment, not a measurement of every German gun’s performance. YT-T22

One returning Hellcat had a damaged arresting hook and was lost in a water landing. The destroyer Algonquin recovered the pilot. Reaching the fleet did not always mean being able to land back aboard a carrier.

Six aircraft from Bennington

A year later, VF-82’s report for 7 April 1945 records six F6F-5s launching from Bennington to attack the Japanese surface force. Other fighter commitments had already absorbed aircraft. Four of the six carried a 1,000-pound general-purpose bomb; the group included a photographic aircraft. YT-Y23

The report records no enemy aircraft encountered. Instead, the fighters attacked destroyers in three pairs, using guns and bombs. This is evidence for their part in the battle around Yamato, not for six Hellcats bombing Yamato herself.

Seeing an effect and proving damage

Lieutenant Commander E. W. Hessel’s bomb failed to release on his first run. The narrative describes a second release but says the bomb did not explode. Elsewhere it claims a hit aft of amidships on a destroyer and a near miss from another aircraft. These observations do not securely identify an individual Japanese destroyer or establish its final damage. YT-Y23

The crews also judged that strafing reduced defensive fire and helped the bombers and torpedo aircraft. The attack table qualifies the effect as lasting at least during the immediate attack. Temporary suppression should not become a claim that those guns were permanently destroyed.

Returning and watching for survivors

All six aircraft returned; the report lists no damage or personnel casualties for this group. Its account of intense fire therefore describes a danger survived, not an absence of danger. Two pilots also circled survivors of a bomber from another carrier until fuel forced them to leave. They reported that rescue was on the way, but did not establish its completion. YT-Y23

Follow Under Carrier Attack and Tungsten and the Return to Repair for the two operations. The aircraft particulars and bomb loads here belong to their identified records; they are not a single specification assigned to every Hellcat variant.

Evidence within reach

Sources for this page

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

YT-Y23Bennington VF-82 Aircraft Action Report No. 66

Original wartime squadron action report · digitised scan

Passage: VF-82 report 66, PDF pp.1–5: aircraft, loads, attacks, losses and return

Six F6F-5s attacking destroyers; four carrying 1,000-pound general-purpose bombs; a photographic aircraft; no own losses or casualties recorded; observed suppression, bomb-release failure and assistance to survivors.

Checked: All seven PDF pages visually inspected on 20 October 2026. Tables compared with narrative; complete scan retained with SHA-256 65b61d1ef4d9bbc9433e95d8cf674f3460f80a1776c3ea8f6d86c8fd6e03b7c4.

Limits: Participant observations, not a Japanese damage survey. Contemporary ship identifications and claimed hit effects are not confirmed individual-ship damage. Suppression is explicitly temporary in the attack table. No enemy aircraft seen by this group does not establish absence throughout the battle. Report says rescue was on the way, not that these pilots witnessed its completion.

View full source record →
YT-T22Admiralty Battle Summary No. 27: Operation Tungsten

Official wartime operational synthesis · scan of printed edition

Passage: Printed pp.2, 7 and 14 / PDF pp.8, 13 and 20: strike organisation, strafing and aircraft particulars

Shared Victorious/Furious strike organisation; squadron exchange; aircraft preparation and fleet protection; planned flying programme; Barracuda II and selected bomb loads; conditional expectations for bomb effects. Reported release heights and the two-aircraft reduction in the second strike.

Checked: Title and source-list pages and the cited printed pages visually inspected on 20 October 2026. Full 40-page scan retained with SHA-256; selected page renders retained. Source list identifies Home Fleet report M.056731/44 and carrier reports dated 5 April 1944. Appendix E read as a programme, not an execution log. Printed p.1 and strike observations on pp.6–7 also visually checked for the gun profiles. Printed pp.2, 7 and 14 / PDF pp.8, 13 and 20 rechecked for Hellcat roles, aircraft particulars and the damaged-hook loss. Printed pp.2, 12, 15, 22 and 24 / PDF pp.8, 18, 21, 28 and 30 visually checked on 20 October 2026 for Emperor’s roster, two fighter groups, Hoare’s loss and the flying programme. Printed pp.7, 12, 14–15 and 24 / PDF pp.13, 18, 20–21 and 30 visually checked on 21 October 2026 for Searcher, Fell’s escort role and the Wildcat variants. Printed pp.4, 6, 12, 15 and 24 / PDF pp.10, 12, 18, 21 and 30 visually checked on 21 October 2026 for Pursuer, Graham, Sleigh, the steering incident and Wilkinson’s return footnote. Printed pp.3, 6, 8, 12 and 24 / PDF pp.9, 12, 14, 18 and 30 visually rechecked on 21 October 2026 for Fencer’s fleet protection, aircraft and flying programme. Printed pp.2–5, 9 and 12 / PDF pp.8–11, 15 and 18 visually rechecked on 21 October 2026 for Royalist, Bisset, Eveleigh, force reorganisation and Sheffield. Printed pp.2, 5, 9 and 12 / PDF pp.8, 11, 15 and 18 visually rechecked on 21 October 2026 for Anson, Moore, McCarthy, guns, Force 7 and the decision to cancel the repeat attack.

Limits: An official synthesis compiled from reports, not the signed original reports of Victorious and Furious. Its source list is evidence of the compiler’s sources, not proof we inspected those manuscripts. Aircraft allocation, actual departures, aircraft attacking and fleet-defence aircraft are distinct counts. The bomb-penetration heights are planning expectations, not confirmed damage results. No exact bomb mark, explosive fill or reconstructed complete flight log is assigned. Its armament footnote is a British assessment, not a dated German final-fit return. Its HA/LA label for the 5.9-inch battery is not adopted; the new profiles do not classify those guns as dual-purpose. Strike descriptions preserve the attackers’ viewpoint. The flying programme is a planned schedule; Emperor’s complete log and squadron records have not been independently compared. The aircraft table lists Wildcat V and VI but does not map them to individual carriers; no mark is assigned to every Searcher aircraft from that table. Pursuer’s steering failure is recorded without a precise mechanical diagnosis; the account describes a narrowly avoided incident, not a collision. The aircrew roster is not a complete flying log. The planned four airborne and four standby Wildcats are not a complete execution log. Twenty-five fleet-defence fighters combine Seafires and Wildcats; nine retained Swordfish do not mean nine continuously airborne. Force 2 and Force 8 are successive operational groupings, not interchangeable labels. Seventeen knots is the mixed force’s stated maximum, not Royalist’s individual maximum. Royalist’s eight 5.25-inch guns are operation-list particulars; no bombardment of Tirpitz or complete fighter-control log is established.

View full source record →

Photograph

Enlarged historical photograph

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