12.07.2015 Views

Coverage and Liability Issues in Sexual Misconduct Claims

Coverage and Liability Issues in Sexual Misconduct Claims

Coverage and Liability Issues in Sexual Misconduct Claims

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

NEW MEXICO<strong>Coverage</strong> Trigger & Number ofOccurrencesIntentional Acts ExclusionsPerpetrator:Non-perpetrator:<strong>Sexual</strong> <strong>Misconduct</strong> ExclusionsStatute of LimitationsIn a case <strong>in</strong>volv<strong>in</strong>g the archdiocese’s alleged negligent retention <strong>and</strong>supervision of priests who sexually molested m<strong>in</strong>ors, court foundcoverage must be calculated on a per-priest, per-year basis despitenumber of persons harmed by a particular priest <strong>in</strong> any one year.Roman Catholic Church of the Archdiocese of Santa Fe v. CentennialIns. Co., NO.SF.-93-1519 (c) (N.Mex. Dist. Ct. March 15, 1995). Inanother case <strong>in</strong>volv<strong>in</strong>g m<strong>in</strong>ors sexually abused from 1968 to 1970who did not realize the nature of their result<strong>in</strong>g <strong>in</strong>juries until 1992, thecourt held that the <strong>in</strong>surers on risk when the abuse took place <strong>and</strong>when claimants became aware of their <strong>in</strong>juries had a duty to defend.Servants of the Paraclete, Inc. v. Great Amer. Ins. Co., 857 F. Supp.822 (D. N.M. 1994), amended <strong>in</strong> part, clarified <strong>in</strong> part, 866 F. Supp.1560 (N.M. 1994).An <strong>in</strong>tentional acts exclusion precludes coverage for an <strong>in</strong>sured’s<strong>in</strong>tentional acts of sexual abuse based on the <strong>in</strong>ferred <strong>in</strong>tent doctr<strong>in</strong>e.See Sena v. Travelers Ins. Co., 801 F. Supp. 471 (D. N.M. 1992); NewMexico Physicians Mut. Liab. Co. v. LaMure, et al., 860 P.2d 734 (N.M.1993) (Crim<strong>in</strong>al acts exclusion barred coverage under professionalliability policy for doctor’s sexual abuse of patient).An exclusion for <strong>in</strong>tentional acts of “the <strong>in</strong>sured” would not barcoverage for alleged negligence of a non-perpetrator connected withthe abuse, but an exclusion for <strong>in</strong>tentional acts of “an <strong>in</strong>sured” wouldbar coverage for a non-perpetrator’s negligence because the bar isfor claims aga<strong>in</strong>st any <strong>in</strong>sured aris<strong>in</strong>g out of underly<strong>in</strong>g sexual abuse.Sena v. Travelers Ins. Co., 801 F. Supp. 471 (D. N.M. 1992).The Supreme Court of New Mexico held that a sexual misconductexclusion bars coverage for all claims aris<strong>in</strong>g from alleged sexualmisconduct; however, the <strong>in</strong>surer has a duty to defend all claimsuntil it can establish that all claims fall with<strong>in</strong> the sexual misconductexclusion. Lopez v. New Mexico Pub. Sch. Ins. Auth., 870 P.2d 745(N.M. 1994).Actions for <strong>in</strong>juries to the person must be brought with<strong>in</strong> three years.N.M. Stat. Ann. §37-1-8.An action based on childhood sexual abuse may be filed the laterof: (1) the victim’s 24th birthday; or (2) three years from when thevictim knew or had reason to know of the abuse <strong>and</strong> that the abusecaused <strong>in</strong>jury to the victim, as established by competent medical orpsychological testimony. Id at §37-1-30. In a case based on §37-1-8 <strong>and</strong> not the childhood sexual abuse statute, the court held thatthe discovery rule did not toll the limitations period beyond the dateclaimant first became aware of significant <strong>in</strong>juries from m<strong>in</strong>or sexualabuse, such as acquisition of venereal disease <strong>and</strong> an unwantedpregnancy. Mart<strong>in</strong>ez-S<strong>and</strong>oval v. Kirsch, et al., 884 P.2d 507 (N.M.Ct. App. 1994).– 44 –

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

Saved successfully!

Ooh no, something went wrong!