ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

The Curse of the USS Indianapolis

Updated on June 7, 2019
The USS Indianapolis
The USS Indianapolis

The Journey

Dawn, 16th July 1945 and the USS Indianapolis left San Francisco Bay for the Island of Trinian, under the captaincy of Charles Butler McVay. Unknown to the crew the cargo was uranium 235 and other parts for the Hiroshima bomb.

The Indianapolis made good time and reached her destination on the 26th July, offloaded her cargo and continued on her way to Leyte.

During the journey bad weather was experienced and the ships captain, fearing for the crews safety, gave the order to cease the protective zigzag manoeuvre, which was implemented to try and avoid torpedoes. This made the Indianapolis an easier target and at 12.14 am on the 30th July, the I-58, a Japanese submarine fired 2 torpedoes. The first struck the bow and the second the midship, causing the vessel to sink.

Of the 1,196 crewmembers on board, 300 went down with the ship. The remaining 880 went into the sea.

In the Pacific

It is at his point that the horror and the confusion of the situation began. Much emphasis has been placed on the reported shark attacks that began at dawn, resulting in the loss of many lives.

This popular and horrific belief was highlighted by Quints telling of the Indianapolis story in the movie Jaws where he states the sharks arrived in their hundreds.

The sea pilot. Lt. Adrian marks, who carried out an open sea landing, is reported to have rescued 56 men from the water and onto the plane. Many strapped to the wings, to prevent the shark attacks, which he is said to have witnessed, from occurring.

Yet it has been catalogued that other survivors say they saw only one shark.

Another reason for the loss of so many lives appears to be the drinking of seawater, which resulted in diarrhoea, dehydration and madness. The Pacific was warm during the day but cold at night, chills resulted in fever and delirium.

From the moment the men went into the sea, they were faced with untold hardships. Many were without life jackets and had to continuously tread water until one became available from a dead colleague. The few with lifejackets did not fair much better as the kapak life jacket was only good for 48 hours and then became waterlogged, dragging the wearer further down into the sea.

By the 1st August the Indianapolis had still not been reported missing and it was by pure chance that the survivors were spotted by Lt Wilbur C Gwinn who was carrying out a routine patrol in his plane on the 2nd August.

On 3rd August, 5 days after the sinking of the Uss Indianapolis, at 11.30 am, Captain McVay was pulled from the waters, one of the last survivors of the ill-fated ship.

The total number of survivors from the crew of 1,196 was 316.

To this day, many unanswered questions still surround the deaths of so many brave men, and the sinking of the USS Indianapolis, one of the greatest disasters of the American Navy.


    0 of 8192 characters used
    Post Comment
    • Seeker7 profile image

      Helen Murphy Howell 

      9 years ago from Fife, Scotland

      This is a tragic and haunting episode that will live in people's memories the world over and as you say, there are so many mysteries yet to be solved about the loss of so many lives and the reason for the ship's loss.

      Great hub - voted up + awesome!


    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

    Show Details
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
    ClickscoThis is a data management platform studying reader behavior (Privacy Policy)