Show Summary Details
Page of

(p. 676) 11. Rylands v Fletcher and Strict Liability 

(p. 676) 11. Rylands v Fletcher and Strict Liability
(p. 676) 11. Rylands v Fletcher and Strict Liability

Jenny Steele

Page of

PRINTED FROM OXFORD LAW TROVE ( © Oxford University Press, 2018. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a title in Oxford Law Trove for personal use (for details see Privacy Policy and Legal Notice).

date: 23 September 2020

All books in this flagship series contain carefully selected substantial extracts from key cases, legislation, and academic debate, providing able students with a stand-alone resource. This chapter analyses the rule in Rylands v Fletcher on liability for damage done by the escape of dangerous things accumulated on one’s land, regardless of fault. It considers the problem in overlap between negligence and strict liability, and how the tort of negligence can impose liability in situations far removed from cases of individual fault, including the situations covered by Rylands v Fletcher. After providing an overview of the case of Rylands v Fletcher and the origins and elements of the rule, the chapter looks at the rule and its categorization and boundaries today, paying particular attention to two major English cases that treat Rylands as an aspect of nuisance: Cambridge Water Company v Eastern Counties Leather plc and Transco v Stockport MBC. Finally, it examines the Australian High Court’s decision in Burnie Port Authority v General Jones Pty Ltd.

Access to the complete content on Law Trove requires a subscription or purchase. Public users are able to search the site and view the abstracts and keywords for each book and chapter without a subscription.

Please subscribe or login to access full text content.

If you have purchased a print title that contains an access code, please see the information provided with the code or instructions printed within the title for information about how to register your code.

For questions on access or troubleshooting, please check our FAQs, and if you can't find the answer there, please contact us.