About The Northwest Policyholder

A Miller Nash Graham & Dunn blog, created and edited by Seth H. Row, an insurance lawyer exclusively representing the interests of businesses and individuals in disputes with insurance companies in Oregon, Washington, and across the Northwest. Please see the disclaimer below.

Tuesday, July 28, 2015

Absolute Pollution Exclusions Are Not Absolute

Insurance is a crucial source of funding for most environmental cleanups. For the past 30 years, comprehensive general liability insurance policies have uniformly included an "absolute pollution exclusion" in some form or another. The earliest such exclusions appeared in the 1950's, but they became ubiquitous boilerplate in the mid-1980s. As a result, most applicable environmental coverage is found in policies pre-1985, and many policyholders incorrectly assume that their post-1985 policies provide no such coverage. This assumption stems from a string of court decisions finding that absolute pollution exclusions eliminate coverage for traditional industrial pollution under Oregon law. Martin v. State Farm Fire & Cas. Co., 146 Or. App. 270, 275-80, 932 P.2d 1207 (1997); Ind. Lumbermens Mut. Ins. Co. v. W. Or. Wood Prod., Inc., 268 F.3d 639 (9th Cir. 2001). While absolute pollution exclusions are broad, and often do exclude pollution from traditional sources, they do not eliminate all coverage for environmental claims, and policyholders should thoroughly review each of their policies to determine whether coverage exists.

Most absolute pollution exclusions are incorporated into standardized forms and use language originally written by the Insurance Services Office (the "ISO"). The ISO's pollution exclusion, which is widely referred to as the "absolute pollution exclusion," actually expressly creates coverage in certain circumstances. For example, the ISO's exclusion does not apply if contamination results from a "hostile fire" or from a failure of equipment used to heat, cool, or dehumidify a building. While the factual scenarios in which express coverage is created are limited, a policyholder should determine whether any such scenarios apply. Even if only part of the environmental claim falls within the scope of express coverage, the insurer may be required to provide a full defense under Oregon law. While the scenarios where coverage is expressly not excluded are few, it is important to review each such scenario at the outset to ensure that no coverage is missed.

Another important analysis is whether the environmental claim involves a pollutant as defined by the policy. If the contamination does not result from the release of a "pollutant," the exclusion typically will not bar coverage. The ISO exclusion includes a very broad definition of what constitutes a pollutant. While many courts have given the term "pollutant" a very broad interpretation, other courts have interpreted "pollutant" to include only traditional or inherently dangerous contaminants. MacKinnon v. Truck Ins. Exch., 31 Cal. 4th 635, 73 P.3d 1205, 3 Cal Rptr. 3d 228 (2003); In re Hub Recycling, Inc., 106 B.R. 372 (D.N.J. 1989). Determining whether a released substance is a pollutant often requires a review of how the substance was used and how it has impacted the property. While many courts have addressed whether commonly applied products, such as pesticides, can be considered pollutants, many of these questions remain unanswered under Oregon law. If contamination has resulted from something other than the accidental release of a regulated substance, a policyholder may have coverage despite the inclusion of an absolute pollution exclusion by showing that the substance is not a "pollutant."

Policyholders also need to be on the lookout for policies that include purported absolute pollution exclusions that do not utilize standardized ISO language. While most policies include standardized ISO exclusions, some insurers have used individualized exclusions that apply less broadly. For example, some of the early insurer-specific absolute pollution exclusions apply only to releases into waterbodies or to claims brought by government authorities. In these cases, coverage remains in place for releases onto land or claims brought by corporations. Insurer-specific absolute pollution exclusions are most commonly found in policies from the 1980s, but a policyholder may run into them at any time.

While absolute pollution exclusions often leave an insured without coverage, they are not as ironclad as their name suggests. The policyholder facing an environmental claim should retain coverage experts as soon as possible to determine which policies create coverage, including those policies that include purported absolute pollution exclusions.

           

Friday, July 24, 2015

Neiman Marcus Data Breach Decision Portends Greater Risk for NW Companies, Need for Cyber Coverage

Earlier this week the Seventh Circuit Court of Appeals, in Illinois, issued a momentous decision for those of us who keep tabs on data breach litigation nationwide.  The decision in Remijas v. Neiman Marcus reinstated class action claims by thousands of shoppers who had their credit card data stolen.  Reversing a trend in the case law driven by a 2013 Supreme Court decision (the Clapper decision), the Seventh Circuit held in effect that even if some class members had not yet experienced a loss of money due to their personal information being stolen, they still had standing to pursue claims for compensation, including for the time and aggravation of having to obtain replacement credit cards, put in place credit monitoring, and take other steps to protect themselves.  It did not matter, said the court, that all of the consumers who had experienced fraudulent charges on their cards had been reimbursed by their banks, that Neiman Marcus had agreed to pay for credit monitoring, or that the consumers could not conclusively rule out that their credit card account information had been stolen in a different hack (e.g. Target).

This decision is only binding in the federal districts within the Seventh Circuit, but as Kevin LaCroix has pointed out in his blog, as a first-in-the-nation decision from an appellate court in this exact scenario, it is likely to be influential.  That is even more true for claims brought in the Northwest, for two reasons.

First, the Seventh Circuit cited extensively to a decision from the Northern District of California in the Adobe Systems data breach case, In re Adobe Sys., Inc. Privacy Litig., No. 13–CV–05226–LHK, 2014 WL 4379916 (N.D. Cal. Sept. 4, 2014).  (That decision is available here.)  The Adobe decision relied on pre-Clapper case law from the Ninth Circuit, and has already been cited twice this year to support a finding of standing in a data breach/data privacy class action, the first brought by Sony employees, and the second by users of the Google Wallet.  Those cases had already established the Ninth Circuit (and therefore the Northwest) as a favorable venue for data breach class actions.

Second, the Premera Blue Cross class action complaints involving the massive data breach at that company, and involving claims under Oregon and Washington law, have all been consolidated in the federal court in Oregon, and have been assigned to Judge Michael Simon.  Judge Simon, a former Perkins Coie partner, is inclined toward issuing cerebral and thoroughly-reasoned decisions that often have a pro-consumer bent.  I would not be surprised to see a lengthy decision from Judge Simon in the near future along the lines of the Seventh Circuit's decision, giving plaintiff's lawyers a road map for obtaining standing in data breach cases and how to properly bring claims under Oregon and Washington law.

What does any of this have to do with insurance?  Well, if you are a non-Northwest company with operations in the Northwest looking at cyber insurance, and trying to assess company-wide risk, you cannot rely on decisions from courts in your "home" jurisdiction that have made it hard for these types of claims to go forward.  If you are a Northwest business that handles a lot of consumer data, the risk of a class action in the event of a breach just went up a little but.  Even if the claims are absolutely meritless, they will get past the motion to dismiss stage, which means that defense costs will be considerable.  All of that should be fodder for your next conversation with your insurance and legal advisers about your company's cyber-coverage, and particularly defense cost coverage and limits.

Update: As reported by my colleague Brian Sniffen in our blog IP Law Trends, Neiman Marcus has now requested en banc review of this decision.  En banc review is rarely granted.

Certain cases reprinted from WestlawNext with permission of Thomson Reuters.  If you wish to check the currency of this case by using KeyCite on WestlawNext, then you may do so by visiting www.next.westlaw.com.

Tuesday, July 14, 2015

Oregon Duty to Defend is Very Broad, as Shown in Two New Cases

Two new decisions from federal courts in Oregon demonstrate just how broad an insurance company's contractual duty to defend its insured truly is.  These decisions should be helpful to policyholders in fighting back against denials of coverage.  Wrongful denials of defense are unfortunately common in Oregon, due to the absence of a meaningful bad faith remedy for most breaches of the duty to defend.  But cases like these demonstrate that if an insured goes to court, more often than not the insured will win.  That may dissuade some insurers from making the wrong decision when it comes to defending.

In the first case, Portland General Electric v. Liberty Mutual Ins. Co., the issue was whether it was appropriate for the court to read an underlying complaint as implying a fact, even though the complaint did not allege the fact directly.  The court said "yes."

Portland General hired a contractor to work on some of its equipment.  The contractor was required to add Portland General as an "additional insured" on its liability policy.  When one of the contractor's employees was injured on the job, he sued Portland General.  (He could not sue his employer, the contractor, because of the workers-compensation exclusive-remedy bar).  Portland General demanded that the contractor's insurer, Liberty Mutual, provide it with a defense.  Liberty Mutual refused, citing Oregon's anti-indemnity statute.  To put it in simple terms, because of the anti-indemnity statute Liberty Mutual could not insure Portland General for Portland General's own negligence.  However, Liberty Mutual could provide coverage to the extent that Portland General were being held liable for the contractor's negligence.  But the employee's lawsuit didn't say anything about the contractor being negligent, making it appear (at least to Liberty Mutual) that Portland General was being sued only for its own negligence.

However, there were allegations in the complaint that some of the equipment chosen for the job was improper, and that clothing worn by the employee also contributed to the accident.  The complaint didn't say who provided the equipment or the clothing.  The court found that even though only Portland General was sued, and the complaint never mentioned the contractor, it was reasonable to infer that the contractor could have provided those items, and therefore that the contractor was at least somewhat negligent.  Because the complaint did not allege only negligence by Portland General, and alleged by implication some negligence by the contractor, the insurer had a duty to defend.

In the second case, Norgren v. Mutual of Enumclaw, District Court Judge Michael Simon took the unusual step of rejecting the recommendation of a Magistrate Judge (Judge Stacie Beckerman), who had ruled in favor of the insurer.  Judge Beckerman held that the insurer had no duty to defend a homeowner against a suit alleging that the homeowner's son assaulted another child, finding that the "intentional acts" exclusion applied to all of the claims against the insured, even to a claim entitled "negligent infliction of emotional distress," because the specific facts alleged all included some element of intent to act.  Judge Simon pointed out, however, that the complaint made other allegations that could be interpreted as alleging mere negligence - even though those allegations were conclusory, and more legal contention than statements of fact.  Judge Simon therefore found a duty to defend.

These two decisions take the famous phrase from Ledford v. Gutoski that in Oregon "any ambiguity in the complaint... is resolved in favor of coverage" and put it into action.  They exemplify the correct approach to Oregon duty to defend questions, which is to scour the complaint for potentially covered claims, rather than generalize about the allegations.  In each case the court rigorously analyzed every contention in the complaints, and resolved every ambiguity in favor of a defense obligation.  It can only be hoped that these two new rulings will help insurers understand that they take a considerable chance if they deny a defense, and that the better course, whenever there is any doubt, is to comply with their contractual defense obligations.

Wednesday, July 1, 2015

Ninth Circuit Hands Oregon Policyholders a Major Win on"Known Loss"

In a June 25, 2015, to-be-published decision in Kaady v. Mid-Continent Casualty Co. the Ninth Circuit adopted a decidedly pro-policyholder interpretation of the oft-contested "known loss" provision that is standard in commercial general liability (CGL) policies, holding that an insured's knowledge of damage to one part of a structure does not allow an insurer to deny coverage for  damage to other parts of the same structure or for a different type of damage to the structure.

Kaady, a masonry subcontractor, installed manufactured stone and masonry caps at a condominium project on Mount Hood.  After the project was complete Kaady was notified that there were cracks in the stone that he had installed.  Later that year Kaady bought a liability policy from Mid-Continent.  Kaady was then sued by the condo association, which alleged that his defective work had contributed to water damage to wood sheathing behind the manufactured stone, and to deck posts on which the masonry caps were sitting.

Mid-Continent denied coverage for those damages under its policy’s "known-loss" provision,  which stated that the policy “applies to . . . property damage only if . . . no insured . . . knew that the . . . property damage had occurred, in whole or in part.”  The policy also excluded coverage for property damage that is a "continuation, change or resumption" of "such [known] property damage."  The policy defined "property damage" in part as "physical injury to tangible property."

In the coverage lawsuit suit the insurer advanced two arguments to justify its denial:  1) that prior knowledge of  any damage to a structure means that any other damage to the same structure is a "known loss;" and 2) that the damage to the sheathing and posts was a "continuation change or resumption" of the cracking that the insured knew about.  The District Court granted summary judgment for Mid-Continent based on the known-loss provision.  The Ninth Circuit reversed.

The insurer argued that the policy's references to "property" and "tangible property" included all portions of that "property," and therefore that knowledge of damage to one portion of "the property" could be attributed to all later damage to that property.  The appeals court disagreed, pointing out that that interpretation conflicts with the way "property" is used throughout CGL policies.  Standard-form policies distinguish between different types of "property" and rely on those distinctions to exclude some kinds of "property" from coverage, such as the insured's own "work" while providing coverage to other kinds of "property."  Therefore, to be consistent, the known-loss provision must operate to allow coverage for damage to some "property" even if the insured knew about damage to other "property" within the same structure.  Moreover, because the known-loss provision talks about knowledge of "the property damage," any damage different in type than the damage about which the insured had knowledge is not excluded by the policy.  In Kaady the damage (deterioration) to the sheathing and deck posts was different in type from the cracking that the insured knew about before buying the policy.

The court also rejected the second argument, holding that Mid-Continent had the burden on summary judgment of proving, through evidence, that the damage to the sheathing and posts was caused by the same cracks that the insured knew about before he bought the policy.  The insurer had failed to put on such evidence, and so summary judgment should not have been granted.

In this decision the Ninth Circuit adopted arguments that have been advanced by policyholders for years, but had not been the subject of a published Oregon state court ruling, creating some uncertainty.  "Known-loss" disputes come up with some frequency, because Oregon law requires property owners to give notice to contractors of alleged defects and an opportunity to cure, and because "punch-list" provisions in standard construction contracts often require owners to give contractors an opportunity to fix problems that occur soon after construction.  This decision will therefore make it difficult for insurers that operate in good faith to deny claims based on "known loss."