<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
>

<channel>
	<title>gCaptain.com &#187; bob.couttie</title>
	<atom:link href="http://gcaptain.com/maritime/blog/author/bobcouttie/feed/" rel="self" type="application/rss+xml" />
	<link>http://gcaptain.com/maritime/blog</link>
	<description>A Blog About Ships</description>
	<lastBuildDate>Fri, 19 Mar 2010 00:22:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<!-- podcast_generator="podPress/8.8" -->
		<copyright>&#xA9; </copyright>
		<managingEditor>admin@gcaptain.com ()</managingEditor>
		<webMaster>admin@gcaptain.com()</webMaster>
		<category></category>
		<ttl>1440</ttl>
		<itunes:keywords></itunes:keywords>
		<itunes:subtitle></itunes:subtitle>
		<itunes:summary>A Blog About Ships</itunes:summary>
		<itunes:author></itunes:author>
		<itunes:category text="Society &amp; Culture"/>
		<itunes:owner>
			<itunes:name></itunes:name>
			<itunes:email>admin@gcaptain.com</itunes:email>
		</itunes:owner>
		<itunes:block>No</itunes:block>
		<itunes:explicit>no</itunes:explicit>
		<itunes:image href="http://gcaptain.com/maritime/blog/wp-content/uploads/feed_images/gCaptain-Anchor-Logo-S.jpg" />
		<image>
			<url>http://gcaptain.com/maritime/blog/wp-content/uploads/feed_images/gCaptain-Anchor-Logo-S.jpg</url>
			<title>gCaptain.com</title>
			<link>http://gcaptain.com/maritime/blog</link>
			<width>144</width>
			<height>144</height>
		</image>
		<item>
		<title>Lashing@sea and Containers – A Disappointment</title>
		<link>http://gcaptain.com/maritime/blog/lashingsea-and-containers-a-disappointment/</link>
		<comments>http://gcaptain.com/maritime/blog/lashingsea-and-containers-a-disappointment/#comments</comments>
		<pubDate>Sat, 06 Mar 2010 06:14:42 +0000</pubDate>
		<dc:creator>bob.couttie</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/lashingsea-and-containers-a-disappointment/</guid>
		<description><![CDATA[
MAC has a particular distaste for psuedoscience. If someone makes claims that they refuse to back up with solid, peer-reviewed evidence he shows them the door. Typically, a claim will be made that is not testable or verifiable, sometime the woo-woo vendor will demand that MAC gives him a considerable amount of money before evidence [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://maritimeaccident.org/http://maritimeaccident.org/wp-content/uploads/2010/03/image6.png"><img src="http://maritimeaccident.org/http://maritimeaccident.org/wp-content/uploads/2010/03/image_thumb6.png" border="0" alt="image thumb6 Lashing@sea and Containers – A Disappointment" width="196" height="158" align="left" title="Lashing@sea and Containers – A Disappointment" /></a></p>
<p>MAC has a particular distaste for psuedoscience. If someone makes claims that they refuse to back up with solid, peer-reviewed evidence he shows them the door. Typically, a claim will be made that is not testable or verifiable, sometime the woo-woo vendor will demand that MAC gives him a considerable amount of money before evidence will be given that something actually works. Now lets discuss The Maritime Research Institute of the Netherlands.</p>
<p>We’ve seen the PR release, but it doesn’t say much and is, frankly, a disappointment. The Maritime Research Institute of the Netherlands boasts that “For the first time ever some of the reasons why containers are lost overboard have been investigated by the pioneering Lashing@Sea project, that has just completed after three years of intensive research.”</p>
<p>I can hear the squeak as you move to the edge of your seat, awaiting for The Maritime Research Institute of the Netherlands to impart this vital information. Unsqueak and sit back. You&#8217;re not going to get it. <span id="more-13222"></span></p>
<p>If you ask what are some of the reasons it refers to, you’ll have a hard time finding out. Whatever the report apparently says, mere mortals are not entitled, in view of the researchers, to know. It is rather like someone saying: “I have the cure for the common cold, but you are not allowed to say what it is.</p>
<p>If the claim: &#8220;For the first time ever some of the reasons why containers are lost overboard have been investigated by the pioneering Lashing@Sea project&#8221; is true then why are these reasons not being published and made public? Secrecy and opacity has been the bane of maritime safety for decades. Which lifeboats kill most seafarers? It is a commercial secret that you must not ask. Your life is at risk because your life is less important than the lifeboat manufacturer&#8217;s.</p>
<p>Now the The Maritime Research Institute of the Netherlands makes a claim that it declines to allow you to verify. That means that you, as a seafarer, as a ship’s officer, aboard a containership, have no way of taking those lessons to make your ship safer.</p>
<p>Says the praise release: “A monitoring campaign of five ships in operation, model tests of secured cargo and an extensive survey asking crew for their input was conducted in the container, ro-ro and heavylift sectors. A consortium of 24 participants representing flag states, classification societies, shipowners and lashing equipment manufacturers, as well as crew from nearly 160 vessels, took part in the project that was sponsored by the Dutch government. “The Dutch government, together with the British and Swedish maritime administrations, are set to make several recommendations to the International Maritime Organisation (IMO) and the International Association of Classification Societies (IACS) in a bid to improve safety levels and operational efficiency. The industry-wide project was led by the Maritime Research Institute of the Netherlands (MARIN).</p>
<p>“Participants included: Maersk Ship Management, CMA CGM, Danaos ship management, Wallenius Wilhelmsen Logistics, Norfolk line, NYK / Monohakobi Technology Institute, Royal Wagenborg, Spliethoff / BigLift Shipping, United European Car Carriers (UECC), ABS, Bureau Veritas, Det Norske Veritas, Germanischer Lloyd, Lloyds Register, Directoraat Generaal Luchtvaart en Maritieme Zaken (DGLM), the Dutch Shipping Inspectorate, Swedish Transport Agency, Maritime and Coastguard Agency (MCA), German Lashing, MacGregor, SEC, Amarcon, MariTerm, SIRI Marine and MARIN.”</p>
<p>It says all that, but keeps the report itself secret. Why?</p>
<p>Hmmm.</p>
<p>When the Maritime Research Institute of the Netherlands acts as a scientific body should do, which is to put its findings in the public domain and make them available for peer review then maybe its praise release can be taken seriously. That is how real science works.</p>
<p>Secrecy for commercial reasons is inimical to the safety of the lives of seafarers. Seafarers have a right to know what hazards they face regardless of any commercial inconvenience it may cause. We know that such secrecy in the lifeboat industry has cost seafarers lives.</p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/maritime/blog/lashingsea-and-containers-a-disappointment/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>S/V Concordia and the Nautical Goat</title>
		<link>http://gcaptain.com/maritime/blog/sv-concordia-and-the-nautical-goat/</link>
		<comments>http://gcaptain.com/maritime/blog/sv-concordia-and-the-nautical-goat/#comments</comments>
		<pubDate>Fri, 05 Mar 2010 04:28:21 +0000</pubDate>
		<dc:creator>bob.couttie</dc:creator>
				<category><![CDATA[Lifesaving Incidents]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[tall_ship]]></category>

		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/sv-concordia-and-the-nautical-goat/</guid>
		<description><![CDATA[
It was not so much Transport Canada’s decision to investigate the capsize and sinking of the Barbados-flagged  sailing vessel Concordia that raised questioning eyebrows as the apparent implication that TSB did not trust the Barbadian maritime authority to do the job properly. The issues surrounding the investigation of what happened to the 58 metre tallship [...]]]></description>
			<content:encoded><![CDATA[<h6><acronym><a href="http://gcaptain.com/maritime/blog/wp-content/uploads/2010/03/image1.png"><img style="margin-left: 0px; margin-right: 0px; border-width: 0px;" src="http://gcaptain.com/maritime/blog/wp-content/uploads/2010/03/image_thumb.png" border="0" alt="image thumb S/V Concordia and the Nautical Goat" width="234" height="244" align="left" title="S/V Concordia and the Nautical Goat" /></a></acronym></h6>
<p>It was not so much <a href="http://www.tsb.gc.ca/">Transport Canada’s</a> decision to investigate the capsize and sinking of the Barbados-flagged  sailing vessel Concordia that raised questioning eyebrows as the apparent implication that TSB did not trust the <a href="http://www.barbadosmaritime.com">Barbadian maritime authority</a> to do the job properly. The issues surrounding the investigation of what happened to the 58 metre tallship <em>Concordia</em> and the subsequent search and rescue operations, SAR, may go somewhat deeper.</p>
<p>Concordia, built in Poland and completed in 1992, apparently capsized swiftly and without warning on 17 February off the coast of Brazil. Its 64 passengers and crew were rescued 40 hours later by a merchant ship and subsequently transferred to Brazilian Navy rescue helicopters.</p>
<p><em>Concordia</em> was registered as a sail-training yacht and operated as a &#8220;floating classroom&#8221; by <a href="http://www.classafloat.com">Class Afloat</a>, for which it was built. It is Canadian-owned and operated out of the port of Lunenburg, Nova Scotia.</p>
<p>What caused the capsize is yet to be determined. Some accounts suggest that she was knocked down by a <a href="http://en.wikipedia.org/wiki/Microburst">microburst</a>, a brief strong downblast of air that has been blamed for aircraft crashes and ship losses. Descriptions of what happened to <em>Concordia</em> are very similar to accounts of the losses of the <em>Albatross</em>, also a floating classroom, in 1961<em> </em>and <em>Pride of Baltimore </em>in May 1986.<span id="more-13204"></span></p>
<p>Another potential culprit may be keel failure. There has been rising concern regarding keel failures from yachts for some years.  In 2006 the yacht<em> <a href="http://www.sailinganarchy.com/fringe/2005/missing_mauritiusdurban.htm">Moquini  was lost</a></em> with all hands during the Mauritius to Durban Yacht Race apparently due to keel failure. In April 2006 ten Dubois 68 vessels participating in the <a href="http://en.wikipedia.org/wiki/Clipper_Round_the_World_Yacht_Race">Clipper Round the World Yacht Race</a> were diverted to Subic Bay Freeport for seven weeks after problems appeared with keel bolts loosening. The discovery was largely accidental and examination showed the problem existed throughout the fleet.</p>
<p>For the moment, however, the cause of the<em> Concordia</em> sinking remains unknown.</p>
<p>Barbados, Concordia’s flag state is a white-list registry. It has announced an investigation which will also cover the Brazilian SAR response. Brazil’s navy has been criticised for an allegedly tardy response, which the <a href="http://www.washingtonpost.com/wp-dyn/content/article/2010/02/21/AR2010022101773.html">navy disputes</a>.</p>
<p>Currently little is known of the Barbados expertise in maritime accident investigation. Of 15 casualties involving vessels in the Barbados registry lodged with the IMO since 1996 only one records a report being lodged with the IMO and none can be found online. This is not unusual among open registries, an unfortunate number of which consider accident investigation reports to be confidential between the flag-state and the shipowner rather than a matter of improving safety. Such investigation, one may suspect, are unlikely to find much wrong with the shipowner’s management.</p>
<p>In 2006 Barbados announced the implementation of safety-based, open investigations. However, it has, as yet, failed to demonstrate a commitment to transparency.</p>
<p>Such a lack of transparency will not sit well with Canada since the vessel was Canadian-owned and 48 Canadians were aboard at the time.</p>
<p>Brazil, as the coastal state, may also launch an investigation by the <em>Comissão de Investigação e Prevenção dos Acidentes da Navegação</em>, <a href="https://www.dpc.mar.mil.br/cipanave/rel_acidentes.htm">CIPANAVE</a>. This is, however, under the authority of the Brazilian Navy, which would raise concerns about its independence in an investigation which must necessarily examine the SAR effectiveness of the Brazilian Navy.</p>
<p>In fact, recently, Brazil has made greater efforts to actively engage the maritime safety and investigation community and greater transparency. It may be that Brazil’s investigation capabilities are independent and that its military superiors support that independence.</p>
<p>Rightly or wrongly any investigation carried out by Brazil will necessarily be assumed to be tainted by self-interest on the part of the navy. Ceasar’s wife must not be beyond reproach, she must be seen to be beyond reproach.</p>
<p>Inevitably, there is a political aspect. Given the circumstances a Canadian government minister will be required to face the country’s parliament and a vibrant opposition, and the Canadian public and a free and questioning press, to field questions surrounding the investigation.</p>
<p>It is, to say the least, difficult to conceive such a minister being able to persuade parliament, the public and the media that such an investigation may safety be left in the hands of a registry run out of a London office under contract with the Barbados government, whose purpose is to raise funds for that government, with no publicly verifiable competence or integrity in maritime accident investigation.</p>
<p>Those who wish to read the entrails of this nautical goat will read closely the official statement by the TSB. An investigation of this sort has defined objectives: How did the incident happen, why did it happen and what can be done to reduce the chances of it happening again.  It is not unusual for two or more agencies with significant interest to work together on an incident which covers different jurisdictions.</p>
<p>Says TSB: “Since the accident, the <acronym>TSB</acronym> has gathered information, in accordance with its own procedures, in order to assess the occurrence. Having gathered enough information to complete its assessment, the <acronym>TSB</acronym> decided to conduct a parallel investigation into this accident independently of the Barbadian investigation. The <acronym>TSB</acronym> made the decision to investigate because the scope and methodology used to uncover causes and contributing factors will likely be different than that of the Barbados authority.”</p>
<p>There is much in that statement, none of it encouraging for the credibility of the Barbados registry.</p>
<p><strong>(Gatineau, Quebec, March 3, 2010)</strong> &#8211; The Transportation Safety Board of Canada (TSB) has decided to conduct a safety investigation (M10F0003) into the capsizing and sinking of the sailing vessel (SV) <em>Concordia</em>, which occurred on February 17, 2010, off the coast of Brazil.</p>
<p>Barbados, the flag state of the <acronym>SV</acronym> <em>Concordia</em>, has opened an investigation.</p>
<p>Since the accident, the <acronym>TSB</acronym> has gathered information, in accordance with its own procedures, in order to assess the occurrence. Having gathered enough information to complete its assessment, the <acronym>TSB</acronym> decided to conduct a parallel investigation into this accident independently of the Barbadian investigation. The <acronym>TSB</acronym> made the decision to investigate because the scope and methodology used to uncover causes and contributing factors will likely be different than that of the Barbados authority. Meanwhile, in accordance with the provisions of international conventions, the <acronym>TSB</acronym> remains committed to providing assistance to the Barbados authority as it proceeds with its investigation.</p>
<p>On February 17, 2010, at approximately 14:22 local time, the <acronym>SV</acronym> <em>Concordia</em> capsized and sank off the coast of Brazil; the 64 passengers and crew were rescued 40 hours later by a merchant ship and subsequently transferred to Brazilian Navy rescue helicopters.</p>
<p>IMO 15 incidents since 1996</p>
<p>Only one report appears to have been logged with the IMO</p>
<p><a title="http://www.tsb.gc.ca/eng/medias-media/communiques/marine/2010/comm_m10f0003.asp" href="http://www.tsb.gc.ca/eng/medias-media/communiques/marine/2010/comm_m10f0003.asp">http://www.tsb.gc.ca/eng/medias-media/communiques/marine/2010/comm_m10f0003.asp</a></p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/maritime/blog/sv-concordia-and-the-nautical-goat/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Flogging and Mutiny in the 21st Century</title>
		<link>http://gcaptain.com/maritime/blog/flogging-and-mutiny-in-the-21st-century-proudly-waving-the-stars-and-stripes/</link>
		<comments>http://gcaptain.com/maritime/blog/flogging-and-mutiny-in-the-21st-century-proudly-waving-the-stars-and-stripes/#comments</comments>
		<pubDate>Fri, 23 Oct 2009 17:30:56 +0000</pubDate>
		<dc:creator>bob.couttie</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Majestic Blue]]></category>
		<category><![CDATA[MARPOL.Mutiny]]></category>

		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/flogging-and-mutiny-in-the-21st-century-proudly-waving-the-stars-and-stripes/</guid>
		<description><![CDATA[When Captain Doug Pine talks of floggings, mutiny and physical fear it’s not a tale of past centuries, but of today. Indeed it’s probably going on as you read this post. And it’s not happening aboard a flag of convenience vessel – the 187 gross tonne Majestic Blue, of which he was master until 18 [...]]]></description>
			<content:encoded><![CDATA[<p>When Captain Doug Pine talks of floggings, mutiny and physical fear it’s not a tale of past centuries, but of today. Indeed it’s probably going on as you read this post. And it’s not happening aboard a flag of convenience vessel – the 187 gross tonne Majestic Blue, of which he was master until 18 October this year, proudly waves the flag of the United States of America at her stern.</p>
<p>We know that because the company itself boasts “Our companies are 100% owned by United States citize <em>(sic)</em> and vessel flies proudly the flag of the United States of America!”. It is unlikely that the United States of America will be proud of the vessel, owned by Majestic Blue Fisheries LLC, which flies its flag.</p>
<p> <span id="more-10965"></span>Until 2009 the vessel,a purse seiner working Western and Central Pacific Ocean tuna fishery along with a sister ship, Pacific Breeze, was registered in South Korea then moved to the US flag. She carried a crew of 23 with, originally a Korean Captain and chief officer, with most of the rest of the crew being unlicensed seafarers from Indonesia and the Philippines. When the ship was registered in the US, the Korean captain became the fishmaster and Captain Pine joined as Captain. It was an uncomfortable relationship.
</p>
<p>Alerted by Steve Gordon of law firm Gordon &amp; Elias, MAC spoke with Doug Pine in Tawara, Kiribati, by cellphone. “As a human being it was appalling to witness, on an American ship, seafarers being beaten,” says Pine. He recalls the first beating he witnessed: “I was sitting in my chair on the navigation bridge with a pleasant young Indonesian, the equivalent of a third officer, near me. Suddenly, the chief engineer came in and punched him with his fist, with full force, then kicked him with full force between the buttocks. Sometime the chief engineer would use a bamboo stick, hitting him about the shoulders, neck and head”.</p>
<p>Pine posted standing orders around the vessel prohibiting further beatings. Some of the crew quietly thanked him, but he believes it may still have continued out of sight. “I think they came to accept the beatings,” he says.</p>
<p>Pine found it difficult to exercise his authority almost from the moment he first boarded the vessel: “The first day I was aboard I asked for the crew list It was ordered by rank. I was Number Two, the fishmaster was number 1. The second officer refused a direct order to change it. The Korean officers refused to obey any routine command activity.”</p>
<p>In fact, Pine was supposed to simply be a ‘paper captain’ to meet the requirements of the US flag and to accept the authority of the fishmaster, the former captain. Pine was unable to manoeuver the vessel or use the navigation equipment on the bridge.</p>
<p>He believes that there was a conspiracy between the ship’s officers and the owners to commit mutiny.</p>
<p>The Korean officers refused to comply with MARPOL regulations, claims Pine. A vessel waste management plan was posted throughout the ship but ignored, even though the vessel had an adequate incinerator ad oily-water separator. “I brought it up at the monthly safety meetings but was ignored,”says Pine, who has video and photographic evidence that the Korean officers ‘intentionally and wilfully” disposed of plastics wastes and oil wastes at sea: ”They didn’t want to waste fuel by using the incinerator”, he says.</p>
<p>When Pine attempted to organise the vessel to arrive in Tarawa, Kiribati for and inspection, the fishmaster ignored him.</p>
<p>When Pine went to the bridge to check the ship’s position the fishmaster began screaming at him, pounding the chart table with his fist and, when the chief officer came onto the bridge pointing at Captain Pine in a way that made him fear physical violence. Pine managed to smuggle a the ship’s satellite phone off the bridge, returned to his cabin and telephoned his wife who recorded a message asking for assistance to be passed on to the US Coast Guard.</p>
<p>After a while in his cabin things quietened down and he was able to return to the bridge and send a couple of emails then received a message from the Majestic Blue’s sister ship, Pacific Breeze that he had a message from the coast guard. Later he received a VHF communication from the Coast Guard asking him to attend a ‘pre-inspection meeting’.</p>
<p>“It was a sort of coded message”, says Pine. He returned to his cabin, collected his belongings and left the ship at Tawara by pilot boat on the morning of 18 October.</p>
<p>Since then he has stayed in Tarawa being interviewed by the US Coast Guard, accompanied by his wife.</p>
<p>For Captain Doug Pine the nightmare is over, for the remaining crew of Majestic Blue it will continue, at least for the time being.</p>
<p>And Majestic Blue Fisheries of Guam is looking for an American captain to board its all American-owned purse seiner flying that all-American flag.</p>
<p><a href="http://www.offshoreinjuries.com/bio/StevenGordon.asp">(With thanks to Steve Gordon)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/maritime/blog/flogging-and-mutiny-in-the-21st-century-proudly-waving-the-stars-and-stripes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Casualty Outlook</title>
		<link>http://gcaptain.com/maritime/blog/casualty-outlook-4/</link>
		<comments>http://gcaptain.com/maritime/blog/casualty-outlook-4/#comments</comments>
		<pubDate>Fri, 28 Aug 2009 01:23:37 +0000</pubDate>
		<dc:creator>bob.couttie</dc:creator>
				<category><![CDATA[Casualty Outlook]]></category>
		<category><![CDATA[Marine Incidents]]></category>
		<category><![CDATA[stcw]]></category>

		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/casualty-outlook-4/</guid>
		<description><![CDATA[ Those of us who spend our time reading casualty reports often end up scratching our heads and muttering “Why the hell did he do that?” Mostly it’s down to a lack of safety awareness and, unfortunately, as the video still here shows, that lack of awareness may begin early in a seafarer’s training.
Here we [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://gcaptain.com/maritime/blog/wp-content/uploads/2009/08/lifeboatinstruction.png"><img style="border-right-width: 0px;border-top-width: 0px;border-bottom-width: 0px;margin-left: 0px;border-left-width: 0px;margin-right: 0px" src="http://gcaptain.com/maritime/blog/wp-content/uploads/2009/08/lifeboatinstruction_thumb.png" border="0" alt="lifeboatinstruction thumb Casualty Outlook" width="244" height="213" align="left" title="Casualty Outlook" /></a> Those of us who spend our time reading casualty reports often end up scratching our heads and muttering “Why the hell did he do that?” Mostly it’s down to a lack of safety awareness and, unfortunately, as the video still here shows, that lack of awareness may begin early in a seafarer’s training.</p>
<p>Here we have an instructor, apparently in Eastern Europe, doing an STCW course. He’s not wearing a hardhat, nor is he wearing a lifejacket. This tells us that he’s not teaching safety, and not teaching safely. He’s only teaching the students to pass STCW certification, not the safety lessons that might keep them alive and injured when they’re on a ship.</p>
<p>If the instructor isn’t taking safety seriously, will his students?</p>
<p>Isle of Man instructors are in Malaysia investigating the collision between the tanker <em>Formosaproduct Brick</em> and <em>Ostende Max, </em>which cost nine seafarers their lives<em>. </em>The Manx investigators do a good job and despite current attempts to hustle things along they know their business well enough to take the time necessary to do the job right.</p>
<p>It’s quite a complex investigation which will cover how the collision happened, how the <em>Formosaproduct Brick</em> caught fire, how the fire was fought and why the nine fatalities occurred, whether the Vessel Traffic Service was on the ball and whether the incident response was timely and appropriate.</p>
<p>It is likely, however, that liability issues and fear of legal action against the two vessels’ officers will hamper the gathering of necessary information for the safety investigation.</p>
<p>It does seem to have some similarities to the 1993 British Trent/Western Winner incident. Hopefully it will have a more satisfactory resolution.</p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/maritime/blog/casualty-outlook-4/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Casualty Outlook</title>
		<link>http://gcaptain.com/maritime/blog/casualty-outlook-3/</link>
		<comments>http://gcaptain.com/maritime/blog/casualty-outlook-3/#comments</comments>
		<pubDate>Thu, 13 Aug 2009 10:41:20 +0000</pubDate>
		<dc:creator>bob.couttie</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[arctic sea]]></category>
		<category><![CDATA[hijack]]></category>
		<category><![CDATA[piracy]]></category>
		<category><![CDATA[pirates]]></category>

		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/casualty-outlook-3/</guid>
		<description><![CDATA[Three serious incidents have dominated the past week with the disappearance of the Arctic Sea, its cargo of timber valued at a little under $2m and its crew of more than a dozen Russian seafarers, garnering most of the bandwidth. That’s only natural, given the mysterious circumstances.
The trouble with speculating about what’s happened to the [...]]]></description>
			<content:encoded><![CDATA[<p>Three serious incidents have dominated the past week with the disappearance of the Arctic Sea, its cargo of timber valued at a little under $2m and its crew of more than a dozen Russian seafarers, garnering most of the bandwidth. That’s only natural, given the mysterious circumstances.</p>
<p>The trouble with speculating about what’s happened to the vessel is that there are simply too many options and not enough facts. Taken by the crew? Hijacked by the Russian Mafia or a disgruntled business interest? Suddenly sunk by a rogue wave? Taken by Somali pirates sporting long range tanks on their skiff outboards? Did she ever actually leave the Baltic? Take a number, but it certainly has got the attention of the security services: Arctic Sea passed through some of the heaviest traffic lanes and patrolled areas on the planet and vanished on the way. Or did she?</p>
<p>That story will run and run for a while but the fate of <a href="http://www.thelocal.se/21196/20090809/">the Langeland and its six crew</a> off the coast of Sweden as she sought a safe haven in bad weather has already faded from what limited attention it did get. Notably within days the wreck of the vessel was found an ROVs sent down to inspect her. A similar search for the missing m/v Rezzak has been a no-go because, we’ve been told, none of the concerned parties want to pay for sidescan sonar to find her.</p>
<p>Ferries in developing countries continued to take their toll in Incident number three: the sinking of the <em>Princess Ashika</em> off Tonga with more than 90 now missing. It is an enormous blow to the island nation.A Royal Commission has been set up to investigate the incident. </p>
<p>Somalia still gets the lion’s share of attention when it comes to piracy so it’s worth remembering that, out of the spotlight, it’s still continuing in the South China Sea with some seven vessels attacked since January, the most recent being the <a href="http://www.recaap.org/incident/pdf/incident/2009/Incident%20Alert%202%20Aug%2009%20%28Tahir%29.pdf">Singaporean-register tug Tahir on August</a> 2<em>.</em></p>
<p>Don’t be surprised to hear that the Danish Maritime Authority wants to tighten up, if that’s the phrase, on alcohol on ships after the report on the grounding of the <em>Karin Schepers</em>. ““He first realized that the ship was aground when a man he did not know came on the bridge…” says the DMA report on the incident, he being the chief officer who was asleep on the bridge, drunk and with the bridge watch alarm switched off and the ‘man he did not know’ being a pilot from a passing vessel. <a href="http://www.maritimeaccident.org/idess/accident-report-karin-schepers-and-the-stranger-on-the-bridge/">Read the report</a> to brighten your day.</p>
<p>If you’re quick you might catch the BBC Radio 4 documentary on the British merchant navy, <a href="http://www.bbc.co.uk/programmes/b00ly4nk">Under The Red Duster</a>, which for once giving the seafarer a bit of the attention he deserves for keeping the world afloat. You can listen to it online.</p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/maritime/blog/casualty-outlook-3/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Playing Russian Roulette At UK container ports?</title>
		<link>http://gcaptain.com/maritime/blog/playing-russian-roulette-at-uk-container-ports/</link>
		<comments>http://gcaptain.com/maritime/blog/playing-russian-roulette-at-uk-container-ports/#comments</comments>
		<pubDate>Fri, 31 Jul 2009 13:16:28 +0000</pubDate>
		<dc:creator>bob.couttie</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/playing-russian-roulette-at-uk-container-ports/</guid>
		<description><![CDATA[ By William Redmond     MAC UK Correspondent
A container crane collapse during ship loading at Southampton Container Terminal on July 13 has raised serious issues about dock workers and ship crews’ safety in which the investigative authority, namely the Health &#38; Safety Executive, HSE, does not emerge entirely unblemished. 
The incident, which [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.freefoto.com"><img style="border-bottom: 0px;border-left: 0px;margin-left: 0px;border-top: 0px;margin-right: 0px;border-right: 0px" border="0" alt="image2 Playing Russian Roulette At UK container ports?" align="left" src="http://gcaptain.com/maritime/blog/wp-content/uploads/2009/07/image2.png" width="244" height="180" title="Playing Russian Roulette At UK container ports?" /></a> By William Redmond     <br />MAC UK Correspondent</p>
<p>A container crane collapse during ship loading at Southampton Container Terminal on July 13 has raised serious issues about dock workers and ship crews’ safety in which the investigative authority, namely the Health &amp; Safety Executive, HSE, does not emerge entirely unblemished. </p>
<p>The incident, which left the crane driver, 33-year old Mr Jay Squibb, with life-threatening injuries closely copied a similar crane collapse 19 months ago involving the same crane manufacturer and design at the same berth, the report on which dock operators are still awaiting.</p>
<p> <span id="more-9551"></span>
</p>
<p><a href="http://gcaptain.com/maritime/blog/wp-content/uploads/2009/07/image3.png"><img style="border-bottom: 0px;border-left: 0px;margin-left: 0px;border-top: 0px;margin-right: 0px;border-right: 0px" border="0" alt="image thumb2 Playing Russian Roulette At UK container ports?" align="right" src="http://gcaptain.com/maritime/blog/wp-content/uploads/2009/07/image_thumb2.png" width="94" height="94" title="Playing Russian Roulette At UK container ports?" /></a>Such investigations must always be painstaking and never rushed but is it unreasonable to ask why such investigations should take so astoundingly long before findings are made public, especially as such reports could prevent future, far worse accidents? </p>
<p>The terminal operator, DP world, which owns 51% of the operation, partnered with Associated British Ports, who own 49%, says the latest crane collapse is unlikely to be related to the previous incident yet the similarities seem to be more than coincidental. Both cranes of the same design, of which there are no other examples in the UK, were made by the defunct British manufacturer, Morris Cranes, in the early 1990s and both were subsequently altered. </p>
<p>In the earlier incident, crane 8 had undergone a 4 mt boom extension by crane contractor, Seward Wyon, during 2006 to enable it to handle bigger vessels. No one was injured in that incident but ship-side operations had to be suspended as a safety precaution and all 11 ship-to-shore cranes were taken out of service and checked one by one by HSE inspectors. The knock-on effects were costly, as it involved the temporary closure of the Swindon-based Honda car factory after its JIT delivery system was disrupted.</p>
<p>Alterations to crane 6 in the latest incident involved raising the crane by 5 mt in 2004. There were no strong winds when the crane’s twin boom collapsed onto the container ship, <em>NYK Themis</em>, and damage to the ship required only minor repairs to one hatch cover but at least four containers were damaged. The incident, however, could have been far worse. </p>
<p>Health and safety officials have identified “some significant lines of enquiry” but Mike Wilcock, the HSE regional head of operations, refused to elaborate on such lines. HSE has, however, requested that the two similar cranes at the terminal be withdrawn from service until further notice and has issued some precautionary advice to the port’s industry. HSE is also telling all users of workshop port cranes made by Morris to carry out urgent safety tests. He added that a team of HSE staff, including inspectors, a specialist mechanical engineer and a metallurgist are working on the investigation which would take “some time” to reach a conclusion. It is to be hoped that, unlike the previous accident, it will not exceed an elephant’s gestation period before findings are made public. </p>
<p>There is serious concern among UK port workers about safety issues and Unite, the union to which, Mr Squibb belongs, says “The matter is of paramount importance”. One dock worker who returned to work after the incident told the local Daily Echo newspaper that he believes staff play “Russian roulette” when they get into cranes, but their concerns are not enough to keep them away. “It isn’t necessarily about he crane maintenance. It is the fact that at any time we can lift locked on boxes and it can cause a crane to collapse,” he said. </p>
<p>Speculation into the accident’s causes at this stage may not be very helpful but the incident, perhaps, stresses the need to hasten the proposed installation of weighers on dock handling equipment, preferably on straddle carriers, reach stackers, and the like before containers are marshalled under a gantry crane’s operational apron. At DP World’s Southampton terminal none of its cranes or straddle carriers is fitted with a weigher, although all machinery is designed to cut out if containers exceed a machine’s safe working load. </p>
<p>All lifting machines also usually have a generous overload margin but even that could be exceeded in certain circumstances involving weather conditions and deliberate, fraudulent under declaration of container payload weights by consignors and container stuffers. This practice costs container shipping lines, ports and governments billions of pounds in lost revenues every year, and imperils ships, their crews and the environment.</p>
<p>There is, however, some good news in that Mr Squibb is out of intensive care and showing positive signs of recovery. </p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/maritime/blog/playing-russian-roulette-at-uk-container-ports/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Maritime Safety &amp; Security News &#8211; 31 July 2009</title>
		<link>http://gcaptain.com/maritime/blog/maritime-safety-security-news-31-july-2009/</link>
		<comments>http://gcaptain.com/maritime/blog/maritime-safety-security-news-31-july-2009/#comments</comments>
		<pubDate>Fri, 31 Jul 2009 09:00:22 +0000</pubDate>
		<dc:creator>bob.couttie</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/maritime-safety-security-news-31-july-2009/</guid>
		<description><![CDATA[Coast Guard Ends Search for 67 Haitians Missing after Shipwreck    Latin American Herald Tribune    Fifteen Haitians died and 119 were rescued in a joint operation by the Coast Guard and Turks and Caicos maritime police. 
Vessels without enough crew &#8216;are a hazard to shipping&#8217;    Scotsman  [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.google.com/url?sa=X&amp;q=http://www.laht.com/article.asp%3FArticleId%3D340413%26CategoryId%3D14092&amp;ct=ga&amp;cd=v8UjDL4_w1A&amp;usg=AFQjCNHOXhiKtYMkG0y78fyAHeNRnm4YSA">Coast Guard Ends Search for 67 Haitians Missing after Shipwreck</a>    <br />Latin American Herald Tribune    <br />Fifteen Haitians died and 119 were rescued in a joint operation by the Coast Guard and Turks and Caicos <b>maritime</b> police. </p>
<p><a href="http://www.google.com/url?sa=X&amp;q=http://news.scotsman.com/uk/Vessels-without-enough-crew-39are.5511264.jp&amp;ct=ga&amp;cd=aiI7_A3hBRc&amp;usg=AFQjCNFloo9j2wXrCXwBP7yhBbA_FEYxkw"><b>Vessels</b> without enough crew &#8216;are a hazard to shipping&#8217;</a>    <br />Scotsman    <br /><b>&#8230;</b> the officer of the watch had been asleep for over three hours before the <b>accident</b>, while the <b>vessel</b> ploughed on like an unguided missile. </p>
<p><a href="http://www.google.com/url?sa=X&amp;q=http://www.csmonitor.com/2009/0730/p06s10-woeu.html&amp;ct=ga&amp;cd=CMY0Iow7HmE&amp;usg=AFQjCNFLUzj2R7rPmNoeCHRVcZQrKJdMWw">Mallorca target of Spain&#8217;s second attack in two days</a>    <br />Christian Science Monitor    <br /><b>&#8230;</b> took the unusual step of shutting the island&#8217;s airport and <b>ship</b> terminals, effectively sealing off the island from the outside world for a few hours. </p>
<p><a href="http://www.lloydslist.com/ll/news/sharp-rise-in-crew-abandonment-cases/20017681520.htm;.5d25bd3d240cca6cbbee6afc8c3b5655190f397f">Sharp rise in crew abandonment cases</a>    <br />Lloyd&#8217;s List &#8211; London,UK    <br />Another example — taken at random from the Lloyd&#8217;s MIU <b>casualty</b> service — is <b>&#8230;</b> to approval at the International <b>Maritime</b> Organization and International </p>
<p><a href="http://www.google.com/url?sa=X&amp;q=http://www.google.com/hostednews/canadianpress/article/ALeqM5jMdUGwzH7Y4fDkJ03R8Joghih3sg&amp;ct=ga&amp;cd=jV3TLoycm2U&amp;usg=AFQjCNH_w-0v-mR1s2Zs0cFboNHTXPTIOg"><b>Fire</b> disrupts Atlantic ferry services for second straight day</a>    <br />The Canadian Press    <br />A firefighter and one crew member were taken to hospital after the <b>fire</b> in the heating unit of the ferry. The <b>vessel</b> returned to North Sydney after the <b>fire</b> <b></b></p>
<p><a href="http://news.bbc.co.uk/2/hi/uk_news/england/devon/8176760.stm">Napoli salvage is declared over</a>    <br />BBC News    <br />It was being taken to Portland in Dorset when the decision was taken to deliberately <b>ground</b> the <b>vessel</b> to try to prevent pollution damage to the world </p>
<p><a href="http://www.google.com/url?sa=X&amp;q=http://businessmirror.com.ph/home/economy/13931-barge-operators-ask-marina-to-exclude-them-from-cpc-requirement-pai-cover.html&amp;ct=ga&amp;cd=PllP5NT0e1Y&amp;usg=AFQjCNGnDA6zoe_apV6Yx53W8yMU9ikYwQ">Barge operators ask Marina to exclude them from CPC requirement <b>&#8230;</b></a>    <br />Business Mirror    <br />“Not all <b>vessels</b> will meet an <b>accident</b>. That is why there should be an actuarial study and the same should be done per sector since financial responsibility</p>
<p><a href="http://www.insidegnss.com/node/1615">US Congress Working on 2010 Appropriations for Loran-C and eloran <b>&#8230;</b></a>    <br />Inside GNSS    <br />eloran also has strong support from the General Lighthouse Authorities (GLA) of the UK and Ireland (equivalent to USCG for <b>maritime safety</b>,</p>
<p><a href="http://www.maritimejournal.com/archive101/2009/august/ferries__and__short_sea_shipping/interferry_joins_imo_ro-pax_safety_review">Interferry joins IMO ro-pax <b>safety</b> review</a>    <br />Maritime Journal    <br />The expert group submitted an initial report to the IMO&#8217;s <b>Maritime Safety</b> Committee after meeting for the first time during the recent MSC 86 session in</p>
<h3>PIRACY/CRIME</h3>
<p><a href="http://www.google.com/url?sa=X&amp;q=http://blog.taragana.com/n/bill-requiring-cruise-lines-to-share-reports-of-on-board-crime-heads-for-vote-of-full-congress-125810/&amp;ct=ga&amp;cd=jV3TLoycm2U&amp;usg=AFQjCNHVZorS4nGb4Au47iA217FingdBiA">Bill requiring cruise lines to share reports of on-board crime <b>&#8230;</b></a>    <br />Gaea Times    <br />The Cruise <b>Vessel</b> Security and Safety Act tightens restrictions on an industry that has long evaded much scrutiny — in part because of the complexity of </p>
<h3>UNDER THE RADAR</h3>
<p><a href="http://blog.taragana.com/n/fire-destroys-replica-of-17th-century-dutch-flagship-a-major-tourist-attraction-125333/"><b>Fire</b> destroys replica of 17th-century Dutch flagship, a major <b>&#8230;</b></a>    <br />By Bureau News     <br /><b>Fire</b> destroys replica of 17th-century Dutch flagship, a major tourist attraction. Bureau News. July 30th, 2009. <b>Fire</b> guts replica of 17th-century tall <b>ship</b>. AMSTERDAM — <b>Fire</b> consumed a replica of the 17th-century flagship of the Dutch </p>
<p><a href="http://www.google.com/url?sa=X&amp;q=http://www.chicagotribune.com/news/local/chi-explosives-guy-north-zone-31jul31,0,5434086.story&amp;ct=ga&amp;cd=qQDymreROZ0&amp;usg=AFQjCNHsy0Gw2BFYws8hiKX7hqQQ-u8hvg">Expert gets in the middle of explosive situations</a>    <br /><b></b></p>
<p>Explosives expert James Dahn was asked by Chinese officials for advice on transporting fireworks after a powerful blast had ripped through a cargo ship bound from Singapore to Hamburg. One crewman was killed, and a spectacular fire burned for four days on the 900-foot vessel.   <br />That scenario could happen again, said Dahn of <a href="http://www.chicagotribune.com/topic/us/illinois/cook-county/rolling-meadows-PLGEO1001005011200000.topic">Rolling Meadows</a>, who will discuss the dangers such cargoes present at a <a href="http://www.chicagotribune.com/topic/crime-law-justice/international-law/united-nations-ORCUL000009.topic">United Nations</a> conference next month in <a href="http://www.chicagotribune.com/topic/intl/japan/tokyo-%28japan%29-PLGEO100100602011300.topic">Tokyo</a>.</p>
<h4><a href="http://www.maritimejournal.com/archive101/2009/july/online_news/mary_rose_grant_fully_approved">Mary Rose grant fully approved</a></h4>
<p>Celebrations to mark the 500th anniversary of Henry VIII’s accession to the throne this year have come to a fitting culmination with the announcement that the Heritage Lottery Fund (HLF) has recently given full approval for a £21m grant to the Mary Rose Trust. </p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/maritime/blog/maritime-safety-security-news-31-july-2009/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Casualty Outlook</title>
		<link>http://gcaptain.com/maritime/blog/casualty-outlook-2/</link>
		<comments>http://gcaptain.com/maritime/blog/casualty-outlook-2/#comments</comments>
		<pubDate>Thu, 30 Jul 2009 21:20:22 +0000</pubDate>
		<dc:creator>bob.couttie</dc:creator>
				<category><![CDATA[Casualty Outlook]]></category>

		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/casualty-outlook-2/</guid>
		<description><![CDATA[It’s been a week of fire, ferries and fortunate rescues, as well as tragedies.
Sweden saw the collision of two ferries, Gotlandia and Gotlandia II, at Nynäshamn port, south of Stockholm, possibly with the help of a small barge. Some 15 injuries were reported. A boiler room fire, apparently in the thermal heating unit (thermal heating?! [...]]]></description>
			<content:encoded><![CDATA[<p>It’s been a week of fire, ferries and fortunate rescues, as well as tragedies.</p>
<p>Sweden saw the collision of <a href="http://www.sr.se/cgi-bin/International/nyhetssidor/artikel.asp?ProgramID=2054&amp;format=1&amp;artikel=2988863">two ferries, <em>Gotlandia</em> and <em>Gotlandia II</em>, at Nynäshamn</a> port, south of Stockholm, possibly with the help of a small barge. Some 15 <a href="http://www.offshoreinjuries.com/PracticeAreas/Offshore-Marine-Vessel-Injuries.asp">injuries</a> were reported. A boiler room fire, apparently in the thermal heating unit (<em>thermal heating?! BDC</em>) forced the ferry <em>Atlantic Vision</em> to return to port in Nova Scotia, the second fire on the vessel since December last year.  A smaller ferry, <em>Captain</em>, grounded on a boat launch on Balboa Island on July 21.</p>
<p>Apart from <em>Atlantic Vision,</em> fire ranged far and wide in the past seven days. Fire gutted a passenger-cum-cargo ship, <em>MV Pemba</em> at <a href="http://thecitizen.co.tz/newe.php?id=14044">Dar es Salaam habour</a>. Thiswas the second fire and fourth incident in Tanzanian waters in the past four months, which included a capsize with loss of life and another in which, says a Tanzanian report, “its backdoor fell off while in the Indian Ocean”. Three men were rescued, one sent to hospital, when the shrimp boat <em>Kemo Sabay</em> caught fire off Protection Island, in the Strait of Juan de Fuca and the somewhat larger,2,545 grt, containership <em>Forum Avarua </em>suffered an engine room fire.</p>
<p>Two whale stories, one of which got worldwide coverage: Princess Cruise Lines’ Sapphire Princess, went inadvertently spear fishing with its bulbous bow and came up with a 70-tonne, rare, fin whale. At the other end of the scale of size and intelligence were the <a href="http://www.theprovince.com/news/Whale+watching+boat+sinks+Mayne+Island/1821788/story.html">32 passengers aboard the whale-watching boat which sank</a> off Mayne Island, Canada – none were wearing lifejackets in the open inflatable.</p>
<p>Thanking their lucky stars this week were two seafarers from the coal carrier <em>United Treasure </em><a href="http://www.illawarramercury.com.au/news/local/news/general/rescued-sailors-thank-the-illawarra/1578127.aspx">whose scaffold collapsed</a> while they were painting a hold, resulting in four badly broken legs, a broken arm and serious spinal bruising. Also in the lotof the fortunate were the 20 crew of the bulker <em>Ioannis NK,</em> rescued by helicopter after the ship capsized and sank 98 nautical miles off Cape Columbine on the West Coast, near to Saldanha Bay.</p>
<p>Inevitably, there were the aftermaths of tragedy: the burial of the first victim of the Ag<a href="http://www.pressandjournal.co.uk/Article.aspx/1328463?UserKey=">uila sinking</a> and the <a href="http://www.upstreamonline.com/live/article183985.ece">naming of an oilman</a> whose body was found after he went missing from the Brent Delta platform in the North Sea.</p>
<p>Be safe out there</p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/maritime/blog/casualty-outlook-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Casualty Outlook</title>
		<link>http://gcaptain.com/maritime/blog/casualty-corner-2/</link>
		<comments>http://gcaptain.com/maritime/blog/casualty-corner-2/#comments</comments>
		<pubDate>Thu, 23 Jul 2009 12:36:45 +0000</pubDate>
		<dc:creator>bob.couttie</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/casualty-corner-2/</guid>
		<description><![CDATA[
Captain  Hristo Papukchiev, pictured right, is an unhappy man. How unhappy? Until April this year he was lead investigator for the Bulgarian Maritime Administration. Then, just a day after being tasked with leading the re-investigation of the sinking of the m/v Vanessa in a storm last year, he resigned.
So far, his story has only appeared [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://gcaptain.com/maritime/blog/wp-content/uploads/2009/07/image.png"><img style="border-right-width: 0px;border-top-width: 0px;border-bottom-width: 0px;margin-left: 0px;border-left-width: 0px;margin-right: 0px" src="http://gcaptain.com/maritime/blog/wp-content/uploads/2009/07/image_thumb.png" border="0" alt="image thumb Casualty Outlook" width="230" height="244" align="right" title="Casualty Outlook" /></a></p>
<p>Captain  Hristo Papukchiev, pictured right, is an unhappy man. How unhappy? Until April this year he was lead investigator for the Bulgarian Maritime Administration. Then, just a day after being tasked with leading the re-investigation of the sinking of the <em>m/v Vanessa </em>in a storm last year, he resigned.</p>
<p>So far, his story has only appeared in a Bulgarian-language magazine, Klass, online at <a href="http://www.maritimeaccident.org/idess/bulgaria-a-man-resigned/">Maritime Accident Casebook</a>, and now, of course, here at gCaptain.</p>
<p>He joined the administration in October 2008 at about the same time as the sinking of the <em>m/v Tolstoy </em>with the loss of eight of her 10 crew, which became his first investigation. Despite attempts at delays interference he and his team completed the investigation and filed reports with EMSA and the IMO.</p>
<p>There were serious regulatory shortfalls revealed in the <em>Tolstoy </em>report – she had been deleted from the North Korean registry a year before the incident but still flew the DPRK flag, as well as shortcomings in the Bulgarian SAR system,which in fact was not in line with the description Bulgaria logged with the IMO.</p>
<p><a href="http://gcaptain.com/maritime/blog/wp-content/uploads/2009/07/image1.png"><img style="border-right-width: 0px;border-top-width: 0px;border-bottom-width: 0px;margin-left: 0px;border-left-width: 0px;margin-right: 0px" src="http://gcaptain.com/maritime/blog/wp-content/uploads/2009/07/image_thumb1.png" border="0" alt="image thumb1 Casualty Outlook" width="244" height="121" align="left" title="Casualty Outlook" /></a> Papukchiev believed there would be calls for action in response to the report.</p>
<p>Instead the report was shelved and no action taken. Neither the IMO nor EMSA encouraged Bulgaria to put its house in order. Today he suggests that if you’re in trouble in the Bulgarian area of responsibility it’s better to depend on a passing ship than the Bulgarian SAR system, which didn’t get underway until up to 10 hours after Tolstoy was on the seabed and around five hours after her EPIRB was activated. In fact the only two seafarers to survive the <em>Tolstoy </em>did so because they were picked up by a passing yacht.</p>
<p>No report has yet been issued on the sinking of <em>m/v Vanessa, </em>which lies undisturbed and unexamined in shallow waters. After Papukchiev accepted the task of re-investigating the loss, which cost the lives of nine crewmembers and a Ukrainian pilot with just one survivor, he was asked by a colleague “Who paid you to re-open the Vanessa case?”.</p>
<p>Says Papukchiev “I was shocked at first, but then started to ponder on the investigations done so far, the report that had been prepared long before my appointment, although not approved &#8230; Well, did this mean that its authors had been paid? Where were they now? These questions were my greatest concern, namely the Vanessa’s case had begun with a false start &#8230; Anyway, I was appointed to proceed with independent investigation because the society expected the truth to come to light. These investigations should be done very precisely and objectively, with facts prevailing not hypotheses. When there are no conditions for an unbiased and objective investigation, a true professional is obliged to resign.”</p>
<p>Bear that in mind if you’re in Bulgarian waters. We’re covering this <a href="http://www.maritimeaccident.org/idess/bulgaria-a-man-resigned/">story in depth at MAC</a>.</p>
<p>Two recent casualties with particular lessons are the Scots scallop dredger Aquila on July 20 with the loss of three lives and the <em>Asian Forest,</em> which foundered 15 miles off Mangalore, fortunately without loss of life.</p>
<p>Commercial fishermen are often reluctant to wear lifejackets, feeling restricted in them, which almost certainly cost the lives of three of the four men aboard the Aquila. There is certainly an argument that commercial fishermen may benefit from a specially designed lifejacket but that’s not an argument to go without one.</p>
<p><em>Asian Forest </em>foundered almost certainly because of liquefaction of her cargo of iron ore fines. It isn’t a cargo normally thought to be subject to liquefaction but at this time of year, with the South West Monsoon, heavy rains are soaking into iron ore fines stored in the open to await shipment  in New Mangalore and the West Coast of India, raising the moisture content.</p>
<p>It has been reported that often the moisture content stated on the certificate given by shippers bears no resemblance to the moisture content of the cargo at loading. If you&#8217;re loading such cargoes in South West India exercise extreme caution.</p>
<p>Stay safe out there.</p>
<p>&#8211;</p>
<p>Were you injured while working offshore?  Know your rights! Speak to <a title="Maritime Injury Attorney" href="http://www.offshoreinjuries.com/">maritime injury attorney</a> today.</p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/maritime/blog/casualty-corner-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Master Of The Alien Invasion &#8211; Captain First to be Charged Under US Anti-Invasive Species Law</title>
		<link>http://gcaptain.com/maritime/blog/master-of-the-alien-invasion/</link>
		<comments>http://gcaptain.com/maritime/blog/master-of-the-alien-invasion/#comments</comments>
		<pubDate>Fri, 17 Jul 2009 10:14:00 +0000</pubDate>
		<dc:creator>bob.couttie</dc:creator>
				<category><![CDATA[Maritime Law]]></category>
		<category><![CDATA[bob couttie]]></category>
		<category><![CDATA[captain]]></category>
		<category><![CDATA[law]]></category>
		<category><![CDATA[Master Mariner]]></category>
		<category><![CDATA[New Orleans]]></category>
		<category><![CDATA[USCG]]></category>

		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/master-of-the-alien-invasion/</guid>
		<description><![CDATA[Master Of The Alien Invasion
Chief Officer Charles P. Posas, has scored a dubious first in legal history. He is the first person to be charged with a violation of the US Anti-Invasive Species Law in addition to two felony counts of lying to the Coast Guard and violating recordkeeping laws. His superior, Captain Panagiotis Lekkas, [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;"><strong>Master Of The Alien Invasion</strong></p>
<p>Chief Officer Charles P. Posas, has scored a dubious first in legal history. He is the first person to be charged with a violation of the US Anti-Invasive Species Law in addition to two felony counts of lying to the Coast Guard and violating recordkeeping laws. His superior, Captain Panagiotis Lekkas, is charged with violating anti-pollution laws, <a title="Maritime Injury Lawyer" href="http://www.offshoreinjuries.com/">ship safety laws</a> and obstructing a US Coast Guard investigation. Both have pleaded guilty in a Federal court in New Orleans, sentencing for both officers defendants is set for 14 October, 2009.</p>
<p>Says the US Department of Justice: “Posas is the first individual ever charged under the anti-invasive species law, a law designed to mitigate the introduction of marine invasive species into waters of the United States. Aquatic nuisance species are non-indigenous species that threaten the diversity or abundance of native species or the ecological stability of infested waters.</p>
<p>“Lekkas, who was the highest ranking officer aboard the ship, pleaded guilty to one count of violating the Act to Prevent Pollution from Ships, one count of obstruction of justice and two counts of violating the Ports and Waterways Safety Act. Posas, who served as the vessel’s chief officer, pleaded guilty to one count of false statement and one count of violating the Nonindigenous Aquatic Nuisance and Prevention Control Act.”<span id="more-9339"></span></p>
<p>Their vessel, <em>M/V</em> <em>Theotokos</em>, is owned by Liberia-based Mirage Navigation Corporation and managed by Polembros Shipping Limited.</p>
<p>In the summer of 2008, on passage from the Suez Canal to China, Lekkas and Posas suspected that the aftpeak ballast tank was leaking, but the crew was unable to confirm a leak during an inspection. Later, while at a dock, offloading cargo in China, Lekkas and Posas saw a crack of about 60 centimetres in the ship’s rudder stem. It was evident that water had passed through the crack because water was streaming out of it from inside of the ship. Lekkas reported the crack to company personnel, but failed to write a written report. Lekkas did not report it to the Coast Guard until he was confronted by Coast Guard inspectors in New Orleans.</p>
<p>In court documents, Lekkas admitted that he knew the crack could have adversely affected the safety and safe handling and operation of the vessel. No repairs were undertaken on the rudder stem crack until the Coast Guard ordered it repaired upon its discovery.</p>
<p>The Port and Waterways Safety Act, PWSA, requires that a vessel operator must report all hazardous conditions to the Coast Guard prior to arrival in a US port. Under the PWSA regulations, a hazardous condition does not have to be a definitive danger or imminent threat, but need only be a condition that may adversely affect the safety of any vessel, bridge, structure or shore area or the environmental quality of any port, harbour or navigable waterway of the United States..</p>
<p>The  US Coast Guard has notification processes in place for vessels arriving at US ports that have identified hazardous conditions onboard, such as excessive leaks and major equipment malfunctions. A vessel operator has several options available, including notifying the Coast Guard 96 hours prior to arrival of the hazardous condition or contacting the applicable ports’ 24-hour Sector Command Center or Vessel Traffic Service.</p>
<p>Through further investigation, the Coast Guard also found fuel was leaking, or &#8220;migrating&#8221;, from the deep fuel tanks into the forepeak ballast tank. Directly astern of the forepeak tank were two fuel tanks, known as the deep fuel tanks.</p>
<p>In mid-September 2008, Lekkas and Posas learned that fuel oil may have been leaking into the forepeak ballast tank because it was reported that the sounding tapes were dirty with oil. After opening the tank’s hatch, two inspections confirmed the presence of oil in the forepeak tank. Following this discovery, Captain Lekkas ordered the crew to undertake a cleaning operation that initially involved skimming the surface of the water in order to remove the oil. In order to facilitate further cleaning, Lekkas ordered the level of the liquid in the tank lowered by pumping it directly overboard through the ballast pump. As the liquid level was lowered the crew could clean more of the tank, with the cleaning operation expanding to rags and a portable pump. The discharged ballast liquid was contaminated with oil.</p>
<p>The Act to Prevent Pollution from Ships and its regulations require that discharges from the machinery spaces of a cargo ship must be fully and accurately recorded in the oil record book. This obligation extends to emergency, accidental, or other exceptional discharges of oil and oily mixtures. Lekkas ordered the ballast discharges and counter-signed each page of the oil record book, certifying its accuracy. However, none of the contaminated ballast water discharges were recorded in the Oil Record Book.</p>
<p>When the vessel was about two days out from arriving in New Orleans, in late September 2008, it was clear that oil was continuing to leak into the forepeak tank. Prior to entering the Mississippi River and about a day out from New Orleans, Lekkas ordered two fitters to fabricate and install an obstruction device onto the forepeak tank’s sounding tube so that during Coast Guard inspections, when taking a sounding, the results would only reveal water and not the presence of oil in the tank. The obstruction device consisted of a rubber hose with a metal stopper at the bottom end. Before being affixed to the sounding tube, the rubber hose was partially filled with water.</p>
<p>On Oct. 1, 2008, the Coast Guard boarded the <em>M/V Theotokos</em> near New Orleans in order to inspect the ship. During the inspection, the Coast Guard oversaw the sounding of the forepeak tank which indicated the presence of water in the tank but did not reveal the oil. Later, as part of the inspection, the Coast Guard had the crew open the hatch to the forepeak tank which revealed approximately one meter of oil in the tank. During the initial inspection, confined spaces safety regulations prevented the Coast Guard inspectors from retrieving the obstruction device. Although the inspection lasted another two days, Lekkas ordered the fitters to remove the rubber hose from the tank and restore the sounding tube to its original condition. The removal occurred before the Coast Guard had an opportunity to enter the tank.</p>
<p>In addition to the obstruction regarding the sounding pipe, Lekkas admitted in court documents that he knew about the fuel leak into the forepeak tank well before coming to New Orleans and that he chose not to report the leaks to the Coast Guard. Lekkas further admitted that the fuel migration may have adversely affected the safety of the <em>M/V Theotokos</em> or the environmental quality of US ports and shores because the oil contamination in the ballast system meant that captain could not have utilized the ballast system, with its attendant direct overboard discharges, without polluting the marine environment.</p>
<p>Additionally, during the inspection, a Coast Guard inspector asked to see complete ballast records for the <em>Theotokos</em>. Posas responded by physically handing the inspector a copy of the 27 September, 2008, ballast report, which is a report of soundings and volumes of water in the ballast system. Posas prepared, signed and maintained these reports as part of his duties as chief officer. In court documents Posas admitted, that at the time he presented the ballast report to the Coast Guard inspector, he knew that the form was false.</p>
<p>Maintenance of accurate ballast water records is required under Ballast Water Management for Control of Nonindigenous Species regulations promulgated under the Nonindigenous Aquatic Nuisance Prevention and Control Act.</p>
<p>&#8220;Invasive marine species are a serious problem that can be transmitted in the ballast water of oceangoing vessels. Today’s pleas should act as a warning to industry and crewmembers alike that we will investigate and prosecute those who ignore not only pollution laws but those laws designed to protect native species,&#8221; said John C. Cruden, Acting Assistant Attorney General for the Justice Department’s Environment and Natural Resources Division.</p>
<p>US Attorney Jim Letten noted, &#8220;The message should be clear that this office, in conjunction with its partnership with the US Coast Guard, the Department of Justice Environmental Crimes Section and all its law enforcement partners, will vigorously prosecute individuals who impede or obstruct the US Coast Guard’s mission and pollute our marine environment.&#8221;</p>
<p>&#8220;This case clearly demonstrates the Coast Guard’s commitment to work with our interagency partners to aggressively enforce all maritime anti-pollution and safety of life at sea laws. The breadth and magnitude of the investigation that underpinned the charges brought forth is a testament to the dedication of all persons who were involved in resolving this matter including the Coast Guard Investigative Service, the US Department of Justice‘s Environmental Crime Section, and the US Attorney for the Eastern District of Louisiana,&#8221; said Rear Admiral Mary Landry, Eighth District Coast Guard commander.</p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/maritime/blog/master-of-the-alien-invasion/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
