ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Asian Titanic Tragedy

Updated on November 12, 2012

MV Dona Paz

The collision that happened on December 20 1987 between Philippine-registered ferry MV Dona Paz and the oil tanker MT Vector was the deadliest ferry disaster in history and is considered the worst peace time maritime disaster in history. Claiming over 4000 lives in total, with an exact reported count of 4375 people, National Geographic has went on to label the MV Dona Paz disaster with MT Vector as Asia’s Titanic.

Prior to becoming a Philippine-registered ferry, the MV Dona Paz was built and registered in Japan in 1963 as Ryukyu Kaiun where it ferried Japanese to and fro Hiroshima and had a passenger capacity of 608 people. Upon the purchase of the ferry by Philippine-owner Sulpicio Lines, it was renamed the Dona Paz in 1981. MV Dona Paz was part of a huge fleet owned by Sulpicio Lines and when tragedy struck the ferry, it was plying the route of Manila, Tacloban, and Catbalogan and return back to Manila where it would make the same trip again, in reverse.

MV Dona Paz

MV Dona Paz
MV Dona Paz

The tragedy happened in the night at 2230HRS, when most of the passengers of MV Dona Paz were asleep. The ferry, traveling over choppy seas along Tablas Strait between Mindoro and Tablas had clear visibility but collided with oil tanker MT Vector, which was carrying an estimated 8000 barrels of gasoline owned by Caltex Philippines. The collision was followed by a chain of events that led to the devastating tragedy. Upon the collision between the ferry and the tanker, the cargo within MT Vector caught fire and with highly-flammable gasoline on board, it quickly spread throughout the tanker and within the confinements of the ferry.

MV DONA PAZ TRAGEDY DOCUMENTARY

An explosion occurred and within mere minutes, the MV Dona Paz sank, causing survivors of the initial fire and explosion to jump off the ship and into the shark infested waters of Tablas Strait. Despite Dona Paz having a ship manifest of only 1500 on board, more than its 1424 allowed on the ferry, it was later found out that the ferry had over 3000-4000 passengers on board and it was heavily overcrowded. Of the thousands that were on board the ferry and the tanker, only twenty six survived through the ordeal. Twenty-four of them were passengers of Dona Paz and two crew members from Vector. Through inquiries and investigations, Vector was found liable for the collision as it was found out that the crew members of the tanker were under qualified and the license of the boat had expired, hence, MT Vector was not seaworthy and that it caused the collision between the tanker and the ferry.

More survivors could have been saved from the collision if authorities took lesser time to find out about the incident. It allegedly took a total of sixteen hours for the Philippine maritime authorities to learn of the incident and begin search and rescue operations. In a collision consisting of highly flammable cargo and shark-infested waters, it was indeed a miracle that twenty six survivors were found. Within days of the incident, due to it being close to Christmas, many officials from countries conveyed their message of condolences to the victims of the incident and those affected by the tragedy. Philippine President Corazon Aquino labeled it a national tragedy. The collision, however, was more than a national tragedy. December 20 will always be remembered as the day the worst ferry disaster in history occurred.

Comments

    0 of 8192 characters used
    Post Comment

    • profile image

      Ellenmuir 

      6 years ago

      It's soo sad

    • profile image

      ...kolotskie... 

      8 years ago

      ...we have a project about ship's collision and sad to say donya paz is my target, it is really devastating to know that this tragedy happened and that it give us a bad perception towards maritime indusry...

    • profile image

      Gábor Korpás 

      8 years ago

      I watched a documentary about this disaster on TV. The survivors told the ferry crew made a celebration on board and the captain was there. Perhaps the other experienced officiers were at celebration and a unexperienced young officier managed the ferry. The gasolin tanker's rudder was wrong so 2 person could stir the stirring wheel. Probably the two ships' crew were responsable for this tragedy.

    • Annette Rozen profile image

      Ann Martin 

      9 years ago

      Thanks for sharing the info.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com 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: https://hubpages.com/privacy-policy#gdpr

    Show Details
    Necessary
    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 googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    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)
    Marketing
    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.
    Statistics
    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)