USS Pintado (SSN-672)
1969 Sturgeon-class submarine

USS Pintado (SSN-672), a short hull Sturgeon-class attack submarine, was the second ship of the United States Navy to be named for the pintado, a large mackerel-like fish, whose elongated spots suggested the Spanish language word meaning "painted."
Construction and commissioning
The contract to build Pintado was awarded to Mare Island Naval Shipyard, at Vallejo, California, on 29 December 1965, and her keel was laid down there on 27 October 1967. She was launched on 16 August 1969, sponsored by Mrs. Bernard A. Clarey, the wife of the Vice Chief of Naval Operations, Admiral Bernard A. "Chick" Clarey (1912–1996), and commissioned on 11 September 1971.
Service history
Pintado was assigned San Diego, California, as her home port. She commenced her first operational deployment to the United States Seventh Fleet in the Western Pacific in November 1972, returning to San Diego, in February 1973. Pintado conducted her second operational deployment from April to September 1974.
In May 1974 Pintado collided with a Soviet Navy YANKEE class ballistic missile submarine in the approaches to the Petropavlovsk-Kamchatsky naval base on the Soviet Union's Kamchatka Peninsula. The collision smashed much of Pintado's sonar sphere, jammed one of her a starboard-side torpedo hatches shut, and moderately damaging one of her diving planes. The commanding officer, then-Commander J. Guy Reynolds, later retired as a vice admiral. The Soviet submarine surfaced immediately, but the extent of damage to her was not known.
“USS Pintado (SSN-672)” enters the record as 1969 Sturgeon-class submarine. Crown Archives preserves that source wording while asking what Pintado, SSN-672 and Sturgeon-class can confirm, complicate or overturn.
Why this record matters
“USS Pintado (SSN-672)” is worth following because a concise public description often conceals a longer documentary argument. Here, Pintado, SSN-672 and Sturgeon-class provides the most credible route into that argument.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Dec 12, 2025. The linked authority identifier is Q499055. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1965, 1967, 1969 and 1912.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “USS Pintado (SSN-672)”, its source revision and the description used here.
- Expand the search: follow USS Pintado (SSN-672) primary sources, USS Pintado (SSN-672) archive and Pintado research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “USS Pintado (SSN-672)”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “USS Pintado (SSN-672)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.