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 />

thus determined to be negligent, then the question whether particular damages are recoverable<br />

depends only on the answer to the question whether they are the direct consequence of the act. . . .<br />

[B]ut when it has been once determined that there is evidence of negligence, the person guilty of it<br />

is equally liable for its consequences, whether he could have foreseen them or not.” . . . In the<br />

present case it is clear that the act causing the plank to fall was in law a negligent act, because<br />

some damage to the ship might reasonably be anticipated. If this is so then the appellants are<br />

liable for the actual loss, that being on the findings of the arbitrators the direct result of the falling<br />

board. . . . On the whole in my opinion the appeal fails <strong>and</strong> must be dismissed with costs.<br />

SCRUTTON, L.J.<br />

. . . I cannot think it useful to say the damage must be the natural <strong>and</strong> probable result.<br />

This suggests that there are results which are natural but not probable, <strong>and</strong> other results which are<br />

probable but not natural. I am not sure what either adjective means in this connection; if they<br />

mean the same thing, two need not be used; if they mean different things, the difference between<br />

them should be defined. . . . In this case, however, the problem is simpler. To determine whether<br />

an act is negligent, it is relevant to determine whether any reasonable person would foresee that<br />

the act would cause damage; if he would not, the act is not negligent. But if the act would or<br />

might probably cause damage, the fact that the damage it in fact causes is not the exact kind of<br />

damage one would expect is immaterial, so long as the damage is in fact directly traceable to the<br />

negligent act, <strong>and</strong> not due to the operation of independent causes having no connection with the<br />

negligent act, except that they could not avoid its results. . . . In the present case it was negligent<br />

in discharging cargo to knock down the planks of the temporary staging, for they might easily<br />

cause some damage either to workmen, or cargo, or the ship. The fact that they did directly<br />

produce an unexpected result, a spark in an atmosphere of petrol vapour which caused a fire, does<br />

not relieve the person who was negligent from the damage which his negligent act directly caused.<br />

For these reasons the experienced arbitrators <strong>and</strong> the judge appealed from came, in my opinion, to<br />

a correct decision, <strong>and</strong> the appeal must be dismissed with costs.<br />

Notes<br />

1. Directness? All three judges agree that the foreseeability of harm affects only the<br />

assessment of negligence, not whether the defendant is liable for the full extent of damages—at<br />

least of damages that are “direct” consequences.<br />

Does this “directness” language actually clarify the st<strong>and</strong>ard? We can add directness to<br />

the list of formulations offered in the Ryan case. Does it help clarify matters in Scott v. Shepherd<br />

a hundred <strong>and</strong> fifty years earlier?<br />

2. Unexpected types? What about the suggestion of appellant’s junior counsel? The<br />

argument, as recounted <strong>and</strong> then rejected in the opinion, was that when the damages are of a<br />

different type than might reasonably have been expected, such damages are remote. Is this a<br />

sound distinction?<br />

343

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

Saved successfully!

Ooh no, something went wrong!