State v. Montes (1/26/11)

We don’t normally blog criminal cases but this one is principally a constitutional case.

In 2006 the Legislature changed the burden of proof of self-defense. In Garcia (2007) the Supreme court held that it hadn’t made the statute retroactive. In 2009 the Legislature passed a statute making it retroactive, back to cases pending in 2006. Montes had been convicted in 2008 of a 2005 murder. Division Two affirmed his conviction by memorandum but when the new statue was passed he moved for reconsideration, arguing that he should have been tried according to the law that now existed then. The court denied the motion, ruling the second statute unconstitutional as an attempt to change a court decision. Division One had ruled otherwise. (The opinion refers simply to “a different panel” of the Court of Appeals. This is technically correct. But since someone surely had to make a conscious decision to avoid saying “Division One,” you wonder whether someone isn’t sensitive to the occasional suggestion that there is some stigma involved in identifying the divisions – namely, to put it frankly, Division Two – and is trying to efface the difference. Since Justice Pelander wrote this opinion, you have to wonder even more.)  The Supreme Court took the petition to straighten things out.

The parties agreed that the Legislature could have made the first statute retroactive to begin with. The State argued that it couldn’t do so after Garcia pointed out that it hadn’t done so. The Supreme Court disagreed. In essence, all Garcia did was to point out that in 2006 the Legislature left out retroactivity language. The 2009 statute therefore didn’t really change that. In any event, “every legislative enactment retroactively changing a court’s pronouncement on a statute is not a per se separation of powers violation.” “[T]he Legislature does not violate separation of powers when it acts to make a law retroactive without disturbing vested rights, overruling a court decision, or precluding judicial decisionmaking.”

The State tried to argue that the victim’s vested rights – to the “finality of a defendant’s conviction” – had been disturbed. The Court says that the victim has no vested right to sustaining a conviction and that it “is a valid exercise of the Legislature’s power to retroactively grant new rights to criminal defendants.”

The 2009 statue not only made the 2006 law retroactive, it said that that had been the Legislature’s intention in 2006. That comes closer to “changing” Garcia. But the Court indicated that that wasn’t germane to the analysis since the other part of the statute – the actual retroactivity portion – didn’t.  “However” this problematic section of the statute “is characterized” – i.e., whether it’s constitutional or not – the Legislature had the power to make the statute retroactive after-the-fact.

 

(link to opinion)

The Planning Group of Scottsdale v. Lake Mathews Mineral Properties (1/21/11)

This is an important personal-jurisdiction case, not because it says anything new but because it restates – at the risk of belaboring – established principles and because it removes an analytical barnacle that the Court of Appeals’ opinion had added. (We blogged the Court of Appeals opinion here.)

TPG sells insurance and makes investments. One of its Arizona insurance clients found out about its investment activities and told his sister, a California attorney who represented a California tin mine that needed investors. It sent TPG a report about its activities and followed that up with emails, faxes, and phone calls. They entered into a preliminary agreement – by which TPG invested money – but hadn’t come to a final agreement when TPG found out that the defendants weren’t really tin miners at all, they just wanted to threaten a nearby water district into condemning their property.

TPG sued corporate and individual defendants in Maricopa County. It alleged breach of contract and securities fraud and also sought declaratory judgment and an accounting. The California defendants moved to dismiss for lack of personal jurisdiction; the trial court granted the motion; the Court of Appeals affirmed. The Supreme Court accepted TPG’s petition “because the jurisdiction of Arizona courts over non-resident defendants is a recurring issue of statewide importance.” (So every personal-jurisdiction case is a Supreme Court case, right?)

The standard-of-review section – that Division One often thinks, judging by the number of words in it, to be the most important thing in an opinion – is a footnote. And not an unimportant one. The trial court ruled on affidavits, so the Supreme Court reviews de novo, “viewing the facts in the light most favorable to the plaintiffs but accepting as true the uncontradicted facts put forward by the defendants.”

Perhaps to atone for that brevity, we next get a definition of jurisdiction and then all the classic cases, starting from the beginning – Pennoyer v. Neff and International Shoe. The Court seems determined to cite all the jurisdiction cases you ever read in law school or have heard of since then. Four pages of them.

But then come the important parts. The Court of Appeals had relied on Ninth Circuit precedent to decide that the thing to do was to figure out whether the Complaint sounded primarily in tort or contract and to apply either the “purposeful availment” (for contracts) or “purposeful direction” (for torts) test. It concluded that the Complaint was in contract, that the defendants had not “purposefully availed themselves of the privilege of conducting business in Arizona,” and that Arizona therefore had no personal jurisdiction over them.

The Supreme Court calls this approach “problematic” and points out that we’re not bound by the Ninth Circuit. The U.S. Supreme Court uses “purposeful availment” and “purposeful direction” interchangeably (though, the Court says, they are often most useful in contract and tort settings, respectively). And a court needn’t try to shoehorn an entire Complaint into the “contract” or “tort” category. The approach should be “holistic”: “Considering all of the contacts . . . did those defendants engage in purposeful conduct for which they could reasonably expect to be haled into that state’s courts with respect to that conduct?”

The Court then notes a couple more general principles that the Court of Appeals tripped over: a defendant can have minimum contacts with more than one state – the question is not where the primary or predominant contacts are; and “jurisdictional contacts are to be analyzed not in isolation, but rather in totality.”

The report and communications sent into Arizona – which TPG alleged violated the securities laws – were purposeful and established minimum contacts. That being enough for one allegation, it is enough for the others – which arose out of the same facts – as well.

(The Court then says that it would come to the same result on the contract count even if analyzing it separately under, apparently, a Ninth-Circuit style “purposeful availment” standard – and for some reason spends time explaining why. Was somebody afraid that if the case went further up then that Ninth Circuit law might come back to bite them after all?)

Under Asahi, after finding minimum contacts the court must analyze the burden-on-the-defendant- and interest-of-the-forum-type factors. The Court does so and decides that they support jurisdiction.

The Court therefore reverses and remands as to some of the defendants; it found, in a short section near the end, that a couple of others didn’t act purposefully toward Arizona, so it affirms as to them.

When we blogged the Court of Appeals decision we said that “Judging by the facts in the opinion, it wasn’t actually a very hard case.” Judging the facts as they are presented in this one, it wasn’t actually a very hard case – the other way around. Shows what the presentation of facts – and knowledge of the result – can do even to the most discerning minds (consider smiley-face inserted here; not everybody’s browser can handle those well, even today). Our gently sarcastic comments there about the newfangled availment/direction distinction are now, we’re glad to say, of historical interest only: The Supreme Court’s is, in the main, a very traditional analysis. This opinion will presumably be the new starting point of personal-jurisdiction discussion in Arizona.

(link to opinion)

Leflet v. Redwood Fire and Casualty (CA1 1/20/11)

This is about a Morris agreement to which an insurance company is a party and about fee awards in a class action.

Homeowners sued their subdivision’s developer for construction defects. The case proceeded as a typical construction-defect case: the developer named several subcontractors as third-party defendants and tendered its defense to them and their insurers, whose policies covered the developer for claims arising from the scope of the subs’ work. But when those insurers accepted under a reservation, the developer and its own insurers entered into a Morris agreement with a judgment less than their policy limits, assigning to plaintiffs all claims against the subs and their insurers. The subs’ insurers intervened to challenge the propriety of this; the trial court granted them summary judgment and fees.

Substantively, the Court of Appeals affirms. It holds, for one thing, that the agreement failed because the subs’ insurers were not given proper notice of it.

But the opinion is concerned mostly to say that the agreement failed not merely for lack of notice but because it was fundamentally defective. A Morris agreement “that avoids the primary insurer’s obligation to pay policy limits and passes liability in excess of those limits on to other insurers” is invalid. Such an agreement is “outside the permitted parameters” of Morris. The agreement favored some of the carriers (the developer’s, with which their interests in the agreement were consistent) over others (the subs’) even though the subs’ carriers were responsible only for the scope of their subs’ work. There is also no precedent for a Morris agreement “shrinking [an insurer’s] liability to less than policy limits.” “Because Morris agreements are fraught with risk of abuse, a settlement that mimics Morris in form but does not find support in the legal and economic realities that gave rise to that decision is both unenforceable and offensive to the policy’s cooperation clause.” Because the developer breached their contracts– viz., the cooperation clauses – the subs’ insurers don’t have to pay anything.

Well, yeah, probably. Unfortunately, the opinion is not closely-reasoned, concentrating more on the effects of such an agreement than on its theoretical defects (or else confusing the two).

The last several pages of the opinion concern the fee issue. The trial court had certified this as a class action. Plaintiffs argued that you can’t award fees under 341.01 (action arising out of contract) against a class-action plaintiff. The opinion holds that although the statute doesn’t exempt class plaintiffs, “special considerations nevertheless apply” to fee awards against them. This is because the court thinks that class plaintiffs’ management of the litigation is more “attenuated” than in normal cases. What the class intended to do was to sue the developer; it didn’t know that the method of settlement was legally iffy. And in this case (though we don’t know what this has to do with class actions) the plaintiffs didn’t sue the subs’ insurers; the insurers intervened. So the trial court abused its discretion in awarding fees against the class members jointly and severally.

The opinion affirms the judgment for the subs’ insurers, vacates the fee award, and remands.

(link to opinion)