<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>gCaptain - Maritime &#38; Offshore &#187; disaster</title>
	<atom:link href="http://gcaptain.com/tag/disaster/feed/" rel="self" type="application/rss+xml" />
	<link>http://gcaptain.com</link>
	<description></description>
	<lastBuildDate>Fri, 10 Feb 2012 13:55:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>How Global Logistics Is Working in Partnership to Cope With Future Catastrophe [VIDEO]</title>
		<link>http://gcaptain.com/global-logistics-evolving-cope/?38409</link>
		<comments>http://gcaptain.com/global-logistics-evolving-cope/?38409#comments</comments>
		<pubDate>Fri, 27 Jan 2012 15:27:01 +0000</pubDate>
		<dc:creator>Rob Almeida</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Maritime News]]></category>
		<category><![CDATA[Multimedia]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Video]]></category>
		<category><![CDATA[disaster]]></category>
		<category><![CDATA[logistics]]></category>
		<category><![CDATA[united nations]]></category>

		<guid isPermaLink="false">http://gcaptain.com/?p=38409</guid>
		<description><![CDATA[More than 250 million people each year are affected by natural disasters. The annual number of natural disasters has more than doubled since 1980 as a result of climate change, [...]]]></description>
			<content:encoded><![CDATA[<p><strong>More than 250 million people each year are affected by natural disasters. The annual number of natural disasters has more than doubled since 1980 as a result of climate change, population increase and rapid urbanization.</strong></p>
<blockquote><p>“When disaster strikes, our job is to mobilize massive assistance and to make sure it reaches those in need - fast! . Private sector expertise and corporate partnerships are critical to helping us save lives.&#8221;</p>
<p>- Josette Sheeran, Executive Director, World Food Programme</p></blockquote>
<p>The establishment of reliable supply chains, and the ability to stand up Logistics Emergency Teams in disaster-prone areas is a critical element to the mitigation of further catastrophe.</p>
<div id="attachment_38411" class="wp-caption alignnone" style="width: 610px"><a href="http://gcaptain.com/wp-content/uploads/2012/01/Picture-55.png"><img class="size-full wp-image-38411" title="Picture 5" src="http://gcaptain.com/wp-content/uploads/2012/01/Picture-55.png" alt="bridge watchstander deck officer ship" width="600" height="311" /></a>
<p class="wp-caption-text">Image courtesy World Economic Forum</p>
</div>
<p>Facilitated by the <a href="http://www.weforum.org/issues/disaster-management">World Economic Forum</a>, Logistics Emergency Teams (LET) are currently being provided pro bono by Agility, AP Möller-Maersk, TNT and UPS&#8230; four leading logistics companies, as well as the United Nations.   These organizations joined forces to  provide surge capacity during interventions in disaster-stricken areas.</p>
<p><a href="http://gcaptain.com/global-logistics-evolving-cope/?38409"><em>Click here to view the embedded video.</em></a></p>
<p>LETs’ support through pre-agreed operating procedures and training includes:</p>
<ul>
<li>Logistics specialists (e.g. airport coordinators, airport managers and warehouse managers)</li>
<li>Logistics assets (e.g. warehouses, trucks, forklifts)</li>
<li>Logistics services (e.g. airlift, trucking, customs management)</li>
</ul>
<p>In 2008-2010, LETs deployed in Mozambique, Myanmar, Haiti, Philippines, Indonesia, Pakistan &amp; Chile. Around 100 trained volunteers are currently on standby.</p>
<p>&#8220;As we move forward, we&#8217;re all looking to prevent supply chain disruptions from happening in the first place.  Making sure that critical components are in place in vulnerable regions.  This is how we see the partnership moving forward over the next few years.&#8221; &#8211; Sean Doherty, Head of Logistics and Transport Industry, World Economic Forum</p>
<p>More can be found regarding the Logistics Emergency Teams by clicking <a href="http://www.logisticsemergency.org/">here</a>.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/global-logistics-evolving-cope/?38409/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Piper Alpha Disaster &#8211; Anniversary Of Tragedy In The North Sea</title>
		<link>http://gcaptain.com/piper-alpha-disaster-19-year-anniversary-of-tragedy/?231</link>
		<comments>http://gcaptain.com/piper-alpha-disaster-19-year-anniversary-of-tragedy/?231#comments</comments>
		<pubDate>Thu, 14 Jul 2011 19:00:46 +0000</pubDate>
		<dc:creator>John Konrad</dc:creator>
				<category><![CDATA[Fire Incidents]]></category>
		<category><![CDATA[Firefighting]]></category>
		<category><![CDATA[Offshore Events]]></category>
		<category><![CDATA[disaster]]></category>
		<category><![CDATA[History]]></category>
		<category><![CDATA[Marine Incidents]]></category>
		<category><![CDATA[photos]]></category>
		<category><![CDATA[Video]]></category>

		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/piper-alpha-disaster-19-year-anniversary-of-tragedy/</guid>
		<description><![CDATA[This week marks the 23th anniversary of the worst offshore oil disaster in history. The Piper Alpha was a North Sea oil production platform operated by Occidental Petroleum (Caledonia) Ltd. [...]]]></description>
			<content:encoded><![CDATA[<p><a title="Piper Alpha Fire" rel="attachment wp-att-230" href="http://gcaptain.com/?attachment_id=230"><img src="http://gcaptain.com/maritime/blog/wp-content/uploads/2007/07/piper-alpha.jpg" alt="Piper Alpha Fire" /></a></p>
<p>This week marks the 23th anniversary of the worst offshore oil disaster in history.</p>
<p>The <strong>Piper Alpha</strong> was a <a title="North Sea" href="http://en.wikipedia.org/wiki/North_Sea" rel="nofollow">North Sea</a> oil production platform operated by Occidental Petroleum (Caledonia) Ltd. It accounted for around ten per cent of the oil and gas production from the <a title="North Sea" href="http://en.wikipedia.org/wiki/North_Sea">North Sea</a> at the time. The platform began production in 1976 first as an oil platform and then later converted to gas production. An explosion and resulting fire destroyed it on July 6, 1988, killing 167 men. Total insured loss was $ 3.4 billion. While the environmental damage was not as severe as the loss of the <a href="http://gcaptain.com/forum/offshore/4805-deepwater-horizon-transocean-oil-rig-fire.html">Deepwater Horizon</a>, it remains world&#8217;s worst offshore oil disaster in terms of lives lost.</p>
<p>The Amazing site <a title="Oil Rig Disasters" href="http://home.versatel.nl/the_sims/rig/index.htm" target="_blank">Oil Rig Disasters</a> writes about the Piper Alpha. they <a title="Piper Alpha Tragedy" href="http://home.versatel.nl/the_sims/rig/pipera.htm" target="_blank">tell us</a>:</p>
<blockquote><p><img title="Piper Alpha Memorial" src="http://www.geograph.org.uk/photos/01/00/010032_d45c91e8.jpg" alt="Piper Alpha Memorial" hspace="20" vspace="20" width="200" align="right" />On 06 July 1988, work began on one of two condensate-injection pumps, designated A and B, which were used to compress gas on the platform prior to transport of the gas to Flotta. A pressure safety valve was removed from compressor A for recalibration and re-certification and two blind flanges were fitted onto the open pipework. The dayshift crew then finished for the day.</p>
<p>During the evening of 06 July, pump B tripped and the nightshift crew decided that pump A should be brought back into service. Once the pump was operational, gas condensate leaked from the two blind flanges and, at around 2200 hours, the gas ignited and exploded, causing fires and damage to other areas with the further release of gas and oil. Some twenty minutes later, the Tartan gas riser failed and a second major explosion occurred followed by widespread fire. Fifty minutes later, at around 2250 hours, the MCP-01 gas riser failed resulting in a third major explosion. Further explosions then ensued, followed by the eventual structural collapse of a significant proportion of the installation.</p>
<p>.</p></blockquote>
<h2>Piper Alpha Video</h2>
<p><a href="http://gcaptain.com/piper-alpha-disaster-19-year-anniversary-of-tragedy/?231"><em>Click here to view the embedded video.</em></a></p>
<p>.</p>
<p>.</p>
<h2>Piper Alpha Photos</h2>
<p><a title="Piper Alpha Before the Fire" rel="attachment wp-att-518" href="http://gcaptain.com/?attachment_id=518"><img src="http://gcaptain.com/maritime/blog/wp-content/uploads/2007/09/piper-alpha-before.jpg" alt="Piper Alpha Before the Fire" /></a><br />
The Piper Alpha, as seen from a crew change helicopter, before the fire started.</p>
<p><a title="The Piper Alpha after the fire." rel="attachment wp-att-519" href="http://gcaptain.com/?attachment_id=519"><img title="The Piper Alpha after the fire." src="http://gcaptain.com/maritime/blog/wp-content/uploads/2007/09/piper-alpha-after.jpg" alt="The Piper Alpha after the fire." width="500" /></a><br />
All that remains of the oil platform after the devastating fire burns out.</p>
<p><a title="The Piper Alpha with fire in full blaze." rel="attachment wp-att-520" href="http://gcaptain.com/?attachment_id=520"><img title="The Piper Alpha with fire in full blaze." src="http://gcaptain.com/maritime/blog/wp-content/uploads/2007/09/piper-alpha-fire.jpg" alt="The Piper Alpha with fire in full blaze." width="500" /></a><br />
The fire in full blaze. Imagine the heat that was generated.</p>
<p><a title="Lifeboat Fire Simulations - Piper Alpha" href="http://www.rgu.ac.uk/eng/mrg/page.cfm?pge=3627" target="_blank"><img title="Lifeboats on fire" src="http://gcaptain.com/maritime/blog/wp-content/uploads/daijiworld.com/graphics/fsImage5.gif" alt="Lifeboats on fire" width="500" /></a><br />
A simulation of the survivability of the Piper Alpha&#8217;s Lifeboats.</p>
<p><a title="Piper Alpha Ablaze at Night" rel="attachment wp-att-521" href="http://gcaptain.com/?attachment_id=521"><img title="Piper Alpha Ablaze at Night" src="http://gcaptain.com/maritime/blog/wp-content/uploads/2007/09/piper-alpha-at-night.jpg" alt="Piper Alpha Ablaze at Night" width="500" /></a><br />
The Blaze lit the night sky for miles in every direction.</p>
<p>Video Links:</p>
<ul>
<li><em><a title="Piper Alpha Tribute Video" href="http://www.youtube.com/v/M2dwVjykXkU" target="_blank"><strong>Piper Alpha Tribute Video </strong><br />
</a></em></li>
<li><a title="Piper Alpha Explosion" href="http://www.exponent.com/multimedia/cases/piper.html" target="_blank">Video animation of Piper Alpha Explosion</a></li>
<li><a title="Piper Alpha Movie Tralier" href="http://www.youtube.com/watch?v=9TcTUNDOHiU" target="_blank">&#8220;My Duke of Edinburgh&#8221; Movie Trailer</a></li>
</ul>
<p>Links:</p>
<ul>
<li><strong><a href="http://home.versatel.nl/the_sims/rig/i-fatal.htm">10 Deadliest Offshore Accidents</a></strong></li>
<li><a title="BBC - Piper Alpha" href="http://news.bbc.co.uk/onthisday/hi/dates/stories/july/6/newsid_3017000/3017294.stm" target="_blank">BBC Report on this incident.</a></li>
<li><a title="Piper Alpha Memories" href="http://news.bbc.co.uk/onthisday/hi/witness/july/6/newsid_3036000/3036510.stm" target="_blank">Memories of the men who died</a></li>
<li><a href="http://www.hse.gov.uk/research/rrpdf/rr089.pdf" target="_blank">UK Study on preventing large shipboard explosions</a></li>
<li><a href="http://www.fabig.com/SearchResults.htm?q=piper%20alpha" target="_blank">Fire and Blast Information Group: Piper Alpha</a></li>
</ul>
<h3>Modern Day Oil Rig Tragedy &#8211; Gulf Of Mexico</h3>
<p>For a look at a discussion on the <a href="http://gcaptain.com/forum/professional-mariner-forum/4805-deepwater-horizon-transocean-oil-rig-fire.html">cause and effect of the Deepwater Horizon &#8211; Gulf Of Mexico Oil Rig Tragedy</a> and the blog post &#8220;<a href="http://gcaptain.com/maritime/blog/breaking-news-transoceans-deepwater/">Deepwater Horizon Explosion &#8211; Breaking News From The Gulf Of Mexico</a>&#8221; for a real time look at the events behind a modern oil rig explosion &#038; fire.</p>
<p><!--adsense--></p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/piper-alpha-disaster-19-year-anniversary-of-tragedy/?231/feed/</wfw:commentRss>
		<slash:comments>15</slash:comments>
		</item>
		<item>
		<title>Deepwater Horizon Oil Spill surpasses IXTOC I as worst oil spill in Gulf of Mexico&#8217;s history</title>
		<link>http://gcaptain.com/deepwater-horizon-oil-spill-surpasses-ixtoc-i-as-worst-oil-spill-in-gulf-of-mexicos-history/?15729</link>
		<comments>http://gcaptain.com/deepwater-horizon-oil-spill-surpasses-ixtoc-i-as-worst-oil-spill-in-gulf-of-mexicos-history/?15729#comments</comments>
		<pubDate>Thu, 01 Jul 2010 16:09:33 +0000</pubDate>
		<dc:creator>Mike Schuler</dc:creator>
				<category><![CDATA[Environment]]></category>
		<category><![CDATA[Oil Spill]]></category>
		<category><![CDATA[disaster]]></category>
		<category><![CDATA[gulf of mexico oil spill]]></category>
		<category><![CDATA[oil-spill]]></category>

		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/?p=15729</guid>
		<description><![CDATA[Wait, the oil spill caused by the Deepwater Horizon blowout wasn&#8217;t previously the worst oil spill in the Gulf of Mexico? That&#8217;s right.  As mentioned in gCaptain.com&#8217;s list of History&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://gcaptain.com/maritime/blog/wp-content/uploads/2010/07/800px-IXTOC_I_oil_well_blowout.jpg"><img class="aligncenter size-full wp-image-15730" title="800px-IXTOC_I_oil_well_blowout" src="http://gcaptain.com/maritime/blog/wp-content/uploads/2010/07/800px-IXTOC_I_oil_well_blowout.jpg" alt="" width="500" height="335" /></a></p>
<p>Wait, the oil spill caused by the Deepwater Horizon blowout wasn&#8217;t previously the worst oil spill in the Gulf of Mexico?</p>
<p>That&#8217;s right.  As mentioned in gCaptain.com&#8217;s list of <a href="http://gcaptain.com/maritime/blog/historys-10-most-famous-oil-spills?808" target="_blank">History&#8217;s 10 Most Famous Oil Spills</a> the previous record holder for worst oil spill in the Gulf of Mexico was <a href="http://gcaptain.com/maritime/blog/ixtoc-transocean-sedco-spill?15644" target="_blank">IXTOC I</a>, a 2 mile deep exploritory well that blew out on June 3, 1979 in the Bahia de Campeche, 600 miles south of Texas in the Gulf of Mexico.  On that day, a loss of drilling mud and circulation caused a blowout on the SEDCO 135 semi-submersible platform (Sedco has since been acquired by Transocean, owner of the <a href="../../../forum/professional-mariner-forum/4805-transocean-deepwater-horizon-fire.html">Deepwater Horizon</a>) which was on lease to Petroleos Mexicanos (PEMEX).  The IXTOC I well continued to gush oil at a rate of 10,000 – 30,000 barrels per day (or 140 million gallons total) until it was finally capped on March 23, 1980.</p>
<p>Today, the oil spill caused by the April 20th blowout of the Deepwater Horizon eclipsed the IXTOC I as the largest ever in the Gulf of Mexico&#8217;s history, with an estimated 140.6 million gallons spilled.  According to AP, this calculation is based on the higher end of the government&#8217;s range of barrels leaked per day, minus the amount BP <em>says</em> it has collected from the blown-out well using two containment systems.</p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/deepwater-horizon-oil-spill-surpasses-ixtoc-i-as-worst-oil-spill-in-gulf-of-mexicos-history/?15729/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>General Slocum Disaster: A look back at New York City&#8217;s worst maritime disaster</title>
		<link>http://gcaptain.com/general-slocum-disaster/?15332</link>
		<comments>http://gcaptain.com/general-slocum-disaster/?15332#comments</comments>
		<pubDate>Tue, 15 Jun 2010 14:33:20 +0000</pubDate>
		<dc:creator>Mike Schuler</dc:creator>
				<category><![CDATA[Fire Incidents]]></category>
		<category><![CDATA[History]]></category>
		<category><![CDATA[Lifesaving Incidents]]></category>
		<category><![CDATA[disaster]]></category>
		<category><![CDATA[new york]]></category>

		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/?p=15332</guid>
		<description><![CDATA[Today, June 15th 2010, marks the 104th aniversary of the General Slocum disaster, a twin-paddlewheel steamboat that caught fire and sank shortly after leaving Manhattan for a daytrip up the [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://gcaptain.com/maritime/blog/wp-content/uploads/2010/06/generalslocum_cover.jpg"><img class="aligncenter size-full wp-image-15333" title="generalslocum_cover" src="http://gcaptain.com/maritime/blog/wp-content/uploads/2010/06/generalslocum_cover.jpg" alt="" width="455" height="327" /></a></p>
<p>Today, June 15th 2010, marks the 104th aniversary of the <em>General Slocum</em> disaster, a twin-paddlewheel steamboat that caught fire and sank shortly after leaving Manhattan for a daytrip up the Long Island Sound. Of the estimated of the 1,342 people on board the vessel, 1,021 were killed, making the event the worst disaster in terms of loss of life for the New York metro area, a title it held for nearly 100 years.</p>
<p>In remberance of the event, here is a look at <a href="http://www.amazon.com/Ship-Ablaze-Tragedy-Steamboat-General/dp/0767909054#" target="_blank">the book</a> <em>&#8220;Ship Ablaze: The Tragedy of the Steamboat General Slocum&#8221;</em> by Edward T. O&#8217;Donnell provided by Failure Magazine:</p>
<blockquote><p>When the twin-paddlewheel steamboat General Slocum departed Manhattan for Long Island Sound on the morning of Wednesday June 15, 1904, the 1,300-plus passengers on board expected nothing more than a relaxing day trip. The itinerary called for a short ride up the East River to Long Island’s Locust Grove, where the travelers would eat, drink and play to their heart’s content before being ferried back home. It’s safe to say that swimming was not one of the planned activities, as the mini-cruise called for participants to wear their Sunday best, and few early 20th century New Yorkers knew how to swim, anyway. But just minutes into the excursion a fire started below deck, and before long flames engulfed the boat, forcing the passengers into the water.<span id="more-15332"></span></p>
<p>In the new book, “Ship Ablaze” (Broadway), historian Edward O’Donnell recounts the General Slocum story, a tragedy that took the lives of 1,021 people—mostly women and children. Initially, the fire and subsequent horrors were viewed as a simple, albeit catastrophic, accident. But when survivors reported the alarming disrepair of the boat’s safety equipment, it became evident that corporate greed, corruption and negligence were to blame for the casualties. Within a week, grand jury hearings were underway to determine culpability, but the victims’ families would get no satisfaction. The decisions and actions that led to the second-deadliest incident in New York’s history went almost entirely unpunished.</p>
<p>Read More at <a href="http://failuremag.com/index.php/feature/article/up_the_creek_without_a_paddle/" target="_blank">FailureMag.com</a></p></blockquote>
<p><em>Above image via FailureMag courtesy of The Mariners&#8217; Museum, Newport News, Virginia.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/general-slocum-disaster/?15332/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Pilotage Paradox &#8211; A Look Into The Cosco Busan Allision</title>
		<link>http://gcaptain.com/pilotage-paradox/?2484</link>
		<comments>http://gcaptain.com/pilotage-paradox/?2484#comments</comments>
		<pubDate>Wed, 17 Sep 2008 10:14:25 +0000</pubDate>
		<dc:creator>gCaptain Staff</dc:creator>
				<category><![CDATA[Environment]]></category>
		<category><![CDATA[Incidents]]></category>
		<category><![CDATA[San Francisco]]></category>
		<category><![CDATA[allision]]></category>
		<category><![CDATA[bay bridge]]></category>
		<category><![CDATA[cosco-busan]]></category>
		<category><![CDATA[disaster]]></category>
		<category><![CDATA[Marine Incidents]]></category>
		<category><![CDATA[maritime pilots]]></category>
		<category><![CDATA[ntsb]]></category>
		<category><![CDATA[oil]]></category>
		<category><![CDATA[safety]]></category>

		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/?p=2484</guid>
		<description><![CDATA[Pilotage Paradox by Paul Drouin The Cosco Busan accident, as with many others that have the same root cause, can be categorized into what I call the pilotage paradox. For [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;">Pilotage Paradox</p>
<p style="text-align: center;">by Paul Drouin</p>
<p>The Cosco Busan accident, as with many others that have the same root cause, can be categorized into what I call the pilotage paradox. For on the one hand, we wish to confide the safety and con of the vessel to the pilot, yet on the other insist it is the crew and captain that are ultimately responsible and accountable for the safe conduct of the vessel.</p>
<p>In the seven minute interval between leaving the inner harbour and striking the bridge pylon, the pilot gave 13 helm orders without the slightest indication on the bridge of the Cosco Busan that anything was amiss. We know this because the National Transportation Safety Board (NTSB) has left an amazing amount of information on their <a href="http://www.ntsb.gov/events/2008/San-Francisco-Bay-CA/Exhibits/default.htm">public docket website</a>, including transcripts of the bridge voice recordings.</p>
<p>Leaving berth 56 (Port of Oakland) and passing under the San Francisco-Oakland Bay Bridge is a relatively simple matter, even under blind pilotage conditions, as only two course changes bring you through the span. The Delta-Echo span of the bridge is wide, with a horizontal clearance of 673 meters, and is equipped with a RACON dead center of the span. For the Cosco Busan, winds were light and the vessel would be stemming the flood current as it passed under the bridge. This maneuver should not give an experienced 3rd Mate cause to sweat, much less an experienced pilot.</p>
<p>Under keel clearance was not great for the Cosco Busan, however, and as a consequence hydrodynamic forces on the hull caused by the flood tide would have been strong as the vessel’s sidebody came to obstruct the flow, which was setting at approximately 130° (T) near the bridge and anywhere up to 168° (T) further from the bridge.<span id="more-2484"></span></p>
<p>While it has subsequently come to light that a passage plan for the pilot assisted portion of the voyage did not exist, the outcome would have probably been the same had there been one. Why? By many accounts, pilotage is still a “one-man-show” in most parts of the world. The intended route is almost inevitably “in the pilot’s head” and a “team approach” is in theory only. Under this paradigm, if the pilot, for any reason, loses situational awareness or makes the wrong decision, the team cannot correct, object or challenge. I have found, in my ten years as an accident investigator, that while crews and pilots are generally well informed of BRM techniques, they do not apply them when a pilot has the con.</p>
<p>I am aware of only one pilotage jurisdiction that has radically changed the way they do business. For ships arriving off Brisbane, bridge teams, and in particular the OOW, can expect to be treated differently by the pilot – they can expect to be treated as an effective member of the navigation team. Brisbane pilots have, for some years, introduced the following procedures;</p>
<ul>
<li>On boarding, the pilot asks to see the ship&#8217;s passage plan and the pilot takes the bridge team through his own passage plan during which time any variances in the two plans are discussed and resolved.</li>
</ul>
<ul>
<li> The pilot will not take over the con of the vessel until the courses on the ships charts and the pilot’s passage plan are the same. Any variances are amended on the ship&#8217;s charts (paper), ENC, and radar.</li>
</ul>
<ul>
<li> The OOW is asked to confirm with the pilot each alter course position as they approach to within 7 cables of the position as well as the mark used to alter course and the next course.</li>
</ul>
<ul>
<li> The bridge team is encouraged to use the pilot’s Portable Pilot Unit (PPU) for comparison purposes – but not as a prime means of monitoring the ships position. The PPU is used as an aid to navigation, independent of the ship&#8217;s equipment.</li>
</ul>
<p>This last point is reassuring as we now see a proliferation of pilotage authorities adopting the use of PPUs by their pilots. While this is not in and of itself a bad thing, if the bridge team is excluded from this equipment we would only be entrenching and validating the “one-man-show” paradigm.</p>
<p>Brisbane pilots must be congratulated for breaking the mold and showing the way forward to a better way of pilotage. Yet, their innovation was not without some resistance. When first developed, a number of their pilots were convinced they could never get foreign crews to competently participate in such an exercise. These preconceptions have proven quite wrong! Today, some six years along, Brisbane pilots have been pleasantly surprised by the competency and cooperation of ship’s crews. And the corresponding response from crews has been one of enthusiasm and a sense of genuine participation in the pilotage operation.</p>
<p>Some jurisdictions, such as those with short pilotage runs (but not exclusively so), may try and rationalize away these procedures as not practicable for their area. But in today’s world of electronic charts, DGPS, centralized vessel traffic control, and easy electronic communication, these are only feeble excuses – a death clutch to the old way of doing things. For a majority of pilotage areas today, there is no reason why standardized pilotage passage plans cannot be transmitted to the vessel beforehand so as to be noted on the charts, electronic or otherwise. When the pilot boards the vessel, any last-minute corrections or changes can be agreed upon, thus proceeding without delay – and everyone is singing from the same song sheet!</p>
<p>In a published report by the Transportation Safety Board of Canada (TSB) one can review circumstances similar to that of the Cosco Busan. While downbound in the river at night and while under pilotage, the container vessel Horizon was allowed to continue past the pilot’s customary course alteration point (see “A” in diagram) by approximately three cables, or, in other words by 50 seconds at a speed of 15 knots.</p>
<p style="text-align: left;"><a href="http://gcaptain.com/maritime/blog/wp-content/uploads/2008/09/horizon.jpg"><img class="alignnone size-full wp-image-2527" title="horizon" src="http://gcaptain.com/maritime/blog/wp-content/uploads/2008/09/horizon.jpg" alt="" width="500" height="296" /></a></p>
<p style="text-align: left;"><em>Vessel Horizon positions before and after grounding (from TSB report M04L0092)</em></p>
<p>No correction or challenge by the OOW was forthcoming as the vessel passed the pilot’s customary course alteration point and plowed into the mud bank on the south side of the River.</p>
<p>Suffice it to say that bridge ergonomics, BRM, as well as pilotage practices and procedures have a ways to go before the precise navigation of a large vessel by a pilot and crew of two or more can be accomplished in a seamless, complementary and consistent manner. With the proper planning, intended courses can be adhered to and mistakes, if made, corrected in time to avoid nasty consequences.</p>
<p>Additionally, maybe vessel bridges will have to change –possibly reduced in size and with a more ergonomic and compact layout to bring the team together. Better all-round visibility would be a great advantage as well. Since BRM was inspired by the air industry’s “cockpit resource management”, maybe so too should the designers of ship’s bridges be inspired by the airplane cockpit.</p>
<p>TSB report M04L0092 – Grounding of the Container Vessel Horizon, 2004.</p>
<p>&#8212;&#8212;&#8211;</p>
<p><em>This post submitted by Paul Drouin is a condensed version of an article written for the September 2008 edition of Seaways Magazine and can be found <a href="http://www.nautinst.org/seaways/latest.htm">HERE</a>.<br />
</em></p>
<p><em>Captain Paul Drouin has over a decade of marine accident investigation<br />
experience. He is a graduate of the Canadian Coast Guard College (class<br />
of 81) and a licensed Master Mariner (Unlimited). After serving for 15<br />
years on all manner of Coast Guard vessels (five as master), Paul moved<br />
to a shore job as Marine Superintendant before beginning his<br />
investigator duties in 1998. He is also founder of SafeShip, a company<br />
dedicated to safer ships and safer crews. He lives in Lac-Beauport,<br />
Quebec with his wife and daughter.</em></p>
<p><em>Paul&#8217;s website: <a href="http://www.safeship.ca/">www.safeship.ca</a></em><br />
&#8212;&#8212;&#8212;</p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/pilotage-paradox/?2484/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Twitter Yourself From Disasters</title>
		<link>http://gcaptain.com/twitter-yourself-from-disasters/?1005</link>
		<comments>http://gcaptain.com/twitter-yourself-from-disasters/?1005#comments</comments>
		<pubDate>Mon, 21 Jan 2008 13:26:25 +0000</pubDate>
		<dc:creator>John Konrad</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[tips]]></category>
		<category><![CDATA[Web 2.0]]></category>
		<category><![CDATA[disaster]]></category>
		<category><![CDATA[emergencies]]></category>
		<category><![CDATA[hurricane]]></category>
		<category><![CDATA[preparedness]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[wired]]></category>

		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/twitter-yourself-from-disasters/</guid>
		<description><![CDATA[If we only had one technology related wish for 2008 it would be that every mariner watched this video. Reminder: This is important people! FROM WIRED: While micro-messaging service Twitter [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://gcaptain-s3.s3.amazonaws.com/maritime/blog/wp-content/uploads/2008/01/red-cross-twitter.gif" alt="Red Cross Twitter Logo" align="right" hspace="6" vspace="6" width="300" /></p>
<p>If we only had one technology related wish for 2008 it would be that every mariner watched this video. Reminder: This is important people!</p>
<p><a href="http://blog.wired.com/27bstroke6/2007/10/in-disasters-ev.html" target="_blank">FROM WIRED</a>:</p>
<p>While micro-messaging service Twitter may be <a href="http://blog.wired.com/27bstroke6/2007/10/firsthand-repor.html">one of the best tools for citizen reporting in emergencies</a> such as the Southern California wildfires, the service&#8217;s real usefulness is its ability to get messages to users&#8217; friends and family and provide evacuation updates &#8212; even when cell networks are overloaded, according to homeland security consultant W. David Stephenson.</p>
<blockquote><p>As important as the <a href="http://blog.wired.com/27bstroke6/2007/10/firsthand-repor.html">updates you wrote</a> about, they&#8217;re nowhere near as important as using <a href="http://twitter.com/">Twitter</a> to let your family know you&#8217;re ok (instead of cell calls, which every time they&#8217;re used in disasters end up crashing the network &#8212; and don&#8217;t get through, either): because they&#8217;re packet based, they&#8217;re cued up until they can route around obstacles or gaps in the network, and the 140-character limit means they take up a tiny amount of bandwidth, leaving it for those who need it most.</p></blockquote>
<p>Even cooler, <a href="http://www.stephensonstrategies.com/">Stephenson</a> tells THREAT LEVEL, are the Red Cross&#8217;s Twitter channels.</p>
<blockquote><p>* The redcross channel lets them push information during a mass evacuation. Since cellphone customers can sign up for Twitter ‘on the fly,’ they will encourage evacuees to text ‘FOLLOW REDCROSS’ to 40404, and sign up for updates. The messages will include information about where the shelters are, distribution sites, and other contact info.</p>
<p>* The safeandwell channel is used more for inbound communication. Those who text ‘FOLLOW SAFEANDWELL’ to 40404 will automatically be followed back. That means they can send their private information as a Direct Message to the American Red Cross. (’D SAFEANDWELL Larry Melman, 205-xxx-xxxx, 1313 Mockingbird Lane, Bay Minette, is safe in a shelter.’) That maintains the privacy of the individual, and also serves to funnel the information to a centralized database.</p></blockquote>
<p>Stephenson shows how to use Twitter in emergencies in this episode of his video series <cite>21st Century Disaster Tips You Won&#8217;t Hear From Officials</cite>:</p>
<p><a href="http://gcaptain.com/twitter-yourself-from-disasters/?1005"><em>Click here to view the embedded video.</em></a></p>
<p>Thanks to <a href="http://radar.oreilly.com/archives/2008/01/mainstream_acce.html" target="_blank">Jesse Robbins</a> for the find.</p>
<h3><a href="http://twitter.com/gcaptain" title="Maritime Tweets" target="_blank">gCaptain&#8217;s Twitter Page</a></h3>
<blockquote></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/twitter-yourself-from-disasters/?1005/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Emergency Housing &#8211; Repurposed Containers</title>
		<link>http://gcaptain.com/emergency-housing-repurposed-containers/?674</link>
		<comments>http://gcaptain.com/emergency-housing-repurposed-containers/?674#comments</comments>
		<pubDate>Tue, 23 Oct 2007 18:25:28 +0000</pubDate>
		<dc:creator>John Konrad</dc:creator>
				<category><![CDATA[Interesting]]></category>
		<category><![CDATA[disaster]]></category>
		<category><![CDATA[shipping containers]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[wired]]></category>

		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/emergency-housing-repurposed-containers/</guid>
		<description><![CDATA[Wired has an interesting article on portable emergency housing. Some of the ideas make use of shipping containers. The tell us; One of the biggest obstacles to emergency-shelter design is [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.wired.com/images/slideshow/2007/10/gallery_instant_housing/cleanhub.jpg" title="Emergency Housing - Repurposed Containers" alt="Emergency Housing - Repurposed Containers" width="500" /></p>
<p>Wired has an interesting article on portable emergency housing. Some of the ideas make use of shipping containers. The tell us;</p>
<blockquote><p> One of the biggest obstacles to emergency-shelter design is finding the right balance between providing a temporary shelter like a tent and working to rebuild permanent homes.</p>
<p>&#8220;You can’t design for disaster after the fact,&#8221; notes Kate Stohr, co-founder of the nonprofit humanitarian design firm Architecture for Humanity. &#8220;Unless it&#8217;s strategically thought about in advance of disaster, these ideas don&#8217;t work.&#8221;Shipping containers, found in abundance all over the world, form the basis for the Future Shack, a self-contained, modular refugee-housing unit. It can be mass-produced with a minimum of materials and is easily stockpiled, making it a versatile emergency-housing unit.</p></blockquote>
<p>You can find the slideshow and attached article <a href="http://www.wired.com/culture/lifestyle/multimedia/2007/10/gallery_instant_housing?slide=2&amp;slideView=3" title="Repurposed Shipping Containers - Emergency Housing" target="_blank">HERE</a>.</p>
<p><!--adsense--></p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/emergency-housing-repurposed-containers/?674/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

