A connected ship profile

USS Hackleback

A faint radar return became a large warship, then a formation. Hackleback had to keep contact, send what she knew and stay clear of the ships screening it.

Profile · Evidence and limits

A submarine underway, seen from its starboard side, with its name printed below.

About 1944 · catalogue attribution

USS Hackleback underway, in a photograph catalogued as about 1944.

US Navy, as attributed by the Commons/NavSource caption · Source · Public domain (source statement)

The location and photographer are unidentified. The reproduced caption attributes this to the US Navy and dates it approximately; this is not a photograph of the Yamato contact.

A warning in the patrol traffic

Hackleback was on her first war patrol when she encountered the Japanese force on the evening of 6 April. Earlier that day, the crew had watched patrol craft and aircraft near the Bungo Suido. Their report describes manoeuvring to be ready to surface in case larger ships were coming out that night. YT-Y25

The encounter survives in F. E. Janney’s patrol report. A separate Navy historical account bound into the same scan identifies the force as Yamato’s. Keeping those documents distinct lets us follow what the crew detected at the time without silently giving them every later identification.

From one echo to a formation

At 2028, Hackleback’s SJ radar picked up a weak return about 30,000 yards away. At first it might have been an aircraft. As the return strengthened and its movement became clearer, the crew judged it to be a large warship. They sent a contact report and increased to full pursuit on four engines. The times here retain the report’s I notation. YT-Y25

Further echoes appeared. Janney reported seven contacts, one much larger than the others, and tracked a nearby vessel thought to be part of a destroyer screen. These were radar observations and tactical interpretations in darkness, not a complete list of individually identified Japanese ships.

Kept outside the screen

The nearby destroyer repeatedly closed towards Hackleback. Each time, the submarine turned away, losing ground on the main formation, then tried to resume a parallel course when the destroyer withdrew. During the third approach, Janney expected gunfire and prepared to dive, but the destroyer turned back towards its own force. YT-Y25

No firing by that destroyer is recorded in this passage. The threat nevertheless shaped what Hackleback could do. Maintaining contact at a distance and reaching a useful torpedo position were different problems. The account records the Japanese force turning away at 2155 and contact being lost at 2207.

When the transmitter failed

Reporting had its own difficulties. After the first contact report, Hackleback tried to notify the other submarines on the area radio frequency, but the transmitter broke down. The crew then heard their message repeated on the fleet broadcast within ten minutes of sending it. Subsequent reports were repeated too; the transmitter was restored within twenty minutes. YT-Y25

At 2300, the fourth report finally went out on a congested radio circuit, giving the estimated course, speed and time of lost contact. Janney explained that Threadfin’s encrypted reports confirmed his information, leaving nothing further to add through that channel. By 2337, unable to regain contact, Hackleback turned towards her assigned patrol area.

Two submarines, separate viewpoints

Threadfin describes a different position, an initial reporting requirement and a separate attempt to get a torpedo shot. Hackleback’s report adds the pressure of the destroyer screen and the fragility of the radio link. Neither account should stand in for the other. YT-Y24 YT-Y25

Their reports helped make the Japanese movement known. Establishing exactly when each headquarters received and acted on them still requires the corresponding communications and command records. Neither submarine’s account is an eyewitness description of the next day’s sinking.

Read The Last Sortie for the departure and Under Carrier Attack for the battle that followed.

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-Y25USS Hackleback: Report of First War Patrol

Original wartime patrol report · digitised microfilm; separate retrospective Navy history bound into the scan

Passage: First-patrol covering letter, PDF p.5; printed pp.16–18 / PDF pp.21–23; retrospective Navy history at PDF p.3

Radar contact on 6 April; reported destroyer approaches; four contact reports; transmitter failure and repair; receipt of rebroadcast reports; loss of contact and return towards assigned patrol area.

Checked: Selected images visually checked on 21 October 2026: PDF pp.3, 5, 7 and 21–23. Complete public archive scan retained with SHA-256 47c58d73ddabb37aab3950a1e19a423d8db4c68d680ee9892b9d1eff67d6fc87. Contact entries read from images, not inferred from search snippets.

Limits: Radar estimates and the commander’s interpretations, not a verified roster of Japanese ships. Times retained with the original I notation. The separate Navy history identifies the force as Yamato’s retrospectively; its sinking and casualty figures are not adopted. The patrol covering letter ends its period on 26 April, while that history gives arrival at Midway on 27 April; no reconciled end date is asserted. A report being rebroadcast is not proof of receipt or action by every command. No direct sighting of Yamato’s sinking or successful torpedo attack is claimed.

View full source record →
YT-Y24USS Threadfin: Report of War Patrol Number Two

Original wartime patrol report · digitised microfilm scan

Passage: Threadfin second patrol, printed pp.12–14 / PDF pp.69–71: separate contact sequence

Contact with Yamato’s force on 6 April; uncertain identification; initial reporting priority before attack; unsuccessful torpedo positioning; further signals; loss of contact and news of the air attack.

Checked: Six selected page images visually inspected on 20 October 2026. Complete scan retained from the Maritime Park Association’s publicly linked file. SHA-256 d4d3886fc5769eba93cfebd5940bb035ea18101779f29bb197f480d36ab98575. The scan has no usable extracted text for these entries; claims were checked against the images.

Limits: Participant patrol report submitted after events, not an independently verified signal-receipt log. Times retained in the report’s ITEM convention. Contemporary ship counts, speeds and identifications are estimates. The written reporting instruction and cancellation signal are described by Foote, not separately inspected order originals. Does not establish what an unmade attack would have achieved, or by itself reconstruct the carrier command decision.

View full source record →

Photograph

Enlarged historical photograph

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