USS Lenawee
1944 Haskell-class attack transport
USS Lenawee (APA-195) was a Haskell-class attack transport in service with the United States Navy from 1944 to 1946 and from 1950 to 1967. She was scrapped in 1975.
History
Lenawee was a Victory ship design, VC2-S-AP5 and was named after Lenawee County, Michigan, USA. She was laid down on 26 May 1944 by Kaiser Shipbuilding Company, Vancouver, Washington, under Maritime Commission contract; launched on 11 September 1944; sponsored by Mrs. Olaf Haugen; and commissioned on 11 October 1944.
World War II service
Built to transport assault troops to hostile shores, Lenawee picked up her complement of landing craft at San Francisco and departed 26 November 1944 for the Pacific theater. Following amphibious training in the Hawaiian Islands, she sailed 27 January 1945 for Saipan. In the Marianas the final rehearsals for her entrance into the battle zone were held, and 1,503 troops of the 5th Marines and the 62nd Naval Construction Battalion embarked. After a 3-day voyage, she arrived at Iwo Jima on 19 February; her boats helped place the first wave of Marines ashore before debarking her own troops 3 days later. Withdrawn on the 27th, she retired to Guam to discharge Marine casualties and prepare for the final large-scale amphibious operation of World War II.
Sailing south to Espiritu Santo, she embarked over 1,000 troops of the Army 27th Division to reinforce the Okinawa invasion forces. Landing troops and cargo each day and retiring to open sea each night, she suffered no damage from kamikaze attacks during the stay in the area 9 to 14 April.
“USS Lenawee” enters the record as 1944 Haskell-class attack transport. Crown Archives preserves that source wording while asking what Lenawee, Haskell-class and attack can confirm, complicate or overturn.
Why this record matters
“USS Lenawee” is worth following because a concise public description often conceals a longer documentary argument. Here, Lenawee, Haskell-class and attack provides the most credible route into that argument.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Sep 22, 2026. The linked authority identifier is Q7871215. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1944, 1946, 1950 and 1967.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. 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 Lenawee”, its source revision and the description used here.
- Expand the search: follow USS Lenawee primary sources, USS Lenawee archive and Lenawee 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 Lenawee”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “USS Lenawee” 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.