My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
02-14-1990 Council Agenda
>
City Council Packets
>
1990-1999
>
1990
>
02-14-1990 Council Agenda
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/10/2013 2:40:35 PM
Creation date
7/10/2013 2:38:51 PM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
109
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Did you know? <br />Peter Tritz <br />How much liability coverage is enough? <br />The Minnesota Supreme Court <br />recently upheld the statute which sets <br />a monetary limit on the state's liability. <br />In Lienhard v. State of Minnesota, the <br />plaintiff had argued that the liability <br />limit denied him equal protection, and <br />that the liability limit did not bear a <br />rational relationship to a legitimate gov- <br />ernmental purpose. (This case is sum- <br />marized in greater detail in the Court <br />Decisions column this month.) <br />There is also a statutory limit of <br />$200,000 per claimant and $600,000 <br />per occurrence on cities' tort liability. <br />Most cities purchase liability coverage <br />equal to the statutory limits. However, <br />some cities do choose to purchase <br />higher limits. Of League of Minnesota <br />Cities Insurance Trust (LMCIT) mem- <br />bers, about one - quarter purchase <br />higher limits of coverage. One of the <br />reasons for this is a concern that the <br />statutory limits might not stand up in <br />court. Now that the Supreme Court <br />has answered many of those concerns, <br />cities are once again reviewing the <br />question of how much liability coverage <br />they should purchase. <br />There are some good reasons why a <br />city should consider higher limits of <br />liability protection. There are also good <br />arguments against it. <br />Constitutional questions <br />First, cities should keep in mind that <br />the Court did not quite close the door <br />entirely on questions about the consti- <br />tutionality of liability limits. In Lienhard, <br />the plaintiff argued among other things <br />that the $100,000 limit on the state's <br />liability that was then in effect was <br />unreasonable. The Court disagreed, <br />but specifically pointed out that the <br />Legislature had periodically reviewed <br />and revised the limit. A particular dollar <br />limit that is reasonable now might not <br />be reasonable in the future, after the <br />effect of several years of inflation. If <br />the Legislature were to leave the limits <br />unchanged during many years of infla- <br />tion, a future Court might decide that <br />16 <br />the limit was no longer reasonable and <br />throw it out on those grounds. <br />The Court also briefly discussed <br />whether the "rational relationship" <br />test was the proper one to use. The <br />court noted that if there was a "funda- <br />mental right" involved, there could be <br />an argument for a stricter standard. <br />The plaintiff in Lienhard hadn't made <br />this argument in the lower courts, so <br />the Supreme Court declined to rule on <br />it. The Court did comment that it had <br />used the "rational relationship" test in <br />considering the constitutionality of <br />other parts of the municipal tort liability <br />law. However, the Court seemed to <br />leave room to consider in a future case <br />whether or not to use a stricter stand- <br />ard constitutional standard. <br />In short, although the Minnesota <br />Court has now upheld the liability limit <br />as constitutional, that may not perma- <br />nently and completely resolve the <br />issue. The court could in the future <br />decide that the limit was no longer <br />reasonable or could decide to apply a <br />tougher standard, which conceivably <br />could lead to a different result. <br />Exceptions to the <br />liability limit statute <br />A second point cities must keep in <br />mind when considering how much liabil- <br />ity coverage to purchase is that the <br />limits don't or may not apply to certain <br />kinds of liability. One example is liability <br />that the city has assumed by contract. <br />This could occur in an indemnification <br />or "hold harmless" clause in a con- <br />tract. The statutory limits might not <br />apply since this liability would be based <br />on a contract rather than on a city tort. <br />Another example is liability under <br />the federal civil rights laws. It seems <br />doubtful whether a state statute can <br />limit liability created by a federal law. <br />See Thompson v. Village of Holes <br />Corners, 340 NW2d 704 (Wis. 1983) <br />for example. <br />The liability limit statute also might <br />not apply to torts that occur in another <br />state. Cities near the Minnesota border <br />might have this kind of exposure if they <br />have mutual aid or other kinds of joint <br />powers agreements with cities in a <br />neighboring state. It could also arise <br />when a city officer attends a conference <br />or seminar in another state. <br />The municipal tort liability limit also <br />does not appl} to liability for illegal <br />liquor sales under the dram shop law <br />(M.S. 340A.801, see M.S. 466.15). <br />Another exception is pollution claims; <br />the liability limit for these claims is <br />double the general municipal tort liabil- <br />ity limit. (See M.S. 466.04, Subd. lc). <br />Of course, the city would need also to <br />check whether the coverage they are <br />considering would apply to these <br />claims. Umbrella policies often exclude <br />pollution and liquor claims; this is also <br />true of the excess coverage LMCIT <br />offers. <br />Gaps in the city's <br />primary coverage <br />A third reason for considering buying <br />higher liability limits is that the city's <br />primary coverage might not cover all of <br />the city's exposure within the statutory <br />limits, even if the coverage limits are <br />set at the same level as the statute. <br />Some insurance companies only offer <br />coverage limits in half- million dollar <br />increments; obviously this amount of <br />coverage will leave a gap for the city. <br />But there are a couple of other less <br />obvious ways in which the underlying <br />coverage can turn out to be inadequate. <br />One such way is if the underlying <br />coverage incorporates an annual aggre- <br />gate limit in addition to a per- person or <br />per - occurrence limit. An annual aggre- <br />gate limit restricts the total amount the <br />policy will pay per year, regardless of <br />the number of claims or occurrences. <br />If there is an annual limit, and if one <br />claim is paid, there conceivably might <br />not be adequate limits left under the <br />policy to cover the city's full potential <br />liability under the statute. <br />Continued page 18 <br />Page 60 6_b 89 <br />Minnesota Cities <br />
The URL can be used to link to this page
Your browser does not support the video tag.