Atmel Corp. v. St. Paul Fire & Marine Insurance

416 F. Supp. 2d 802, 2006 U.S. Dist. LEXIS 9842, 2006 WL 436171
CourtDistrict Court, N.D. California
DecidedFebruary 21, 2006
DocketC 04-04082 SI
StatusPublished
Cited by2 cases

This text of 416 F. Supp. 2d 802 (Atmel Corp. v. St. Paul Fire & Marine Insurance) is published on Counsel Stack Legal Research, covering District Court, N.D. California primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Atmel Corp. v. St. Paul Fire & Marine Insurance, 416 F. Supp. 2d 802, 2006 U.S. Dist. LEXIS 9842, 2006 WL 436171 (N.D. Cal. 2006).

Opinion

ORDER GRANTING IN PART AT-MEL’S MOTION FOR PARTIAL SUMMARY JUDGMENT AND DENYING ST. PAUL’S MOTION FOR SUMMARY JUDGMENT

ILLSTON, District Judge.

On February 17, 2006, the Court heard oral argument on Atmel’s motion for partial summary judgment and St. Paul’s motion for summary judgment. Having carefully considered the arguments of counsel and the papers submitted, the Court hereby GRANTS IN PART Atmel’s motion and DENIES St. Paul’s motion.

BACKGROUND

Plaintiff Atmel Corporation (“Atmel”) is a company that manufactures computer chips. Atmel obtained general liability and errors and omissions insurance from defendant St. Paul Fire & Marine Insurance Company (“StPaul”) beginning January 1, 2002. This lawsuit arises out of St. Paul’s refusal to defend Atmel in a now-settled lawsuit brought by one of Atmel’s customers, Seagate Corporation. In that lawsuit, which the parties refer to as the “Seagate Action,” Seagate alleged that At-mel sold it defective computer chips and that Seagate had notified Atmel of the problems in the fall of 2001. St. Paul denied a defense in the Seagate Action and, after Atmel filed the instant lawsuit, St. Paul unilaterally rescinded Atmel’s insurance policy on the ground that Atmel knew about the Seagate problems before the policy was issued and failed to disclose them in its applications for insurance.

Although the parties dispute the significance and meaning of virtually all of the facts surrounding Atmel’s application for insurance and St. Paul’s rescission of the insurance policy, it is undisputed that At-mel did not identify any problems with Seagate or the allegedly defective computer chips on its applications for insurance. The errors and omissions application asked: “Does anyone in your organization have knowledge or information of any act, error or omission which might reasonably be expected to result in an Errors & Omissions claim?” The ACORD application similarly asked Atmel to identify “all claims or occurrences that may give rise to claims for the prior 5 years.”

After it was sued in July of 2002, Atmel tendered the Seagate Action to St. Paul and to its previous insurer, Royal Indemnity Company, which had provided Atmel with insurance through December 31, 2001. Atmel and St. Paul characterize the events that followed the tender in markedly different ways. Atmel contends that after St. Paul acknowledged notice of the lawsuit on August 20, 2002, it began a “fishing expedition” by unreasonably requesting more and more information while refusing to defend in the meantime. St. Paul, in contrast, claims that Atmel failed to cooperate with its investigation into the claim, and that Atmel was not forthcoming about the extent or nature of its knowledge of the problems with Seagate. The parties exchanged a series of letters between February and July 2004 regarding whether St. Paul had a duty to defend Atmel in the Seagate Action, and relatedly whether St. Paul was entitled to rescind the policy because Atmel should have disclosed any issues related to Seagate on its insurance applications.

*804 On September 27, 2004, Atmel filed the instant lawsuit seeking damages and declaratory relief against St. Paul for breach of contract and breach of the implied covenant of good faith and fair dealing. St. Paul counterclaimed, alleging rescission, breach of contract, intentional misrepresentation/concealment, negligent misrepresentation, and breach of the implied covenant of good faith and fair dealing. St. Paul has also raised rescission as one of several affirmative defenses. On November 2, 2004, after this lawsuit was filed, St. Paul tendered rescission of the policy and offered Atmel a check for the premiums paid to date, stating “St. Paul hereby rescinds the above-referenced policies in their entirety, rendering them void from inception.” Cusack Deck, Ex. T. Atmel rejected the tender of rescission on November 5, 2004, and returned the proffered check.

In addition, after Atmel tendered the Seagate Action in July or August of 2002, it sought to renew its policies with St. Paul. The renewal process took place in the Fall of 2002. Cusack Deck Ex. I at 27:16-18. During the renewal process, the St. Paul employee in charge of processing Atmel’s renewal, Ken Falvey, was aware of the tender of the Seagate Action, and spoke with the St. Paul claims handler, Jim Runkel, who was handling the tender of the Seagate Action. Id. at 27-28. Runkel has testified that during that conversation, which occurred “at the end of 2002,” Falvey asked Runkel what he knew about the Seagate claim, and Runkel responded that his knowledge was limited to what was alleged in the complaint. Cu-sack Deck Ex. S at 75-76. 1 Runkel also testified that Falvey did not ask him to send him any information about the claim. Id. at 76. At some point—it is unclear when—Falvey received a copy of the Sea-gate complaint, which alleged that Atmel was aware of the mold compound issues in the Fall of 2001. Cusack Deck Ex. I at 27:14-15. It is undisputed that during the renewal process Falvey did not ask Atmel about the Seagate Action, nor did Falvey request any information about Atmel’s knowledge of the Seagate issues either at the time it initially applied for insurance or at the time it was seeking renewal. St. Paul renewed the policies, which were effective January 1, 2003. Cusack Deck Ex. UU.

LEGAL STANDARD

Summary adjudication is proper when “the pleadings, depositions, answers to interrogatories, and admissions on file, together with affidavits, if any, show that there is no genuine issue- as to any material fact and that the moving party is entitled to a judgment as a matter of law.” Fed.R.Civ.P. 56(c). In a motion for summary judgment, “[if] the moving party for summary judgment meets its initial burden of identifying for the court those portions of the materials on file that it believes demonstrate the absence of any genuine issues of material fact, the burden of production then shifts so that'the non-moving party must set forth, by affidavit or as otherwise provided in Rule 56, specific facts showing that there is a genuine issue for trial.” See T.W. Elec. Service, Inc., v. Pac. Elec. Contractors Ass’n, 809 F.2d 626, 630 (9th Cir.1987) (citing Celotex Corp. v. Catrett, 477 U.S. 317, 106 S.Ct. 2548, 91 L.Ed.2d 265 (1986)).

*805 In judging evidence at the summary judgment stage, the Court does not make credibility determinations or weigh conflicting evidence, and draws all inferences in the light most favorable to the non-moving party. See T.W. Electric, 809 F.2d at 630-31 (citing Matsushita Elec. Indus. Co., Ltd. v. Zenith Radio Corp., 475 U.S. 574, 106 S.Ct.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Cite This Page — Counsel Stack

Bluebook (online)
416 F. Supp. 2d 802, 2006 U.S. Dist. LEXIS 9842, 2006 WL 436171, Counsel Stack Legal Research, https://law.counselstack.com/opinion/atmel-corp-v-st-paul-fire-marine-insurance-cand-2006.