Tehachapi's Online Community News & Entertainment Guide

Articles from the 'Sos Indianapolis' series


Sorted by date  Results 1 - 3 of 3

  • SOS Indianapolis: Behind the sinking of the heavy cruiser, part 3

    Marty Pay, MBA, CLU, LUTC-F, contributing writer|Jul 23, 2022

    [Editor's note: This is the conclusion of the article from our July 9, 2022 issue.] In 1990, Dan Kurzman's "Fatal Voyage" took a comprehensive look at the Indianapolis story. After reading a San Francisco Chronicle article about the book, Young reached out to Kurzman. According to a Jan. 30, 1991, article in the Chronicle, Kurzman had several conversations with Young and concluded, "I believe that what Young says is true." Kurzman rewrote a passage in the paperback edition of his book, adding...

  • SOS Indianapolis: Behind the sinking of the heavy cruiser, part 2

    Marty Pay, MBA, CLU, LUTC-F, contributing writer|Jul 9, 2022

    [Editor's note: This is the continuation of the article from our June 25, 2022 issue.] Questions regarding the Indianapolis disaster – the U.S. Navy's largest loss of life at sea from a single vessel – began almost before the rescue vessels reached shore. Why did the cruiser not have a destroyer escort? Why wasn't McVay notified of Japanese submarine activity along his route? Why wasn't Indianapolis listed as missing when it failed to arrive in the Philippines as scheduled? For the time bei...

  • SOS Indianapolis: Behind the sinking of the heavy cruiser, part 1

    Marty Pay, MBA, CLU, LUTC-F, contributing writer|Jun 25, 2022

    It took a sailor, a schoolboy and survivors more than half a century to disperse the cloud hanging over the sinking of the heavy cruiser. July 30, 1955, marked the 10th anniversary of the worst disaster in American naval history – the sinking of USS Indianapolis. That Saturday retired salesman and World War II Navy veteran Clair Young was at home in Southern California reading a day-old Los Angeles Times article that related how men in the heavy cruiser's Radio Room 2 knew an SOS message had gon...