Port of Seattle v. Lexington Insurance

111 Wash. App. 901
CourtCourt of Appeals of Washington
DecidedMay 28, 2002
DocketNo. 49640-9-I
StatusPublished
Cited by15 cases

This text of 111 Wash. App. 901 (Port of Seattle v. Lexington Insurance) is published on Counsel Stack Legal Research, covering Court of Appeals of Washington primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Port of Seattle v. Lexington Insurance, 111 Wash. App. 901 (Wash. Ct. App. 2002).

Opinion

Agid, J.

The Port of Seattle (Port) appeals from two orders dismissing its action to recover insurance proceeds against its 1997 and 1998 insurers for the expenses it incurred upgrading its computer systems to avoid Year 2000 (Y2K) date recognition problems at the turn of the century. At issue is whether the Port timely filed its suit and whether the policies under which it sued covered its Y2Krelated expenses. Because the Port’s Y2K problem did not constitute a “computer virus,” we affirm the trial court’s order. We also hold that despite the Port’s fortuitous loss and timely suit, the sue and labor provision does not provide coverage and the inherent vice exclusion precludes it.

[905]*905FACTS

In the early to mid-1990s, the Port of Seattle began working on making its computer systems Y2K compliant. Although it took some measures at that time, its efforts did not begin in earnest until 1997. And it was not until testing and assessment of its systems in 1998 that the Port discovered it would incur losses on or after January 1, 2000.

In December 1998, the Port filed claims with several insurers with which it had policies in effect during that year (1998 insurers), seeking reimbursement for its upgrade expenses. In November 1999, it provided notice of claims to insurers that provided coverage during 1997 (1997 insurers). The 1998 insurers issued policies to the Port in effect from January 1, 1998, to January 1, 1999. The provisions of the 1998 agreements are identical in their pertinent provisions to those in the 1997 policies, with the exception that the term of the 1997 policies is January 1,1997, to January 1, 1998.

In November 1999, the Port brought suit against both groups of insurers. In June 2000, the 1997 insurers moved for judgment on the pleadings, arguing that the Port’s suit was untimely because it was not brought within the 12-month suit limitation period allegedly incorporated in the policies. The trial court granted the motion, and the Port then filed a motion for reconsideration. The trial court denied the motion.

In September 2000, the 1998 insurers moved for summary judgment, asserting not only the same 12-month suit limitation position, but also arguing that the Port sustained no covered loss during the policy period, the known loss/risk doctrine and the inherent vice exclusion precluded coverage, and the sue and labor provision did not provide coverage. The trial court granted the motion and denied the Port’s motion for partial summary judgment on the 1998 policies. The Port timely appeals the trial court’s orders dismissing its claims.

[906]*906DISCUSSION

Standards of Review

The Port’s action against its 1997 insurers was dismissed on their motion for judgment on the pleadings. We review rulings granting a motion to dismiss under CR 12(b)(6) de novo. Dismissal is appropriate only if “ ‘it appears beyond a reasonable doubt that no facts exist that would justify recovery.’"1 We accept as true the allegations in a plaintiff’s complaint and any reasonable inferences therein.2

The Port’s suit against the 1998 insurers was dismissed under CR 56(c). Summary judgment is proper when there is no genuine issue about any material fact and the moving party is entitled to judgment as a matter of law.3 This court conducts the same inquiry as the trial court in reviewing a summary judgment order.4 We review summary judgment orders de novo,5 and view all evidence in the light most favorable to the nonmoving party.6

“Computer Virus”

The Port seeks coverage for “loss of computer resources” due to a “computer virus” under the insurance agreements’ “Data Processing Media” inclusion provisions.7 The [907]*907insurers maintain that the Port’s Y2K-related expenses are not covered because its Y2K problem did not constitute a “computer virus” and it did not suffer a “loss of computer resources.” They also argue that the policies’ inherent vice exclusion provision precludes coverage because the Port’s Y2K problem was an internal, not external, cause of its losses. We hold that the Port’s Y2K problem was not a computer virus because it was not able to replicate itself and it could not infect other programs by modifying them to include a version of itself.

The policies do not define the term “computer virus.” Undefined terms in an insurance contract must be given their plain, ordinary, and popular meaning.8 To determine the plain meaning of an undefined term, we look to standard English dictionaries.9 The language of insurance contracts is to be interpreted in accordance with the way it would be understood by the average person rather than in a technical sense.10

The interpretation of an insurance policy is a question of law, and summary judgment is appropriate if the contract has only one reasonable meaning when viewed in the light of the parties’ objective manifestations.11 Insurance policies are to be construed as a whole, with force and [908]*908effect given to each clause.12 “Overall, a policy should be given a practical and reasonable interpretation rather than a strained or forced construction that leads to an absurd conclusion, or that renders the policy nonsensical or ineffective.”13 An inclusionary clause in an insurance contract should be liberally construed to provide coverage whenever possible.14 Exclusionary clauses are to be construed strictly against the insurer.15

The insurers cite multiple consistent definitions of the term “computer virus.” In general, their definitions define computer virus as “a computer program usu. hidden within another seemingly innocuous program that produces copies of itself and inserts them into other programs and that usu. performs a malicious action.”16 The key feature of the definitions the insurers urge is that the virus be self-replicating. The Port does not define the term computer virus. Rather, it provides a definition for the term “virus,” asserting that it is “the causative agent of an infectious disease.”17 It argues that under its definition there is no requirement that a virus be self-replicating.

The Port defines biological viruses, not those related to computers. A computer system cannot suffer from a physical virus. And even under the Port’s definition, the virus must be transferable. Its Y2K programming problem, however, was merely the result of an original programming decision. It was not infected by anything external nor was it [909]*909communicable. The Port, nevertheless, briefly asserts that its Y2K problem was self-replicating when, “[f]or example, if a microprocessor-controlled sprinkler system is connected to a fire alarm, the failure of the sprinkler system to activate may, in turn, affect activation of the fire alarm.” This example is not persuasive. It illustrates a potential Y2K-caused problem, not a self-replicating computer program.

The Port also contends that deliberate encoding of a two-digit year field is a computer virus. We disagree.

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

Related

Matthew Noffke, V. Susan Karstedt
Court of Appeals of Washington, 2024
Penny Arneson v. Gary Nordlund
Court of Appeals of Washington, 2019
Patriot General Insurance v. Gutierrez
344 P.3d 1277 (Court of Appeals of Washington, 2015)
Zurich American Insurance v. Public Storage
743 F. Supp. 2d 525 (E.D. Virginia, 2010)
Wirtz v. Gillogly
216 P.3d 416 (Court of Appeals of Washington, 2009)
Ash Grove Cement Co. v. Employers Ins. of Wausau
513 F. Supp. 2d 1200 (D. Kansas, 2007)
Dilley v. S & R HOLDINGS, LLC
154 P.3d 955 (Court of Appeals of Washington, 2007)
Dilley v. S&R Holdings, LLC
137 Wash. App. 774 (Court of Appeals of Washington, 2007)
Pacific Ins. Co. v. Catholic Bishop of Spokane
450 F. Supp. 2d 1186 (E.D. Washington, 2006)
GTE Corp. v. Allendale Mutual Insurance
258 F. Supp. 2d 364 (D. New Jersey, 2003)
Port of Seattle v. Lexington Ins. Co.
48 P.3d 334 (Court of Appeals of Washington, 2002)

Cite This Page — Counsel Stack

Bluebook (online)
111 Wash. App. 901, Counsel Stack Legal Research, https://law.counselstack.com/opinion/port-of-seattle-v-lexington-insurance-washctapp-2002.