Maguire v. Teuber

120 Wash. App. 393
CourtCourt of Appeals of Washington
DecidedMarch 8, 2004
DocketNo. 51484-9-I
StatusPublished
Cited by6 cases

This text of 120 Wash. App. 393 (Maguire v. Teuber) 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
Maguire v. Teuber, 120 Wash. App. 393 (Wash. Ct. App. 2004).

Opinion

Agid, J.

— The State of Washington, one of three defendants in this case, appeals the trial court’s order denying its motion to dismiss the other two defendants after they settled with the plaintiff. The settlement is memorialized in a covenant not to execute, which the trial court determined did not release the settling defendants. We hold that the covenant not to execute does operate as a release, and we reverse and remand to dismiss the settling defendants.

FACTS

In October 1999, Steven A. Teuber rear-ended John Maguire on Interstate 5 while driving a vehicle owned by William Hadsall. Maguire was severely injured. In November 2000, Maguire and his wife (collectively Maguire) sued Teuber and Hadsall. In August 2001, Maguire settled with both defendants, and the parties signed a covenant not to execute.1 In the covenant, Teuber and Hadsall agreed to pay Maguire $100,000, and Maguire promised not to execute or otherwise seek to collect any judgment entered in the pending lawsuit against Teuber and Hadsall. In April 2002, Maguire amended his complaint to bring faulty highway design claims against the state of Washington.

In October 2002, the State moved to dismiss Teuber and Hadsall as parties in the lawsuit. The State argued their continued presence in the case was designed to create joint and several liability among the three defendants. The trial court strictly interpreted the applicable statute and denied the motion. A commissioner of this court denied discretionary review, but we later granted the State’s motion to modify that ruling.

[395]*395DISCUSSION

Before the legislature adopted the tort reform act (TRA) in 1986,2 concurrent and successive tortfeasors were held jointly and severally liable.3 The TRA changed this general rule, abolishing joint and several liability in favor of proportionate liability in most circumstances.4 But the statute continues to require joint and several liability in actions involving a faultless plaintiff and multiple tortfeasors.5 In such a case, defendants against whom judgment has been entered are jointly and severally liable for the plaintiff’s total damages.6 If a plaintiff has released a defendant, that defendant is not jointly and severally liable with his codefendants,7 and he has no liability for contribution.8

Because of this statutory framework, the State in the present case risks joint and several liability for the damages caused by Teuber and Hadsall if all three are parties at trial.9 The State seeks to avoid this liability, arguing that the parties’ covenant not to execute limits Teuber and Hadsall’s liability to $100,000 regardless of what damages the jury imposes after trial. The State also contends that Teuber and Hadsall’s continued presence in the litigation puts the State at a disadvantage because they are disinterested defendants who will not adequately defend Maguire’s claims.

The central issue in this case is the meaning of “release” as it is used in the TRA. Statutory interpretation [396]*396is a question of law that we review de novo.10 In interpreting a statute, we examine its language as well as that of closely related statutes in light of the underlying legislative purpose. 11 RCW 4.22.060 sets forth the types of arrangements that may constitute a settlement and treats as equivalent “[a] release, covenant not to sue, covenant not to enforce judgment, or similar agreement.” RCW 4.22.070, the statute imposing joint and several liability, refers to “release” not as a noun but as a verb, providing that “judgment shall be entered against each defendant except those who have been released . . . .” Read as a whole,12 this statute suggests that releases, covenants and similar agreements all constitute “releases” for purposes of determining who had been “released” under RCW 4.22.070. As such, a covenant not to execute, signed by the parties to document a settlement, is one type of agreement that will release a party. Scholars agree with this interpretation.13

Maguire argues that “release” should be strictly defined because RCW 4.22.070 is in derogation of the common law and must receive a narrow and restrictive construction.14 But the statute uses the word “release” to refer to all of the “similar” settlement agreements enumerated in RCW 4.22.060 used to memorialize a settlement in which the [397]*397settling defendants have no further liability. This interpretation is consistent with the legislature’s intent.15

This interpretation is also consistent with case law. The Washington Supreme Court has generally treated a settlement as synonymous with a release for joint and several liability purposes. Before the TRA, the court held that a covenant not to execute was a binding settlement that left no justiciable issues to be resolved, and therefore the settling defendant must be dismissed.16 After the TRA, the Supreme Court interpreted RCW 4.22.070 to require that “[sjettling parties, released parties, and immune parties are not parties against whom judgment is entered and will not be jointly and severally liable . . . .”17 In another case, the court described the statutory scheme and concluded that “settling, released defendants do not have judgment entered against them within the meaning of RCW 4.22-.070(1), and therefore are not jointly and severally liable defendants.”18

The settlement document in this case has the practical effect of releasing the defendants. We recognize that the covenant attempts to keep Teuber and Hadsall in the lawsuit by referring to the possibility that judgment will be entered against them and that it expressly states it is not to be construed as benefiting the State in any way. But the covenant also expressly provides that the parties are settling “for the purpose of avoidance of the uncertainties, inconvenience, and expenses of the pending lawsuit. . . .” Moreover, the covenant states that it “is intended to consti[398]*398tute a complete resolution of all claims by the plaintiffs against defendants Teuber and Hadsall under RCW 4.22-.060 such that any and all contribution claims against those defendants will be extinguished by this settlement.”19 This is release language. It cannot be construed any other way.

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

Related

Barton v. Department of Transportation
308 P.3d 597 (Washington Supreme Court, 2013)
Barton v. Dep't of Transp.
Washington Supreme Court, 2013
Bradbury Co., Inc. v. Teissier-Ducros
413 F. Supp. 2d 1209 (D. Kansas, 2006)
Romero v. West Valley School District
98 P.3d 96 (Court of Appeals of Washington, 2004)
Maguire v. Teuber
85 P.3d 939 (Court of Appeals of Washington, 2004)

Cite This Page — Counsel Stack

Bluebook (online)
120 Wash. App. 393, Counsel Stack Legal Research, https://law.counselstack.com/opinion/maguire-v-teuber-washctapp-2004.