06.09.2021 Views

Torts - Cases, Principles, and Institutions Fifth Edition, 2016a

Torts - Cases, Principles, and Institutions Fifth Edition, 2016a

Torts - Cases, Principles, and Institutions Fifth Edition, 2016a

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Witt & Tani, TCPI 9. Liability without Fault?<br />

warnings is greater than their additional printing fees alone. Some commentators have observed<br />

that the proliferation of label detail threatens to undermine the effectiveness of warnings<br />

altogether. See James A. Henderson, Jr. & Aaron D. Twerski, Doctrinal Collapse in Products<br />

Liability: The Empty Shell of Failure to Warn, 65 N.Y.U. L. Rev. 265, 296-97 (1990). As<br />

manufacturers append line after line onto product labels in the quest for the best possible warning,<br />

it is easy to lose sight of the label’s communicative value as a whole. Well-meaning attempts to<br />

warn of every possible accident lead over time to voluminous yet impenetrable labels-too prolix to<br />

read <strong>and</strong> too technical to underst<strong>and</strong>.<br />

By contrast, Ryobi’s warnings are clear <strong>and</strong> unequivocal. Three labels on the saw itself<br />

<strong>and</strong> at least four warnings in the owner’s manual direct the user not to operate the saw with the<br />

blade guards removed. Two declare that “serious injury” could result from doing so. . . . Ryobi<br />

provided warnings sufficient to apprise the ordinary consumer that it is unsafe to operate a<br />

guardless saw-warnings which, if followed, would have prevented the injury in this case.<br />

It is apparent, moreover, that the vast majority of consumers do not detach this critical<br />

safety feature before using this type of saw. Indeed, although Ryobi claims to have sold<br />

thous<strong>and</strong>s of these saws, Hood has identified only one fifteen-year-old incident similar to his.<br />

Hood has thus not shown that these clear, unmistakable, <strong>and</strong> prominent warnings are insufficient<br />

to accomplish their purpose. Nor can he prove that increased label clutter would bring any net<br />

societal benefit. We hold that the warnings Ryobi provided are adequate as a matter of law.<br />

. . . .<br />

AFFIRMED.<br />

Notes<br />

1. Who decides when a warning is adequate? The Hood court mentions the law review article<br />

by James A. Henderson, Jr. <strong>and</strong> Aaron D. Twerski to support the assertion that there exists such a<br />

thing as too many warnings. The court does not, however, address the central question raised in<br />

the article, namely: who is best positioned to decide what constitutes an adequate warning? Is it<br />

primarily a question of fact for the jury or, as Henderson & Twerski urge, should the judge<br />

assume an active role? Which do you think the Hood court favors?<br />

2. Defective products with adequate warnings. Since the 1970s, Maryl<strong>and</strong>’s courts have<br />

interpreted the Restatement (Second) of <strong>Torts</strong> § 402A cmt. j (1965) to mean that a plaintiff’s<br />

failure to follow an adequate warning negates any claim of design defect. See Erin O’Dea, B.<br />

Maintaining an Unrealistic St<strong>and</strong>ard: Maryl<strong>and</strong> Holds It Is Not Reasonably Foreseeable for<br />

Consumers to Fail to Follow Product Warnings, 65 MD. L. REV. 1303 (2006). This suggests that<br />

Hood’s failure to follow the warnings would have prevented him from recovering, even if Ryobi<br />

might have adopted a more reasonable, safer design. Maryl<strong>and</strong> is one of only a couple<br />

jurisdictions that maintain this interpretation. See Ferguson v. F.R. Winkler GMBH & Co. KG, 79<br />

F.3d 1221(D.C. Cir. 1996); Dugan v. Sears, Roebuck & Co., 447 N.E.2d 1055 (Ill. App. 1983).<br />

582

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!