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 7. Proximate Cause<br />

beyond the offense committed. It is to be considered, also, that if the negligent party is liable to<br />

the owner of a remote building thus consumed, he would also be liable to the insurance companies<br />

who should pay losses to such remote owners. The principle of subrogation would entitle the<br />

companies to the benefit of every claim held by the party to whom a loss should be paid. . . .<br />

The remoteness of the damage, in my judgment, forms the true rule on which the question<br />

should be decided, <strong>and</strong> which prohibits a recovery by the plaintiff in this case.<br />

Judgment should be affirmed.<br />

Notes<br />

1. Rationales for Ryan. Few tort jurists today think that liability ought to be cut off as<br />

sharply as the Ryan court believed. But virtually all observers agree that at some point, where<br />

some point is represented by the letter N, there ought to be a distinction between the first house<br />

<strong>and</strong> the “Nth” house. But where do we draw the line between proximate <strong>and</strong> remote damages?<br />

Judge Hunt’s opinion in Ryan offers up a whole laundry list of possible ways to articulate the key<br />

distinction. He talks about ordinariness, nature, expectations, accident, <strong>and</strong> immediacy. Which of<br />

these rationales, if any, explains the location of the line as the Ryan court sees it?<br />

2. An insurance explanation? One explanation articulated in the Ryan decision for cutting<br />

off liability is that even if none of these doctrinal formulations hold, the plaintiff could have<br />

insured his property against fire. The defendant, by contrast, could not take out a policy on the<br />

plaintiff’s property because in 1866 liability insurance was unavailable on the theory that it was<br />

against public policy. For a long time, liability insurance had been thought to create dangerous<br />

incentives for careless conduct. Some say it still does! Yet not long after Ryan was decided, the<br />

law in most states began to permit liability insurance. Today, it is pervasive.<br />

Today, the law permits people <strong>and</strong> firms to purchase liability insurance protecting the<br />

policy-holder’s interest in insuring against tort damages judgments. Sometimes, as in automobile<br />

insurance regulations, the law now requires liability insurance. If you have owned a car, you have<br />

almost certainly bought a liability insurance policy yourself. Some of you will have bought<br />

liability insurance as part of an apartment renter’s insurance policy, or perhaps a homeowners’<br />

policy.<br />

way?<br />

If liability insurance had been widespread in 1866, would Ryan have come out the other<br />

Note that today, Ryan is almost certainly not a good statement of the law: Courts today<br />

virtually always draw the line between proximate injuries <strong>and</strong> remote ones more broadly than<br />

Judge Hunt did. Although never explicitly overruled, Ryan was soon distinguished into oblivion.<br />

In 1872, the New York Court of Appeals held that there was proximate cause where a railroad<br />

negligently started a fire that spread from its own property to the property of others. Webb v.<br />

Rome, W. & O. R. Co., 49 N.Y. 420, 428 (1872) (“We are not to be controlled by the authority<br />

[Ryan] more than we are by that of the long line of cases which preceded it . . .”). Later<br />

interpretations of these two contrary cases in subsequent railroad fire cases have l<strong>and</strong>ed firmly on<br />

336

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

Saved successfully!

Ooh no, something went wrong!