<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Admiralty and Maritime - Louisiana Law Blog</title>
<link>http://www.louisianalawblog.com/cat-admiralty-and-maritime.html</link>
<description>Louisiana Lawyers, Attorneys &amp; Law Firm</description>
<language>en-us</language>
<copyright>Copyright 2011</copyright>
<lastBuildDate>Mon, 14 Nov 2011 08:58:19 -0600</lastBuildDate>
<pubDate>Fri, 02 Dec 2011 12:51:43 -0600</pubDate>
<generator>http://www.movabletype.org/?v=3.34</generator>
<docs>http://blogs.law.harvard.edu/tech/rss</docs> 

<item>
<title>Supreme Court to Decide Whether Longshore Coverage Moves Landward for Offshore Workers</title>
<description><![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1190496.html">Brett P. Fenasci</a></p>
<p>The U.S. Supreme Court granted a writ of certiorari in <em>Pacific Operators Offshore, LLP v. Valladolid</em>, 131 S.Ct. 1472 (2011) to resolve a split among the U.S. Circuit Courts of Appeal regarding the issue of whether an outer continental shelf worker who is injured on land may be afforded coverage under the Longshore and Harbor Workers Compensation Act (&ldquo;LHWCA&rdquo;), as made applicable by the Outer Continental Shelf Lands Act (&ldquo;OCSLA&rdquo;).</p>
<p>Coverage under the LHWCA is limited primarily to two broad categories of workers. First, a worker may be covered &ldquo;directly&rdquo; under the provisions of the LHWCA. Such direct coverage is primarily limited to longshore and harbor workers, shipbuilders, and shipbreakers. Second, non-seaman oilfield workers who are engaged in the exploration or development of natural resources on the Outer Continental Shelf (&ldquo;OCS&rdquo;) may be entitled to LHWCA benefits by virtue of section 1333(b) of OCSLA. 43 U.S.C. &sect; 1331(b). <em>Valladolid </em>deals with this second category of workers. <br />
&nbsp;</p>]]><![CDATA[<p>Section 1333(b) of OCSLA provides that an injured OCS worker who does not qualify as a seaman will be covered by the provisions of the LHWCA if the worker&rsquo;s injury is &ldquo;the result of operations conducted on the Outer Continental Shelf for the purpose of exploring for, developing, removing, or transporting by pipeline the natural resources &hellip; of the seabed of the [OCS].&rdquo; There is a split among the circuit courts regarding the question of whether section 1333(b) contains a &ldquo;situs&rdquo; requirement. The U.S. Fifth Circuit has answered this question in the affirmative and has refused to extend LHWCA benefits to OCS workers who are not injured on a fixed platform on the OCS or on navigable waters over the OCS. In contrast, the U.S. Third Circuit has construed 1333(b) as containing only a &ldquo;but for&rdquo; test &ndash; coverage will exist if it can be said that the injury would not have occurred &ldquo;but for&rdquo; operations on the shelf. Curtis v. Schlumberger Offshore Service, Inc., 849 F.2d 805 (3d Cir. 1988). Thus, an employee injured in a car accident on his way to meet a helicopter that would take him to an offshore platform was entitled to recover LHWCA benefits. <em>Id</em>. at 806, 811.</p>
<p>As illustrated by <em>Valladolid</em>, the Ninth Circuit has adopted the approach of the Third Circuit. <em>Valladolid </em>involved the death of Juan Valladolid, a general laborer who was employed by Pacific Operations, a company that operates two drilling platforms located on the outer continental shelf off the coast of California. While Valladolid was primarily stationed on one of these platforms, he was killed on the grounds of Pacific Operations when he was crushed by a forklift. He would not have been injured &quot;but for&quot; oil and gas operations on the OCS.</p>
<p>Citing opinions from the Third Circuit, Valladolid's widow argued that LHWCA benefits were recoverable under OCSLA. The Administrative Law Judge and Benefits Review Board applied the Fifth Circuit's situs requirement and held that benefits were not recoverable because Valladolid's accident did not occur on an OCS platform or on navigable waters over the OCS. The Ninth Circuit reversed. In doing so, the court held, as a matter of statutory construction, that section 1333(b) of OCSLA does not contain language indicative of a situs requirement.</p>
<p>The Supreme Court has granted a writ of certiorari to address the growing conflict between the federal circuit courts of appeal. If the Supreme Court agrees with the Third and Ninth Circuits, employers who conduct operations on the OCS can anticipate an increase in LHWCA claims by their land-based workers.<br />
&nbsp;</p>]]></description>
<link>http://www.louisianalawblog.com/admiralty-and-maritime-supreme-court-to-decide-whether-longshore-coverage-moves-landward-for-offshore-workers.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/admiralty-and-maritime-supreme-court-to-decide-whether-longshore-coverage-moves-landward-for-offshore-workers.html</guid>
<category>Admiralty and Maritime</category>
<pubDate>Mon, 14 Nov 2011 08:58:19 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>
<item>
<title>Outer Continental Shelf Safety and Environmental Management Systems: Imminent Deadlines, New Guidance and Proposed Rules</title>
<description><![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1669644.html">Lee Vail</a></p>
<p>On October 15, 2010, the former Bureau of Ocean Energy Management, Regulation and Enforcement (&ldquo;BOEMRE&rdquo;)&nbsp;issued new regulations, incorporating in its entirety and making mandatory the implementation of the American Petroleum Institute&rsquo;s Recommended Practice 75 (API RP 75). &nbsp;The rule requires development of Safety and Environmental Management Systems (SEMS)&nbsp;plans by &ldquo;a lessee, the owner or holder of operating rights, a designated operator or agent of the lessee(s), a pipeline right-of-way holder, or a state lessee granted a right-of-use and easement.&rdquo;  30 C.F.R &sect; 250.105.  According to BOEMRE, &ldquo;the purpose of SEMS is to enhance the safety and cleanliness of operations by reducing the frequency and severity of accidents.&rdquo; This final rule applies to all Outer Continental Shelf oil and gas and sulphur operations and the facilities under BOEMRE jurisdiction including drilling, production, construction, well workover, well completion, well servicing, and DOI pipeline activities.</p>
<p>Responsibility for developing and implementing a SEMS program lies with the lessee (or owner or holder of an operating right), unless it delegates the responsibility to another (likely the operator).  Contractors are not responsible for developing the plan; however if compliant, contractor procedures may be incorporated into the lessee&rsquo;s/operator&rsquo;s SEMS plan.<br />
&nbsp;</p>]]><![CDATA[<p>This rule requires completion of two significant efforts by November 15, 2011, including:</p>
<ul>
    <li>SEMS program must be complete and in effect, 40 C.F.R. 250.1900(a); and</li>
    <li>Initial hazard analysis, 40 C.F.R 250.1911(a).</li>
</ul>
<p>On October 11, 2011, the Bureau of Safety and Environmental Enforcement (&ldquo;BSEE&rdquo;) issued guidance concerning the implementation of the rule. While repeating required elements of a SEMS plan, the guidance provides examples of adequate documentation and coordination between the operator and its contractors.  As described below, operators must do more than rely on assurances made by the contractor.  Under the SEMS program, the operator must:</p>
<ul>
    <li>agree with and accept the contractor&rsquo;s safety procedures and make them available during an inspection;</li>
    <li>document that each contractor is knowledgeable and experiences (by auditing / testing);</li>
    <li>perform periodic evaluations of contract employees;</li>
    <li>inform the contractor of any known hazards; and</li>
    <li>verify how contractors are trained.</li>
</ul>
<p>While the SEMS rule was progressing to final promulgation, BOEMRE proposed amendments to the rule to add further requirements for SEMS programs. It is apparent from the proposal that BOEMRE believes employees need additional rights to affect the development of the SEMS plan and to stop and report unsafe acts to the government.  Comments are due on the proposal by November 14, 2011.  The proposed rules include the following additions to the SEMS program:</p>
<ul>
    <li>procedures to allow any employee to stop work;</li>
    <li>clearly defined requirements as who has authority to make safety decisions;</li>
    <li>demonstrations that employees are involved in development of the SEMS plan;</li>
    <li>guidelines for employees to report unsafe conditions and request a BSEE inspection; and,</li>
    <li>requirements for third party audits.</li>
</ul>
<p>&nbsp;</p>
<!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:TrackMoves/>
  <w:TrackFormatting/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>EN-US</w:LidThemeOther>
  <w:LidThemeAsian>X-NONE</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:DontVertAlignCellWithSp/>
   <w:DontBreakConstrainedForcedTables/>
   <w:DontVertAlignInTxbx/>
   <w:Word11KerningPairs/>
   <w:CachedColBalance/>
  </w:Compatibility>
  <m:mathPr>
   <m:mathFont m:val="Cambria Math"/>
   <m:brkBin m:val="before"/>
   <m:brkBinSub m:val="&#45;-"/>
   <m:smallFrac m:val="off"/>
   <m:dispDef/>
   <m:lMargin m:val="0"/>
   <m:rMargin m:val="0"/>
   <m:defJc m:val="centerGroup"/>
   <m:wrapIndent m:val="1440"/>
   <m:intLim m:val="subSup"/>
   <m:naryLim m:val="undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
  DefSemiHidden="true" DefQFormat="false" DefPriority="99"
  LatentStyleCount="267">
  <w:LsdException Locked="false" Priority="0" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Normal"/>
  <w:LsdException Locked="false" Priority="9" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="heading 1"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 1"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 2"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 3"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 4"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 5"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 6"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 7"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 8"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 9"/>
  <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/>
  <w:LsdException Locked="false" Priority="10" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Title"/>
  <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/>
  <w:LsdException Locked="false" Priority="11" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/>
  <w:LsdException Locked="false" Priority="22" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Strong"/>
  <w:LsdException Locked="false" Priority="20" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/>
  <w:LsdException Locked="false" Priority="59" SemiHidden="false"
   UnhideWhenUsed="false" Name="Table Grid"/>
  <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/>
  <w:LsdException Locked="false" Priority="1" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 1"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 1"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 1"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/>
  <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/>
  <w:LsdException Locked="false" Priority="34" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/>
  <w:LsdException Locked="false" Priority="29" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Quote"/>
  <w:LsdException Locked="false" Priority="30" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 1"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 1"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 2"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 2"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 2"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 2"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 2"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 3"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 3"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 3"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 3"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 3"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 4"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 4"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 4"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 4"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 4"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 5"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 5"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 5"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 5"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 5"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 6"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 6"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 6"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 6"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 6"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/>
  <w:LsdException Locked="false" Priority="19" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/>
  <w:LsdException Locked="false" Priority="21" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/>
  <w:LsdException Locked="false" Priority="31" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/>
  <w:LsdException Locked="false" Priority="32" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/>
  <w:LsdException Locked="false" Priority="33" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Book Title"/>
  <w:LsdException Locked="false" Priority="37" Name="Bibliography"/>
  <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/>
 </w:LatentStyles>
</xml><![endif]--><!--[if gte mso 10]>
<style>
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-qformat:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin-top:0in;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:10.0pt;
	mso-para-margin-left:0in;
	line-height:115%;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:"Times New Roman";
	mso-fareast-theme-font:minor-fareast;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;}
</style>
<![endif]-->
<p><span style="font-size: smaller;"> </span></p>
<p style="background: none repeat scroll 0% 0% white;">&nbsp;</p>
<p><del>
<p style="background: none repeat scroll 0% 0% white;"><font class="Apple-style-span" face="'Times New Roman', serif"><span class="Apple-style-span" style="line-height: 13px;"><br />
</span></font></p>
</del></p>
<p class="MsoFootnoteText">&nbsp;</p>]]></description>
<link>http://www.louisianalawblog.com/environmental-litigation-and-regulation-outer-continental-shelf-safety-and-environmental-management-systems-imminent-deadlines-new-guidance-and-proposed-rules.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/environmental-litigation-and-regulation-outer-continental-shelf-safety-and-environmental-management-systems-imminent-deadlines-new-guidance-and-proposed-rules.html</guid>
<category>Admiralty and Maritime</category><category>Coastal/Wetlands Issues</category><category>Energy</category><category>Environmental Litigation and Regulation</category>
<pubDate>Thu, 27 Oct 2011 18:17:02 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>
<item>
<title>Recent Fifth Circuit Decision Illustrates Importance of Including Demurrage Clause in Contract for Sale and Transport of Goods by Sea</title>
<description><![CDATA[<div>
<p>By&nbsp;<a href="http://www.keanmiller.com/lawyer-attorney-1669770.html">Brittany L. Buckley</a></p>
</div>
<p>Maritime attachment is a powerful procedure that allows an aggrieved party to garnish any of the defendant's property located within a particular federal judicial district.&nbsp; Attachment is especially powerful because the garnished property can be used to ensure satisfaction of a claim, even if the property within the judicial district is not related to the claim that has been filed there.&nbsp; This right can prove invaluable for securing payment of claims from a foreign defendant who cannot be easily traced down and sued.&nbsp; This particular species of attachment is unique to admiralty law and is only available to satisfy &quot;admiralty&quot; or &quot;maritime&quot; claims, including contractual obligations that are separable from an non-maritime aspects of a contract.&nbsp;</p>]]><![CDATA[<p>The Fifth Circuit&rsquo;s recent decision in <em>Alphamate Commodity GMBH v. CHS Europe SA</em>, 627 F.3d 183 (5th Cir. 2010) narrowly defines maritime claims, thereby limiting the availability of maritime attachment proceedings in cases involving contractual disputes. In <em>Alphamate</em>, AFL (a Libyan company) entered into a contract to purchase grain from a European grain merchant (Alphamate). AFL allegedly breached the contract when it failed to timely obtain letters of credit, and Alphamate claimed it was owed damages of $8,000,000 for this breach. Importantly, Alphamate claimed that at least half of these damages were for demurrage and detention, both of which are traditionally admiralty claims. Detention is a legal remedy, in the form of damages, which is available to a shipowner who loses use of the vessel and profits due to a charterer&rsquo;s failure to timely return the vessel. Demurrage is a sum fixed in a contract, which serves to remunerate a shipowner for detention of the vessel beyond the number of days allowed by the contract for loading and unloading.</p>
<p>While AFL and Alphamate were arbitrating this contractual dispute in Europe, Alphamate also initiated maritime attachment proceedings in the United States District Court for the Eastern District of Louisiana. Through maritime attachment, Alphamate seized a shipment of corn in New Orleans while it was aboard a third party&rsquo;s vessel <em>en route </em>to AFL. The Fifth Circuit found that Alphamate could not use maritime attachment to seize the corn because the underlying dispute between AFL and Alphamate did not involve a maritime claim. In particular, the court determined that the AFL-Alphamate contract primarily called for the sale of grain and that the obligation to ship the grain by sea did not convert the contract into a maritime claim. The Fifth Circuit further rejected Alphamate&rsquo;s argument that the demurrage and detention claims were independent maritime obligations capable of sustaining maritime attachment proceedings. The court reasoned that these claims were too intertwined with the non-maritime breach of contract claims to provide a basis for maritime jurisdiction.</p>
<p>Notwithstanding the Fifth Circuit&rsquo;s rejection of maritime attachment proceedings in <em>Alphamate</em>, the Court left open the possibility that a party can still use maritime attachment to secure payment of loss-of-use damages if the breached contract includes an independent obligation for demurrage. This ruling emphasizes the importance of including a contractual clause that expressly sets forth an obligation to pay demurrage fees in the event that a vessel is unjustly detained by the charterer. According to the Fifth Circuit, this clause is necessary to establish maritime jurisdiction over claims for demurrage and detention, thereby allowing an aggrieved party to utilize maritime attachment to secure payment of such fees from foreign defendants. Absent such an express demurrage provision, <em>Alphamate </em>illustrates that damages for loss of use can only be recovered through a breach of contract action &ndash; a more arduous process that, unlike maritime attachment, fails to provide security for the satisfaction of successful claims.<br />
&nbsp;</p>]]></description>
<link>http://www.louisianalawblog.com/admiralty-and-maritime-recent-fifth-circuit-decision-illustrates-importance-of-including-demurrage-clause-in-contract-for-sale-and-transport-of-goods-by-sea.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/admiralty-and-maritime-recent-fifth-circuit-decision-illustrates-importance-of-including-demurrage-clause-in-contract-for-sale-and-transport-of-goods-by-sea.html</guid>
<category>Admiralty and Maritime</category><category>Business Litigation</category><category>Louisiana In General</category>
<pubDate>Thu, 18 Aug 2011 17:01:11 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>
<item>
<title>Does the Spoliation of Evidence Doctrine Apply to a Seaman who Elects to Undergo a Post-Accident Surgery Prior to an Independent Medical Examination?</title>
<description><![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1194685.html">Michael J. O'Brien</a></p>
<p>The spoliation of evidence doctrine concerns the intentional destruction of relevant evidence by a party. In the event that relevant evidence is spoiled (i.e., intentionally destroyed), the court may exercise its discretion to impose sanctions on the responsible party. The seriousness of the sanctions that a court may impose depends on the consideration of: (1) the degree of fault of the party who altered or destroyed the evidence; (2) the degree of prejudice suffered by the opposing party; and (3), whether there is a lesser sanction that will avoid substantial unfairness to the opposing party and, where the offending party is seriously at fault, will serve to deter such conduct by others in the future. Exclusion of spoiled evidence is a drastic sanction the courts generally try to avoid. However, the court may issue an instruction that will allow the jury to infer that the party spoiled the evidence because the evidence was unfavorable to the party&rsquo;s case.</p>]]><![CDATA[<p>When a seaman is injured, the injured areas of his body become evidence. For example, the cervical and/or lumbar spine of a seaman complaining of neck and/or back pain is the only objective evidence of his injuries. Surgery irreparably alters and/or destroys the allegedly damaged area. This begs the question: Does a seaman spoil the evidence of his injury by electing to proceed with surgery prior to appearing for an Independent Medical Examination (&ldquo;IME&rdquo;)?<br />
&nbsp;</p>
<p>In <em>Menges v. Cliffs Drilling Company</em>, 2000 WL 765082 (E.D. La. 2000), Chief Judge Sarah Vance addressed this issue when she denied a request by an employer to invoke the Spoliation of Evidence Doctrine against an injured party that had elected to undergo surgery. Specifically, Cliffs sought to exclude evidence of Mr. Menges&rsquo; post-accident back surgery or obtain an adverse jury instruction because Mr. Menges had undergone a post-accident lumbar surgery prior to undergoing an IME. The surgery occurred before there was any litigation between the parties. However, when Mr. Menges agreed to undergo lumbar surgery, he arguably knew that the condition of his lower back would be pertinent to any future litigation. Moreover, Mr. Menges was represented by counsel when he underwent the surgery, and his counsel paid for the surgery. Yet, Judge Vance held that even if Mr. Menges had a duty to notify Cliffs of his surgery so that he could be examined by an independent medical examiner, breach of the duty to notify did not amount to spoliation of evidence. Additionally, Judge Vance held that Mr. Menges did not intentionally destroy evidence by undergoing surgery. She highlighted the fact that Mr. Menges provided Cliffs with full access to his medical records prior to the surgery. As such, she noted that Cliffs had ample opportunity to investigate Mr. Menges&rsquo; condition and to require an IME before he underwent surgery.</p>
<p>Based on Judge Vance&rsquo;s ruling in <em>Menges</em>, it is highly unlikely that the Spoliation of Evidence Doctrine will apply to an injured party who proceeds with a surgery prior to an IME. However, it is important to note that there is jurisprudence holding a plaintiff and his attorney can be sanctioned for their failure to appear at scheduled IMEs. Therefore, if there is even the faintest possibility that that an injured party will undergo a future surgery, an employer should promptly investigate the party&rsquo;s condition and probably schedule an IME as soon as possible. <br />
&nbsp;</p>]]></description>
<link>http://www.louisianalawblog.com/admiralty-and-maritime-does-the-spoliation-of-evidence-doctrine-apply-to-a-seaman-who-elects-to-undergo-a-postaccident-surgery-prior-to-an-independent-medical-examination.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/admiralty-and-maritime-does-the-spoliation-of-evidence-doctrine-apply-to-a-seaman-who-elects-to-undergo-a-postaccident-surgery-prior-to-an-independent-medical-examination.html</guid>
<category>Admiralty and Maritime</category>
<pubDate>Tue, 16 Aug 2011 10:02:49 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>
<item>
<title>Parties Cannot Avoid Patent Infringement by Conducting Negotiations Outside the United States for Products that will be Delivered and Utilized in the United States</title>
<description><![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1669644.html">R. Lee Vail</a></p>
<p>In <em>Transocean Offshore Deepwater Drilling, Inc. v. Maersk Contractors USA, Inc</em>, 617 F.3d 1296 (Fed. Cir. 2010), the Federal Circuit reversed a district court&rsquo;s summary judgment decision that no patent infringement occurred when a US company made an offer to sell to another US company when the sale negotiations occurred outside of the US.</p>
<p>Transocean filed suit for infringement of patents related to an improved apparatus for conducting offshore drilling. In order to drill for oil and other offshore resources, drilling rigs must lower several components to the seabed including the drill bit, casings, BOB&rsquo;s, and the drill string. A conventional offshore drilling rig utilizes a derrick with a single top drive and drawworks that can only lower one element at a time in a time consuming process. Transocean patented a specialized derrick to improve the efficiency of lowering the above components. The specialized derrick included &ldquo;two stations &ndash; a main advancing station and an auxiliary advancing station that can each assemble drill strings and lower components to the seabed.&rdquo; Id. at 1301. This duel-activity rig could significantly decrease&nbsp;the time required to complete a borehole. Id at 1302. Transocean sued Maersk rig for infringement of the specialized derrick patent. <br />
&nbsp;</p>]]><![CDATA[<p>35 U.S.C. Section 271(a) states that &ldquo;whoever without authority makes, uses, offers to sell, or sells any patented invention, within the United States &hellip; infringes [a] patent.&rdquo; Maersk had negotiated an offer to sell with another company to deliver a rig to the United States that infringed upon Transocean&rsquo;s patent. However, the offer to sell was negotiated in Norway. Maersk argued that for there to be an &ldquo;offer to sell within the United States,&rdquo; the offer activities must occur within the U.S. The district court agreed with Maersk, holding that since the contract was negotiated and executed outside the United States, it was not an offer to sell within the United States.</p>
<p>Thus, one of the questions before the Federal Circuit was whether an offer to sell, made in Norway by a U.S. Company to another U.S. company, to sell a product within the U.S. for delivery and use within the U.S. constituted an offer to sell &ldquo;within the U.S.&rdquo; under the definition of Section 271(a). Ultimately, the Federal Circuit determined that the focus should not be the location of the offer; rather, the focus must be on the location of the future sale that would occur pursuant to the offer. There was no question that the patent infringing rig was to be delivered to the US and utilized in the Gulf of Mexico. As such, the Federal Circuit vacated the district courts summary judgment of non-infringment noting the real harm that would be created by such a decision because U.S. companies could simply travel and contract abroad to avoid patent infringement. Id at 1309-10.</p>
<p>On remand, a jury found on April 21, 2011 that Maersk infringed Transocean&rsquo;s valid patent and awarded Transocean $15 million. 2011 WL 2604769 (S.D. Tex 2011). Transocean&rsquo;s victory was short-lived as on June 30, 2011, Judge Hoyt found pursuant to Fed. R. Civ. P. 50(b) that Maersk did not infringe the patents because the evidence did not support the jury&rsquo;s findings.</p>
<p>Also of interest is a potential conflict between the prior decisions of the Federal Circuit and Judge Hoyt. The Maersk contract contained a provision allowing for the design to change if needed to avoid patent infringement. The Federal Circuit stated that schematics attached to the contract could support a finding of an infringed sale and that subsequent alterations were irrelevant. 617 F.3d at 1311. Judge Hoyt found that the contract anticipated alteration and therefore &ldquo;no rig was offered for sale, or sold in violation of 35 U.S.C &sect; 271(a).&rdquo; 2011 WL 2604769 at 5. Further, Judge Hoyt found that under such circumstance, awarding a reasonable royalty would be unconscionable if the delivered drilling rig was altered to avoid infringement as Transocean would suffer no harm. <br />
&nbsp;</p>]]></description>
<link>http://www.louisianalawblog.com/intellectual-property-parties-cannot-avoid-patent-infringement-by-conducting-negotiations-outside-the-united-states-for-products-that-will-be-delivered-and-utilized-in-the-united-states.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/intellectual-property-parties-cannot-avoid-patent-infringement-by-conducting-negotiations-outside-the-united-states-for-products-that-will-be-delivered-and-utilized-in-the-united-states.html</guid>
<category>Admiralty and Maritime</category><category>Business and Corporate</category><category>Energy</category><category>Intellectual Property</category>
<pubDate>Wed, 10 Aug 2011 11:35:22 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>
<item>
<title>&quot;Pipeline Infrastructure and Community Protection Act&quot; Hearings Focus on Recent Pipeline Incidents</title>
<description><![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1669644.html">R. Lee Vail </a>and <a href="http://www.keanmiller.com/lawyer-attorney-1192569.html">Maureen N. Harbourt</a></p>
<p>On July 15, 2011, the House of Representative, Committee on Energy and Power, Subcommittee on Energy and Commerce held hearings on a draft of the &ldquo;Pipeline Infrastructure and Community Protection Act of 2011.&rdquo;&nbsp; Chairman Fred Upton&rsquo;s initial comments focused on recent pipeline incidents: the 20,000 barrel oil spill into Talmadge Creek, Michigan in the summer of 2010, the September 2010 gas pipeline explosion that killed 8 people in San Bruno, California and the most recent spill of 1,000 barrels of oil near Billings, Montana. <span style="font-size: smaller;">(1)&nbsp; </span>Chairman Upton concluded that these incidents indicate that pipeline laws must be strengthened. Included within the draft legislation are the following provisions:</p>
<ul>
    <li>one-hour time limit to report incidents;</li>
    <li>use of automatic or remote control shutoff-valves;</li>
    <li>better leak detection technology;</li>
    <li>substantial increase in civil penalties for releases from pipeline;</li>
    <li>enhanced inspection techniques; more miles of pipeline inspected; and</li>
    <li>increased number of pipeline inspectors.<br />
    &nbsp;</li>
</ul>
<p>Cynthia Quarterman, Administrator of the Pipeline and Hazardous Materials Safety Administration (&ldquo;PHMSA&rdquo;), within the Department of Transportation, appeared and offered general support for the bill. However she offered specific recommendations to various provisions to strengthen the legislation. Among the recommendations were: <span style="font-size: smaller;">(2)<br />
</span></p>
<ul>
    <li>higher administrative penalties should apply in High Consequence Areas;</li>
    <li>eliminate statutory exemption for gathering lines; and</li>
    <li>clarity should be added that shut-off valve requirements apply to gas and hazardous pipelines.<br />
    &nbsp;</li>
</ul>
<p>Because changes in regulatory programs often occur quickly after incidents such as these recent three pipeline events, interested parties should be aware of the above issues and recommendations. Owners and operators of regulated pipelines should expect more inspection/detection requirements and the likelihood of enhanced PHSMA and state agency inspections and enforcement actions.<br />
&nbsp;</p>
<p><span style="font-size: smaller;">(1)&nbsp; &nbsp;Opening Statement of Chairman Fred Upton (July 15, 2011), found at <a href="http://republicans.energycommerce.house.gov/Media/file/Hearings/Energy/071511/Upton%20.pdf ">http://republicans.energycommerce.house.gov/Media/file/Hearings/Energy/071511/Upton%20.pdf </a>(last visited July 18, 2011).</span></p>
<p><span style="font-size: smaller;">(2)&nbsp; Written Statement of Cynthia Quarterman, Administrator, PHMSA (July 15, 2011) found at <a href="http://www.phmsa.dot.gov/staticfiles/PHMSA/DownloadableFiles/Testimony/House%20Energy%20and%20Commerce%20Written%20Testimony%20-%20July%2015%202011%20-%20For%20Web%20_2_.pdf">http://www.phmsa.dot.gov/staticfiles/PHMSA/DownloadableFiles/Testimony/House%20Energy%20and%20Commerce%20Written%20Testimony%20-%20July%2015%202011%20-%20For%20Web%20_2_.pdf</a> (last visited July 18, 2011).<br />
</span></p>]]></description>
<link>http://www.louisianalawblog.com/admiralty-and-maritime-pipeline-infrastructure-and-community-protection-act-hearings-focus-on-recent-pipeline-incidents.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/admiralty-and-maritime-pipeline-infrastructure-and-community-protection-act-hearings-focus-on-recent-pipeline-incidents.html</guid>
<category>Admiralty and Maritime</category><category>Coastal/Wetlands Issues</category><category>Environmental Litigation and Regulation</category><category>Louisiana In General</category>
<pubDate>Mon, 18 Jul 2011 16:12:24 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>
<item>
<title>Louisiana DNR Extends Offshore Drilling Emergency Order</title>
<description><![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1669644.html">R. Lee Vail</a></p>
<p>In response to the Gulf of Mexico Deepwater Horizon Incident, the Louisiana Department of Natural Resources (&ldquo;DNR&rdquo;), Office of Conservation (&ldquo;Conservation&rdquo;) issued a series of emergency rules with effective dates: July 15, 2010<span style="font-size: smaller">(1) </span>, December 9, 2010<span style="font-size: smaller">(2)</span>, January 12, 2011<span style="font-size: smaller">(3)&nbsp;</span>and most recently May 12, 2011<span style="font-size: smaller">(4).&nbsp;&nbsp;</span>. The initial emergency rule created:</p>
<p style="margin-left: 40px">&ldquo;a new Chapter within Statewide Order No. 29-B (LAC 43:XIX.Ch. 2) to provide additional rules concerning the drilling and completion of oil and gas wells at water locations, specifically providing for the following: rig movements and reporting requirements, additional requirements for applications to drill, casing-header requirements, mandatory diverter systems and blowout preventer requirements, oil and gas workover operations, diesel engine safety requirements, and drilling fluid regulations.&rdquo; See, 36 La. Reg. 1427.</p>
<p>The initial emergency rule also amended Statewide Order No. 29-B-a (LAC 43:XIX. Ch. 11) &ldquo;to provide for and expand upon rules concerning the use of storm chokes in oil and gas wells at water locations.&rdquo; <em>Id.</em></p>
<p>In the emergency rules, Conservation has reviewed and incorporated &ldquo;all provisions of the MMS [Minerals Management Service] regulations concerning well control issues at water locations&rdquo; that were not repetitive, duplicative or otherwise inapplicable to the situations encountered in Louisiana waters. <em>See</em>, 37 La. Reg. 1548. In addition to providing Conservation more time promulgate final comprehensive rules, the most recent version of the emergency rules contains a few noteworthy changes from the January 2011 version of the rule. These are:</p>
<ul>
    <li>The Oil and Gas Well-Workover Operations section, located at LAC 43:XIX.211, contains specific requirements for blow out preventer components and configuration. Conservation removed a provision (formally located at LAC 43:XIX.213.L) allowing the Commissioner to grant an exemption from specific equipment requirements mandated by that section. The January 2011 version of the rule allowed an exemption from specific equipment requirements where the operator could demonstrate the unavailability of the mandated equipment and that anticipated surface pressures minimize the opportunity for loss of well control.</li>
</ul>
<ul>
    <li>Conservation changed the mandatory industry standard for design and operation of subsurface safety valves (&ldquo;SSSV&rdquo;) from &ldquo;API RP 14B&rdquo; to &ldquo;API RP 14H&rdquo;. <em>See</em>, LAC 43:XIX.1104.E (making the emergency rule consistent with 30 C.F.R. &sect;250.804(a)(5)).&nbsp;</li>
</ul>
<ul>
    <li>All four versions of the emergency rule require that installed subsurface-controlled SSSV&rsquo;s be removed and tested every twelve or six months, depending on whether they were installed on a landing nipple or not. However, the most recent emergency rule also included a requirement that all SSSVs be inspected for leakage every month to six weeks. See, LAC 43:XIX.1104.E.2.a.</li>
</ul>
<p>*******************************</p>
<p><span style="font-size: smaller">(1)&nbsp; 36 Louisiana Register 1427, July 20, 2010, available at: </span><a href="http://www.doa.louisiana.gov/osr/reg/1007/1007.pdf"><span style="font-size: smaller">http://www.doa.louisiana.gov/osr/reg/1007/1007.pdf</span></a><span style="font-size: smaller"><br />
(last visited June 27, 2011).<br />
</span></p>
<p><span style="font-size: smaller">(2)&nbsp; 36 Louisiana Register 2823, Dec. 20, 2010, available at: </span><a href="http://www.doa.louisiana.gov/osr/reg/1012/1012.pdf "><span style="font-size: smaller">http://www.doa.louisiana.gov/osr/reg/1012/1012.pdf </span></a><span style="font-size: smaller"><br />
(last visited June 27, 2011).<br />
</span></p>
<p><span style="font-size: smaller">(3)&nbsp; 37 Louisiana Register 460, Feb. 20, 2011, available at: </span><a href="http://www.doa.louisiana.gov/osr/reg/1102/1102.pdf"><span style="font-size: smaller">http://www.doa.louisiana.gov/osr/reg/1102/1102.pdf</span></a><span style="font-size: smaller"><br />
(last visited June 27, 2011).</span>&nbsp;</p>
<p><span style="font-size: smaller">(4)&nbsp; 37 Louisiana Register 1547, June 20, 2011, available at: </span><a href="http://www.doa.louisiana.gov/osr/reg/1106/1106.pdf "><span style="font-size: smaller">http://www.doa.louisiana.gov/osr/reg/1106/1106.pdf </span></a><span style="font-size: smaller">(last visited June 27, 2011).<br />
</span>&nbsp;</p>]]></description>
<link>http://www.louisianalawblog.com/admiralty-and-maritime-louisiana-dnr-extends-offshore-drilling-emergency-order.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/admiralty-and-maritime-louisiana-dnr-extends-offshore-drilling-emergency-order.html</guid>
<category>Admiralty and Maritime</category><category>Coastal/Wetlands Issues</category><category>Energy</category><category>Environmental Litigation and Regulation</category><category>Louisiana In General</category>
<pubDate>Wed, 29 Jun 2011 13:16:04 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>
<item>
<title>Environmental Groups Attempt to Block Shell Deepwater Gulf of Mexico Drilling</title>
<description><![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1669644.html">R. Lee Vail</a></p>
<p>Deepwater oil and gas production from the Gulf of Mexico has become a significant portion of the current production within the United States, equal to over 1.6 million barrels per day of oil equivalent; total U.S oil production is around 5.3 million barrels per day. <span style="font-size: smaller">(1)&nbsp;</span>&nbsp;Worldwide shallow water oil production peaked around the year 2000 whereas worldwide deep water production has risen to around 5 million barrels per day. On May 10, 2011, the Bureau of Ocean Energy Management, Regulation and Enforcement (&ldquo;BOEMRE&rdquo;) approved Royal Dutch Shell&rsquo;s Exploration Plan S-0744 to better define discoveries announced in 2009 and 2010. <span style="font-size: smaller">(2)&nbsp; </span></p>
<p>Several environmental groups filed suit in an attempt to block the approved plan. Gulf Restoration Network, Inc., Florida Wildlife Federation, and Sierra Club Inc. filed a petition on June 8, 2011, in the United States Court of Appeals, 11th Circuit, in an attempt to set aside BOEMRE&rsquo;s approval of the plan. The allegations in the petition are relatively general, alleging violation of the National Environmental Policy Act (&ldquo;NEPA&rdquo;) (i.e., for BOEMRE&rsquo;s alleged failure to appropriately conduct the required environmental assessments and/or impact statements) and further alleging elements required pursuant to 43 U.S.C &sect;1349(c) necessary to maintain the suit under the Outer Continental Shelf Lands Act (&ldquo;OCSLA&rdquo;).<br />
&nbsp;</p>]]><![CDATA[<p>Details of the alleged violations of NEPA are located in comments supplied by Earth Justice to docket number BOEM 2011-0021. Earth Justice, a public interest law firm, submitted the comments on behalf of themselves and the environmental groups named above. Among the complaints made by Earth Justice is that Shell&rsquo;s actual compliance with BOEMRE regulations is unlikely and that BOEMRE&rsquo;s risk analysis is flawed.</p>
<p>In response to the Deepwater Horizon Incident, on June 18, 2010, BOERMRE issued new regulations concerning exploration, production and development plans. In interpreting one of these, BOEMRE Notice to Lessees (NTL) No. 2010-N06, establishes that calculation of the worst case discharge (&ldquo;WCD&rdquo;) is &ldquo;the daily rate of an uncontrolled flow from all producible reservoirs into the open wellbore.&rdquo; <span style="font-size: smaller">(3)</span>&nbsp; In compliance with the regulation and notice, Shell calculated a theoretical worst case discharge (&ldquo;WCD&rdquo;) that exceeded estimates of the Deepwater Horizon incident. <span style="font-size: smaller">(4)&nbsp;&nbsp;</span></p>
<p>The plan includes Shell&rsquo;s evaluation of potential mitigating factors, effectiveness of intervention devices (including redundant blow out preventers &ldquo;BOPs&rdquo;) and containment methods (sub-sea containment assembly and other specialized connection devices). Earth Justice&rsquo;s comments contend it is unreasonable for exploration plans to rely on use of BOPs in light of the failure of BOPs during the Deepwater Horizon incident and dismiss planned containment methods as &ldquo;reliance on an unproven system of unknown reliability.&rdquo;&nbsp; <span style="font-size: smaller">(5) </span></p>
<p>The Shell Exploration Plan relies on new technology developed by Marine Well Container Co. (&ldquo;MWCC&rdquo;), a consortium of oil companies operating in the Gulf of Mexico. MWCC recently announced that the new system can operate at depths of up to 10,000 feet. <span style="font-size: smaller">(6)</span>&nbsp; According to a Dow Jones press release, &ldquo;MWCC&rsquo;s containment system improves on techniques that were gradually developed by BP after several failed attempts to cap the Deepwater Horizon spill. It consists of a capping stack that would stop the high-pressure flow of oil and gas from a runaway well, and ship the hydrocarbons to a surface vessel if needed.&rdquo; <span style="font-size: smaller">(7)</span>&nbsp; BOEMRE previously approved an exploration plan that used the MWCC containment system for drilling a prospect in 6,941 feet of water. <span style="font-size: smaller">(8) </span></p>
<p>In its comments, Earth Justice further questioned BOEMRE methodology in determining that the likelihood of a spill. In an attempt to diminish the historical successful drilling of offshore wells without incident, Earth Justice argues that BOEMRE should reduce the set of comparable wells to only those in the Gulf of Mexico drilled in water of similar depths or complexity. Considering the single catastrophic failure in the Gulf (Deepwater Horizon), this approach, which lowers the number of comparable wells drilled in the Gulf, presumably would result in a greater risk of failure for future wells. <span style="font-size: smaller">(9)</span></p>
<p>Given the importance of oil and gas production from deep water Gulf of Mexico, this challenge will be an interesting test of the adequacy of industry efforts to comply with regulations developed by BOEMRE in response to the Deepwater Horizon incident and of BOEMRE&rsquo;s adequacy in addressing NEPA requirements when approving drilling plans.&nbsp;</p>
<p>&nbsp;</p>
<p><span style="font-size: smaller">(1) &nbsp;Rafael Sandrea, Deepwater Crude Output: How Large Will it Be?, Oil &amp; Gas Journal, 48-51 (Nov. 1, 2010). <br />
</span></p>
<p><span style="font-size: smaller">(2) GoM: Shell Receives BOEMRE Approval for Appomattox Deep Water Exploration Plan in the Gulf of Mexico, <a href="http://www.energy-pedia.com/article.aspx?articleid=145375 ">http://www.energy-pedia.com/article.aspx?articleid=145375 </a>(last visited June 15, 2011).<br />
</span></p>
<p><span style="font-size: smaller">(3) NTL No. 2010-N06, Frequently Asked Questions, No. 14, <a href="http://www.gomr.boemre.gov/homepg/regulate/regs/ntls/2010NTLs/10-n06-FAQs.pdf">http://www.gomr.boemre.gov/homepg/regulate/regs/ntls/2010NTLs/10-n06-FAQs.pdf</a> (last visited June 14, 2011),<br />
</span></p>
<p><span style="font-size: smaller">(4) Supplemental Exploration Plan, Section 2(j) Blowout scenario, <a href="http://www.gomr.boemre.gov/PI/PDFImages/PLANS/30/31468.pdf ">http://www.gomr.boemre.gov/PI/PDFImages/PLANS/30/31468.pdf </a>(last visited June 14, 2011).<br />
</span></p>
<p><span style="font-size: smaller">(5)&nbsp;Earth Justice Comments dated April 21, 2011, <a href="http://www.courthousenews.com/2011/06/14/ShellDoc.pdf ">http://www.courthousenews.com/2011/06/14/ShellDoc.pdf </a>(last visited June 14, 2011).<br />
</span></p>
<p><span style="font-size: smaller">(6) Angel Gonzalez (Dow Jones Newswire), MWCC Oil Spill Containment System Approved for 10,000-Foot Depths, Oil &amp; Gas Journal (June 14, 2011), <a href="http://online.wsj.com/article/BT-CO-20110614-713284.html?mod=WSJ_Energy_middleHeadlines ">http://online.wsj.com/article/BT-CO-20110614-713284.html?mod=WSJ_Energy_middleHeadlines </a>(last visited June 15, 2011).<br />
(7)&nbsp; Id.<br />
</span></p>
<p><span style="font-size: smaller">(8)&nbsp; BOERMRE&rsquo;s Fourth Permit with MWCC System, Oil &amp; Gas Journal, p. 5 (March 28, 2011).<br />
</span></p>
<p><span style="font-size: smaller">(9)&nbsp; Ultra-deep Gulf of Mexico exploration started in 2005 resulting in a lower number of comparable events. Deepwater drilling also occurs worldwide. <br />
</span></p>]]></description>
<link>http://www.louisianalawblog.com/energy-environmental-groups-attempt-to-block-shell-deepwater-gulf-of-mexico-drilling.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/energy-environmental-groups-attempt-to-block-shell-deepwater-gulf-of-mexico-drilling.html</guid>
<category>Admiralty and Maritime</category><category>Energy</category><category>Environmental Litigation and Regulation</category><category>Louisiana In General</category><category>New Orleans/Louisiana Recovery</category>
<pubDate>Thu, 16 Jun 2011 10:26:44 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>
<item>
<title>BOEMRE  Notice Requires  Hurricane and Tropical Storm Effects Reports</title>
<description><![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1669644.html">R. Lee Vail</a></p>
<p>On June 1, 2011, the Bureau of Ocean Energy Management, Regulation and Enforcement (BOEMRE) issued a notice to Gulf of Mexico Outer Continental Shelf Region (GOMR) lease and pipeline right-of-way (ROW) holders on reporting hurricane and tropical storm effects. Specifically, the recent notice, designated NTL No. 2011-G01<span style="font-size: smaller">(1)</span>, requires four reports, as appropriate:</p>
<ul>
    <li>Evacuation and Production curtailment statistic report &ndash; partially evacuated platforms are not considered evacuated</li>
    <li>Facility shut-in reports &ndash; including facilities that are partially shut-in</li>
    <li>Facility damage reports &ndash; including platforms, rigs and pipelines</li>
    <li>Pollution reports - facility discharged or continues to discharge oil during or as a result of the event<br />
    &nbsp;</li>
</ul>
<p>The <strong>Evacuation and Production curtailment statistic report </strong>and the <strong>Facility shut-in report overlap </strong>in subject matter. They differ in that the first report is general and requires overall company statistics (number of facilities evacuated or not evacuated, overall production shut-in); the second report is specific, requiring statistics platform by platform. <strong>Facility damage reports </strong>are to be submitted <strong>as soon as the information becomes available</strong>. <strong>Other reports </strong>are to be submitted <strong>daily as long as the condition exists</strong>. Reports may be submitted by e-mail or through the BOEMRE GOMR internet-based Permitting and Reporting System (eWell). Although the notice outlines the specific information and instructions required when the transmission is by e-mail, BOEMRE GOMR strongly encourages use of eWell to transmit the required data.</p>
<p>The eWell system, described in NTL No. 2007-G15 (<span style="font-size: smaller">2)</span>, was developed to increase efficiency of well permitting and reporting transactions between OCS lessees and operators and the GOMR by both reducing the time (and cost) required to process data and to reduce input errors. The system is designed to simplify submittal of multiple reports and subsequent daily reports. Interested lessees and operators and pipeline ROW holders must apply to BOEMRE GOMR for access to the eWell system.<br />
&nbsp;</p>
<p style="margin: 0in 0in 0pt"><span style="font-size: smaller"><span style="line-height: 115%">[1]</span> BOEMRE, Hurricane and Tropical Storm Effects Reports, NTL No. 2011-G01, </span><a href="http://www.gomr.boemre.gov/homepg/regulate/regs/ntls/2011NTLs/11-G01.pdf"><span style="font-size: smaller">http://www.gomr.boemre.gov/homepg/regulate/regs/ntls/2011NTLs/11-G01.pdf</span></a><span style="font-size: smaller"> (last visited June 10, 2011).</span></p>
<p style="margin: 0in 0in 0pt">&nbsp;</p>
<p style="margin: 0in 0in 0pt"><span style="font-size: smaller"><span style="line-height: 115%">[2]</span> BOERME, eWell Permitting and Reporting System, NTL- No. 2007-G15, </span><a href="http://www.gomr.boemre.gov/homepg/regulate/regs/ntls/2007NTLs/07-g15.pdf"><span style="font-size: smaller">http://www.gomr.boemre.gov/homepg/regulate/regs/ntls/2007NTLs/07-g15.pdf</span></a><span style="font-size: smaller"> (last visited June 10, 2011).</span></p>
<p>&nbsp;</p>
<p>&nbsp;</p>]]></description>
<link>http://www.louisianalawblog.com/admiralty-and-maritime-boemre-notice-requires-hurricane-and-tropical-storm-effects-reports.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/admiralty-and-maritime-boemre-notice-requires-hurricane-and-tropical-storm-effects-reports.html</guid>
<category>Admiralty and Maritime</category><category>Energy</category><category>Environmental Litigation and Regulation</category><category>Hurricane Gustav</category><category>Hurricane Katrina</category><category>Louisiana In General</category><category>New Orleans/Louisiana Recovery</category>
<pubDate>Fri, 10 Jun 2011 16:24:53 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>
<item>
<title>Office of Conservation Issues Emergency Order Imposing Affirmative Obligations on Oilfield Sites, Facilities, Structures, Injection Wells and Pipelines Throughout the State</title>
<description><![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1669644.html">R. Lee Vail</a></p>
<p>On April 28, 2011, Governor Bobby Jindal declared a State of Emergency as a result of growing concern over the predicted crest of the Mississippi River well above flood stage in many areas. Consistent with his authority, on May 13, 2011, James Welsh, Commissioner of Conservation, also issued an emergency and administrative order. It is expected that substantial flooding in the state will likely lead to adverse effects on many oilfield sites which could result in serious threats to public safety and the environment. The order specifically applies to following throughout the state:</p>
<ul>
    <li>Oilfield sites &ndash; including injection wells</li>
    <li>Other facilities &ndash; including commercial E&amp;P waste disposal and transfer stations</li>
    <li>Structures and Pipelines</li>
</ul>
<p><br />
Ordered actions are both general calls for alert monitoring of the situation and a more specific list of necessary steps (as appropriate). The Order contains a practical, common sense mandate, to keep track of forthcoming proclamations, orders, warnings, predictions, forecasts, directives or other communications from federal, state and local authorities and to monitor water levels and weather activity. Additionally, the order requires operators to take all necessary steps and perform all necessary actions to avoid damage to the environment or threats to life or safety, including the following, where appropriate:</p>
<ul>
    <li>Empty petroleum tanks and re-fill with water</li>
    <li>Remove chemicals from sites</li>
    <li>Remove or secure loose items</li>
    <li>Ensure that storm chokes or downhole plugs are installed in wells</li>
    <li>Empty active pits of E&amp;P waste</li>
    <li>Shut in and secure wells where necessary</li>
    <li>Protect sites from stray debris</li>
</ul>
<p>The above list of actions is discretionary, tasking each operator with the duty to determine which actions are necessary as each operator is in the best position to assess the potential risks and dangers.</p>
<p>The Order also requires notification to the Office of Conservation within 12 hours should an operator shut down one of the covered facilities. The Order will extend for 120 days, unless modified or extended. The order may be <a href="http://dnr.louisiana.gov/assets/OC/eng_div/Emergency_Order_No_2011-001_20110513.pdf">found here</a>.&nbsp;</p>]]></description>
<link>http://www.louisianalawblog.com/louisiana-in-general-office-of-conservation-issues-emergency-order-imposing-affirmative-obligations-on-oilfield-sites-facilities-structures-injection-wells-and-pipelines-throughout-the-state.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/louisiana-in-general-office-of-conservation-issues-emergency-order-imposing-affirmative-obligations-on-oilfield-sites-facilities-structures-injection-wells-and-pipelines-throughout-the-state.html</guid>
<category>Admiralty and Maritime</category><category>Coastal/Wetlands Issues</category><category>Environmental Litigation and Regulation</category><category>Louisiana In General</category>
<pubDate>Tue, 17 May 2011 10:27:12 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>
<item>
<title>A Recent U.S. Fifth Circuit Decision Shows the Importance of Including a Release of &quot;Any and All Claims&quot; in a Settlement Agreement</title>
<description><![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1355945.html">Sean T. McLaughlin</a></p>
<p>When drafting a settlement agreement, the parties almost always have competing interests. The Plaintiff will push for a vaguely-worded settlement in an attempt to take another &ldquo;bite-at-the-apple&rdquo; down the road; the Defendant will push for a broad, all-encompassing release of liability (i.e., &ldquo;any and all claims&rdquo;) in an attempt to &ldquo;close-the-books&rdquo; on the Plaintiff&rsquo;s claims. Sometimes, the parties will compromise by executing a settlement agreement which falls somewhere in the middle. However, both parties should be aware that compromises made during the settlement negotiations can lead to unintended consequences down the road.</p>
<p>In <em>Cooper v. Intern. Offshore Services, LLC,</em> 2009 WL 5175216 (E.D. La. Dec. 17, 2009), <em>aff&rsquo;d,</em> 2010 WL 3034497 (5th Cir. Aug. 3, 2010), the Plaintiff sustained injuries while working on a ramp connected to a vessel owned by his employer, International Marine. International Marine thereafter paid the Plaintiff benefits pursuant to the Longshore and Harbor Workers&rsquo; Compensation (&ldquo;LHWCA&rdquo;). After the Plaintiff recovered from his injuries, he agreed to settle his claim for &ldquo;compensation&rdquo; against International Marine. The text of the settlement agreement stated that the Plaintiff released International Marine from &ldquo;any and all obligations [&hellip;] for any benefits under the LHWCA&rdquo; as a result of his accident. Id. at *2. Under &sect; 908(i), all settlements of compensation benefits must be submitted to the District Director for approval. <br />
&nbsp;</p>]]><![CDATA[<p>The District Director approved this settlement agreement and issued a compensation order stating that the Plaintiff had settled &ldquo;any and all claims&rdquo; which he may have had against International Marine arising out of his injury. Id. at *3. Although this &ldquo;any and all claims&rdquo; language of the Compensation Order was slightly different than the &ldquo;any and all obligations [&hellip;] for benefits under the LHWCA&rdquo; language of the settlement agreement, the Plaintiff did not seek review the Compensation Order with the Benefits Review Board.</p>
<p>Several months later, the Plaintiff filed a Complaint against International Marine pursuant to the Jones Act or, alternatively, &sect; 905(b) of the LHWCA in the United States District Court for the Eastern District of Louisiana. Shortly thereafter, International Marine filed a Motion for Summary Judgment. In that pleading, International Marine argued that the Plaintiff&rsquo;s claims were barred by <em>res judicata </em>due to the terms of the District Director&rsquo;s Compensation Order. Id. at *1.</p>
<p>The Plaintiff opposed the Motion for Summary Judgment and argued that the District Director&rsquo;s order was &ldquo;erroneous&rdquo; because the Plaintiff did not intend to settle his &sect; 905(b) claim. Instead, the Plaintiff claimed that he only intended to settle his claim for &ldquo;compensation benefits.&rdquo; Id. at *2. In essence, the Plaintiff was attempting to appeal the District Director&rsquo;s Compensation Order. However, International Marine averred that the District Court was without jurisdiction to review the District Director&rsquo;s Order. Id. at *3 per &sect; 921 of the LHWCA.</p>
<p>Applying the Compensation Order as written, the District Court held that the Plaintiff&rsquo;s claims against International Marine were barred by the doctrine of res judicata. Id. at *4. The U.S. Fifth Circuit affirmed. 2010 WL 3034497 (5th Cir. Aug. 3, 2010). In doing so, the U.S. Fifth Circuit noted that the unambiguous language of the District Director&rsquo;s <em>compensation order </em>required the application of the doctrine of res judicata. Id. at *7.</p>
<p>This case shows the importance of including a release of &ldquo;any and all claims&rdquo; in settlement agreements. Had such language been included in both the settlement agreement and the District Director&rsquo;s findings of fact, Plaintiff may not have ever filed suit. In addition, this case also shows the importance of carefully reviewing the District Director&rsquo;s Compensation Order following the execution of a &sect; 908(i) settlement. If a party believes the language to be in error, there is a specific procedure which must be followed to appeal same &ndash; and failure to do so can render the decision non-reviewable.<br />
&nbsp;</p>]]></description>
<link>http://www.louisianalawblog.com/admiralty-and-maritime-a-recent-us-fifth-circuit-decision-shows-the-importance-of-including-a-release-of-any-and-all-claims-in-a-settlement-agreement.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/admiralty-and-maritime-a-recent-us-fifth-circuit-decision-shows-the-importance-of-including-a-release-of-any-and-all-claims-in-a-settlement-agreement.html</guid>
<category>Admiralty and Maritime</category>
<pubDate>Wed, 05 Jan 2011 11:30:56 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>
<item>
<title>Is the Limitation of Liability Act Going to Sink with the Deepwater Horizon?</title>
<description><![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1195210.html">Karen Waters Shipman</a></p>
<p>The recent tragedy involving the Mobile Offshore Drilling Unit <em>Deepwater Horizon </em>has shed a very bright and very public light on a much and often litigated 159-year old law previously known to very few outside of the maritime industry&mdash;the Shipowner&rsquo;s Limitation of Liability Act, (&ldquo;the Limitation Act&rdquo;), 46 U.S.C. &sect; 30505 (formerly 46 U.S.C. &sect; 183). What the Limitation Act does is entitle a vessel owner to limit its liability after a maritime incident or casualty to the <em>post casualty </em>value of the vessel and its pending freight, which may be zero if the vessel is a total loss, except when the loss occurred due to the vessel owner&rsquo;s &quot;privity or knowledge.&quot; Privity or knowledge is found to exist where the acts of negligence or unseaworthiness that caused the casualty were known or should have been known to the vessel owner.</p>
<p>In addition to limiting a vessel owner&rsquo;s liability, the Limitation Act also has several procedural benefits in that it allows the vessel owner in some instances to force all claims involving a vessel casualty to be litigated in a single Federal forum, often of the vessel owner&rsquo;s choosing. Additionally, claimants in a vessel casualty can also benefit to some extent in that they have some security for their claims in a limitation proceeding because the vessel owner must either deposit the claimed value of the post-casualty vessel at issue in the registry of the Court or post a bond for such amount with the Court. <br />
&nbsp;</p>]]><![CDATA[<p>The Limitation Act was passed by Congress in 1851 to encourage investment in the American shipping industry and level the playing field for U.S. vessel owners who were then competing against foreign vessel owners already benefiting from similar liability protection. Without the Limitation Act, it was felt that claims for injury, death, property or cargo loss could far exceed a vessel&rsquo;s value, which would only serve to discourage maritime commerce. Notably, the Limitation Act applies to all seagoing vessels, as well as all vessels used on lakes, rivers, or in inland navigation, including canal boats, barges, and lighters, but only to incidents or casualties occurring on the navigable waters of the United States. The most famous application of the Limitation Act to date would probably be when the U.S. Supreme Court allowed the owners of the Titanic to limit their liability to the value of the Titanic&rsquo;s surviving lifeboats, a mere $92,000 at the time, after the Titanic sank in April of 1912 claiming more than 1,500 lives. Despite public outrage at the time, however, the long-standing Limitation Act survived, having accomplished its intended purpose, and it has been invoked by vessel owners countless times in the last century in all manners of maritime casualties.</p>
<p>The Deepwater Horizon is a floating drilling platform capable of navigation, similar to a vessel, and, thus, it has the legal status necessary for its owners to seek limitation of liability for the explosion in the Gulf of Mexico. Transocean filed a Limitation of Liability proceeding in Federal Court in Texas, submitting that the post-casualty value of the Deepwater Horizon, which sank in the Gulf of Mexico, is no more than $27 million, which is considerably less than its pre-casualty value of around $650 million. Transocean&rsquo;s filing of that Limitation proceeding has sparked a new national, and perhaps worldwide, debate about the viability of the Limitation Act in modern times.</p>
<p>Many in the maritime and legal community have argued both for and against the Limitation Act over the years. The arguments against the Limitation Act being that the public policy behind the Limitation Act is antiquated and unnecessary because vessel owners today can readily procure liability insurance to protect themselves from damage claims caused by a vessel&rsquo;s alleged unseaworthiness or negligence. While it appears often reported in today&rsquo;s latest debate on the Limitation Act that U.S. Courts have already begun to disfavor the Limitation Act, it would not be accurate to state that the Limitation Act is not still being successfully invoked by vessel owners in serious marine casualties.</p>
<p>In fact, a review of recent case law in the U.S. Fifth Circuit reveals that the Court <em>granted </em>limitation of liability to vessel owners in at least two cases in the last two years. Indeed, the vessel owners in those two cases limited their liability to the value of the vessel, which was considerably less in both cases than the claimants&rsquo; alleged damages, because, generally, owners of a vessel may delegate non-managerial duties and discretion to experienced employees, like vessel captains, without subjecting the vessel owner to unlimited liability.</p>
<p>One of the two recent U.S Fifth Circuit cases involved a fishing vessel limiting its liability to $340,000 after it struck an offshore oil platform that had been in place for twenty years, allegedly causing $4 million dollars in damage to the platform and oil well and injuring three passengers on the fishing vessel. The other case involved two barges that broke free from their moorings, struck, and damaged a bridge on Interstate 10 during Hurricane Katrina. Further, relying on the foregoing trend in the U.S. Fifth Circuit, the U.S. Sixth Circuit also recently granted a vessel owner limitation of liability, similarly finding that the vessel owner had rightfully relied upon the navigational expertise of a competent ship&rsquo;s master in an accident where the owner&rsquo;s tugboat created a wake that swamped a recreational fishing boat, killing one of the fishing boat&rsquo;s passengers. Thus, the Limitation Act has clearly not altogether fallen out of favor with the Courts or with vessel owners.</p>
<p>Nevertheless, despite what appears to have been a recent trend in favor of the application of the Limitation Act, the recent Deepwater Horizon disaster and the ensuing media blitz and worldwide attention as to how the injured parties will be compensated, may prove to be the event that finally sinks the Limitation Act. To that end, bills were recently introduced in both houses of Congress that would, if enacted into law, repeal most of the Limitation Act by lifting the liability limit and also allowing claimants to seek noneconomic damages such as pain, suffering, emotional distress and other types of damages not provided for in the Limitation Act. Perhaps if the pervasive media and instantaneous information exchange that exists now had existed in 1912 when the Titanic sank, the longstanding Limitation Act would have perished sooner. In the end, however, it remains to be seen what effect, if any, the repeal of the Limitation Act, would have on the American shipping and vessel industry and whether the repeal will be retroactive such that Transocean will no longer be able to seek Limitation for the Deepwater Horizon. <br />
&nbsp;</p>]]></description>
<link>http://www.louisianalawblog.com/admiralty-and-maritime-is-the-limitation-of-liability-act-going-to-sink-with-the-deepwater-horizon.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/admiralty-and-maritime-is-the-limitation-of-liability-act-going-to-sink-with-the-deepwater-horizon.html</guid>
<category>Admiralty and Maritime</category>
<pubDate>Mon, 03 Jan 2011 10:53:32 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>
<item>
<title>District Courts Continue To Agree That Production SPARs Are Not Vessels</title>
<description><![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1669644.html">R. Lee Vail</a></p>
<p>A spar is a nautical structure designed to float with the bulk of the hull below the waves-something akin to a giant buoy. <em>Fields v. Pool Offshore, Inc., </em>182 F.3d 353(5th Cir. 1999). Spars are essential to the expansion of oil production in deep water and their use has led to the legal question of their status. Are they vessels? Consistent with the Fifth Circuit Court of Appeals&rsquo;s three part test, several recent decisions in Texas District Courts have found that a SPAR is a work platform and not a vessel. The finding is important since jurisdiction of a Jones Act action requires the existence of a vessel.</p>
<p>In <em>Fields</em>, the Fifth Circuit laid out the three part test to distinguish &ldquo;stationary&rdquo; work platforms from vessels. These factors include the function of the structure, whether it is moored or secured at the time of the accident, and that it has greater than theoretical mobility. <em>Fields </em>distinguished spars from drilling rigs, as rig move from site to site; spars are committed to a particular location. Spars have elaborate methods of attaching to the sea floor which would be difficult and expensive to undue; drilling rigs do not. Subsequent to <em>Fields</em>, the United States Supreme Court clarified that the distinction was not time dependent; that is it did not flip back and forth dependent on when the accident occurred. Following is a summary of recent cases which have applied the above test.<br />
&nbsp;</p>]]><![CDATA[<p>In <em>Jordan v. Shell Oil Co</em>., 2007 WL 2220986 (S.D.Tex. 2007), the court granted a request for summary judgment since the spar, the URSA was not vessel. The court noted that spar was towed in portions, assembled over a period of years and once assembled was practically incapable of maritime transportation.</p>
<p>In contrast, in <em>Nottingham v. Murphy Oil USA, Inc., </em>2009 WL 50160 (E.D. La. 2009), the court found that &ldquo;both the MEDUSA and the lifeboats possess some vessel characteristics&rdquo; and denied the defendants motion for summary judgment considering the question of a vessel was a question of fact to be decided by a jury. Murphy Oil subsequently settled the case and was dismissed by order dated November 11, 2010.</p>
<p>In <em>Moore v. Bis Salamis, Inc., </em>2010 WL 3745023 (E.D.Tex. 2010) and, <em>Scroggs v. Bis Salamis, Inc., </em>2010 WL 3910563 (E.D.Tex. 2010), the court found the reasoning in <em>Jordan </em>persuasive, likewise dismissing the case under summary judgment, despite also finding that &ldquo;Thunder Horse&rsquo;s attachment to its current location less extensive than URSA&rsquo;s&rdquo;. The court further found that Thunder Horse&rsquo;s capability of moving laterally within a 700 foot radius as &ldquo;merely incidental to its function as a work platform and, thus does not render it practically capable of maritime transportation.&rdquo; The court put the greatest weight on Thunder Horse&rsquo;s &ldquo;extensive attachment to the ocean floor and long term commitment to a single location.&rdquo;</p>
<p>Most recently, in <em>Mendez v. Anadarko Petroleum, Corp</em>., 2010 WL 4644049 (S.D. Tex. 2010) the court found, as a matter of law, that the Red Hawk spar was not a vessel and denied the plaintiffs motion to remand to state court. The court was unmoved by the fact that Anadarko had performed a study and determine the cost ($42 million) to move the spar. A theoretical capability was insufficient. Further, the presence of safety equipment consistent with a vessel (life jackets, ring buoys, inflatable rafts) did not weigh in favor of finding the spar to be a vessel. It was the type of equipment one expected to see on a structure 120 miles from the coast.</p>
<p>&nbsp;</p>]]></description>
<link>http://www.louisianalawblog.com/admiralty-and-maritime-district-courts-continue-to-agree-that-production-spars-are-not-vessels.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/admiralty-and-maritime-district-courts-continue-to-agree-that-production-spars-are-not-vessels.html</guid>
<category>Admiralty and Maritime</category>
<pubDate>Tue, 28 Dec 2010 09:05:07 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>
<item>
<title>Recent Developments in E-Discovery in Louisiana</title>
<description><![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1190286.html">Katie D. Bell</a></p>
<p>Electronic Discovery, or &ldquo;E-Discovery&rdquo;, is not considered the &ldquo;novel issue&rdquo; it once was. However, E-Discovery still presents problems that litigants and courts struggle with. Below is a summary of recent Louisiana Federal Court opinions dealing with the issues surrounding E-Discovery.</p>
<p>In <em>Frees, Inc. v. McMillian</em>, 2007 WL 184889 (W.D. La. Jan. 22, 2007), the Western District of Louisiana granted the plaintiff&rsquo;s motion to compel. In an unfair competition and trade secret theft action, the plaintiff claimed that the defendant, a former employee, had stolen various data files. Plaintiff had unsuccessfully requested production of defendant&rsquo;s laptop and desktop. The Court granted the motion to compel the defendant to produce these two items because they were the most likely places that the data files would be located. The Court did institute protective measures so as to prevent the disclosure of any irrelevant or personal information. <br />
&nbsp;</p>]]><![CDATA[<p>In <em>Auto Club Family Ins. Co. v. Ahner</em>, 2007 WL 2480322 (E.D. La. Aug. 29, 2007), the Eastern District of Louisiana denied a non-party&rsquo;s motion for a protective order when the non-party was subpoenaed to produce electronically stored information. The non-party in the insurance suit stemming from Hurricane Katrina was subpoenaed to provide hard copies of its investigation files and the corresponding electronic data. The Court held that the non-party did not meet its burden in proving to the Court that &ldquo;the data sought is not reasonably accessible because of undue burden or cost&rdquo; and therefore had to produce the electronic data in addition to the hard copies.<br />
&nbsp;</p>
<p>In <em>Green v. Fluor Corp</em>., 2009 WL 1668376 (M.D. La. June 11, 2009), a case in the Middle District of Louisiana, the defendant sought access to the plaintiff&rsquo;s phone and e-mail system to obtain the original version of a photograph the plaintiff had given to the defendant as part of discovery. The defendant claimed the produced photograph taken from a phone was of low quality and wanted access to the plaintiff&rsquo;s phone and e-mail to obtain a clearer picture. The Court denied the motion because the defendant failed to ask for the particular form of the discovery in regards to the picture and therefore had to settle with what the plaintiff had produced.</p>
<p>In <em>Marketfare Annunciation, LLC v. United Fire &amp; Casualty Ins. Co</em>., 2007 WL 3273440 (E.D. La. Nov. 5, 2007), the Eastern District of Louisiana dealt with a spoliation issue involving electronic evidence in a claim that arose due to Hurricane Katrina. The defendant failed to produce certain e-mails even after the plaintiff put the defendants on notice to preserve them. However, the plaintiff waited until the eve of the close of discovery to file sanctions and therefore the court denied the request.</p>
<p>In <em>Thomas v. IEM</em>, 2008 WL 695230 (M.D. La. Mar. 12, 2008), the Middle District of Louisiana dealt with a civil rights violation. The plaintiff served a Rule 45 subpoena on the defendant in order to obtain access to nine named individuals&rsquo; e-mail boxes. The Court held this was an attempt to circumvent discovery deadlines under Rules 26 and 34 and therefore did not grant the request.</p>
<p>In <em>Canon USA, Inc. v. SAM, Inc</em>., 2008 WL 2522087 (E.D. La. June 20, 2008), the Eastern District of Louisiana granted a motion to compel electronically stored data that the defendant had at his home in Florida. After Hurricane Katrina, defendant moved his computer to Florida but when discovery requests were made he did not search the computer to provide complete answers to interrogatories. The court held that this &ldquo;lackadaisical&rdquo; treatment of discovery was unacceptable and held that any undeleted information on the computer was discoverable. The Court ordered the defendant to obtain the services of a &ldquo;forensic computer specialist&rdquo; and fully respond to the discovery request.</p>
<p><em>In re </em>Riverside Healthcare, Inc., 2008 WL 4183609 (M.D. La. Sept. 11, 2008), a case in the Middle District of Louisiana, a bankruptcy liquidating supervisor accused a creditor of destroying evidence and sought the adverse presumption that follows spoliation. The creditor had deleted e-mails that the liquidating supervisor considered necessary evidence. However, the court held that spoliation requires bad faith and here there was no bad faith due to the fact that the creditor destroyed e-mails automatically every sixty to ninety days.</p>
<p>In <em>Johnson v. Big Lots Stores, Inc., </em>2008 WL 2191357 (E.D. La. May 7, 2008), the Eastern District of Louisiana ruled that a plaintiff could not take another deposition of the defendant&rsquo;s representatives regarding how the defendants preserved and collected electronic data. The Court stated that since the plaintiffs failed to list &ldquo;e-Discovery&rdquo; as an issue at the original deposition and since they waited until two days before the close of discovery, the motion to compel the second deposition was denied. The Court also stated that &ldquo;e-discovery&rdquo; matters are no longer the novel issues that they once were with the advent of the Internet and wide expansion of computerized data collection and the plaintiffs had no legitimate excuse as to why they failed to make issue of &ldquo;e-discovery&rdquo; at the original deposition.</p>
<p>In <em>Hoover v. Fla. Hydro, Inc., </em>2008 WL 4467661 (E.D. La. Oct. 1, 2008), the Eastern District of Louisiana allowed discovery of two non-parties&rsquo; computers. In this breach of contract claim, the defendant sought the electronic data from the plaintiff&rsquo;s mother and a friend who helped him in his business. The Court held that this would not create an undue burden on the mother because the non-party was involved in the plaintiff&rsquo;s business and would have relevant information stored on her computer. The subpoena was quashed as to the friend because he had adequately answered the discovery request.</p>
<p>In <em>May v. Fedex Freight Southeast, Inc</em>., et al., 2009 WL 1605211 (M.D. La. June 8, 2009), a Middle District of Louisiana case, the plaintiff brought suit for sexual harassment while she was employed by the defendant. Plaintiff sought &ldquo;any and all e-mails referencing, as well as those sent to and from, plaintiff and [the accused sexual harasser].&rdquo; The defendant claimed that this was not possible because the e-mail was inaccessibly archived and unsorted. The Court held that the plaintiff and defendant had to meet with the defendant&rsquo;s IT department to discuss the &ldquo;burden and expense of producing the e-mails requested by plaintiff.&rdquo; If then there was still no agreement, the plaintiff was urged to reassert her motion to compel.<br />
&nbsp;</p>]]></description>
<link>http://www.louisianalawblog.com/louisiana-in-general-recent-developments-in-ediscovery-in-louisiana.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/louisiana-in-general-recent-developments-in-ediscovery-in-louisiana.html</guid>
<category>Admiralty and Maritime</category><category>Benzene Litigation</category><category>Business Litigation</category><category>Class Action</category><category>Construction Law</category><category>Environmental Litigation and Regulation</category><category>General Litigation</category><category>Labor and Employment Law</category><category>Legacy Oil Field Sites</category><category>Louisiana In General</category><category>Products Liability</category><category>Professional Liability</category><category>Toxic Tort Litigation</category>
<pubDate>Thu, 07 Oct 2010 14:38:13 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>
<item>
<title>Immigration Status is Irrelevent Under the Longshore and Harbor Workers&apos; Compensation Act</title>
<description><![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1496057.html">Amanda L. Howard</a></p>
<p>In <em>Bollinger Shipyards, Inc. v. Director, Office of Worker&rsquo;s Compensation Programs, U.S. Dept. of Labor, </em>(5th Cir. 2010) the United States Fifth Circuit upheld the award of workers compensation benefits to an undocumented immigrant worker who was injured on the job as a pipefitter.</p>
<p>The <em>Bollinger </em>plaintiff, Jorge Rodriguez, fell and allegedly injured himself while welding for his employer, Bollinger Shipyards, Inc.&nbsp; At the time of his alleged injury, Rodriguez had been working for Bollinger for approximately eight months, having initially obtained employment by falsely holding himself out as a United States citizen.&nbsp; Rodriguez presented Bollinger with a false Social Security Card.&nbsp; Bollinger initially paid Rodriguez temporary disability benefits and reimbursed him for a portion of his medical bills. <br />
&nbsp;</p>]]><![CDATA[<p>Two years later, however, Bollinger terminated all payments after discovering that Rodriguez was an undocumented immigrant.&nbsp; Rodriguez then filed for benefits under the LHWCA and the case proceeded to an administrative hearing.&nbsp; The ALJ ruled in favor of Rodriguez on all issues, concluding that he was unable to work and that he was not at maximum medical improvement.&nbsp; The ALJ also held that undocumented workers, such as Rodriguez, were indeed eligible for benefits.&nbsp; Bollinger appealed the ALJ&rsquo;s ruling to the Benefit Review Board; however, the BRB affirmed.&nbsp; Thereafter, Bollinger appealed to the Fifth Circuit.</p>
<p>The primary question on appeal was whether an undocumented immigrant could be eligible for benefits under the LHWCA.&nbsp; Bollinger argued that Rodriguez&rsquo;s injury caused him no loss of wage earning capacity because he had no legal wage earning capacity at the time he was injured.&nbsp; As such, Bollinger argued that Rodriguez was <em>per se </em>ineligible under the Act.&nbsp; Bollinger further argued that the Benefit Review Board&rsquo;s ruling undermined the Congressional policies embedded in the Immigration Reform and Control Act of 1986.&nbsp; Bollinger relied on a line of Supreme Court cases, including <em>Hoffman Plastic Compounds, Inc. v. NLRB</em>, 535 U.S. 137 (2002), which made the distinction as to whether wages could be paid legally in declining to award some types of relief under the NLRA in order to avoid a conflict with the immigration laws, which prohibit the employment of aliens who enter or remain in the country illegally and which also criminalizes the use of false documentation to obtain work.</p>
<p>The Director, OWCP and several <em>amici curiae </em>filed briefs in support of Rodriguez&rsquo;s eligibility for benefits under the LHWCA, arguing that failing to require workers&rsquo; compensation for immigrant workers encourages employers to hire undocumented workers.&nbsp; The Fifth Circuit reviewed the statutory language of the LHWCA and concluded that the statute provides coverage to undocumented immigrants.&nbsp; The Court found the precise language of &sect;909(g) persuasive.&nbsp; Section 909 (g) states that &ldquo;[c]ompensation under the [the LHWCA] to aliens not residents (or about to become nonresidents) of the United States or Canada shall be the same <em>in amount as provided for residents.</em>&rdquo;&nbsp; The Fifth Circuit noted that other courts, have concluded that the unmodified term &ldquo;alien&rdquo; encompasses both documented and undocumented immigrants.&nbsp; The court noted that compensation under the LHWCA is a non-discretionary statutory remedy.&nbsp; Unlike the NLRA, the LHWCA is a substitute for tort law, abrogating fault of either the employer or the employee.&nbsp; Further, the court held that awarding death or disability benefits <em>post hoc</em> to an undocumented immigrant under the LHWCA does not &ldquo;unduly trench upon&rdquo; the IRCA, because Congress chose to include a provision in the LHWCA expressly authorizing the award of benefits.</p>
<p>Finally, the court held that Fifth Circuit precedent has been that undocumented immigrants are eligible under the LHWCA, citing <em>Hernandez v. M/V Rajaan</em>, 841 F.2d 582, amended after rehearing, 848 F.2d 498 (5th Cir. 1988), the court held that Rodriguez was entitled to benefits because Bollinger failed to provide any evidence that Rodriguez was &ldquo;about to be deported or would surely be deported.&rdquo;&nbsp; The court also found persuasive the D.C. Circuit&rsquo;s opinion in <em>Rivera v. United Masonry, Inc., </em>948 F.2d 774, 775 (D.C. Cir. 1991), in which the court declined to take into consideration an immigrants undocumented status when determining his eligibility for benefits.</p>
<p>Bollinger filed a petition for review which was denied in all respects. (5th Cir. April 22, 2010).&nbsp; Although the Fifth Circuit seems to have made it clear that undocumented immigrant will remain eligible for benefits under the LHWCA, the court left open the possibility that an alien who was about to be deported or was sure to be deported might not be eligible for future lost wage benefits calculated as they would be earned in the U.S.<br />
&nbsp;</p>]]></description>
<link>http://www.louisianalawblog.com/admiralty-and-maritime-immigration-status-is-irrelevent-under-the-longshore-and-harbor-workers-compensation-act.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/admiralty-and-maritime-immigration-status-is-irrelevent-under-the-longshore-and-harbor-workers-compensation-act.html</guid>
<category>Admiralty and Maritime</category><category>Labor and Employment Law</category>
<pubDate>Thu, 12 Aug 2010 13:02:23 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>
<item>
<title>United States Fifth Circuit Reiterates Rule That Crew Members Are Not Entitled to a Salvage Award for Assistance Rendered to Their Own Vessel</title>
<description><![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1194685.html">Michael J. O'Brien</a></p>
<p>In <em>Solana v. GSF Development Driller I,</em> et al., 587 F.3d 266 (5th Cir. 2009), the United States Fifth Circuit reiterated the longstanding rule that generally, a seaman belonging to a vessel in peril cannot claim a salvage compensation for saving his vessel.</p>
<p>The facts in <em>Solana </em>are quite interesting.&nbsp; As Hurricane Katrina approached the Gulf Coast, Global Santa Fe (GSF) evacuated its jack-up and anchored rigs in the Gulf of Mexico, which included the Development Driller I (DDI), a $350 million dollar semi-submersible drilling rig. The DDI&rsquo;s power was shut off and its crew was evacuated.&nbsp; Solana, a 20 year GSF employee and Offshore Installation Manager (OIM) of the DDI, and Lally, a ballast control operator and senior dynamic positioning operator, were among those employees who were evacuated from the rig. <br />
&nbsp;</p>]]><![CDATA[<p>The DDI was seriously damaged as Katrina steamrolled through the Gulf.&nbsp; After the storm had passed, a representative of GSF sought volunteers to return to the DDI to attempt to save the vessel. Solana and Lally agreed to return to the DDI as part of the GSF team.&nbsp; While en route to the DDI, the GSF team noticed that the vessel was out of position, severely listing, and dragging its anchors.&nbsp; Quite simply, the DDI was in severe peril.&nbsp; The helicopter transporting the GSF team was unable to land on the vessel because the helicopter deck was sloped at an angle.&nbsp; Each member of the GSF team jumped from the airborne helicopter onto the DDI&rsquo;s deck.&nbsp; The team conducted a damage assessment, stopped flooding aboard the vessel, and attempted to stabilize the drilling unit.&nbsp; Two days after the GSF team began their efforts to save the vessel, a professional salvage team boarded the DDI.&nbsp; Solana and Lally worked with the professional salvage team for a few days until the vessel was finally stabilized.</p>
<p>Solana and Lally later filed suit seeking an award of pure salvage because they were part of the team that ultimately salvaged the vessel.&nbsp; Solana and Lally likely envisioned an enormous &ldquo;payday&rdquo; as the DDI was worth more than 350 million dollars.&nbsp; GSF moved for Summary Judgment asserting the longstanding rule that crew members are not entitled to a salvage award for assistance rendered to their own vessel.&nbsp; Solana and Lally countered with the argument that in certain circumstances, crew members can be salvors.&nbsp; Specifically, Plaintiffs cited existing jurisprudence holding that extraordinary events may occur in which a seaman&rsquo;s connection may be dissolved <em>de facto</em>, or by operation of law, or they may exceed their proper duty, in which case they may be permitted to assert a claim as salvors.&nbsp; The Fifth Circuit disagreed holding that the rule barring a crew member from a salvage award is longstanding and rooted in a crew member&rsquo;s duty to save both ship and cargo.&nbsp; Obviously, it is unwise to tempt a crew member to let their ship and cargo slip into a position of danger in order to claim a salvage award.</p>
<p>Ultimately, the Fifth Circuit held that Solana and Lally did not volunteer service to the DDI when it was in distress as volunteers within the parameters of the law of salvage.&nbsp; Instead, Solana and Lally had been asked by GSF to board the DDI following Katrina, and they expressly agreed to do so.&nbsp; Moreover, they expected to be compensated by GSF for their efforts to stabilize the DDI after it was damaged by Katrina regardless of whether those efforts were successful.&nbsp; A binding agreement to pay for salvage services irrespective of the success of the enterprise will defeat a claim for pure salvage.&nbsp; As such, Solana and Lally&rsquo;s claims for pure salvage were dismissed.<br />
&nbsp;</p>]]></description>
<link>http://www.louisianalawblog.com/admiralty-and-maritime-united-states-fifth-circuit-reiterates-rule-that-crew-members-are-not-entitled-to-a-salvage-award-for-assistance-rendered-to-their-own-vessel.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/admiralty-and-maritime-united-states-fifth-circuit-reiterates-rule-that-crew-members-are-not-entitled-to-a-salvage-award-for-assistance-rendered-to-their-own-vessel.html</guid>
<category>Admiralty and Maritime</category><category>Hurricane Katrina</category>
<pubDate>Fri, 06 Aug 2010 10:40:22 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>
<item>
<title>Structuring the Purchase of a Vessel Through a Corporate Entity for Tax Purposes Can Have Unintended Consequences</title>
<description><![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1355945.html">Sean T. McLaughlin</a></p>
<p>It is a fairly common practice for individuals purchasing pleasure yachts to take calculated steps to minimize sales taxes on their purchases. In fact, a simple &ldquo;Google&rdquo; search on the subject reveals many websites offering free advice on this issue. One of the tactics suggested by several websites seems fairly simple: instead of the individual purchasing the yacht, the <em>individual </em>forms a <em>corporation</em>, and the <em>corporation </em>purchases the yacht.</p>]]><![CDATA[<p>First and foremost, the author strongly recommends that any individuals considering purchasing a yacht seek the advice of legal counsel. The author specifically recommends seeking the advice of <u>both </u>a <em>tax </em>attorney and a <em>litigation </em>attorney. Why? A tax attorney can offer qualified legal advice concerning the <em>sales tax </em>issues surrounding the purchase. A litigation attorney can advise that structuring a purchase through a corporate entity can have significant <em>non tax-related </em>implications, including a <u>complete </u>bar against the recoverability of an entire class of damages.</p>
<p>In <em>Kelly v. Porter, Inc., </em>687 F. Supp. 2d 632 (E.D. La. 2010), the Eastern District of Louisiana made it clear that individuals who purchase recreational vessels through corporate entities <u>cannot </u>recover for any emotional distress or loss of enjoyment that the <em>individual LLC member </em>sustains when the vessel is damaged. The <em>Kelly </em>plaintiff wished to purchase a yacht for his own personal use. In an attempt to minimize the sales tax on that purchase, the <em>Kelly </em>plaintiff formed a new limited liability company (LLC) and named himself the sole member. Although the yacht was titled in the name of the LLC, the <em>Kelly </em>plaintiff considered himself to be the &ldquo;true&rdquo; owner of the yacht.</p>
<p>Shortly after it was purchased, the yacht was extensively damaged when it took on water while docked in its slip. The <em>Kelly </em>plaintiff and the LLC filed suit against the defendants alleging that they sustained &ldquo;emotional damages&rdquo; and &ldquo;loss of enjoyment&rdquo; due to the yacht being damaged. In response, the defendants filed a motion for summary judgment seeking to have <u>all </u>of the claims of the <em>individual </em>plaintiff dismissed for lack of standing. The defendants cited La. R.S. 12:1329, which states that the members of a LLC do not have an ownership interest in property owned by the LLC. Although the <em>Kelly </em>plaintiff attempted to claim that he was the &ldquo;equitable&rdquo; owner of the yacht, the Court disagreed and dismissed <u>all </u>of his claims. <br />
<br />
Additionally, the defendants sought to have the LLC&rsquo;s claims for &ldquo;emotional damages&rdquo; and &ldquo;loss of enjoyment&rdquo; (<em>i.e., </em>&ldquo;non-pecuniary damages&rdquo;) dismissed as well. The Court dismissed those claims, citing a litany of cases holding that corporations &ldquo;cannot recover non-pecuniary damages such as loss of enjoyment or emotional damages.&rdquo;</p>
<p>This decision makes it clear the Courts will not allow would-be yacht purchasers to &ldquo;have it both ways.&rdquo; Therefore, the author suggests that individuals considering purchasing a yacht should carefully consider <u>all </u>of the consequences of purchasing a yacht through an LLC and make a well-informed decision.<br />
&nbsp;</p>]]></description>
<link>http://www.louisianalawblog.com/admiralty-and-maritime-structuring-the-purchase-of-a-vessel-through-a-corporate-entity-for-tax-purposes-can-have-unintended-consequences.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/admiralty-and-maritime-structuring-the-purchase-of-a-vessel-through-a-corporate-entity-for-tax-purposes-can-have-unintended-consequences.html</guid>
<category>Admiralty and Maritime</category><category>Business and Corporate</category>
<pubDate>Wed, 04 Aug 2010 17:02:09 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>
<item>
<title>Limitation of Liability - Effect of Notice to a Single Co-Owner</title>
<description><![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1496024.html">William M. Burst</a></p>
<p>The Limitation of Liability Act provides, <em>inter alia</em>, that a vessel owner may petition a district court of competent jurisdiction for limitation of liability within six months of receiving written notice of a claim.&nbsp; <em>See generally </em>46 U.S.C.A &sect;&sect; 30501-30512 (West 2010).&nbsp;&nbsp;If the vessel owner fails to petition the court and the six month period lapses, it is thereafter precluded from seeking the Act&rsquo;s protection.&nbsp;&nbsp;The Act, however, does not address the effect that one co-owner&rsquo;s failure to file a petition for limitation has on another co-owner&rsquo;s right to subsequently seek limitation of liability. In other words, if co-owner &ldquo;X&rdquo; of a vessel receives notice of a claim against it and fails to file for limitation of liability within the requisite six-month period, is co-owner &ldquo;Y,&rdquo; who did not receive notice, precluded from filing for limitation of liability?</p>]]><![CDATA[<p>The Middle District of Florida is the only court to have addressed this issue.&nbsp; <em>See In re Complaint of LADY JANE, IN</em>C., 818 F. Supp. 1470 (M.D. Fla. 1992).&nbsp; In <em>LADY JANE</em>, the court held that a co-owner of a vessel who has not received notice of a claim against it cannot be prejudiced by another co-owner&rsquo;s failure to file for limitation of liability within six months of a claim being asserted against only her. <em>Id</em>. at 1474.</p>
<p>The court addressed a scenario in which a vessel was owned by a corporation with a lone shareholder.&nbsp; The shareholder received notice of a claim against her, but the corporation did not.&nbsp; Six months passed without any filing for limitation of liability.&nbsp; Thereafter, the corporation sought protection under the Limitation of Liability Act.&nbsp;&nbsp;After determining that the shareholder and the corporation were both owners of the vessel, the court addressed whether notice to one owner (the shareholder) and her subsequent failure to file for limitation, precluded the other owner (the corporation) from filing same.&nbsp;&nbsp;The court held that the corporation had never been on notice of any claim against it and as such, it could seek protection under the Act.&nbsp;&nbsp;Thus, in the aforementioned scenario, if co-owner &ldquo;X&rdquo; fails to file for limitation of liability within six months of receiving written notice, and co-owner &ldquo;Y&rdquo; subsequently receives notice of a claim against it, co-owner &ldquo;Y&rdquo; is not prejudiced by the failures of co-owner &ldquo;X.&rdquo;</p>
<p>Notably, <em>LADY JANE </em>cites no authority to support its holding nor is <em>LADY JANE </em>cited in any other federal opinions.&nbsp; It appears that, at this time, <em>LADY JANE </em>is the only authority on this matter.<br />
&nbsp;</p>]]></description>
<link>http://www.louisianalawblog.com/admiralty-and-maritime-limitation-of-liability-effect-of-notice-to-a-single-coowner.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/admiralty-and-maritime-limitation-of-liability-effect-of-notice-to-a-single-coowner.html</guid>
<category>Admiralty and Maritime</category>
<pubDate>Wed, 19 May 2010 10:00:11 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>
<item>
<title>A Jones Act Seaman Does Not Have Greater Remedies Against A Non-Employer Than He Does Against His Employer</title>
<description><![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1355945.html">Sean T. McLaughlin</a></p>
<p>It is well known that a seaman who is injured on the job can file suit against his employer in negligence due to the statutory provisions of the Jones Act. 45 U.S.C.A &sect;&sect; 30104.&nbsp; However, in a Jones Act suit, the injured seaman is prohibited from recovering &ldquo;non-pecuniary&rdquo; damages from his employer, a category which includes punitive damages and loss of consortium. (1).&nbsp; This limitation on recoverable damages is due to the language of Jones Act itself. <em>Miles v. Apex</em>, 498 U.S. 19 (1990).</p>
<p>In addition to bringing claims against his employer pursuant to the Jones Act, a seaman injured on the job often also files claims against non-employers. These claims are not dependant on the Jones Act, but rather general maritime law. In this situation, plaintiffs often attempt to recover non-pecuniary damages from the non-employer. Plaintiffs suggest that since there is no specific prohibition against the recovery of non-pecuniary damages in general maritime law, then why should an injured seaman be denied recovering non-pecuniary damages from non-employers? <br />
&nbsp;</p>]]><![CDATA[<p>Although this argument may initially appear to have merit, it is also problematic because it creates non-uniformity of a seaman&rsquo;s recovery based solely on the employer/non-employer distinction Fortunately, the U.S. Fifth Circuit resolved this dispute in <em>Scarborough v. Clemco</em>, 391 F. 3d 660 (5th Cir. 2004). In <em>Scarborough</em>, the U.S. Fifth Circuit held that a seaman cannot recover non-pecuniary damages from non-employer third parties, even though general maritime law contains no such prohibition.</p>
<p>Although <em>Scarborough </em>was decided by the U.S. Fifth Circuit in 2004, Plaintiffs continually try to ignore it. For example, in <em>Walker v. Rowan Companies, Inc</em>., 2009 WL 2030605 (E.D. La. July 9, 2009), the plaintiff attempted to recover non-pecuniary damages from a non-employer under the general maritime law. In an attempt to avoid the rule of <em>Scarborough</em>, the plaintiff argued that a distinction should be made when the alleged negligence occurred on land, as opposed to at sea. In rejecting the plaintiff&rsquo;s claim, Judge Engelhardt of the Eastern District of Louisiana noted that it was bound by Scarborough, and that the location of the alleged negligence bore &ldquo;no significance.&rdquo; Id. at *2.</p>
<p>Thus, it is highly recommended that non-employer defendants in such lawsuits should attempt to dismiss a plaintiff&rsquo;s claims for non-pecuniary damages at an early stage by way of a motion for summary judgment.&nbsp;</p>
<p>**************************</p>
<p><span style="font-size: smaller">&nbsp;(1) &ldquo;Non-pecuniary&rdquo; references non-economic damages, such as loss of enjoyment, etc. Although pain and suffering is certainly non-pecuniary, the Courts have made an exception to the rule for such damages</span>.<br />
&nbsp;</p>]]></description>
<link>http://www.louisianalawblog.com/admiralty-and-maritime-a-jones-act-seaman-does-not-have-greater-remedies-against-a-nonemployer-than-he-does-against-his-employer.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/admiralty-and-maritime-a-jones-act-seaman-does-not-have-greater-remedies-against-a-nonemployer-than-he-does-against-his-employer.html</guid>
<category>Admiralty and Maritime</category>
<pubDate>Fri, 14 May 2010 09:49:27 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>
<item>
<title>Medical Bills Are Not Admissible to Prove Pain and Suffering</title>
<description><![CDATA[<p>By <a href="http://www.keanmiller.com/lawyer-attorney-1194685.html">Michael J. O'Brien</a></p>
<p>Due to the non-pecuniary nature of pain and suffering, Jones Act seamen will often use various methods to provide the trier of fact with a concrete basis for a damage award for pain and suffering.&nbsp; One method that Plaintiffs may utilize is to introduce their medical bills for the sole purpose of highlighting the cost of their medical care.&nbsp; Once the bills have been admitted, Plaintiffs will argue to the trier of fact that the high dollar amount of their medical bills corroborate their pain and suffering.&nbsp; Alternatively, Defendants may introduce medical bills and point to the low cost of a Plaintiff&rsquo;s medical care to prove the Plaintiff&rsquo;s lack of pain and suffering.</p>]]><![CDATA[<p>It is interesting that the United States Fifth Circuit has not commented on this issue. However, several cases outside the Fifth Circuit hold that there is no correlation between the amount charged by a healthcare provider and a Plaintiff&rsquo;s pain and suffering.&nbsp; In <em>Francis v. National RR Passenger Co., </em>661 F Supp 244, 246 (D.MD. 1998), the District Court held that the &ldquo;price tag of medical treatment does not tend to prove or disprove anything about the nature and extent of injuries, save for what it cost to treat the injury.&rdquo;&nbsp;&nbsp; Thus, evidence of the cost of a Plaintiff&rsquo;s medical bills is irrelevant.&nbsp; Evidence of the cost of Plaintiff&rsquo;s medical bills was also excluded in <em>Clark v. National Railway Passenger Corp., </em>653 F Supp, 376 (DDC 1987), and <em>Pierson v. Illinois Central Railroad,</em> 2008 W.L. 905915 (S.D. Il.).</p>
<p>In a recent ruling closer to home, United States District Judge Lance Africk agreed that the amount of expense associated with Plaintiff&rsquo;s medical bill would not assist the Jury in arriving at a pain and suffering award.&nbsp; Judge Africk held that &ldquo;such evidence does not tend to prove a matter at issue in the case, or an inference of any consequential fact.&rdquo;&nbsp; As such, the medical bills were excluded.</p>
<p>It is important to note that the jurisprudence cited above is applicable only when a party attempts to introduce medical bills to prove/disprove a seaman&rsquo;s pain and suffering.&nbsp; Medical bill can be relevant and admissible if they are the subject of a dispute in the case.&nbsp; If, for example, in a maintenance and cure action, the employer/vessel owner has denied Plaintiff cure, then the medical bills will be relevant and admissible.&nbsp; Medical bills may also be relevant in the event that an employer/vessel owner argues that the cost of a Plaintiff&rsquo;s medical treatment is not fair and reasonable pursuant to the cure doctrine. <br />
&nbsp;</p>]]></description>
<link>http://www.louisianalawblog.com/admiralty-and-maritime-medical-bills-are-not-admissible-to-prove-pain-and-suffering.html</link>
<guid isPermaLink="false">http://www.louisianalawblog.com/admiralty-and-maritime-medical-bills-are-not-admissible-to-prove-pain-and-suffering.html</guid>
<category>Admiralty and Maritime</category>
<pubDate>Tue, 11 May 2010 15:07:02 -0600</pubDate>
<dc:creator>Steven Boutwell</dc:creator>

</item>


</channel>
</rss>
