<?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; Fire Incidents</title>
	<atom:link href="http://gcaptain.com/tag/fire-incidents/feed/" rel="self" type="application/rss+xml" />
	<link>http://gcaptain.com</link>
	<description></description>
	<lastBuildDate>Fri, 10 Feb 2012 18:01:27 +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>Arctic Cruise Ship Disaster &#8211; The Prinsendam&#8217;s Effect On Coast Guard Response</title>
		<link>http://gcaptain.com/cruise-liner-prinsendam-arctic/?38805</link>
		<comments>http://gcaptain.com/cruise-liner-prinsendam-arctic/?38805#comments</comments>
		<pubDate>Tue, 31 Jan 2012 15:22:05 +0000</pubDate>
		<dc:creator>gCaptain Staff</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[Fire Incidents]]></category>
		<category><![CDATA[USCG]]></category>
		<category><![CDATA[Cruise Ship]]></category>
		<category><![CDATA[search and rescue]]></category>

		<guid isPermaLink="false">http://gcaptain.com/?p=38805</guid>
		<description><![CDATA[With the Costa Concordia disaster headlining global news the questions most asked by mariners is: How will that disaster change the cruise ship industry? For insight into this question we [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://gcaptain.com/wp-content/uploads/2012/01/cruise-ship-Prinsendam-in-the-Gulf-of-Alaska.jpeg"><img class="alignright  wp-image-38806" title="cruise ship Prinsendam in the Gulf of Alaska" src="http://gcaptain.com/wp-content/uploads/2012/01/cruise-ship-Prinsendam-in-the-Gulf-of-Alaska.jpeg" alt="cruise ship Prinsendam in the Gulf of Alaska" width="448" height="306" /></a>With the <a href="http://gcaptain.com/tag/costa-concordia/">Costa Concordia disaster </a>headlining global news the questions most asked by mariners is: <em>How will that disaster change the cruise ship industry?</em></p>
<p>For insight into this question we bring you an article by the US Coast Guard on how a mostly forgotten tragedy changed the face of future rescue operations in this country.</p>
<p>Thirty-one years ago the Coast Guard led one of the nation’s largest search and rescue cases when the 519 passengers and crew of the Dutch cruise ship Prinsendam were forced to abandon ship more than 150-miles off the coast of Alaska after an engine room fire spread throughout the vessel.</p>
<p>Over the course of 24 hours, Coast Guard Cutters <a href="http://www.uscg.mil/pacarea/cgcboutwell/">Boutwell</a>, <a href="http://www.uscg.mil/history/webcutters/CutterAccidents.asp">Woodrush</a> and <a href="http://www.uscg.mil/pacarea/cgcmellon/history5.asp">Mellon</a> as well as rescue aircraft deployed from Air Stations <a href="http://www.uscg.mil/d17/airstasitka/">Sitka</a> and <a href="http://www.uscg.mil/d17/airstakodiak/">Kodiak</a> would work side-by-side with the U.S. Air Force, Canadian navy and an <a href="http://www.amver.com/">AMVER</a>-tasked tanker to rescue all hands from 12 to 15 foot seas and 25 to 30 knot winds generated by a nearby Arctic typhoon.</p>
<div id="attachment_20518">
<div id="attachment_38884" class="wp-caption aligncenter" style="width: 570px"><a href="http://gcaptain.com/wp-content/uploads/2012/01/Prinsendam005-560x375.jpg"><img class="size-full wp-image-38884" title="Prinsendam005-560x375" src="http://gcaptain.com/wp-content/uploads/2012/01/Prinsendam005-560x375.jpg" alt="" width="560" height="375" /></a>
<p class="wp-caption-text">USCG Photo</p>
</div>
<p>The Prinsendam was a 427-foot long cruise liner built in 1973. The liner was transiting through the Gulf of Alaska, approximately 120 miles south of Yakutat, Alaska, at midnight Oct. 4, 1980, when fire broke out in the engine room.</p></div>
<p>With conditions too dangerous for the deployment of small boats from the cutters, survivors were forced to climb aboard the tanker and cutters with the help of two Air Force pararescuemen while hypothermic survivors were ferried to shore by rescue helicopters. The helicopters would then refuel and head back out to the scene for their next load of passengers.</p>
<p>In the immediate aftermath of the rescue, the Coast Guard identified areas of improvement in <a href="http://www.uscg.mil/lantarea/docs/USCG%20Top%2010%20Rescues.doc">search and rescue operations</a> which would save tens of thousands of lives in the decades ahead.</p>
<p>In the findings of the Prinsendam investigation, Rear Adm. Richard Knapp noted, “The training and expertise of the Air Force pararescuemen was responsible for the survival of passengers …. It is notable that we were forced to rely on another agency to provide these personnel. I recommend we develop a similar, highly-trained, well-equipped rescue elite.”</p>
<p>Those “rescue elite” would of course become the <a href="http://www.gocoastguard.com/find-your-career/enlisted-opportunities/enlisted-ratings-descriptions/aviation-survival-technician-(ast)">aviation survival technicians</a> of the Coast Guard <a href="http://www.uscg.mil/history/articles/USCG_Rescue_Swimmer_History.asp">rescue swimmer program</a>.</p>
<p>Another deficiency cited in the investigation was the need for rescue helicopters to return to shore to refuel while survivors remained in the water. The critical role rescue helicopters play during extended search and rescue cases would ultimately lead to the helicopter in-flight refueling capability now standard on Coast Guard rescue helicopters.</p>
<div id="attachment_20519">
<div id="attachment_38885" class="wp-caption alignright" style="width: 310px"><a href="http://gcaptain.com/wp-content/uploads/2012/01/Prinsendam007-560x376.jpg"><img class="size-medium wp-image-38885" title="Prinsendam007-560x376" src="http://gcaptain.com/wp-content/uploads/2012/01/Prinsendam007-560x376-300x201.jpg" alt="Prinsendam" width="300" height="201" /></a>
<p class="wp-caption-text">U.S. Coast Guard photo.</p>
</div>
<p>The rescue of the Prinsendam was particularly significant because of the distance traveled by the rescuers, the coordination of independent organizations and the fact that all 519 passengers and crew were rescued without loss of life or serious injury.</p></div>
<p>These new capabilities would more than prove their value in future cases ranging from the Coast Guard response to Hurricane Katrina to another Arctic rescue when the Alaska Ranger was lost at sea.</p>
<p>At a time when America considers its Arctic future and the role the Coast Guard will play in protecting American lives and national interests in the often harsh conditions found above the Arctic Circle, the Prinsendam rescue serves as a stark reminder of the necessity for a robust Coast Guard presence in America’s Arctic waters.</p>
<hr />
<p><em>This article was originally written by  <a title="Visit Christopher Lagan’s website" href="http://coastguard.dodlive.mil/author/clagan/" rel="external">Christopher Lagan</a> and <em>Ademide Adedokun for the blog <a href="http://coastguard.dodlive.mil/2011/10/history-arctic-rescue-changes-face-of-coast-guard-operations/">CG Compass</a>. </em></em></p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/cruise-liner-prinsendam-arctic/?38805/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Explosion Aboard South Korean Tanker Kills Five, Others Still missing</title>
		<link>http://gcaptain.com/explosion-aboard-south-korean/?37566</link>
		<comments>http://gcaptain.com/explosion-aboard-south-korean/?37566#comments</comments>
		<pubDate>Sun, 15 Jan 2012 18:00:10 +0000</pubDate>
		<dc:creator>gCaptain Staff</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Fire Incidents]]></category>
		<category><![CDATA[tragic_incident]]></category>

		<guid isPermaLink="false">http://gcaptain.com/?p=37566</guid>
		<description><![CDATA[An explosion tore through a South Korean tanker on Sunday morning killing five crew members and leaving 6 others missing.   The unexplained explosion occurred off the coast of Incheon [...]]]></description>
			<content:encoded><![CDATA[<div id="attachment_37567" class="wp-caption alignright" style="width: 310px"><img class="size-medium wp-image-37567" title="doola-no-3" src="http://gcaptain.com/wp-content/uploads/2012/01/s-korean-tanker-sinks-in-yellow-sea-3-crewmen-dead-1326614537-7364-300x225.jpg" alt="" width="300" height="225" />
<p class="wp-caption-text">Doola No. 3 tanker</p>
</div>
<p>An explosion tore through a South Korean tanker on Sunday morning killing five crew members and leaving 6 others missing.   The unexplained explosion occurred off the coast of Incheon located on the western shore of South Korea after the vessel unloaded a cargo of oil products.  Five people aboard the ship were rescued.</p>
<p>Photos of the tanker, the 4191-ton <em>Doola No. 3</em>, show that the vessel was nearly torn in half by the explosion and was left partially submerged.  The explosion took place about three miles north of Jawol Island near Incheon at around 8:05 a.m. local time, the Coast Guard said.</p>
<p>The <em>Doola No. 3</em>, which usually carries refined petroleum products and chemicals, was carrying 80 tons of Bunker-C oil and 40 tons of diesel oil for fuel when it exploded, according to a coast guard statement.</p>
<p>&#8220;The vessel usually transports diesel, but this time it carried gasoline. We are now examining whether it had any relation to the explosion,&#8221; an official from Doola Shipping, the owner of the vessel, said in a statement that was obtained by <a href="http://english.yonhapnews.co.kr/national/2012/01/15/29/0302000000AEN20120115003300315F.HTML" target="_blank">Yonhap news agency</a>.</p>
<p>Yonhap has <a href="http://english.yonhapnews.co.kr/national/2012/01/15/29/0302000000AEN20120115003300315F.HTML" target="_blank">also reported</a> that the ship&#8217;s captain said the explosion may have been caused by static electricity that ignited gasoline vapors from an onboard tank where 11 crew members were working before the blast.</p>
<p>A total of 11 Korean and 5 Myanmarese were aboard the <em>Doola No. 3</em>, the Coast Guard said.</p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/explosion-aboard-south-korean/?37566/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>UPDATE 2: US Air Force to the Rescue!  C-130 Departs McMurdo With Injured Korean Sailors</title>
		<link>http://gcaptain.com/force-rescue-starlifter-dispatched/?37196</link>
		<comments>http://gcaptain.com/force-rescue-starlifter-dispatched/?37196#comments</comments>
		<pubDate>Wed, 11 Jan 2012 23:44:04 +0000</pubDate>
		<dc:creator>gCaptain Staff</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Incidents]]></category>
		<category><![CDATA[Lifesaving Incidents]]></category>
		<category><![CDATA[Maritime News]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[antarctica]]></category>
		<category><![CDATA[Fire Incidents]]></category>
		<category><![CDATA[rescue]]></category>
		<category><![CDATA[tragic_incident]]></category>

		<guid isPermaLink="false">http://gcaptain.com/?p=37196</guid>
		<description><![CDATA[Update 2: 13 Jan 2012 A United States Airforce (USAF) C-130 Hercules aircraft departed McMurdo station at 12.35pm today (NZDT) with the 7 injured crew on board. Three of the [...]]]></description>
			<content:encoded><![CDATA[<div id="attachment_37338" class="wp-caption alignnone" style="width: 610px"><img class="size-full wp-image-37338" title="IMG_4225" src="http://gcaptain.com/wp-content/uploads/2012/01/IMG_4225.jpg" alt="US Air Force C-130 antarctica" width="600" height="400" />
<p class="wp-caption-text">Photo courtesy of the National Science Foundation</p>
</div>
<p><strong>Update 2: 13 Jan 2012</strong></p>
<blockquote><p>A United States Airforce (USAF) C-130 Hercules aircraft departed McMurdo station at 12.35pm today (NZDT) with the 7 injured crew on board. Three of the men are seriously injured.</p>
<ul>
<li>The aircraft’s ETA in Christchurch is 8.45pm this evening (NZDT).</li>
<li>The injured crew will be taken to Christchurch hospital on arrival for assessment and further treatment as required.</li>
<li>Note that photos and video are not available. The USAF advise there will be no media access or interviews when the aircraft lands in Christchurch.</li>
<li>RCCNZ’s role in the incident will come to an end once the aircraft lands in Christchurch</li>
</ul>
</blockquote>
<p><strong>UPDATE 13 Jan 2012</strong>:</p>
<blockquote><p>The USAF C-17 Globemaster III aircraft was unable to make its scheduled flight from Christchurch to McMurdo Base overnight because of weather conditions at the destination.</p>
<ul>
<ul>
<li>The <em><strong>Nathaniel B. Palmer</strong></em> carrying the injured crew has arrived at McMurdo, and the injured crew are being transferred by helicopter to the base.</li>
<li>They will be flown to Christchurch this afternoon (leaving approximately 12.15pm NZDT) on a special flight using a C-130 which was already at McMurdo. The flight is expected to arrive at Christchurch at around 8pm NZDT.</li>
</ul>
</ul>
</blockquote>
<p>(MARITIME NZ) A United States Airforce (USAF) C17 <del>Starlifter</del> Globemaster III aircraft will leave Christchurch tonight to help recover seven crew injured in a fire on board the Korean fishing vessel <em>Jeong Woo 2</em> in the Ross Sea early on Wednesday morning (NZDT).</p>
<p>The Rescue Coordination Centre New Zealand (RCCNZ) is currently working with a range of agencies to help facilitate the recovery of the seven injured men from the Korean vessel back to New Zealand for hospital treatment.</p>
<p>RCCNZ Search and Rescue Mission Coordinator Greg Johnston said attempts were being made to get a team, including Vietnamese and Indonesian interpreters, on board the aircraft, which was already on a scheduled flight due to leave Christchurch about 9.30pm today.</p>
<p>“Weather permitting, it’s expected that the USAF aircraft will get to McMurdo base about 2am tomorrow (Friday), arriving about the same time as the American research vessel <em>Nathaniel B Palmer</em>, which is currently making her way through the ice with the seven injured crew on board.</p>
<p>“The rescue mission is, however, dependent on the weather and sea conditions, with fog at McMurdo currently causing poor visibility. However, a back up aircraft, a LC 130 Hercules based at McMurdo, is also available if the larger C17 aircraft can’t take off.”</p>
<p>Mr Johnston said once both the vessel and the aircraft had reached McMurdo, the injured crew would be transferred to the aircraft and flown back to Christchurch for treatment.</p>
<p>“All going well, the aircraft will depart McMurdo about 5am, arriving back in New Zealand around 10am, but there are still a number of factors that could cause this to be delayed.”</p>
<p>Two of the seven injured men have received extensive burns (50% and 30% respectively), but have recovered consciousness, and five others have received lighter burns injuries. The <em>Nathaniel B Palmer </em>has medical staff and facilities on board to assess the injured crew’s medical needs, with advice that they are currently stable. The ship’s progress will depend on ice and weather conditions. Three crew have died in the fire.</p>
<p>In the meantime, the 30 surviving crew are all on board the <em>Jeong Woo 2</em>’s sister ship, the<em> Jeong Woo 3, </em>with plans for the vessel to rendezvous with the Korean ice-breaker the <em>Araon</em>, which will collect the crew and take them back to Lyttleton, with the ship estimated to arrive on January 19.</p>
<div id="attachment_37202" class="wp-caption alignnone" style="width: 580px"><img class="size-full wp-image-37202" title="Picture 1" src="http://gcaptain.com/wp-content/uploads/2012/01/Picture-129.png" alt="Jeong Woo 2 fire" width="570" height="378" />
<p class="wp-caption-text">Shot of the Jeong Woo 2 taken from the vessel Nathaniel B Palmer, Credit: Johnny Pierce/Nathaniel B Palmer</p>
</div>
<p>Once safe to do so, the wreck of the <em>Jeong Woo 2 </em>will be towed by its sister ship to a position north of 60 degrees south when her future will be decided.</p>
<p>The 51 metre fishing vessel <em>Jeong Woo 2 </em>caught fire in the Ross Sea about 2000 nautical miles (3704 kilometres) southeast of New Zealand and about 600 kilometres north-northeast of McMurdo Base.</p>
<p>A number of vessels responded to the vessel’s distress call, issued in the early hours of Wednesday morning (NZDT). The call was picked up by another Korean fishing vessel, <em>Hong Jin 707</em>, and relayed to RCCNZ by the New Zealand vessel <em>Antarctic Chieftain</em> just before 3am (NZDT) on 11 January.</p>
<div></div>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/force-rescue-starlifter-dispatched/?37196/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Antarctic Fishing Vessel Catches Fire Killing Three Crew, Injuring Others</title>
		<link>http://gcaptain.com/antartic-fishing-vessel-catches/?37120</link>
		<comments>http://gcaptain.com/antartic-fishing-vessel-catches/?37120#comments</comments>
		<pubDate>Wed, 11 Jan 2012 15:53:10 +0000</pubDate>
		<dc:creator>gCaptain Staff</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Maritime News]]></category>
		<category><![CDATA[Fire Incidents]]></category>
		<category><![CDATA[new zealand]]></category>
		<category><![CDATA[tragic_incident]]></category>

		<guid isPermaLink="false">http://gcaptain.com/?p=37120</guid>
		<description><![CDATA[A Korean fishing vessel caught fire early Wednesday morning in the Ross Sea, approximately 2,000 nautical miles southeast of New Zealand, killing three crew members and injuring several others.  The [...]]]></description>
			<content:encoded><![CDATA[<div id="attachment_37125" class="wp-caption alignright" style="width: 360px"><img class="size-full wp-image-37125" title="800px-Antarctica_Nathaniel_B_Palmer" src="http://gcaptain.com/wp-content/uploads/2012/01/800px-Antarctica_Nathaniel_B_Palmer.jpg" alt="" width="350" height="263" />
<p class="wp-caption-text">The R/V Nathaniel B Palmer icebreaker. Photo: Wiki Commons</p>
</div>
<p>A Korean fishing vessel caught fire early Wednesday morning in the Ross Sea, approximately 2,000 nautical miles southeast of New Zealand, killing three crew members and injuring several others.  The RCCNZ says that as many as 40 crew members were on<em></em>board when it caught fire.</p>
<p>The vessel, the 51 meter <em>Jeong Woo 2</em>, sent out a distress call during the early hours of Wednesday morning which was picked up by another Korean fishing vessel in the area and then relayed to officials from the Rescue Coordination Centre New Zealand (RCCNZ). A number of vessels responded to the call including the two Korean fishing vessels, the <em>Jeong Woo 3</em> and <em>Hong Jin 707</em>, were able to reach the <em>Jeong Woo 2</em> and evacuate the crew from the burning vessel.</p>
<p>Three of the crew members were reported missing and presumed dead after the fire tore through the accomodation block of the vessel.  Two others are understood to have suffered extensive burn injuries and another five crew members are also injured with less serious burns, RCCNZ says.</p>
<p>The RCCNZ later confirmed that the injured crew members from the burning vessel had been transferred to the United States research vessel <em>Nathaniel B Palmer</em>, which has medical staff and facilities on board.  The vessel is now sailing to McMurdo Base about 600 kilometers to the southwest.  The trip is expected to take between 24 and 30 hours, depending on ice and weather conditions.</p>
<p>Search and Rescue Mission Coordinator Geoff Lunt said the <em>Nathaniel B Palmer</em> reported on Wednesday evening that the vessel was well alight from bow to stern, but still on an even keel.</p>
<p>It&#8217;s been a busy couple weeks for rescue coordinators at RCCNZ.  In December, <a href="http://gcaptain.com/russian-fishing-vessel-crew-water/?35548">a fishing vessel with 32 crew began taking on water</a> in the same general area of the Ross Sea and it took <a href="http://gcaptain.com/arrives-stricken-fishing-vessel/?36045">10 days for the rescues to reach the stranded ship</a> due to ice conditions.   Earlier, in 2010, a <a href="http://gcaptain.com/korean-fishing-vessel-sinks-southern/?19141">Korean fishing vessel sank with a crew of 42 while fishing in the Southern Ocean</a>. Only 20 were rescued in that incident.</p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/antartic-fishing-vessel-catches/?37120/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Russian Ballistic Missile Submarine Catches Fire</title>
		<link>http://gcaptain.com/russian-ballistic-missile-submarine/?36204</link>
		<comments>http://gcaptain.com/russian-ballistic-missile-submarine/?36204#comments</comments>
		<pubDate>Fri, 30 Dec 2011 14:15:56 +0000</pubDate>
		<dc:creator>gCaptain Staff</dc:creator>
				<category><![CDATA[Engineering News]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[Fire Incidents]]></category>
		<category><![CDATA[Incidents]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Russian Navy]]></category>
		<category><![CDATA[submarines]]></category>

		<guid isPermaLink="false">http://gcaptain.com/?p=36204</guid>
		<description><![CDATA[MOSCOW (Dow Jones)&#8211;Some crew members were still aboard a Russian nuclear submarine ablaze early Friday after its hull caught fire during shipyard repairs but there was no radiation threat, officials said. &#8220;A [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignnone size-full wp-image-36205" title="Russian Submarine" src="http://gcaptain.com/wp-content/uploads/2011/12/Russian-Submarine.jpg" alt="russian submarine Yekaterinburg" width="496" height="404" /></p>
<p>MOSCOW (Dow Jones)&#8211;Some crew members were still aboard a Russian nuclear submarine ablaze early Friday after its hull caught fire during shipyard repairs but there was no radiation threat, officials said.</p>
<p>&#8220;A part of the crew is on board the submarine and is monitoring the temperature and carbon dioxide parameters in all sections of the boat,&#8221; RIA Novosti quoted a defense ministry statement as saying.</p>
<p>The 11,740-metric ton Yekaterinburg, one of Russia&#8217;s most powerful nuclear submarines, was undergoing repairs in the northern region of Murmansk near Norway when some wooden structures in the shipyard caught fire Thursday.</p>
<p>The flames spread quickly to the outer hull of the submarine and continued to burn overnight despite a massive salvage operation involving 11 fire brigades along with several helicopters and a navy fire boat.</p>
<p>Nine firemen were suffering from smoke inhalation, an emergency situations ministry source was quoted as saying.</p>
<p>The local emergencies ministry said the radiation levels on board the vessel were normal and posed no threat because its two nuclear reactors had been switched off before repairs.</p>
<p>&#8220;These parameters are within the limits of natural radiation fluctuation levels. There is no threat to the population,&#8221; the Murmansk emergencies ministry said in a statement.</p>
<p>The submarine was also stripped of its 16 inter-continental ballistic missiles and conventional rockets, defense officials said.</p>
<p>It was not immediately clear how many crew members were aboard the boat. Russian news reports said the Yekaterinburg can carry up to 140 seamen.</p>
<p>The flames were first reported to be contained overnight but defense officials said the craft continued to smoulder Friday morning and that fire fighters were still working on the scene.</p>
<p>&#8220;There are no open flames,&#8221; a defense ministry statement said.</p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/russian-ballistic-missile-submarine/?36204/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fatal Fire Aboard Russian Nuclear Icebreaker</title>
		<link>http://gcaptain.com/fatal-fire-aboard-russian-nuclear/?35516</link>
		<comments>http://gcaptain.com/fatal-fire-aboard-russian-nuclear/?35516#comments</comments>
		<pubDate>Thu, 15 Dec 2011 18:14:18 +0000</pubDate>
		<dc:creator>gCaptain Staff</dc:creator>
				<category><![CDATA[Maritime News]]></category>
		<category><![CDATA[Fire Incidents]]></category>
		<category><![CDATA[Icebreaker]]></category>

		<guid isPermaLink="false">http://gcaptain.com/?p=35516</guid>
		<description><![CDATA[A fire broke out aboard the Russian nuclear-powered icebreaker, Valgach, killing two crew members and seriously injuring one.  The fire occurred early Thursday morning as the icebreaker was escorting ship [...]]]></description>
			<content:encoded><![CDATA[<div id="attachment_35518" class="wp-caption alignnone" style="width: 610px"><img class="size-full wp-image-35518 " title="170257334" src="http://gcaptain.com/wp-content/uploads/2011/12/170257334.jpg" alt="" width="600" height="340" />
<p class="wp-caption-text">© Photo Vaygach nuclear icebreaker archive via RIA Novosti</p>
</div>
<p>A fire broke out aboard the Russian nuclear-powered icebreaker, <em>Valgach</em>, killing two crew members and seriously injuring one.  The fire occurred early Thursday morning as the icebreaker was escorting ship through Yenisei Bay in northern Siberia.</p>
<p>The fire reportedly tore through the living quarters of the ship and an initial investigation said it was likely started by an electical short circuit.  Officials said in a statement that the nuclear reactor aboard the ship was not damaged in the fire and no radiation was leaked.  The fire has since been extinguished.</p>
<p>Earlier this year, a sister ship, the Taimyr, leaked radioactive cooling water from its reactor in the same area and had to be escorted to Murmansk for repairs, according to <a href="http://www.themoscowtimes.com/news/article/fire-aboard-nuclear-icebreaker-kills-2/449984.html" target="_blank">a report by the Moscow Times</a>.</p>
<p>You can read the official statement from the ship owner <a href="http://www.rosatomflot.ru/index.php?menuid=23&amp;date=2011-12-0&amp;newsid=389" target="_blank">HERE</a> (if you can read Russian)</p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/fatal-fire-aboard-russian-nuclear/?35516/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tragedy Strikes at Keppel Shipyard, 5 Workers Killed in Fire</title>
		<link>http://gcaptain.com/tragedy-strikes-keppel-shipyard/?32209</link>
		<comments>http://gcaptain.com/tragedy-strikes-keppel-shipyard/?32209#comments</comments>
		<pubDate>Fri, 07 Oct 2011 13:31:09 +0000</pubDate>
		<dc:creator>gCaptain Staff</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Fire Incidents]]></category>
		<category><![CDATA[Incidents]]></category>
		<category><![CDATA[Maritime News]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[keppel]]></category>

		<guid isPermaLink="false">http://gcaptain.com/?p=32209</guid>
		<description><![CDATA[SINGAPORE (Dow Jones)&#8211;Keppel Corp. Ltd (BN4.SG) Friday said that five workers have been killed in an accident at the company&#8217;s shipyard in the Philippines. The incident occurred this morning at the Keppel [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignright size-full wp-image-32210" title="keppel_corporation" src="http://gcaptain.com/wp-content/uploads/2011/10/keppel_corporation.jpg" alt="keppel corporation" width="250" height="200" />SINGAPORE (Dow Jones)&#8211;Keppel Corp. Ltd (BN4.SG) Friday said that five workers have been killed in an accident at the company&#8217;s shipyard in the Philippines.</p>
<p>The incident occurred this morning at the Keppel Subic Shipyard where a vessel was being repaired, Keppel Subic Shipyard President and General Manager Mok Kim Whang said in a statement Friday.</p>
<p>Seven workers were also injured.</p>
<p>Keppel said it is cooperating with the Philippine&#8217;s authorities and will provide further updates when more details are available.</p>
<p><em>-By Gaurav Raghuvanshi, Dow Jones Newswires</em></p>
<p>UPDATE:  According to an update from Keppel, the incident occurred at a dock where a vessel was being repaired. A stern ramp fell on a scaffolding underneath a ramp where the workers were working.</p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/tragedy-strikes-keppel-shipyard/?32209/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Lentera Bangsa &#8211; CNOOC Oil Storage Tanker Ablaze In Jakarta</title>
		<link>http://gcaptain.com/lentera-bangsa-cnooc-ablaze-jakarta/?31352</link>
		<comments>http://gcaptain.com/lentera-bangsa-cnooc-ablaze-jakarta/?31352#comments</comments>
		<pubDate>Fri, 23 Sep 2011 20:31:41 +0000</pubDate>
		<dc:creator>John Konrad</dc:creator>
				<category><![CDATA[Fire Incidents]]></category>
		<category><![CDATA[Offshore News]]></category>
		<category><![CDATA[CNOOC]]></category>

		<guid isPermaLink="false">http://gcaptain.com/?p=31352</guid>
		<description><![CDATA[Built in 1983, the 261 meter-long &#38; 127575 DWT oil tanker Lentera Bangsa caught fire 100 miles from the coast of Jakarta Bay Friday morning. The vessel was being used as a Floating [...]]]></description>
			<content:encoded><![CDATA[<p><img class="aligncenter size-full wp-image-31355" title="Lentera-Bangsa" src="http://gcaptain.com/wp-content/uploads/2011/09/Lentera-Bangsa.png" alt="CNOOC FSO Lentera-Bangsa" width="629" height="356" /></p>
<p>Built in 1983, the 261 meter-long &amp; 127575 DWT oil tanker Lentera Bangsa caught fire 100 miles from the coast of Jakarta Bay Friday morning. The vessel was being used as a Floating Storage and Offloading (FSO) vessel in the Widuri field of the Java Sea and was operating in close proximity  to a China National Offshore Oil Corporation (CNOOC) offshore drilling rig when the fire broke out.</p>
<p>The fire, which broke out at 9 a.m. local time on Friday, injured at least four workers among the crew of 30 and one individual remains missing. A local official has asserted that the fire has been extinguished, but was unable to provide details regarding the nature of the fire, where, or how it started.  Witness reports are mixed with some believing the fire started in the vessel&#8217;s engine room while others stating it started in a cabin.</p>
<p>The FSO has a storage capacity of 700,000 barrels of oil a day, was upgraded from a tanker to FSO by COSCO Guangdong Shipyard in October 2010 and began working the Widuri field early in 2011.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/lentera-bangsa-cnooc-ablaze-jakarta/?31352/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>UPDATE: Oil Tanker Fire Off Yemen Extinguished After Attack</title>
		<link>http://gcaptain.com/update-tanker-fire-yemen-extinguished/?27616</link>
		<comments>http://gcaptain.com/update-tanker-fire-yemen-extinguished/?27616#comments</comments>
		<pubDate>Thu, 07 Jul 2011 10:58:45 +0000</pubDate>
		<dc:creator>gCaptain Staff</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Fire Incidents]]></category>
		<category><![CDATA[Firefighting]]></category>
		<category><![CDATA[Incidents]]></category>
		<category><![CDATA[Maritime News]]></category>
		<category><![CDATA[Maritime Security Incidents]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Piracy]]></category>
		<category><![CDATA[Tankers]]></category>
		<category><![CDATA[crude_oil_tanker]]></category>
		<category><![CDATA[piracy]]></category>

		<guid isPermaLink="false">http://gcaptain.com/?p=27616</guid>
		<description><![CDATA[Image by Dmitrios LONDON (Dow Jones)&#8211;A fire that broke out on an oil tanker after a pirate attack off the Yemeni coast has now been extinguished, an official at the company managing [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.shipspotting.com/gallery/photo_search.php?submitter=45160"><img class="size-full wp-image-27617 alignnone" title="M/V Brilliante Virtuoso" src="http://gcaptain.com/wp-content/uploads/2011/07/1166214.jpg" alt="M/V Brilliante Virtuoso tanker" width="600" height="450" /></a><br />
<span style="color: #888888;"><em>Image by Dmitrios</em></span></p>
<p>LONDON (Dow Jones)&#8211;A fire that broke out on an oil tanker after a pirate attack off the Yemeni coast has now been extinguished, an official at the company managing the ship said Wednesday.</p>
<p>Though a large-scale oil disaster appears to have been avoided, news of the fire on the 1 million barrels tanker will revive security fears on a shipping route that has suffered increasingly bold attacks from Somali pirates.</p>
<p>The fire &#8220;was extinguished,&#8221; said Andreas Louka, a legal adviser at Athens&#8217; Central Mare Inc., the company managing the Brillante Virtuoso tanker.</p>
<p>Asked if the tanker, which was on its way from Ukraine to China, could still deliver its cargo, Louka said &#8220;they are going to assess&#8221; the damage first.</p>
<p>&#8220;The crew is safe, the vessel is safe. There is no pollution,&#8221; the official has previously said.</p>
<p><span style="color: #888888;"><em>-By Benoit Faucon, Dow Jones Newswires</em></span></p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/update-tanker-fire-yemen-extinguished/?27616/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>BOEMRE Report: GoM Mariner Platform Fire Caused By Aging Component</title>
		<link>http://gcaptain.com/boemre-report-mariner-platform/?26048</link>
		<comments>http://gcaptain.com/boemre-report-mariner-platform/?26048#comments</comments>
		<pubDate>Wed, 25 May 2011 19:32:43 +0000</pubDate>
		<dc:creator>gCaptain Staff</dc:creator>
				<category><![CDATA[Offshore News]]></category>
		<category><![CDATA[boemre]]></category>
		<category><![CDATA[Fire Incidents]]></category>
		<category><![CDATA[gulf of mexico]]></category>
		<category><![CDATA[Reports]]></category>

		<guid isPermaLink="false">http://gcaptain.com/?p=26048</guid>
		<description><![CDATA[​Vermillion 380-A Platform fire courtesy BOEMRE HOUSTON (Dow Jones)&#8211;U.S. regulators said Wednesday that a fire that took place aboard a Mariner Energy Inc. oil and gas platform last September was [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://gcaptain.com/wp-content/uploads/2011/05/Screen-shot-2011-05-25-at-12.30.07-PM.png"><img class="alignnone size-full wp-image-26049" title="Vermillion 380-A platform fire" src="http://gcaptain.com/wp-content/uploads/2011/05/Screen-shot-2011-05-25-at-12.30.07-PM.png" alt="" width="600" height="467" /></a><br />
<span style="color: #888888;"><em>​Vermillion 380-A Platform fire courtesy BOEMRE</em></span></p>
<p>HOUSTON (Dow Jones)&#8211;U.S. regulators said Wednesday that a fire that took place aboard a Mariner Energy Inc. oil and gas platform last September was caused by the failure of a nearly 30-year-old piece of equipment.</p>
<p>In addition, the emergency generator failed to start and couldn&#8217;t supply power to the firewater pump, forcing the 13-person crew to abandon the platform and jump into the water, approximately 102 miles off the Louisiana coast. The crew were later rescued. The fire aboard Mariner&#8217;s Vermillion 380-A platform came amid an increased focus on offshore safety in the wake of the Deepwater Horizon explosion in April 2010, which killed 11 and unleashed the worst accidental offshore oil spill in U.S. history.</p>
<p>In a statement, the Bureau of Ocean Energy Management, Regulation and Enforcement said that a fire tube collapsed inside the platform&#8217;s &#8220;heater-treater,&#8221; a piece of equipment designed to separate oily water emulsions into oil and water. The fire tube progressively weakened over many years due to such factors as corrosion and heat. &#8220;The report underscores the need for offshore operators to maintain their equipment consistent with existing standards, to protect the safety of personnel working onboard and to protect the environment,&#8221; the agency said.</p>
<p>The BOEMRE panel that investigated the incident recommended that the agency issue non-compliance citations to Mariner Energy Inc., which has since been acquired by Apache Corp. (APA). Those citations could be used as the basis for future civil penalties, BOEMRE said.</p>
<p>Apache didn&#8217;t immediately respond to requests for comment.</p>
<p><span style="color: #888888;"><em>-By Angel Gonzalez, Dow Jones Newswires</em></span></p>
<p>The full report can be download at <a href="http://www.boemre.gov/ooc/pdfs/Panel_VR380AMAY23FullReport.pdf" target="_blank">http://www.boemre.gov/ooc/pdfs/Panel_VR380AMAY23FullReport.pdf.</a></p>
]]></content:encoded>
			<wfw:commentRss>http://gcaptain.com/boemre-report-mariner-platform/?26048/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

