The Trackpads collection

FIND YOUR NEXT DISCOVERY.

Search the people, battles, citations, stories, books and audio behind military history.

Type at least two letters or numbers.Full search & filters

Medal of Honor Recipient

Henry Brutsche

U.S. Navy · U.S. Civil War

MOH-RC-002219Source-based record

The award

Representative medal image: early Navy star design and striped ribbon. Not a portrait or a photograph of this recipient’s own medal.
Navy Medal of HonorAction-era reference: 1864

Portrait not yet available. Representative medal shown.

About this image

Presentation date is not usable for design selection. This is an action-era reference; a later presentation or replacement medal may differ.

Medal imagery and historical designs →

Medal of Honor

October 31, 1864

Plymouth, North Carolina, USA

Rank at action
Landsman
Service
U.S. Navy
Conflict
U.S. Civil War
Unit or command
U.S.S. Tacony

The Citation

Sources ↓
Served on board the U.S.S. Tacony during the taking of Plymouth, N.C., 31 October 1864. Carrying out his duties faithfully during the capture of Plymouth, Brutsche distinguished himself by a display of coolness when he participated in landing and spiking a 9-inch gun while under a devastating fire from enemy musketry.
Separately preserved current-source wording

Captured from the linked current recipient source; it is not a new comparison with an original General Order.

Served on board the U.S.S. Tacony during the taking of Plymouth, N.C., 31 October 1864. Carrying out his duties faithfully during the capture of Plymouth, Brutsche distinguished himself by a display of coolness when he participated in landing and spiking a 9-inch gun.

Sources & record notes

General Order comparison: pending. Current-profile review does not mean that the underlying original order has been examined.

  1. Henry Brutsche — current Society profile ↗Congressional Medal of Honor Society · Checked 2026-08-30

    current identity, service, action metadata, and citation comparison

  2. Henry Brutsche — Naval History and Heritage Command ↗Naval History and Heritage Command · Checked 2026-08-30

    official Navy identity, U.S.S. Tacony assignment, Plymouth action, and 31 October 1864 action date

Transcription, metadata & provenance notes
Award ID
MOH-AW-002229
Transcription status
Conflicting official citation variants preserved
Last source check
2026-08-30
Recorded order reference (not verified against the original)
45
Other source date wording
1863-05-23
Accredited to
Pennsylvania
Archive transcription SHA-256
51b2fb16050aa573c18ac44dd91102392c3a6b65bde29fa0db6b1b1fe2dd47e6

Official institutional sources disagree on a citation detail. The inherited canonical wording and the current Society wording are retained separately with supporting source records; no silent overwrite was performed.

The inherited rank-1 Society candidate was confirmed by substantive comparison of identity, service, rank, unit or command, action context, and citation; candidate rank or successful rendering alone was not treated as verification. The controlled canonical unit or command is U.S.S. Tacony; the inherited wording Not documented remains preserved as a separately attributed variant. The current authoritative evidence controls the action date as 1864-10-31 and classifies the action under U.S. Civil War; the inherited unnormalized date and conflict values remain preserved in the audit record. The controlled historical action place is Plymouth, North Carolina, USA; the complete inherited geocoder value Plymouth, NC, USA remains preserved in the audit evidence. The Society structured action date is 1863-05-23; additional or conflicting date context in the rendered citation and supplemental official evidence is preserved separately. Official structured, citation, or supplemental-source date renderings differ. Each exact attributed value is preserved without silent overwrite. The inherited full citation remains canonical and checksum-protected; current rendered wording is preserved separately where transcribed. No underlying General Order was examined, so the exact-order gate remains pending and no General Order verification is claimed.