Skip to content

Menu

LexBlog, Inc. logo
NetworkSub-MenuBrowse by SubjectBrowse by PublisherJoin the NetworkGet StartedSubscribeSupportContact
Search
Close

A Primer on the Efficient Proximate Cause Doctrine in California

By Kyle Bugden & Daniel Veroff on August 30, 2020
Email this postTweet this postLike this postShare this post on LinkedIn
knuckles of dominoes falling one after another, pointing a finger

In California, the combination of both a covered loss and an uncovered loss can still be covered under the Efficient Proximate Cause Doctrine provided that the covered loss is the efficient proximate cause of the loss. California Courts have interpreted California Insurance Code sections 530 and 532 to codify the efficient proximate cause doctrine.

An insurer is liable for a loss of which a peril insured against was the proximate cause, although a peril not contemplated by the contract may have been a remote cause of the loss; but it is not liable for a loss of which the peril insured against was only a remote cause.1

If a peril is specially excepted in a contract of insurance and there is a loss which would not have occurred but for such peril, such loss is thereby excepted even though the immediate cause of the loss was a peril which was not excepted.2

The California Supreme Court has interpreted Cal. Ins. Code §530 and §532 to mean an incorporation into law of the “efficient proximate cause doctrine.”3 This means that when a loss is caused by a combination of a covered and specifically excluded risks, the loss is covered if the covered risk was the efficient proximate cause of the loss.4

Additionally, an Insurer cannot exclude the application of efficient proximate cause by inconsistent policy language.5 Also, the insurer cannot contract around the efficient proximate cause doctrine by a provision excluding concurrent causes.6 The “efficient proximate cause” is the reasonable expectations of the insurer and insured under the terms of the contract.7 Finally, the California courts have found coverage under the efficient proximate cause for third party negligence proper.8

An exclusion will not be void unless it makes the contract illusory or violates Cal. Ins. Code.9 In Julian, a heavy rain caused a mudslide which damaged the plaintiff’s property. The policy provided coverage from losses from rain but not for earth movement. The plaintiffs argued that this should be a covered loss because the weather condition of rain caused the mudslide. The appellate court went through a careful analysis of the efficient proximate cause doctrine in California and stated that an insurer cannot exclude the application of the efficient proximate cause doctrine by inconsistent policy language.10 The court defined the “efficient proximate cause” as providing a fair result between the reasonable expectations of the insured and insurer.11 In applying this standard, the court stated that the insured should expect the provision excluding earth movement to include rain induced earth movement.12
_____________________________
1 Cal. Ins. Code § 530 (West).
2 Cal. Ins. Code § 532 (West).
3 Sabella v. Wiser, (1963) 377 P.2d 889, 895-897.
4 State Farm Fire & Cas. Co. v. Von Der Lieth, (1991) 820 P.2d 285, 291.
5 Julian v. Hartford Underwriters Ins. Co., (2005) 110 P.3d 903, 907-908 citing Garvey v. State Farm Fire & Cas. Co., 770 P.2d 704.
6 Julian, 110 P.3d at 907.
7 Id. at 912.
8 State Farm Fire & Cas. Co. v. Von Der Lieth, (1991) 820 P.2d 285.
9 See generally, Julian v. Hartford Underwriters Ins. Co., (1991) 820 P.2d 285.
10 Julian, 110 P.3d at 907.
11 Id. at 912.
12 Id. at 912-13.

  • Posted in:
    Insurance
  • Blog:
    Property Insurance Coverage Law Blog
  • Organization:
    Merlin Law Group, P.A.
  • Article: View Original Source

Call us at 1-800-913-0988 or email sales@lexblog.com.

Facebook LinkedIn Twitter RSS
The Library at LexBlog
  • About LexBlog
  • The Field We Built
  • Library at LexBlog
  • Our Beliefs
  • Our Team
  • Contact LexBlog
  • Disclaimer
  • Editorial Policy
  • Terms of Service
  • Get Started
  • Publishing Solutions
  • Compass
  • Submit a Request
  • Support Center
  • System Status
Copyright © 2026, LexBlog, Inc. All Rights Reserved.
Law blog design & platform by LexBlog LexBlog Logo