USS Oconto
1944 Haskell-class attack transport
USS Oconto (APA-187) was a Haskell-class attack transport acquired by the U.S. Navy during World War II for the task of transporting troops to and from combat areas.
World War II service
Oconto (APA–187), formerly MCV Hull 655, was laid down under a United States Maritime Commission contract 5 April 1944 by Kaiser Shipbuilding Corporation, Vancouver, Washington; launched 20 June 1944; sponsored by Mrs. J. Wallace Neighbor; acquired by the Navy 2 September 1944; and commissioned the same day.
Landing troops and their equipment in the Philippines
After fitting out and shakedown off the U.S. West Coast, Oconto loaded mail and troops in San Francisco, and sailed 27 October 1944 for New Guinea, arriving Oro Bay 14 November. Several days later she left for Nouméa, New Caledonia, where she remained for a month prior to conducting amphibious exercises off Guadalcanal in preparation for the Lingayen Gulf landings on Luzon. Oconto departed Manus 2 January 1945 and, after sailing the length of the Philippines, offloaded troops and cargo for two days beginning the 11th. Returning south, the transport again loaded troops, at Biak, Netherlands East Indies, and landed them on Mindoro. Retiring to Leyte Gulf 12 February, she prepared the following six weeks for her next objective: Okinawa.
End-of-war operations
This landing proved to be the most trying yet for Oconto. During her time off the beach from 1 to 4 April, there were numerous air raids, as she downed her first kamikaze and assisted in splashing a second.
Begin with the source’s own compact description: “USS Oconto” is 1944 Haskell-class attack transport. The dossier treats that line as a proposition to test through Oconto, Haskell-class and attack, not as a finished interpretation.
Why this record matters
The phrase “1944 Haskell-class attack transport” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Sep 22, 2026. The linked authority identifier is Q7872395. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1944 and 1945.
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 Oconto”, its source revision and the description used here.
- Expand the search: follow USS Oconto primary sources, USS Oconto archive and Oconto 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 Oconto”?
- What terminology or title could unlock a more precise catalogue search?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “USS Oconto” 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.