The question is whether "Father" is the actual father of D.P., because if he is, he's likely entitled to a lot more statutory and constitutional protections than he was given in this case. And there's some evidence that Father is indeed the actual biological father of D.P. since Mother -- who presumably has some clue as to who the father is -- "named father [I think that should read "Father"] as D.P.’s biological father . . . and told the court father was currently in federal prison in Victorville for illegally
entering the country." So Father wants to get a paternity test to figure out if he is, in fact, the father of D.P.
But the trial court denied him that right. The Court of Appeal affirms.
Justice Codrington says that there's simply no way that Father could actually be the father of D.P., so he had no right to paternity test. She says:
"The hospital discharge summary, dated May 20, 2013, attached to the
jurisdiction/disposition report filed May 31, 2013, states D.P. was born prematurely at 28
to 37 weeks. D.P. was thus conceived in late August 2012, after father was incarcerated
in July 2012. Taking into account D.P. was conceived after father was arrested and incarcerated on July 10, 2012, the juvenile court reasonably denied father paternity
testing, since father could not have fathered D.P. while father was incarcerated."
A couple of questions.
First, I'm pretty sure the hospital discharge report doesn't mean that D.P. "was thus conceived in late August 2012." I think that what Justice Codrington means to say is that if D.P. was born prematurely at 28 to 37 weeks, and if he was born around (say) May 15, 2013, then he must have been conceived no earlier than late August 2012, but could have been conceived as late as November 5, 2012. No reason to unnecessarily pin down a conception date that's not supported by the evidence.
Second, I might be a tiny less certain about the precision of a hospital discharge report than the Court of Appeal seems to be. When you're talking about a difference of a month or so (i.e., conception in maybe August 2012 versus incarceration in July 2012), and when the discharge report gives a huge range of 28 to 37 weeks for gestation, I'm not certain I'd rely on that much on a mathematical calculation to "prove" that someone who mother has identified as the father was definitely not, in fact, the father.
I'd instead probably rely less on the hospital discharge report than on simply the date of birth. If D.P. was born around May 15, 2013, and if Mother said that the last time she and Father had sex was prior to his incarceration on July 10, 2012, then that would require a gestation period of over 44 weeks (e.g., over 10 months). Which is not likely. Especially since D.P. was born prematurely. I'd rely more on the fact that a 10-month-plus pregnancy is pretty uncommon, especially for (as here) a meth-addicted mother, alongside the existence of a somewhat premature birth, rather than trying to precisely calculate a conception date based upon a hospital discharge report that wasn't trying to be precise and that included an exceptionally wide range.
Finally, as a practical matter, is it really impossible for Father to be the father just because he was in prison? Mother says he's the father. They definitely appear to have had a relationship. Now, I admit, it'd certainly be difficult to conceive a child while the father's in prison. But the Court of Appeal might have a slightly different perspective than I do on what conduct that in fact takes place in the visiting room of the Victorville prison. I recall one federal prison in California I visited in which an inmate convicted of murder pointed out an isolated area in the visiting room partially shielded by vending machines that he indicated was the place where inmates went to have sex on visitation days. I'm not saying that's necessarily the case here. But even if Father was in prison, I'm not sure I'd be confident that it would require another Immaculate Conception [* See Postscript] for Father to in fact be the biological father of D.P.
My money's admittedly on someone else given the underlying dates. But it definitely ain't a sure thing.
POSTSCRIPT - My reference to the immaculate conception demonstrates conclusively that I needed to pay far more attention in CCD than I apparently did. A reader correctly notes that the Immaculate Conception refers to conception free of original sin. I don't think D.P. needs that. (Though it wouldn't help.) I meant to refer to "virgin birth". My bad. (Doubly bad since I teach at a Catholic law school, no less.)
Thoughts on recent Ninth Circuit and California appellate cases from Professor Shaun Martin at the University of San Diego School of Law.
Wednesday, September 23, 2015
Tuesday, September 22, 2015
Alamo Recycling Co. v. Anheuser Busch Inbev Worldwide (Cal. Ct. App. - Aug. 24, 2015)
There's slim pickings from the California appellate courts today. The Ninth Circuit published nothing today (and the California Court of Appeal published nothing yesterday). And as of lunchtime, the Court of Appeal has only published two things today -- one of which merely amends a prior opinion to add a single-sentence footnote, and the other of which involves the proper way for California to tax intangible private possessory interests that exist in a publicly owned airplane hanger at the Santa Monica Municipal Airport. And, honestly, it's unclear which one of these opinions I'd be more hard-pressed to say something interesting about.
So I thought I'd go back a tiny bit to last month and briefly mention a lawsuit that shows a lot of cojones by a tiny little recycling company:
So I thought I'd go back a tiny bit to last month and briefly mention a lawsuit that shows a lot of cojones by a tiny little recycling company:
"Plaintiffs Alamo Recycling, LLC (Alamo) and Chino Valley Recycling, LLC
(Chino) operate “recycling center[s]” where beverage containers sold in California may
be redeemed for their “California Redemption Value.” In this action, plaintiffs sued
defendant Anheuser Busch Inbev Worldwide, Inc. and other companies that sell or distribute beverages containers in California . . . . The gravamen of the complaint is that defendants knowingly and “falsely” label
beverage containers sold both inside and outside California with “CA CRV,” “California
Redemption Value,” or similar labels when, in fact, under California law, only containers
purchased inside California may be redeemed in California. The complaint alleges that
containers sold outside California are transported into California and redeemed at
recycling centers like those operated by plaintiffs, and this exposes plaintiffs to state
regulatory fines and penalties, risks rendering the “California Beverage Recycling Fund”
insolvent, and thereby risks the economic viability of plaintiffs’ recycling businesses."
It's a creative argument. But, not surprisingly, one that doesn't work. For a variety of different reasons, one of which can be summarized in three words:
Dormant. Commerce. Clause.
Sorry about that. Yeah, it's a hassle that some people drive in cans from Arizona to redeem them in California. But there are ways to solve, or at least try to solve, that problem short of the nationwide relabeling that plaintiffs seek.
Sorry about that. Nice try, though.
Monday, September 21, 2015
Jones v. County of Los Angeles (9th Cir. - Sept. 21, 2015)
Judge Murguia begins this opinion by saying:
"The Jones family—Jill, Michael, and their son G.J.—brought this action under 42 U.S.C. § 1983 alleging that Dr. Claudia Wang violated their Fourth and Fourteenth Amendment rights and committed various torts during her investigation into whether G.J. had been abused."
Which led me to conclude, correctly, that the Jones family was going to win the appeal. On the theory that you generally don't use the first names of the parties in the first sentence of the opinion unless you're going to find in their favor. You'd instead depersonalize them and describe them by role.
It's a fact-bound dispute about whether there was a sufficient basis to suspect child abuse here. Judge Murguia authors the majority opinion, joined by Judge Randy Smith. Judge McNamee, sitting by designation from the Arizona district court, dissents.
It always takes more time to get an opinion out when there's a dissent. But the Ninth Circuit case number here begins with a 12-. And it took nearly a year and a half after oral argument to issue an opinion in this interlocutory appeal. With respect, that's too long.
Now the case goes back for more pretrial events, and potentially a trial.
Or maybe the parties will settle. Which they should. Since it's by no means a slam dunk on either side.
"The Jones family—Jill, Michael, and their son G.J.—brought this action under 42 U.S.C. § 1983 alleging that Dr. Claudia Wang violated their Fourth and Fourteenth Amendment rights and committed various torts during her investigation into whether G.J. had been abused."
Which led me to conclude, correctly, that the Jones family was going to win the appeal. On the theory that you generally don't use the first names of the parties in the first sentence of the opinion unless you're going to find in their favor. You'd instead depersonalize them and describe them by role.
It's a fact-bound dispute about whether there was a sufficient basis to suspect child abuse here. Judge Murguia authors the majority opinion, joined by Judge Randy Smith. Judge McNamee, sitting by designation from the Arizona district court, dissents.
It always takes more time to get an opinion out when there's a dissent. But the Ninth Circuit case number here begins with a 12-. And it took nearly a year and a half after oral argument to issue an opinion in this interlocutory appeal. With respect, that's too long.
Now the case goes back for more pretrial events, and potentially a trial.
Or maybe the parties will settle. Which they should. Since it's by no means a slam dunk on either side.
Friday, September 18, 2015
Marilley v. Bonhom (9th Cir. - Sept. 18, 2015)
Judge Graber is pretty darn smart.
She loses this case, so as long as the panel's opinion holds, California won't be able to charge non-residents more for commercial fishing licenses.
But check out her dissent anyway. It's extremely erudite.
She loses this case, so as long as the panel's opinion holds, California won't be able to charge non-residents more for commercial fishing licenses.
But check out her dissent anyway. It's extremely erudite.
Thursday, September 17, 2015
S.M. v. Los Angeles USD (Cal. Ct. App. - Sept. 16, 2015)
The California Supreme Court should depublish this opinion. If not do more.
I don't say that lightly. I'm generally not a fan of the regime (e.g., under Chief Justice Lucas) in which the California Supreme Court depublishes tons of cases from the Court of Appeal instead of granting review. I'm happy that the graph of the recent depublication rate looks something like this:
Moreover, I'm not going to quibble about the result reached here by the Court of Appeal. There were definitely some seriously problematic rulings in this lawsuit, which involved the molestation of a 14-year old student by her eighth-grade math teacher. The trial court allowed introduction of evidence about her sexual history with other people; that could definitely be a problem. The trial court also seemed to think it helpful to instruct the jury that a 14-year old could validly "consent" to intercourse with her teacher; that could definitely be a problem as well.
So as far as the result goes, I'm on board for granting the plaintiff a new trial. Despite the fact that the jury found that the Los Angeles Unified School District wasn't liable at all, maybe that finding was influenced by some rulings that aren't kosher. So is everyone on the panel.
But the bulk of the opinion is devoted to why a particular (modified) jury instruction, CACI 426, was improperly given in this case, and why a new trial is principally required on that ground. And that's a holding that I believe is both (1) wrong, and (2) pernicious. Both in this case as well as many others.
This is a "negligent hiring" (or retention) case. It's not enough that Los Angeles Unified employed someone who molested a kid. Plaintiff's got to prove that L.A. Unified knew or should have known that this guy was someone who might well molest someone.
The standard instruction in these types of cases is CACI 426. Which says:
“[Name of plaintiff] claims that [he/she] was harmed by [name of employee] and that [name of employer defendant] is responsible for that harm because [name of employer defendant] negligently [hired/ supervised/ [or] retained] [name of employee]. To establish this claim, [name of plaintiff] must prove all of the following:
1) That [name of employee] was [unfit/ [or] incompetent] to perform the work for which [he/she] was hired;
2) That [name of employer defendant] knew or should have known that [name of employee] was [unfit/ [or] incompetent] and that this [unfitness/ [or] incompetence] created a particular risk to others;
3) That [name of employee]’s [unfitness/ [or] incompetence] harmed [name of plaintiff]; and
4) That [name of employer defendant]’s negligence in [hiring/ supervising/ [or] retaining] [name of employee] was a substantial factor in causing [name of plaintiff]'s harm."
That's indeed the basic rule. We've got to modify this instruction somewhat, since saying that the teacher here was "unfit [or] incompetent" doesn't really express what we mean (much less clearly). What we're trying to get at is that L.A. Unified is only liable if they knew or should have known that the guy was someone who's going to molest one of his students.
Now, there's a reason this case goes to trial, rather than resolved on summary judgment (or with a settlement). The teacher here allegedly does some stuff that might well put L.A. Unified on notice that there's a problem here. He's popular with female students. Very popular. He hugs 'em. A lot. His classroom conversations sometimes reflect personal stuff. Very personal stuff. And he sets up his classroom furniture so there's a nice little hidden alcove.
Mind you, what I've just said could potentially apply equally to lots of teachers I know. Lots. But in an eighth grade teacher, maybe this should put L.A. Unified on notice to at least check the dude out, if not have a stern conversation with him about the nature of professionalism when dealing with 14-year olds.
That's why we have a jury. Up to them to decide just how "weird" this stuff is and what red flags (if any) it should have raised.
But we have to tell this to the jury in non-legalese. In words they'll understand. And using terms like "unfitness" or "incompetence" for the job just don't cut it.
So the trial court modifies CACI 426 so it says that L.A. Unified is liable if it knew or should have known, based on these facts, that the teacher here (instead of being "unfit" or "incompetent") had a "dangerous propensity to sexually abuse minors."
That seems right to me.
But the Court of Appeal says it's not. Indeed, that it's reversible error. On the ground that requiring proof that someone has a "dangerous propensity to sexually abuse minors" would require plaintiffs to prove that the dude had already molested someone else. And that, instead, the jury should have been instructed that L.A. Unified was liable if they knew or should have known that the teacher "had the potential for sexually abusing minors" (emphasis in original).
I disagree with all of that. Strongly.
For one thing, I think that "dangerous propensity" is precisely what we're trying to get at. We want to impose liability when you know (or should know) that a guy's acting sufficiently strangely in a way that suggests that he may well be the kind of guy who'll touch minors. "Dangerous propensity" is, to me, a great way to express that idea. Legal enough to satisfy the Court of Appeal (as opposed to, say, "sufficiently strangely") yet common sense enough to actually assist jurors in making a decision.
For an other thing, I strongly disagree that "dangerous propensity" to do X means -- or even is commonly understood to mean -- that someone's already done X. The Court of Appeal cites an online dictionary that says that “If you have a propensity for something, then it’s something that comes naturally to you or something you just do a lot.” (emphasis in original). Let's be willing for a moment to entirely ignore the wisdom of judiciary relying on definitions from vocabulary.com -- and, for the record, color me skeptical on the authoritative nature of this particular source. The simple fact is that to have a "propensity" to do something does not mean that you, in fact, have already done it a lot. It just means that you have an inclination to do it. Whether this is your first or fiftieth time.
Yes, I admit, if you do, in fact, do something a lot, that may well be pretty good evidence that you do in fact have a propensity for it. That's why the definition the Court of Appeal cites has an or in it. To have a propensity for X is to say that "it's something that comes naturally to you or something you just do a lot." See the "or"?
When I say someone has a "propensity" for something, that just means that they're the kind of person who might well be into that sort of thing. When I say that a jittery guy who's wandering around a shopping mall in camouflage clothing mumbling incoherently about space aliens and Obama being out to get him, and who's carrying a machine gun, is a guy who has a "propensity" for committing mass murder, I definitely do not mean that he's already killed twenty people. I'm saying that he's the type of guy who may well commit mass murder in the future. And, parenthetically, that anyone who sees the guy doing all this stuff either knows or should have knows that this is true.
If anyone came up to me and said: "Professor Martin, I disagree with you: This guy definitionally doesn't have the propensity to commit mass murder since there's no proof that he's actually killed anyone yet," I'd respond that, with respect, they don't know what the word "propensity" means.
Yet that's precisely what the Court of Appeal holds.
To tell a jury, as the trial court did here, that L.A. Unified is liable if they knew or should have known that one of its teachers had a "dangerous propensity" to molest kids based on what they saw from him does not, in fact, hold L.A. Unified liable only if the teacher had previously molested someone. I can say that someone has a "propensity" to commit suicide even if they've never done it before. Ditto for someone with a "propensity" to molest students.
The Court of Appeal's contrary holding is, with respect, simply wrong.
But it gets worse.
The Court of Appeal holds that instead of "dangerous propensity," the jury should have been told that L.A. Unified was liable if it knew or should have known that the teacher "had the potential for sexually abusing minors" (emphasis in original).
That's definitely wrong.
Of course the teacher had the potential for sexually abusing minors. Anyone with arms and/or legs has the potential to sexually abuse minors. They can sexually abuse minors. They indeed have that potential. But that doesn't make their employer liable. Because all teachers have that "potential".
If that doesn't make intuitive sense to you, I'll use the Court of Appeal's own authoritative source, vocabulary.com. Which says that "[i]f you can describe something as possible but not yet actual, choose the adjective 'potential.'" Or, to the same effect, "[i]t describes something or someone that has the power to become something." A teacher has the power to become a child molester -- i.e., the 'potential' -- by mere fact that he's a teacher. To say that L.A Unified is liable if it knew or should have known that one of its teachers "had the power" to molest students is to say that it's always liable.
And that's not, in fact, the law. Nor what CACI 426 is trying to get at.
So, normally, given all this, I'd say that this was a great -- and important -- case that's deserving of review by the California Supreme Court.
With one problem.
The Court of Appeal here granted a new trial. On multiple grounds (e.g., instructional error, various evidentiary errors, etc.). I've got a huge beef with one of those bases for reversal. But the others are much more pedestrian, and (perhaps even more importantly) much more likely to be right.
So the California Supreme Court may well not want to grant review on all these issues. And may well not want to grant review on one of them either, since the result will remain the same (i.e., a new trial) even if one of the multiple bases for the Court of Appeal's holding was wrong. As the Court often says, it reviews judgments, not reasons. And the judgment here may well be right, even if one of the reasons for this judgment is horribly wrong.
Plus there's a practical problem. Who's going to move for review? L.A. Unified is the one aggrieved by the erroneous holding. But unless they think they can get review granted on all of the bases of the Court of Appeal's ruling (a definite longshot), from a new trial perspective, it doesn't help to merely get review of one of them.
Yet, at the same time, the public policy consequences here are serious. The Court of Appeal has invalidated a perfectly good CACI. Worse, its articulation of the correct jury instruction is (in my view) way off the mark, and makes for virtually limitless liability. Those instructions will be used not only in this case (on remand), but in thousands of others.
That's a problem. A serious one.
In the best of all possible worlds, the Court of Appeal would grant rehearing and reverse its opinion on the CACI issue. Of course, that's not likely to happen. The panel made a decision -- unanimous (albeit with a waiver objection by one of the members) as to the merits -- and it's unlikely to change its mind just because some law professor somewhere thinks it's wrong. So practically, the chances of this resolution are nil.
The second best world would be for the Court of Appeal to delete the first part of its opinion and rest its judgment on the alternative bases for reversal. Since the CACI issue is unnecessary to the result, this is possible. But such a resolution by the panel is practically unlikely as well. Not only because their minds are (probably) made up, but also because there's going to be a retrial, at which they will want a proper jury instruction. Since they think the one given in the first trial in wrong, they'll want to give guidance. Both in this case and others.
As a result, the panel's not likely to solve the problem.
Which leaves the California Supreme Court.
As I said, in a normal situation, I'd think this case would more than justify review. But I understand (for the reasons previously expressed) that the Court may not want to do that here.
But at a minimum, I'd want the California Supreme Court to depublish the Court of Appeal's (unnecessary and erroneous) holding as to the CACI instruction. Such a result admittedly won't help L.A. Unified in this case, since there's going to be a retrial, and unless there's review, depublication would still mean that the Court of Appeal's ruling would be law of the case, which means that (in my view) L.A. Unified gets an unjust and inequitable jury instruction on remand.
But at least that's better than leaving the opinion published and having this be the result in all future molestation cases. Which is what's going to happen unless the Court depublishes this one. Since trial courts will otherwise read the Court of Appeal's opinion and modify the CACI accordingly in light of that ruling. To the serious detriment of defendants and (in my view) to the equitable rule of law.
I agree with the vast majority of opinions I read. (And the overwhelming majority of those are thus not worth any comment on my end.) I disagree with some opinions, and try not to be shy about my honest take on those.
A very, very few opinions fall into the category of those as to which I both strongly disagree and find them exceptionally important.
This is one of them.
I don't say that lightly. I'm generally not a fan of the regime (e.g., under Chief Justice Lucas) in which the California Supreme Court depublishes tons of cases from the Court of Appeal instead of granting review. I'm happy that the graph of the recent depublication rate looks something like this:
Moreover, I'm not going to quibble about the result reached here by the Court of Appeal. There were definitely some seriously problematic rulings in this lawsuit, which involved the molestation of a 14-year old student by her eighth-grade math teacher. The trial court allowed introduction of evidence about her sexual history with other people; that could definitely be a problem. The trial court also seemed to think it helpful to instruct the jury that a 14-year old could validly "consent" to intercourse with her teacher; that could definitely be a problem as well.
So as far as the result goes, I'm on board for granting the plaintiff a new trial. Despite the fact that the jury found that the Los Angeles Unified School District wasn't liable at all, maybe that finding was influenced by some rulings that aren't kosher. So is everyone on the panel.
But the bulk of the opinion is devoted to why a particular (modified) jury instruction, CACI 426, was improperly given in this case, and why a new trial is principally required on that ground. And that's a holding that I believe is both (1) wrong, and (2) pernicious. Both in this case as well as many others.
This is a "negligent hiring" (or retention) case. It's not enough that Los Angeles Unified employed someone who molested a kid. Plaintiff's got to prove that L.A. Unified knew or should have known that this guy was someone who might well molest someone.
The standard instruction in these types of cases is CACI 426. Which says:
“[Name of plaintiff] claims that [he/she] was harmed by [name of employee] and that [name of employer defendant] is responsible for that harm because [name of employer defendant] negligently [hired/ supervised/ [or] retained] [name of employee]. To establish this claim, [name of plaintiff] must prove all of the following:
1) That [name of employee] was [unfit/ [or] incompetent] to perform the work for which [he/she] was hired;
2) That [name of employer defendant] knew or should have known that [name of employee] was [unfit/ [or] incompetent] and that this [unfitness/ [or] incompetence] created a particular risk to others;
3) That [name of employee]’s [unfitness/ [or] incompetence] harmed [name of plaintiff]; and
4) That [name of employer defendant]’s negligence in [hiring/ supervising/ [or] retaining] [name of employee] was a substantial factor in causing [name of plaintiff]'s harm."
That's indeed the basic rule. We've got to modify this instruction somewhat, since saying that the teacher here was "unfit [or] incompetent" doesn't really express what we mean (much less clearly). What we're trying to get at is that L.A. Unified is only liable if they knew or should have known that the guy was someone who's going to molest one of his students.
Now, there's a reason this case goes to trial, rather than resolved on summary judgment (or with a settlement). The teacher here allegedly does some stuff that might well put L.A. Unified on notice that there's a problem here. He's popular with female students. Very popular. He hugs 'em. A lot. His classroom conversations sometimes reflect personal stuff. Very personal stuff. And he sets up his classroom furniture so there's a nice little hidden alcove.
Mind you, what I've just said could potentially apply equally to lots of teachers I know. Lots. But in an eighth grade teacher, maybe this should put L.A. Unified on notice to at least check the dude out, if not have a stern conversation with him about the nature of professionalism when dealing with 14-year olds.
That's why we have a jury. Up to them to decide just how "weird" this stuff is and what red flags (if any) it should have raised.
But we have to tell this to the jury in non-legalese. In words they'll understand. And using terms like "unfitness" or "incompetence" for the job just don't cut it.
So the trial court modifies CACI 426 so it says that L.A. Unified is liable if it knew or should have known, based on these facts, that the teacher here (instead of being "unfit" or "incompetent") had a "dangerous propensity to sexually abuse minors."
That seems right to me.
But the Court of Appeal says it's not. Indeed, that it's reversible error. On the ground that requiring proof that someone has a "dangerous propensity to sexually abuse minors" would require plaintiffs to prove that the dude had already molested someone else. And that, instead, the jury should have been instructed that L.A. Unified was liable if they knew or should have known that the teacher "had the potential for sexually abusing minors" (emphasis in original).
I disagree with all of that. Strongly.
For one thing, I think that "dangerous propensity" is precisely what we're trying to get at. We want to impose liability when you know (or should know) that a guy's acting sufficiently strangely in a way that suggests that he may well be the kind of guy who'll touch minors. "Dangerous propensity" is, to me, a great way to express that idea. Legal enough to satisfy the Court of Appeal (as opposed to, say, "sufficiently strangely") yet common sense enough to actually assist jurors in making a decision.
For an other thing, I strongly disagree that "dangerous propensity" to do X means -- or even is commonly understood to mean -- that someone's already done X. The Court of Appeal cites an online dictionary that says that “If you have a propensity for something, then it’s something that comes naturally to you or something you just do a lot.” (emphasis in original). Let's be willing for a moment to entirely ignore the wisdom of judiciary relying on definitions from vocabulary.com -- and, for the record, color me skeptical on the authoritative nature of this particular source. The simple fact is that to have a "propensity" to do something does not mean that you, in fact, have already done it a lot. It just means that you have an inclination to do it. Whether this is your first or fiftieth time.
Yes, I admit, if you do, in fact, do something a lot, that may well be pretty good evidence that you do in fact have a propensity for it. That's why the definition the Court of Appeal cites has an or in it. To have a propensity for X is to say that "it's something that comes naturally to you or something you just do a lot." See the "or"?
When I say someone has a "propensity" for something, that just means that they're the kind of person who might well be into that sort of thing. When I say that a jittery guy who's wandering around a shopping mall in camouflage clothing mumbling incoherently about space aliens and Obama being out to get him, and who's carrying a machine gun, is a guy who has a "propensity" for committing mass murder, I definitely do not mean that he's already killed twenty people. I'm saying that he's the type of guy who may well commit mass murder in the future. And, parenthetically, that anyone who sees the guy doing all this stuff either knows or should have knows that this is true.
If anyone came up to me and said: "Professor Martin, I disagree with you: This guy definitionally doesn't have the propensity to commit mass murder since there's no proof that he's actually killed anyone yet," I'd respond that, with respect, they don't know what the word "propensity" means.
Yet that's precisely what the Court of Appeal holds.
To tell a jury, as the trial court did here, that L.A. Unified is liable if they knew or should have known that one of its teachers had a "dangerous propensity" to molest kids based on what they saw from him does not, in fact, hold L.A. Unified liable only if the teacher had previously molested someone. I can say that someone has a "propensity" to commit suicide even if they've never done it before. Ditto for someone with a "propensity" to molest students.
The Court of Appeal's contrary holding is, with respect, simply wrong.
But it gets worse.
The Court of Appeal holds that instead of "dangerous propensity," the jury should have been told that L.A. Unified was liable if it knew or should have known that the teacher "had the potential for sexually abusing minors" (emphasis in original).
That's definitely wrong.
Of course the teacher had the potential for sexually abusing minors. Anyone with arms and/or legs has the potential to sexually abuse minors. They can sexually abuse minors. They indeed have that potential. But that doesn't make their employer liable. Because all teachers have that "potential".
If that doesn't make intuitive sense to you, I'll use the Court of Appeal's own authoritative source, vocabulary.com. Which says that "[i]f you can describe something as possible but not yet actual, choose the adjective 'potential.'" Or, to the same effect, "[i]t describes something or someone that has the power to become something." A teacher has the power to become a child molester -- i.e., the 'potential' -- by mere fact that he's a teacher. To say that L.A Unified is liable if it knew or should have known that one of its teachers "had the power" to molest students is to say that it's always liable.
And that's not, in fact, the law. Nor what CACI 426 is trying to get at.
So, normally, given all this, I'd say that this was a great -- and important -- case that's deserving of review by the California Supreme Court.
With one problem.
The Court of Appeal here granted a new trial. On multiple grounds (e.g., instructional error, various evidentiary errors, etc.). I've got a huge beef with one of those bases for reversal. But the others are much more pedestrian, and (perhaps even more importantly) much more likely to be right.
So the California Supreme Court may well not want to grant review on all these issues. And may well not want to grant review on one of them either, since the result will remain the same (i.e., a new trial) even if one of the multiple bases for the Court of Appeal's holding was wrong. As the Court often says, it reviews judgments, not reasons. And the judgment here may well be right, even if one of the reasons for this judgment is horribly wrong.
Plus there's a practical problem. Who's going to move for review? L.A. Unified is the one aggrieved by the erroneous holding. But unless they think they can get review granted on all of the bases of the Court of Appeal's ruling (a definite longshot), from a new trial perspective, it doesn't help to merely get review of one of them.
Yet, at the same time, the public policy consequences here are serious. The Court of Appeal has invalidated a perfectly good CACI. Worse, its articulation of the correct jury instruction is (in my view) way off the mark, and makes for virtually limitless liability. Those instructions will be used not only in this case (on remand), but in thousands of others.
That's a problem. A serious one.
In the best of all possible worlds, the Court of Appeal would grant rehearing and reverse its opinion on the CACI issue. Of course, that's not likely to happen. The panel made a decision -- unanimous (albeit with a waiver objection by one of the members) as to the merits -- and it's unlikely to change its mind just because some law professor somewhere thinks it's wrong. So practically, the chances of this resolution are nil.
The second best world would be for the Court of Appeal to delete the first part of its opinion and rest its judgment on the alternative bases for reversal. Since the CACI issue is unnecessary to the result, this is possible. But such a resolution by the panel is practically unlikely as well. Not only because their minds are (probably) made up, but also because there's going to be a retrial, at which they will want a proper jury instruction. Since they think the one given in the first trial in wrong, they'll want to give guidance. Both in this case and others.
As a result, the panel's not likely to solve the problem.
Which leaves the California Supreme Court.
As I said, in a normal situation, I'd think this case would more than justify review. But I understand (for the reasons previously expressed) that the Court may not want to do that here.
But at a minimum, I'd want the California Supreme Court to depublish the Court of Appeal's (unnecessary and erroneous) holding as to the CACI instruction. Such a result admittedly won't help L.A. Unified in this case, since there's going to be a retrial, and unless there's review, depublication would still mean that the Court of Appeal's ruling would be law of the case, which means that (in my view) L.A. Unified gets an unjust and inequitable jury instruction on remand.
But at least that's better than leaving the opinion published and having this be the result in all future molestation cases. Which is what's going to happen unless the Court depublishes this one. Since trial courts will otherwise read the Court of Appeal's opinion and modify the CACI accordingly in light of that ruling. To the serious detriment of defendants and (in my view) to the equitable rule of law.
I agree with the vast majority of opinions I read. (And the overwhelming majority of those are thus not worth any comment on my end.) I disagree with some opinions, and try not to be shy about my honest take on those.
A very, very few opinions fall into the category of those as to which I both strongly disagree and find them exceptionally important.
This is one of them.
Wednesday, September 16, 2015
Grace v. Mansourian (Cal. Ct. App. - Sept. 15, 2015)
I always tell my students that requests for admission are valuable tools that should be propounded far more than they are. But I also tell them that it's incredibly rare for courts to actually impose cost of proof sanctions at the end of trial, both because most cases settle and because judges are reluctant to actually impose them.
Today's case proves the latter point. But it's also incredibly valuable, because the Court of Appeal reverses, holding that the trial court abused its discretion by not imposing cost of proof sanctions, and that this was true even in a he said/she said case of "who ran the red light". The fact that an issue was actively disputed at trial, and even the fact that there might have been "substantial evidence" in favor of both sides of the dispute (e.g., that would preclude summary judgment), doesn't matter.
That's a great -- and rare -- holding. You should cite it often. Both when requesting cost of proof sanctions and when threatening the other side with 'em.
Today's case proves the latter point. But it's also incredibly valuable, because the Court of Appeal reverses, holding that the trial court abused its discretion by not imposing cost of proof sanctions, and that this was true even in a he said/she said case of "who ran the red light". The fact that an issue was actively disputed at trial, and even the fact that there might have been "substantial evidence" in favor of both sides of the dispute (e.g., that would preclude summary judgment), doesn't matter.
That's a great -- and rare -- holding. You should cite it often. Both when requesting cost of proof sanctions and when threatening the other side with 'em.
U.S. v. Rosales-Gonzales (9th Cir. - Sept. 16, 2015)
Guadalupe Rosales-Gonzales was previously deported but was in the United States, so the United States charged him with this offense. The parties struck a deal and jointly requested that he be given ninth months in prison.
The district judge, Larry Burns (down here in San Diego), had some "preliminary thoughts" on the deal. Namely, that it was absurd.
Judge Burns first wanted to know why the deal was to give defendant nine months in prison when he had been previously convicted of this same offense and given 14 months in prison. Shouldn't your second offense at least subject you to more time than the first?
That made sense to the government. Or at least they realized the likely futility of arguing otherwise.
So the U.S. decided to ask for 15 months rather than 9. One more month than the guy got last time.
But Judge Burns still wasn't satisfied. Even with the extra month. And wanted to know why 15 months was an appropriate sentence for someone who'd been deported 35 times.
To which the U.S. could respond only that the defendant had quickly entered a guilty plea, waived all appeals, and efficiently resolved the matter. So from the government's perspective, 15 months was an appropriate sentence.
Judge Burns nonetheless sentenced Mr. Rosales-Gonzales to 27 months.
Defendant appealed. But the Ninth Circuit affirms. Sentence recommendations aren't binding. A district court don't have to follow a fast-track deal.
Makes sense to me.
The district judge, Larry Burns (down here in San Diego), had some "preliminary thoughts" on the deal. Namely, that it was absurd.
Judge Burns first wanted to know why the deal was to give defendant nine months in prison when he had been previously convicted of this same offense and given 14 months in prison. Shouldn't your second offense at least subject you to more time than the first?
That made sense to the government. Or at least they realized the likely futility of arguing otherwise.
So the U.S. decided to ask for 15 months rather than 9. One more month than the guy got last time.
But Judge Burns still wasn't satisfied. Even with the extra month. And wanted to know why 15 months was an appropriate sentence for someone who'd been deported 35 times.
To which the U.S. could respond only that the defendant had quickly entered a guilty plea, waived all appeals, and efficiently resolved the matter. So from the government's perspective, 15 months was an appropriate sentence.
Judge Burns nonetheless sentenced Mr. Rosales-Gonzales to 27 months.
Defendant appealed. But the Ninth Circuit affirms. Sentence recommendations aren't binding. A district court don't have to follow a fast-track deal.
Makes sense to me.
Tuesday, September 15, 2015
People v. Nelson (Cal. Ct. App. - Sept. 15, 2015)
You can be found guilty of soliciting someone to kill your future ex-wife. Even if you're merely asking someone to find a hit man for you, and even if you subsequently back out of it.
Something that Eric Nelson will get to think about for the next eight years.
Something that Eric Nelson will get to think about for the next eight years.
AP-Colton LLC v. Ohaeri (Cal. Ct. App. - Sept. 15, 2015)
I love it when the Court of Appeal makes my job incredibly easy. Especially on a rainy day in San Diego.
Justice Ramirez tells you everything you need to know in the first three paragraphs of this opinion. Just look how crisp, clean, and comprehensive those paragraphs are:
"Defendants Charles and Stella Ohaeri (Ohaeris) leased space for a thrift store in a
shopping center owned by plaintiff AP-Colton LLC (AP-Colton). The thrift store was
not a success, and the Ohaeris stopped paying rent. According to the Ohaeris, AP-Colton
had fraudulently induced them to enter into the lease by stating that a church was going to
move into the space next to theirs, but a competing store moved in instead.
AP-Colton originally filed the case as a limited civil action, in which damages are
limited to $25,000. The Ohaeris filed a cross-complaint seeking more than $25,000, but
they did not pay the $140 fee required to reclassify the case as an unlimited civil action.
Thereafter, AP-Colton filed an amended complaint seeking more than $25,000; as the
Ohaeris should already have paid the reclassification fee, AP-Colton did not pay it. After
a bench trial, the trial court rejected the Ohaeris’ fraud claims and awarded AP-Colton
$126,437.25.
The Ohaeris now contend, among other things, that the case remained a limited
civil action, and thus, the trial court erred by awarding damages of more than $25,000.
We do agree that the case should have remained a limited civil action. The Ohaeris,
however, took the position below that the case had become an unlimited civil action, and
the trial court accepted this position by awarding AP-Colton damages in excess of
$25,000; we will hold that, as a result, the Ohaeris are judicially estopped to deny that the
case was an unlimited civil action. Accordingly, on condition that it pays the $140
reclassification fee, AP-Colton can recover the full award."
How awesome of a summary is that?
Beautiful
Monday, September 14, 2015
U.S. v. Myers (9th Cir. - Sept. 14, 2015)
This is an important opinion. That may well not get nearly the judicial attention that it deserves.
The question presented is whether you can have a consensual settlement conference with a magistrate judge in a federal criminal case. Those familiar with the criminal side may say: "How is that actually a question? There are settlement rules in tons of federal courts that expressly allow this practice, and the Ninth Circuit has repeatedly held that this practice is okay." And that's exactly right. Whereas the federal judge who's in charge of your case can't participate in plea negotiations (since there's too great of a risk of coercion), the Ninth Circuit has long held that it's perfectly okay for a different judge to act as a mediator and to try to see if the parties can't work out a mutually beneficial deal.
But today, the Ninth Circuit says that's no longer the rule. No judicial involvement in plea deals. Not even with "neutral" (non-involved) judges. Period.
Personally, I'm agnostic about whether settlement judges in federal criminal cases are a good idea. I am definitely against the involvement of the judge in the particular case being involved in negotiations -- that's way too dangerous, since the defendant (and/or prosecutor) might think that if she refuses a proposed deal that the judge says is a good one the judge might take it out on them at trial and/or at sentencing. But a "neutral" judge that's otherwise not involved at all in the underlying case? That's a different situation. Maybe it's a good idea, since those judges have expertise and can help the parties settle. But maybe it's still a bad idea, since there might still be the fear of coercion in other cases; e.g., in other cases the prosecutor or public defender may have in front of this judge.
In short, I'm not at all sure what the right rule should be. I can see very plausible arguments on both sides.
But the Ninth Circuit holds today that the rule is that judges categorically can't be involved. In an opinion that may well be subject to substantial doctrinal critique.
For one thing, there's this little thing called circuit precedent. The Ninth Circuit has repeatedly held that settlement conference precisely like the one that transpired here are perfectly okay; moreover, that such conferences don't violate Rule 11(c)'s command that the federal court not be involved in any plea negotiations. Judge Murguia's opinion says that these cases are inconsistent with the subsequent 2013 holding of the Supreme Court in Davila. When I first read today's opinion, Judge Murguia's interpretation of that case seemed right. But when I then actually went and read Davila, I'm not at all certain that Davila actually justifies the panel's non-en banc departure from circuit precedent. If only because Davila's discussion of the issue is not only way dicta, but is also world's apart from what's at issue here.
In the present situation, we're dealing with (1) a settlement conference, (2) that everyone attended, and (3) was conducted pursuant to a district court rule. By contrast, in Davila, the magistrate judge simply sua sponte pulled in the criminal defendant in an ex parte proceeding and essentially told him that he'd be better off pleading guilty than going to trial.
In that setting, the United States admitted that the judge's conduct was improper. And the Supreme Court accepted that (undisputed) concession, noting that "the prohibition [in FRCP 11] was included out of concern that a defendant might be induced to plead guilty rather than risk displeasing the judge who would preside at trial." (Remember: We're not talking in the present case about involving the judge who would preside at trial. We're talking about involving a totally unrelated judge.) And then the Supreme Court's opinion went on to discuss the only issue on which it actually granted certiorari: whether a violation of Rule 11 was structural error requiring automatic reversal. ("We granted certiorari to resolve a Circuit conflict concerning the consequences of a Rule 11(c)(1) violation.")
That's what Davila was about. The introductory two paragraphs on page 7 of that opinion that discuss the history of Rule 11 and why we (rightly) don't allow the trial judge to participate in plea negotiations don't seem dispositive of whether we should allow some other judge to do so. Now, in Davila, it wasn't the trial judge who pulled in the defendant -- it was a magistrate judge. But the fact that the Supreme Court accepted an admission that this was improper, and then held that this did not require reversal, hardly to me seems to require that a panel in the Court of Appeals to invalidate circuit precedent that says that formal settlement conferences in front of neutral judges are okay. I could easily see a judge saying that one of these things was not okay whereas another was just fine. Particularly given the factual contexts in which these two issues presented themselves; e.g., the clearly non-coercive judicial conversation at issue in the present case versus the very different types of judicial statements at issue in Davila.
So, as a matter of precedent, I'm not sure that today's opinion is on incredibly solid footing. I think there's a very decent argument that the panel wasn't free to depart from what the Ninth Circuit has repeatedly said is the right rule.
Moreover, as a matter of text, I also don't think that Judge Murguia's opinion is entirely bulletproof. She says that the prior Ninth Circuit cases didn't "address, much less resolve, the conflict between the plain language of Rule 11(c)(1)—which categorically prohibits “[t]he court” from participating in plea negotiations—and the local rule’s allowance of judge-led criminal settlement conferences." Put to one side that these cases nonetheless approved the practice at issue as consistent with Rule 11 and drew the longstanding distinction (at issue here) between involvement of the trial/sentencing judge versus a "neutral" judge. Simply as a matter of textual interpretation, I'm not so sure that Rule 11 is nearly as "plain" as Judge Murguia reads it.
Today's opinion says that Rule 11(c)(1) is crystal clear since it prohibits "the court" from engaging in any plea negotiations. Judge Murguia then says that this phrase unambiguously applies to the judge here since Rule 1(b)(2) defines "court" as including a federal judge performing any judicial function and Rule 1(b)(3) says that includes magistrate judges.
Fair enough. But I'm not sure that the word "court" is really the one that's at issue. Rather, it seems to me that we're focusing on what Rule 11 means when it says that "the" court isn't allowed to be involved in plea negotiations. Does "the" court refer to the trial court (i.e., the trial/sentencing court), which is the distinction that prior circuit precedent draws, or does it merely mean "any" court (i.e., even the otherwise uninvolved magistrate judge)? That's the relevant textual issue. And there's no definition anywhere of the word "the".
(Oh, and for what it's worth, the Federal Rules of Criminal Procedure use the phrase "a court" rather than "the court" in about a dozen or so different rules, including Rules 12, 32.2, 49, and 56, making it at least plausible to argue that when the rule makers wanted to preclude any court from doing a certain thing, they knew perfectly well how to do so, and that there's a textual distinction been "the" court and "a" court doing a particular thing.)
Remember that we're talking about whether the panel was permitted to overrule circuit precedent here. That seems a very sticky wicket, especially since the proper resolution of this issue is (despite Judge Murguia's textual and precedential analysis) far from clear.
So why do I think this very important case -- one that'll strike down formal settlement programs in the Northern District of California and elsewhere -- might not get the judicial attention it may well deserve? Two reasons.
One, the composition of the panel. The opinion is unanimous. It's written by Judge Murguia and joined by Judges McKeown and Friedland. That's a credible bunch. As well as three votes of active judges presumptively against en banc review.
Second, and perhaps even more importantly, because the case here comes out against the defendant. The panel holds that the judicial involvement of the magistrate judge here was error -- and hence district courts will have to dismantle their criminal settlement programs -- but that the error here did not prejudice this defendant's substantial rights because he knowingly participated in the process and indeed benefited from it. Hence his conviction is affirmed.
Given this result, who's going to petition for rehearing en banc or seek of writ of certiorari? Sure, the defendant might, claiming that his rights were indeed violated, but that's going nowhere. By contrast, the United States might be seriously unhappy with the Rule 11 holding, but they won, so a petition by them may not get nearly the traction that one might otherwise receive were they actually to have lost the case.
Sort of a Marbury v. Madison type of thing. Effectively unreviewable notwithstanding the fact that review is possible.
A very important case. One that affects a ton of criminal cases.
We'll see what -- if anything -- happens to the opinion from here.
The question presented is whether you can have a consensual settlement conference with a magistrate judge in a federal criminal case. Those familiar with the criminal side may say: "How is that actually a question? There are settlement rules in tons of federal courts that expressly allow this practice, and the Ninth Circuit has repeatedly held that this practice is okay." And that's exactly right. Whereas the federal judge who's in charge of your case can't participate in plea negotiations (since there's too great of a risk of coercion), the Ninth Circuit has long held that it's perfectly okay for a different judge to act as a mediator and to try to see if the parties can't work out a mutually beneficial deal.
But today, the Ninth Circuit says that's no longer the rule. No judicial involvement in plea deals. Not even with "neutral" (non-involved) judges. Period.
Personally, I'm agnostic about whether settlement judges in federal criminal cases are a good idea. I am definitely against the involvement of the judge in the particular case being involved in negotiations -- that's way too dangerous, since the defendant (and/or prosecutor) might think that if she refuses a proposed deal that the judge says is a good one the judge might take it out on them at trial and/or at sentencing. But a "neutral" judge that's otherwise not involved at all in the underlying case? That's a different situation. Maybe it's a good idea, since those judges have expertise and can help the parties settle. But maybe it's still a bad idea, since there might still be the fear of coercion in other cases; e.g., in other cases the prosecutor or public defender may have in front of this judge.
In short, I'm not at all sure what the right rule should be. I can see very plausible arguments on both sides.
But the Ninth Circuit holds today that the rule is that judges categorically can't be involved. In an opinion that may well be subject to substantial doctrinal critique.
For one thing, there's this little thing called circuit precedent. The Ninth Circuit has repeatedly held that settlement conference precisely like the one that transpired here are perfectly okay; moreover, that such conferences don't violate Rule 11(c)'s command that the federal court not be involved in any plea negotiations. Judge Murguia's opinion says that these cases are inconsistent with the subsequent 2013 holding of the Supreme Court in Davila. When I first read today's opinion, Judge Murguia's interpretation of that case seemed right. But when I then actually went and read Davila, I'm not at all certain that Davila actually justifies the panel's non-en banc departure from circuit precedent. If only because Davila's discussion of the issue is not only way dicta, but is also world's apart from what's at issue here.
In the present situation, we're dealing with (1) a settlement conference, (2) that everyone attended, and (3) was conducted pursuant to a district court rule. By contrast, in Davila, the magistrate judge simply sua sponte pulled in the criminal defendant in an ex parte proceeding and essentially told him that he'd be better off pleading guilty than going to trial.
In that setting, the United States admitted that the judge's conduct was improper. And the Supreme Court accepted that (undisputed) concession, noting that "the prohibition [in FRCP 11] was included out of concern that a defendant might be induced to plead guilty rather than risk displeasing the judge who would preside at trial." (Remember: We're not talking in the present case about involving the judge who would preside at trial. We're talking about involving a totally unrelated judge.) And then the Supreme Court's opinion went on to discuss the only issue on which it actually granted certiorari: whether a violation of Rule 11 was structural error requiring automatic reversal. ("We granted certiorari to resolve a Circuit conflict concerning the consequences of a Rule 11(c)(1) violation.")
That's what Davila was about. The introductory two paragraphs on page 7 of that opinion that discuss the history of Rule 11 and why we (rightly) don't allow the trial judge to participate in plea negotiations don't seem dispositive of whether we should allow some other judge to do so. Now, in Davila, it wasn't the trial judge who pulled in the defendant -- it was a magistrate judge. But the fact that the Supreme Court accepted an admission that this was improper, and then held that this did not require reversal, hardly to me seems to require that a panel in the Court of Appeals to invalidate circuit precedent that says that formal settlement conferences in front of neutral judges are okay. I could easily see a judge saying that one of these things was not okay whereas another was just fine. Particularly given the factual contexts in which these two issues presented themselves; e.g., the clearly non-coercive judicial conversation at issue in the present case versus the very different types of judicial statements at issue in Davila.
So, as a matter of precedent, I'm not sure that today's opinion is on incredibly solid footing. I think there's a very decent argument that the panel wasn't free to depart from what the Ninth Circuit has repeatedly said is the right rule.
Moreover, as a matter of text, I also don't think that Judge Murguia's opinion is entirely bulletproof. She says that the prior Ninth Circuit cases didn't "address, much less resolve, the conflict between the plain language of Rule 11(c)(1)—which categorically prohibits “[t]he court” from participating in plea negotiations—and the local rule’s allowance of judge-led criminal settlement conferences." Put to one side that these cases nonetheless approved the practice at issue as consistent with Rule 11 and drew the longstanding distinction (at issue here) between involvement of the trial/sentencing judge versus a "neutral" judge. Simply as a matter of textual interpretation, I'm not so sure that Rule 11 is nearly as "plain" as Judge Murguia reads it.
Today's opinion says that Rule 11(c)(1) is crystal clear since it prohibits "the court" from engaging in any plea negotiations. Judge Murguia then says that this phrase unambiguously applies to the judge here since Rule 1(b)(2) defines "court" as including a federal judge performing any judicial function and Rule 1(b)(3) says that includes magistrate judges.
Fair enough. But I'm not sure that the word "court" is really the one that's at issue. Rather, it seems to me that we're focusing on what Rule 11 means when it says that "the" court isn't allowed to be involved in plea negotiations. Does "the" court refer to the trial court (i.e., the trial/sentencing court), which is the distinction that prior circuit precedent draws, or does it merely mean "any" court (i.e., even the otherwise uninvolved magistrate judge)? That's the relevant textual issue. And there's no definition anywhere of the word "the".
(Oh, and for what it's worth, the Federal Rules of Criminal Procedure use the phrase "a court" rather than "the court" in about a dozen or so different rules, including Rules 12, 32.2, 49, and 56, making it at least plausible to argue that when the rule makers wanted to preclude any court from doing a certain thing, they knew perfectly well how to do so, and that there's a textual distinction been "the" court and "a" court doing a particular thing.)
Remember that we're talking about whether the panel was permitted to overrule circuit precedent here. That seems a very sticky wicket, especially since the proper resolution of this issue is (despite Judge Murguia's textual and precedential analysis) far from clear.
So why do I think this very important case -- one that'll strike down formal settlement programs in the Northern District of California and elsewhere -- might not get the judicial attention it may well deserve? Two reasons.
One, the composition of the panel. The opinion is unanimous. It's written by Judge Murguia and joined by Judges McKeown and Friedland. That's a credible bunch. As well as three votes of active judges presumptively against en banc review.
Second, and perhaps even more importantly, because the case here comes out against the defendant. The panel holds that the judicial involvement of the magistrate judge here was error -- and hence district courts will have to dismantle their criminal settlement programs -- but that the error here did not prejudice this defendant's substantial rights because he knowingly participated in the process and indeed benefited from it. Hence his conviction is affirmed.
Given this result, who's going to petition for rehearing en banc or seek of writ of certiorari? Sure, the defendant might, claiming that his rights were indeed violated, but that's going nowhere. By contrast, the United States might be seriously unhappy with the Rule 11 holding, but they won, so a petition by them may not get nearly the traction that one might otherwise receive were they actually to have lost the case.
Sort of a Marbury v. Madison type of thing. Effectively unreviewable notwithstanding the fact that review is possible.
A very important case. One that affects a ton of criminal cases.
We'll see what -- if anything -- happens to the opinion from here.
Wabakken v. California Dep't of Corrections (9th Cir. - Sept. 14, 2015)
Usually when the Ninth Circuit lists the counsel for the parties, it includes the lawyer's name followed by his or her firm. But here, counsel for appellant is listed simply as "Derek T. Anderson, Attorney at Law."
The unadorned name doesn't matter, though. He wins.
The unadorned name doesn't matter, though. He wins.
Friday, September 11, 2015
In Re Landmark Fence (9th Cir. - Sept. 11, 2015)
Judge McKeown is right in this bankruptcy appeal. There's no appellate jurisdiction here. The case isn't over. There's no final judgment. So the appeal is properly dismissed.
Judge McKeown is also a bit snarky about the inexplicable delay in being told by the parties that the underlying bankruptcy petition had been dismissed seven months prior to the scheduled oral argument in the Ninth Circuit. But this snark seems justified. I'd be snarky too. And do the same thing that she (and the rest of the panel) do: dismiss the appeal and leave the mootness issue for resolution by the lower courts. They can sort it out.
One more thing. Isn't it ironic that the first sentence of the legal analysis in Judge McKeown's opinion reads: "Although both parties urge us to decide this appeal on its merits, “[i]t needs no citation of authorities to show that the mere consent of parties cannot confer upon a court of the United States the jurisdiction to hear and decide a case.'" And then cites a case.
Judge McKeown is also a bit snarky about the inexplicable delay in being told by the parties that the underlying bankruptcy petition had been dismissed seven months prior to the scheduled oral argument in the Ninth Circuit. But this snark seems justified. I'd be snarky too. And do the same thing that she (and the rest of the panel) do: dismiss the appeal and leave the mootness issue for resolution by the lower courts. They can sort it out.
One more thing. Isn't it ironic that the first sentence of the legal analysis in Judge McKeown's opinion reads: "Although both parties urge us to decide this appeal on its merits, “[i]t needs no citation of authorities to show that the mere consent of parties cannot confer upon a court of the United States the jurisdiction to hear and decide a case.'" And then cites a case.
Grupp v. DHL Express (Cal. Ct. App. - Sept. 11, 2015)
Sometimes the California Supreme Court wants the Court of Appeal to reconsider its opinion. So it does.
And sometime this is what the Court of Appeal says:
"We filed our original opinion in this matter on April 11, 2014, and affirmed. Subsequently, the Relators petitioned our Supreme Court for review, and that petition was granted. On May 20, 2015, our Supreme Court transferred review of the matter to us under California Rules of Court, rule 8.528(d) with instructions that we reconsider our prior opinion in light of People ex rel. Harris v. PAC Anchor Transportation, Inc. (2014) 59 Cal.4th 772 (Pac Anchor). After considering Pac Anchor, we conclude it has no application here, and again affirm the trial court’s order."
Your turn, California Supreme Court.
And sometime this is what the Court of Appeal says:
"We filed our original opinion in this matter on April 11, 2014, and affirmed. Subsequently, the Relators petitioned our Supreme Court for review, and that petition was granted. On May 20, 2015, our Supreme Court transferred review of the matter to us under California Rules of Court, rule 8.528(d) with instructions that we reconsider our prior opinion in light of People ex rel. Harris v. PAC Anchor Transportation, Inc. (2014) 59 Cal.4th 772 (Pac Anchor). After considering Pac Anchor, we conclude it has no application here, and again affirm the trial court’s order."
Your turn, California Supreme Court.
Thursday, September 10, 2015
Shirley v. University of Idaho (9th Cir. - Sept. 10, 2015)
Plaintiff says X in his original complaint. Plaintiff subsequently amends his complaint to say Y.
The district court thinks that Y (the allegation in the amended complaint) is inconsistent with X (an allegation in the original pleading), so dismisses the lawsuit.
The Ninth Circuit summarily reverses. Holding that factual allegation Y is not, in fact, inconsistent with factual allegation X.
But what if it was?
On that -- admittedly irrelevant (at least here) issue -- both Judge Canby and Judge Kozinski want you to know their views. (While Judge Schroeder, who was also on the motions panel, exercises her right to remain silent.)
There's a prior Ninth Circuit opinion (PAE) that says you can't dismiss an amended complaint merely because it contradicts an earlier complaint. But there's a different prior Ninth Circuit opinion (Reddy) that says that a complaint can be dismissed with prejudice -- i.e., without leave to amend -- if any amended complaint would (impermissibly) contradict the allegations of the original complaint.
Judge Canby thinks those two cases are inconsistent. Judge Kozinski, by contrast, thinks those two authorities are consistent.
So both of 'em write a concurrence that explains their respective views of precedent.
Despite the fact that everyone agrees that this dispute doesn't matter in the slightest in the present case. In which the competing allegations in the various complaints do not, in fact, contradict each other.
It's an interesting dispute. And since Judges Canby and Kozinski think it's valuable to express their views, I'll tell you mine.
Judge Kozinski's a little bit right that the cases are doctrinally distinguishable. He says -- correctly -- that the PAE line of cases holds that you're not allowed to dismiss a complaint on the ground that it contradicts an earlier complaint because there's simply no rule that authorizes such a dismissal. On this point, he's right. You can look at every page of the FRCP and you're not going to find such an express provision. Sure, you might be sanctioned under Rule 11 or the like. But there's no rule that expressly authorizes the actual dismissal of a complaint on the grounds of a factual contradiction.
By contrast, Judge Kozinski says, there is a rule that says that you're not required to grant leave to amend when an amendment would be "futile". That rule, Judge Kozinski says, is why a court is not only allowed to, but must look at the prior complaint to see if any future amendment would plausibly articulate a claim. 'Cause leave to amend is required unless amendments are futile, and amendments are futile if they will contradict a prior allegation. That explains the Reddy line of precedent.
Hence, Judge Kozinski says, the two situations are distinguishable.
And he has a point.
Judge Canby, by contrast, thinks those two lines of precedent aren't rationally distinguishable. And he has a pretty darn good point as well.
Let me articulate Judge Canby's point in a way that's a bit more expansive than the way he puts it. (A feat that's necessary in part because Judge Canby's four-paragraph concurrence doesn't really explain his conclusion apart from pointing out -- correctly -- that the two lines of cases seem darn similar and are facially contradictory.) Here's how I'd put it:
The best argument for inconsistency, in my view, is that it makes absolutely no sense to say that a court must accept an amended complaint that contradicts the original complaint -- i.e., isn't allowed to dismiss the amended complaint on grounds of inconsistency -- and yet is simultaneously allowed to stop the amended complaint from ever being filed in the first place on precisely such inconsistency grounds. Judge Kozinski admits that Ninth Circuit precedent (Reddy) says that a district court can prevent a party from contradicting itself by finding that an amended complaint would contradict the original complaint and hence be "futile" -- thereby dismissing the original complaint without leave to amend and with prejudice. Well, if it's permissible to stop the filing of a contradictory complaint in the first place, then why can't you dismiss that same complaint once it's filed?! A regime that said (1) we can -- and affirmatively want to -- stop people from filing contradictory complaints in the first place, and a district court can permissibly do that, but (2) once a contradictory complaint is filed, we have to let it go forward; well, such a regime would make no sense. It'd be intellectually incoherent. The justification for (1) would be inconsistent with the justification for (2).
It'd be -- ironically enough, given the topic -- inconsistent for the judiciary to so hold.
Now, Judge Kozinski might perhaps respond: "Hey, dude, I just enforce the rules, I don't make 'em. The FRCP says you can dismiss a lawsuit in (1), but doesn't say you can do it in (2). I'm not saying that necessarily makes any sense. But that's what it says, so that's what I'm doing. Your beef is with the Supreme Court and Congress if you want the FRCP as a whole to make sense."
That's a plausible response. But it only goes so far. For two reasons.
First, there are lots of procedural rules that we routinely apply that aren't in the FRCP. Judicial estoppel, for one. Tons of others. So I'm not at all sure you can't say that just like you apply those common law rules to authorize dismissal of complaints, a similar common law rule doesn't authorize dismissal in cases where the amended complaint contradicts the original. See, e.g., dismissals based on judicial estoppel. Oh, and, by the way, among the other common law requirements that we impose is the rule that Judge Kozinski applies regarding futility. Look in the entire FRCP. You won't find the word "futility" once. It's a common law gloss on what it means for "justice" to either allow or disallow amendments. It's a judge-made rule. If that's a judge-made rule against inconsistency in proposed amendments, and you're fine with that, it seems like we can be equally fine with a similar judge made rule against inconsistency in actual amendments as well.
Second, we are interpreting words here. Namely, in situation (1), the meaning of the word "futile" (albeit in the context of what that means for a judge-made doctrine). Because if you really thought that parties were allowed to actually file amend pleadings that contradicted their original complaint -- e.g., that a court was not allowed to dismiss such pleadings -- then it wouldn't be "futile" to allow such an amendment, now would it? And yet Reddy says that it is "futile" to allow amendments that would contradict the original pleading. It's "futile" only if that contradictory amendment would be dismissed. Yet PAE says that such a contradictory amendment cannot, in fact, be dismissed.
Doesn't make sense.
Plus, wholly apart from the logical, doctrinal, and policy-based inconsistencies, there's a practical one as well. Which rule applies when?
Judge Kozinski would say that Reddy applies when a court dismisses an original complaint and is "thinking" about a "hypothetical" amended complaint. That's when you can permissibly reject those complaints that would contain contradictory allegations. Whereas, according to Judge Kozinski, when the amended (contradictory) complaint has already been filed, there's nothing you can do about it (or at least, even if you can sanction it, you can't dismiss it).
But what about when -- as in the present case -- there's an existing original complaint and the plaintiff asks permission to file an amended complaint. Hasn't yet. Is asking (as often required by Rule 15) to file it. What rule? Presumably now there's a text (Rule 15) that says that a court can refuse to allow such an amendment, so those things get bounced, right? Yet doesn't it seem totally bizarre to say that an allegation filed on Day 21 (e.g., as a matter of right) goes forward, even though totally belied by the original pleading, and yet that same allegation filed on Day 22 (e.g., when leave of court is required) gets categorically bounced. As well as that an allegation filed on Day 22 can't be bounced if the adverse party has stipulated to it (e.g., no permission is required).
Not that Judge Canby's view doesn't have distinction problems of its own. For example, let's say that the original complaint says that a tort transpired on December 7, 1941 (a date outside the limitations period), but the amended complaint says it instead transpired on December 7, 2014 (which would be inside it). Absent a darn good explanation (e.g., a typo), a consistent view of inconsistency would say that the amended complaint gets bounced because it contradicts the first.
But what if the situation was reversed; e.g., the original complaint says December 7, 2014 but the amended complaint says 1941? Are we really going to say that the guy can't amend his complaint because it contradicts the first? And what's the remedy: Do we bounce the entire dispute, or do we simply let the first complaint go forward? (Assume that the guy here has an absolute right to amend, so permission isn't required, and the second "automatically" displaces the first. Is there dismissal of the second complaint on inconsistency grounds and then that's it? Seems like it. Even though what we'd really want to do, if justice is our goal (and it is), is to go back to the first.)
So here's where I come out:
Judge Kozinski is right that you can ostensibly distinguish the two cases. In the same way that you could distinguish the two cases by saying: "Well, in one case, the plaintiff's name was an acronym, and in the other case, he had an actual spelled-out name." In short, yeah, you could distinguish the two cases, but that distinguishing characteristic would make no sense. It wouldn't create a good or principled rule. The principle that motivates the one set of cases is intellectually inconsistent from the result in the second group of cases."
Which is a bit more like Judge Canby's position.
So, in the end, we have an interesting -- albeit entirely unnecessary (in the context of the present case, anyway) -- dispute.
One that may well matter in a ton of cases. And that we'll eventually have to, or at least should, get right.
The district court thinks that Y (the allegation in the amended complaint) is inconsistent with X (an allegation in the original pleading), so dismisses the lawsuit.
The Ninth Circuit summarily reverses. Holding that factual allegation Y is not, in fact, inconsistent with factual allegation X.
But what if it was?
On that -- admittedly irrelevant (at least here) issue -- both Judge Canby and Judge Kozinski want you to know their views. (While Judge Schroeder, who was also on the motions panel, exercises her right to remain silent.)
There's a prior Ninth Circuit opinion (PAE) that says you can't dismiss an amended complaint merely because it contradicts an earlier complaint. But there's a different prior Ninth Circuit opinion (Reddy) that says that a complaint can be dismissed with prejudice -- i.e., without leave to amend -- if any amended complaint would (impermissibly) contradict the allegations of the original complaint.
Judge Canby thinks those two cases are inconsistent. Judge Kozinski, by contrast, thinks those two authorities are consistent.
So both of 'em write a concurrence that explains their respective views of precedent.
Despite the fact that everyone agrees that this dispute doesn't matter in the slightest in the present case. In which the competing allegations in the various complaints do not, in fact, contradict each other.
It's an interesting dispute. And since Judges Canby and Kozinski think it's valuable to express their views, I'll tell you mine.
Judge Kozinski's a little bit right that the cases are doctrinally distinguishable. He says -- correctly -- that the PAE line of cases holds that you're not allowed to dismiss a complaint on the ground that it contradicts an earlier complaint because there's simply no rule that authorizes such a dismissal. On this point, he's right. You can look at every page of the FRCP and you're not going to find such an express provision. Sure, you might be sanctioned under Rule 11 or the like. But there's no rule that expressly authorizes the actual dismissal of a complaint on the grounds of a factual contradiction.
By contrast, Judge Kozinski says, there is a rule that says that you're not required to grant leave to amend when an amendment would be "futile". That rule, Judge Kozinski says, is why a court is not only allowed to, but must look at the prior complaint to see if any future amendment would plausibly articulate a claim. 'Cause leave to amend is required unless amendments are futile, and amendments are futile if they will contradict a prior allegation. That explains the Reddy line of precedent.
Hence, Judge Kozinski says, the two situations are distinguishable.
And he has a point.
Judge Canby, by contrast, thinks those two lines of precedent aren't rationally distinguishable. And he has a pretty darn good point as well.
Let me articulate Judge Canby's point in a way that's a bit more expansive than the way he puts it. (A feat that's necessary in part because Judge Canby's four-paragraph concurrence doesn't really explain his conclusion apart from pointing out -- correctly -- that the two lines of cases seem darn similar and are facially contradictory.) Here's how I'd put it:
The best argument for inconsistency, in my view, is that it makes absolutely no sense to say that a court must accept an amended complaint that contradicts the original complaint -- i.e., isn't allowed to dismiss the amended complaint on grounds of inconsistency -- and yet is simultaneously allowed to stop the amended complaint from ever being filed in the first place on precisely such inconsistency grounds. Judge Kozinski admits that Ninth Circuit precedent (Reddy) says that a district court can prevent a party from contradicting itself by finding that an amended complaint would contradict the original complaint and hence be "futile" -- thereby dismissing the original complaint without leave to amend and with prejudice. Well, if it's permissible to stop the filing of a contradictory complaint in the first place, then why can't you dismiss that same complaint once it's filed?! A regime that said (1) we can -- and affirmatively want to -- stop people from filing contradictory complaints in the first place, and a district court can permissibly do that, but (2) once a contradictory complaint is filed, we have to let it go forward; well, such a regime would make no sense. It'd be intellectually incoherent. The justification for (1) would be inconsistent with the justification for (2).
It'd be -- ironically enough, given the topic -- inconsistent for the judiciary to so hold.
Now, Judge Kozinski might perhaps respond: "Hey, dude, I just enforce the rules, I don't make 'em. The FRCP says you can dismiss a lawsuit in (1), but doesn't say you can do it in (2). I'm not saying that necessarily makes any sense. But that's what it says, so that's what I'm doing. Your beef is with the Supreme Court and Congress if you want the FRCP as a whole to make sense."
That's a plausible response. But it only goes so far. For two reasons.
First, there are lots of procedural rules that we routinely apply that aren't in the FRCP. Judicial estoppel, for one. Tons of others. So I'm not at all sure you can't say that just like you apply those common law rules to authorize dismissal of complaints, a similar common law rule doesn't authorize dismissal in cases where the amended complaint contradicts the original. See, e.g., dismissals based on judicial estoppel. Oh, and, by the way, among the other common law requirements that we impose is the rule that Judge Kozinski applies regarding futility. Look in the entire FRCP. You won't find the word "futility" once. It's a common law gloss on what it means for "justice" to either allow or disallow amendments. It's a judge-made rule. If that's a judge-made rule against inconsistency in proposed amendments, and you're fine with that, it seems like we can be equally fine with a similar judge made rule against inconsistency in actual amendments as well.
Second, we are interpreting words here. Namely, in situation (1), the meaning of the word "futile" (albeit in the context of what that means for a judge-made doctrine). Because if you really thought that parties were allowed to actually file amend pleadings that contradicted their original complaint -- e.g., that a court was not allowed to dismiss such pleadings -- then it wouldn't be "futile" to allow such an amendment, now would it? And yet Reddy says that it is "futile" to allow amendments that would contradict the original pleading. It's "futile" only if that contradictory amendment would be dismissed. Yet PAE says that such a contradictory amendment cannot, in fact, be dismissed.
Doesn't make sense.
Plus, wholly apart from the logical, doctrinal, and policy-based inconsistencies, there's a practical one as well. Which rule applies when?
Judge Kozinski would say that Reddy applies when a court dismisses an original complaint and is "thinking" about a "hypothetical" amended complaint. That's when you can permissibly reject those complaints that would contain contradictory allegations. Whereas, according to Judge Kozinski, when the amended (contradictory) complaint has already been filed, there's nothing you can do about it (or at least, even if you can sanction it, you can't dismiss it).
But what about when -- as in the present case -- there's an existing original complaint and the plaintiff asks permission to file an amended complaint. Hasn't yet. Is asking (as often required by Rule 15) to file it. What rule? Presumably now there's a text (Rule 15) that says that a court can refuse to allow such an amendment, so those things get bounced, right? Yet doesn't it seem totally bizarre to say that an allegation filed on Day 21 (e.g., as a matter of right) goes forward, even though totally belied by the original pleading, and yet that same allegation filed on Day 22 (e.g., when leave of court is required) gets categorically bounced. As well as that an allegation filed on Day 22 can't be bounced if the adverse party has stipulated to it (e.g., no permission is required).
Not that Judge Canby's view doesn't have distinction problems of its own. For example, let's say that the original complaint says that a tort transpired on December 7, 1941 (a date outside the limitations period), but the amended complaint says it instead transpired on December 7, 2014 (which would be inside it). Absent a darn good explanation (e.g., a typo), a consistent view of inconsistency would say that the amended complaint gets bounced because it contradicts the first.
But what if the situation was reversed; e.g., the original complaint says December 7, 2014 but the amended complaint says 1941? Are we really going to say that the guy can't amend his complaint because it contradicts the first? And what's the remedy: Do we bounce the entire dispute, or do we simply let the first complaint go forward? (Assume that the guy here has an absolute right to amend, so permission isn't required, and the second "automatically" displaces the first. Is there dismissal of the second complaint on inconsistency grounds and then that's it? Seems like it. Even though what we'd really want to do, if justice is our goal (and it is), is to go back to the first.)
So here's where I come out:
Judge Kozinski is right that you can ostensibly distinguish the two cases. In the same way that you could distinguish the two cases by saying: "Well, in one case, the plaintiff's name was an acronym, and in the other case, he had an actual spelled-out name." In short, yeah, you could distinguish the two cases, but that distinguishing characteristic would make no sense. It wouldn't create a good or principled rule. The principle that motivates the one set of cases is intellectually inconsistent from the result in the second group of cases."
Which is a bit more like Judge Canby's position.
So, in the end, we have an interesting -- albeit entirely unnecessary (in the context of the present case, anyway) -- dispute.
One that may well matter in a ton of cases. And that we'll eventually have to, or at least should, get right.
Wednesday, September 09, 2015
People v. Mendoza (Cal. Ct. App. - Sept. 2, 2015)
The evidence that Mr. Mendoza molested a kid is fairly overwhelming. So he's convicted of that.
The evidence that he "possessed child pornography," by contrast, is incredibly slim. The mother of the molested child says that she broke into his Facebook account (where images from his cell phone were, she says, automatically backed up) and saw two pictures of him molesting her child, which she says she immediately deleted. But Facebook can't find them anywhere (because deleted images are "forever deleted") and even a detailed forensic examination of Mr. Mendoza's phone and other records can't find any evidence whatsoever that such pictures were ever taken.
But the mother says she saw them, and the Court of Appeal says that alone is sufficient proof beyond a reasonable doubt. A jury can believe a witness if it wants even if we'd expect computer forensics to find deleted images but doesn't.
So Mr. Mendoza gets a total sentence of 67 years to life.
The Court of Appeal's right that you don't need direct evidence of a crime and that credibility questions are for a jury. Mr. Mendoza is right that it's incredibly unusual to be found guilty of child pornography when there are no actual pictures put into evidence, especially when the computer people say there's no physical evidence they were actually ever there either.
But, unfortunately for Mr. Mendoza, given the overwhelming evidence against him on the molestation counts, I'm fairly confident his plight does not create overwhelming sympathy for his legal position in the Court of Appeal. Or anywhere else, for that matter.
The evidence that he "possessed child pornography," by contrast, is incredibly slim. The mother of the molested child says that she broke into his Facebook account (where images from his cell phone were, she says, automatically backed up) and saw two pictures of him molesting her child, which she says she immediately deleted. But Facebook can't find them anywhere (because deleted images are "forever deleted") and even a detailed forensic examination of Mr. Mendoza's phone and other records can't find any evidence whatsoever that such pictures were ever taken.
But the mother says she saw them, and the Court of Appeal says that alone is sufficient proof beyond a reasonable doubt. A jury can believe a witness if it wants even if we'd expect computer forensics to find deleted images but doesn't.
So Mr. Mendoza gets a total sentence of 67 years to life.
The Court of Appeal's right that you don't need direct evidence of a crime and that credibility questions are for a jury. Mr. Mendoza is right that it's incredibly unusual to be found guilty of child pornography when there are no actual pictures put into evidence, especially when the computer people say there's no physical evidence they were actually ever there either.
But, unfortunately for Mr. Mendoza, given the overwhelming evidence against him on the molestation counts, I'm fairly confident his plight does not create overwhelming sympathy for his legal position in the Court of Appeal. Or anywhere else, for that matter.
Tuesday, September 08, 2015
Harkonen v. U.S. Dep't of Justice (9th Cir. - Sept. 8, 2015)
Here's a great example -- both doctrinally as well as normatively -- of how Chevron deference works.
The U.S. Department of Justice issues a press release about Dr. Harkonen. Dr. Harkonen asserts that the press release contains demonstrably false information about him. He finds a statute that says that federal agencies are required to develop effective administrative procedures "allowing affected persons to seek and obtain correction of information maintained and disseminated by the agency." So he asks the DOJ to remove the false information about him, or at least allow him an administrative procedure to try to prove that the stuff is false.
But the DOJ says that its press releases are categorically exempt from the statute because they don't really count as "information . . . disseminated by the agency." So it tells Dr. Harkonen to pound sand.
The Ninth Circuit agrees.
The statute's ambiguous. An agency (OMB) is entrusted with interpreting it. It has done so. While perhaps erroneous, its construction is at least reasonable. End of story.
That's how Chevron deference works. A concise little opinion by Judge Noonan explains it.
The U.S. Department of Justice issues a press release about Dr. Harkonen. Dr. Harkonen asserts that the press release contains demonstrably false information about him. He finds a statute that says that federal agencies are required to develop effective administrative procedures "allowing affected persons to seek and obtain correction of information maintained and disseminated by the agency." So he asks the DOJ to remove the false information about him, or at least allow him an administrative procedure to try to prove that the stuff is false.
But the DOJ says that its press releases are categorically exempt from the statute because they don't really count as "information . . . disseminated by the agency." So it tells Dr. Harkonen to pound sand.
The Ninth Circuit agrees.
The statute's ambiguous. An agency (OMB) is entrusted with interpreting it. It has done so. While perhaps erroneous, its construction is at least reasonable. End of story.
That's how Chevron deference works. A concise little opinion by Judge Noonan explains it.
Friday, September 04, 2015
Mak v. City of Berkeley Rent Stabilization Bd. (Cal. Ct. App. - Sept. 2, 2015)
Jason and Karen Mak own four apartment units in Berkeley. They want to raise the rent, but there's a problem. Their tenant, Elizabeth Burns, has lived in the unit for 28 years. So they want her out and a higher rent.
Not surprisingly, however, Berkeley's rent control ordinance doesn't allow that. So they figure out a workaround. They'll evict her and say that one of the owners (Jason) wants to live there. That's an okay reason to kick her out under the ordinance. So they give her a 60-day notice.
But there's one problem. Once you serve a 60-day notice, and kick the tenant out, you can't then raise the rent (for a period of time, anyway) if the owner does not, in fact, take over the unit.
But the Maks have a workaround for that as well. They strike a deal with the tenant. They'll give her some compensation (e.g., free rent) and she'll agree (1) to vacate the unit, and to (2) deem the 60-day notice withdrawn. Which will mean that, she's she's "voluntarily" left the thing, the Maks can raise the rent to where they want.
Good for everyone.
Except the Court of Appeal sees through this "transparent attempt to circumvent the provisions of local rent control provisions." Affirming the trial court's decision that these machinations don't work and that the rent remains controlled.
That's surely the right rule. But don't think that the Court of Appeal's holding here really solves all that much. It merely slightly moves the statutory inflection point.
All the Maks had to do (in my view) to make this scheme work was to strike a deal with the tenant before the 60-day notice went out. They just show up and say: "We want to kick you out and raise the rent, and you want money/free rent. So -- in the words of Monte Hall -- 'Let's Make a Deal.'"
If that happens, everyone wins. (Except the City and future tenants, of course.) The tenant leaves the apartment "voluntarily" and the rents effectively get raised.
The only thing it requires is slightly more sophisticated planning. Strike the deal before the 60-day notice rather than after.
Same result.
In academia, we all this "regulatory arbitrage". If there's a statute that obtains a certain public benefit, parties can usurp for themselves this benefit by arbitraging the statutory dictates. That strategy works in a number of regulatory settings.
Including here. At least if you're smart about it.
So good job Court of Appeal. Just remember that you haven't actually solved the problem. You've merely moved the strategy up in time a tiny bit.
Not surprisingly, however, Berkeley's rent control ordinance doesn't allow that. So they figure out a workaround. They'll evict her and say that one of the owners (Jason) wants to live there. That's an okay reason to kick her out under the ordinance. So they give her a 60-day notice.
But there's one problem. Once you serve a 60-day notice, and kick the tenant out, you can't then raise the rent (for a period of time, anyway) if the owner does not, in fact, take over the unit.
But the Maks have a workaround for that as well. They strike a deal with the tenant. They'll give her some compensation (e.g., free rent) and she'll agree (1) to vacate the unit, and to (2) deem the 60-day notice withdrawn. Which will mean that, she's she's "voluntarily" left the thing, the Maks can raise the rent to where they want.
Good for everyone.
Except the Court of Appeal sees through this "transparent attempt to circumvent the provisions of local rent control provisions." Affirming the trial court's decision that these machinations don't work and that the rent remains controlled.
That's surely the right rule. But don't think that the Court of Appeal's holding here really solves all that much. It merely slightly moves the statutory inflection point.
All the Maks had to do (in my view) to make this scheme work was to strike a deal with the tenant before the 60-day notice went out. They just show up and say: "We want to kick you out and raise the rent, and you want money/free rent. So -- in the words of Monte Hall -- 'Let's Make a Deal.'"
If that happens, everyone wins. (Except the City and future tenants, of course.) The tenant leaves the apartment "voluntarily" and the rents effectively get raised.
The only thing it requires is slightly more sophisticated planning. Strike the deal before the 60-day notice rather than after.
Same result.
In academia, we all this "regulatory arbitrage". If there's a statute that obtains a certain public benefit, parties can usurp for themselves this benefit by arbitraging the statutory dictates. That strategy works in a number of regulatory settings.
Including here. At least if you're smart about it.
So good job Court of Appeal. Just remember that you haven't actually solved the problem. You've merely moved the strategy up in time a tiny bit.
Thursday, September 03, 2015
National Council of La Raza v. Cegavske (9th Cir. - Sept. 3, 2015)
Is Judge Jones becoming the new Judge Real?
Three civil rights organizations claim that Nevada isn't following the National Voter Registration Act of 1993. That statute creates a private cause of action, and plaintiffs have some pretty good evidence that Nevada isn't, in fact, doing what the statute requires. (For example: Plaintiffs "showed that the number of voter registration applications submitted to Nevada public assistance offices “decreased precipitously”—by 95% from 2001–2002’s high point to 2009–2010’s low point—despite a four-fold increase in the number of food stamp applications during this period. Second, the letter cited U.S. Census Bureau data from 2010, which showed that only 47.6% of low-income Nevadans were registered to vote, compared to 72.4% of high-income Nevadans. Third, the letter presented the results of field investigations Plaintiffs conducted in December 2011, approximately five months before they sent the letter. Plaintiffs’ investigators visited Nevada public assistance offices and surveyed the clients and clerks of thoseo ffices. They discovered that clerks in seven of nine offices they visited provided voter registration application forms only to people who affirmatively requested them. Office staff indicated that this was “standard procedure.” Of the clients surveyed, only one out of the five who affirmatively requested a voter registration application form received one. Two of the nine offices did not have voter registration application forms at all. Only nine out of the 51 clients surveyed received voter registration application forms with their benefits applications or other forms. Only two of nine sites displayed the notifications required by state law.")
So plaintiffs sued. Following, as they were required to do, the various administrative prerequisites to such a lawsuit.
The district court nonetheless dismissed the lawsuit. Virtually sua sponte. Doing so in a series of maneuvers that, at a minimum, are unusual, and -- to some viewers, no doubt -- outright bizarre.
I shan't describe in detail all that transpired in Judge Jones' courtroom. For that, you'll have to read the entire opinion. But, in the end, the Ninth Circuit not only reverses Judge Jones, but assigns the case to a different judge on remand. Saying:
"The reasons for our conclusion are apparent from what we have written above, and we review them only briefly here. The judge sua sponte sought to limit the effectiveness of representation by insisting unreasonably that only two of Plaintiffs’ chosen out-of-state attorneys be given pro hac vice status. [Citation]. The judge did this despite the plea of Plaintiffs’ Nevada lawyer that he needed the expert assistance of out-of-state counsel who specialize in NVRA litigation, and over the objection of one of the would-be out-of-state counsel that the judge’s ruling would prevent depositions from being taken in Nevada by associates in his firm. The judge’s actions came very shortly after the Ninth Circuit had deemed “troubling” his comments regarding out-of-state counsel in another case involving a different Nevada agency. [Citation]. Based on this and other cases, a reasonable observer could conclude that the judge’s feelings against out-of-state attorneys are both well-established and inappropriately strong. See Great Basin Res. Watch v. United States Dep’t of the Interior, No. 3:13-CV- 00078-RCJ, 2014 WL3697107, at *3 (D. Nev. July 23, 2014) (this same judge expressly stated he would “presume[] that the out-of-state lawyers are unwilling to obey the ethical strictures that govern all other attorneys”). Further, the judge sua sponte and without notice dismissed Plaintiffs’ case based on a motion the State had previously withdrawn, pursuant to a joint stipulation by the parties. Still further, the judge misread the complaint when he concluded that Plaintiffs had failed to allege that they had changed their behavior and had thus suffered no injury, when Plaintiffs had alleged that they had expended additional resources on voter registration as a result of the State’s violation of Section 7. Finally, the judge dismissed the complaint without leave to amend despite Plaintiffs’ explicit request that they be allowed to amend their complaint if the judge found its allegations insufficient."
That's a pretty telling indictment of the district court's conduct. As is the assignment to a different judge.
And it's not the first time, either.
Maybe it's just Judge Jones' distaste for out-of-state lawyers that's the problem. Or maybe there's a larger problem here as well.
But today's opinion suggests, at a minimum, that there's a problem.
One that hasn't -- and likely won't -- go away.
Three civil rights organizations claim that Nevada isn't following the National Voter Registration Act of 1993. That statute creates a private cause of action, and plaintiffs have some pretty good evidence that Nevada isn't, in fact, doing what the statute requires. (For example: Plaintiffs "showed that the number of voter registration applications submitted to Nevada public assistance offices “decreased precipitously”—by 95% from 2001–2002’s high point to 2009–2010’s low point—despite a four-fold increase in the number of food stamp applications during this period. Second, the letter cited U.S. Census Bureau data from 2010, which showed that only 47.6% of low-income Nevadans were registered to vote, compared to 72.4% of high-income Nevadans. Third, the letter presented the results of field investigations Plaintiffs conducted in December 2011, approximately five months before they sent the letter. Plaintiffs’ investigators visited Nevada public assistance offices and surveyed the clients and clerks of thoseo ffices. They discovered that clerks in seven of nine offices they visited provided voter registration application forms only to people who affirmatively requested them. Office staff indicated that this was “standard procedure.” Of the clients surveyed, only one out of the five who affirmatively requested a voter registration application form received one. Two of the nine offices did not have voter registration application forms at all. Only nine out of the 51 clients surveyed received voter registration application forms with their benefits applications or other forms. Only two of nine sites displayed the notifications required by state law.")
So plaintiffs sued. Following, as they were required to do, the various administrative prerequisites to such a lawsuit.
The district court nonetheless dismissed the lawsuit. Virtually sua sponte. Doing so in a series of maneuvers that, at a minimum, are unusual, and -- to some viewers, no doubt -- outright bizarre.
I shan't describe in detail all that transpired in Judge Jones' courtroom. For that, you'll have to read the entire opinion. But, in the end, the Ninth Circuit not only reverses Judge Jones, but assigns the case to a different judge on remand. Saying:
"The reasons for our conclusion are apparent from what we have written above, and we review them only briefly here. The judge sua sponte sought to limit the effectiveness of representation by insisting unreasonably that only two of Plaintiffs’ chosen out-of-state attorneys be given pro hac vice status. [Citation]. The judge did this despite the plea of Plaintiffs’ Nevada lawyer that he needed the expert assistance of out-of-state counsel who specialize in NVRA litigation, and over the objection of one of the would-be out-of-state counsel that the judge’s ruling would prevent depositions from being taken in Nevada by associates in his firm. The judge’s actions came very shortly after the Ninth Circuit had deemed “troubling” his comments regarding out-of-state counsel in another case involving a different Nevada agency. [Citation]. Based on this and other cases, a reasonable observer could conclude that the judge’s feelings against out-of-state attorneys are both well-established and inappropriately strong. See Great Basin Res. Watch v. United States Dep’t of the Interior, No. 3:13-CV- 00078-RCJ, 2014 WL3697107, at *3 (D. Nev. July 23, 2014) (this same judge expressly stated he would “presume[] that the out-of-state lawyers are unwilling to obey the ethical strictures that govern all other attorneys”). Further, the judge sua sponte and without notice dismissed Plaintiffs’ case based on a motion the State had previously withdrawn, pursuant to a joint stipulation by the parties. Still further, the judge misread the complaint when he concluded that Plaintiffs had failed to allege that they had changed their behavior and had thus suffered no injury, when Plaintiffs had alleged that they had expended additional resources on voter registration as a result of the State’s violation of Section 7. Finally, the judge dismissed the complaint without leave to amend despite Plaintiffs’ explicit request that they be allowed to amend their complaint if the judge found its allegations insufficient."
That's a pretty telling indictment of the district court's conduct. As is the assignment to a different judge.
And it's not the first time, either.
Maybe it's just Judge Jones' distaste for out-of-state lawyers that's the problem. Or maybe there's a larger problem here as well.
But today's opinion suggests, at a minimum, that there's a problem.
One that hasn't -- and likely won't -- go away.
Wednesday, September 02, 2015
Sequeira v. Lincoln National Life Ins. Co. (Cal. Ct. App. - Sept. 1, 2015)
There are plenty of people in this world who hate insurance companies. Absolutely hate 'em. Think they're abusive, sleazy, money-grubbing bastards.
I'm not one of those people. As a whole, I think the industry's no worse -- and no better -- than other business lines. Sure, companies want to constrain costs, so aren't looking to pay out money to others when they can avoid it. But that's true for pretty much everyone.
Admittedly, insurance companies often deal with people in vulnerable situations; their spouse has just died, they're in the hospital, etc. So we might want to them to be a bit more compassionate than your average business. But I'm not in the "Insurers Are Evil" camp. Far from it.
Except for here.
In my view, what the Lincoln National Life Insurance Company did here is classic example of why many people absolutely hate insurance companies. Because their decision here was intolerable and unacceptable.
Donald Sequeira was a long-time employee with the City of Vacaville. In the fall of 2009, the City changed its life insurance carrier to Lincoln National. So in October 2009, Mr. Sequeria filled out an enrollment form for $275,000 of basic life insurance and submitted it to Lincoln National. Lincoln National accepted the application and issued the policy. Moreover, during 2009, Mr. Sequeria made two premium payments on the policy, and Lincoln National happily cashed his checks.
Then 2010 arrives. January 1, 2010 was a holiday, so Mr. Sequeria didn't work that day. The next day, January 2, 2010, he suddenly became ill, and died on January 6, without ever returning to work.
That's sad. He leaves a widow, so the widow then seeks the $275,000 from the insurance policy that Mr. Sequeria purchased.
At which point Lincoln National tells her to go to hell.
It's not that Mr. Sequeria lied, or that his checks bounced, or anything like that. And it's not even that there's a ton of money at stake.
But in language only a lawyer could love, with multiple subclauses and optional ("the latest of") dates, the policy technically says that Mr. Sequeria was only covered on the day he "resume[d] Active Work, if you are not Actively at Work on the day you become eligible." And, in 2010, since Mr. Sequeria didn't work on January 1 -- since it was a holiday -- and didn't work on January 2 (since that's the day he became sick), and died promptly thereafter, ha! No money. The fact that the guy had worked two decades for the same company, was an active employee throughout the entire period, had paid multiple premiums for the policy, and didn't work in 2010 because the company wasn't open and then he was sick doesn't matter at all to Lincoln National. They've got an excuse not to pay his widow the money she's due -- or at least they've got an argument not to pay -- so she's going to either get stiffed or have to pay a lawyer, and wait, and hope the courts decide her way in order get paid. Oh, yeah, and in the meantime, she has to bury her dead husband.
Ultimately the Court of Appeal reverses the trial court and orders Lincoln National to pay. Despite its hypertechnical argument -- which the trial court bought -- that ostensibly excused it from paying the proceeds of the insurance policy to the grieving widow.
So, ultimately, Mrs. Sequeria gets paid the money to which she's entitled.
But here's the thing. She shouldn't have been forced to wait six years. She shouldn't have had to fight an insurance company. She shouldn't have been forced to pay a lawyer a healthy portion of the insurance proceeds at issue.
Lincoln National should have simply paid the $275,000. It's a tiny amount of money, in the scheme of things, to the insurer. It's for a long term employee who got sick on January 2, 2010, and died on January 6, 2010, for a life insurance policy designed to cover him in 2010. Only the most heartless and/or ruthless insurer would try to screw a widow out of the life insurance for which she paid in a context like this one.
But that's nonetheless the course that Lincoln National elected. From the claims adjuster at the bottom to the highest levels at Lincoln National at which this case was reviewed.
Okay. Fine. You can do that.
But when people hate you, and others like you, don't be surprised. At all.
And they'll have a point.
I'm not one of those people. As a whole, I think the industry's no worse -- and no better -- than other business lines. Sure, companies want to constrain costs, so aren't looking to pay out money to others when they can avoid it. But that's true for pretty much everyone.
Admittedly, insurance companies often deal with people in vulnerable situations; their spouse has just died, they're in the hospital, etc. So we might want to them to be a bit more compassionate than your average business. But I'm not in the "Insurers Are Evil" camp. Far from it.
Except for here.
In my view, what the Lincoln National Life Insurance Company did here is classic example of why many people absolutely hate insurance companies. Because their decision here was intolerable and unacceptable.
Donald Sequeira was a long-time employee with the City of Vacaville. In the fall of 2009, the City changed its life insurance carrier to Lincoln National. So in October 2009, Mr. Sequeria filled out an enrollment form for $275,000 of basic life insurance and submitted it to Lincoln National. Lincoln National accepted the application and issued the policy. Moreover, during 2009, Mr. Sequeria made two premium payments on the policy, and Lincoln National happily cashed his checks.
Then 2010 arrives. January 1, 2010 was a holiday, so Mr. Sequeria didn't work that day. The next day, January 2, 2010, he suddenly became ill, and died on January 6, without ever returning to work.
That's sad. He leaves a widow, so the widow then seeks the $275,000 from the insurance policy that Mr. Sequeria purchased.
At which point Lincoln National tells her to go to hell.
It's not that Mr. Sequeria lied, or that his checks bounced, or anything like that. And it's not even that there's a ton of money at stake.
But in language only a lawyer could love, with multiple subclauses and optional ("the latest of") dates, the policy technically says that Mr. Sequeria was only covered on the day he "resume[d] Active Work, if you are not Actively at Work on the day you become eligible." And, in 2010, since Mr. Sequeria didn't work on January 1 -- since it was a holiday -- and didn't work on January 2 (since that's the day he became sick), and died promptly thereafter, ha! No money. The fact that the guy had worked two decades for the same company, was an active employee throughout the entire period, had paid multiple premiums for the policy, and didn't work in 2010 because the company wasn't open and then he was sick doesn't matter at all to Lincoln National. They've got an excuse not to pay his widow the money she's due -- or at least they've got an argument not to pay -- so she's going to either get stiffed or have to pay a lawyer, and wait, and hope the courts decide her way in order get paid. Oh, yeah, and in the meantime, she has to bury her dead husband.
Ultimately the Court of Appeal reverses the trial court and orders Lincoln National to pay. Despite its hypertechnical argument -- which the trial court bought -- that ostensibly excused it from paying the proceeds of the insurance policy to the grieving widow.
So, ultimately, Mrs. Sequeria gets paid the money to which she's entitled.
But here's the thing. She shouldn't have been forced to wait six years. She shouldn't have had to fight an insurance company. She shouldn't have been forced to pay a lawyer a healthy portion of the insurance proceeds at issue.
Lincoln National should have simply paid the $275,000. It's a tiny amount of money, in the scheme of things, to the insurer. It's for a long term employee who got sick on January 2, 2010, and died on January 6, 2010, for a life insurance policy designed to cover him in 2010. Only the most heartless and/or ruthless insurer would try to screw a widow out of the life insurance for which she paid in a context like this one.
But that's nonetheless the course that Lincoln National elected. From the claims adjuster at the bottom to the highest levels at Lincoln National at which this case was reviewed.
Okay. Fine. You can do that.
But when people hate you, and others like you, don't be surprised. At all.
And they'll have a point.
People v. Vasquez (Cal. Ct. App. - Aug. 31, 2015)
Who needs me when you have Justice Gilbert, who write the following as the first two sentences of this opinion:
"The new owner of a house prepares to move in. She transfers utilities to
her name, installs locks, leaves personal items in the house, paints an interior wall of the
garage, and comes and goes during daytime hours narrowly missing defendant's two
intrusions. Here we hold these facts are sufficient to establish her house is an inhabited
dwelling for purposes of first degree burglary."
Pretty darn informative, eh? Concise, too.
Tuesday, September 01, 2015
Michaels v. Turk (Cal. Ct. App. - Aug. 31, 2015)
I can tell you why the Court of Appeal decided to publish this opinion. Indeed, I'll be blunt about the Court of Appeal's intended message:
"Trial courts: PUT THE STIPULATION TO A COMMISSIONER ON THE RECORD. We don't care that pretty much every family law case is, in fact, resolved by a commissioner, and that pretty much every single litigant is practically forced to stipulate thereto. We also don't care that in both Riverside County and pretty much everywhere else, there are signs everywhere that say that your case will be heard by a commissioner unless you object. YOU'VE GOT TO PUT IT ON THE RECORD. Or else we're required to reverse."
Sage counsel. Worthy of publication, even.
"Trial courts: PUT THE STIPULATION TO A COMMISSIONER ON THE RECORD. We don't care that pretty much every family law case is, in fact, resolved by a commissioner, and that pretty much every single litigant is practically forced to stipulate thereto. We also don't care that in both Riverside County and pretty much everywhere else, there are signs everywhere that say that your case will be heard by a commissioner unless you object. YOU'VE GOT TO PUT IT ON THE RECORD. Or else we're required to reverse."
Sage counsel. Worthy of publication, even.
Monday, August 31, 2015
Creech v. Frauenheim (9th Cir. - Aug. 31, 2015)
It's a state habeas case, with all the usual deference regalia. Judge Paez agrees that the petition should be dismissed, and his opinion makes sense. The guy clearly did stuff he shouldn't have done, and his Apprendi challenge to California's low-mid-high sentencing scheme faces a serious uphill battle.
I mention the case only because I wanted to get your take on his offenses.
Here's what the guy did:
"Creech and his wife, Reanna, have a four-year-old daughter, Sofia, and a three-year-old son, Zachary. 2 One evening in September 2007, Creech and Reanna had an argument because Creech told Reanna he had obtained a shotgun. Reanna decided to leave him that night. A few weeks later, she took the kids to her father’s house in Napa. Several days later, Creech and Reanna spoke on the phone. She told him the kids were at her father’s and suggested that they talk another time to arrange for Creech to see them.
Later that night, Creech went to Reanna’s father’s house and asked him if he could see the children. Creech’s fatherin-law said “no.” When Reanna returned to her father’s home later that night, she saw Creech waiting there and drove away. He followed her. A highway patrol officer stopped Reanna for “driving 15 miles an hour in a 45.” Reanna, who had been crying, explained to the officer the circumstances with Creech and their kids. At the time she was pulled over, Reanna was on the phone with the sheriff’s department. Creech had contacted the police department and explained that he was trying to get in contact with his children, and that he had been “threatened off [his father-in-law’s] property.” The patrol officer told Reanna that, because Creech was the only custodial parent at her father’s house, she had to go back to her father’s, otherwise Creech would be allowed to take the children. Reanna decided to return to her father’s house.
Creech testified at trial that he was angry with his fatherin-law for not allowing him to see his children. So, he decided to return the following morning to shoot at and damage his house. He grabbed bird shot ammunition because “shooting through things. . . wasn’t [his] intent.”
Late that morning, Reanna, who was at her father’s house, heard a “solid thud.” She looked outside and saw Creech holding a shotgun about fifteen to twenty feet away from the house. Reanna shouted to her stepsister, Jennifer Curry, to grab Sofia. Jennifer saw glass flying everywhere. Jennifer also looked out of a window and saw Creech standing about fifteen to thirty feet away, aiming his shotgun and tracking her and Sofia with the barrel of the gun. Reanna grabbed Zachary and went to the downstairs bathroom, and Jennifer and Sofia joined them. Juliane Rush, Reanna’s stepmother, heard a “very loud pop” from the front of the house. She saw Creech standing about fifteen feet away from the front door. . . .
Officers arrived at the Napa house minutes after the shooting, but Creech had left. They found three shells in front of the house. There were many very small perforations in the front door, and the outer pane of the double-paned window in the upper portion of the door was broken. Both layers of a double-paned window in the study were also broken. . . .
A forensic expert, Dr. John Thornton testified at trial. Among other tests, he performed ballistic gelatin testing “to mimic the behavior expected from human flesh . . . if a human body was shot with that projectile.” He performed these tests “without glass at a distance of 45 feet . . . [his] best approximation of the distance between the cluster of shotgun shells in front of the door and the door.” From this test, he opined that “there would be a minimum of an inch and a half of penetration into flesh.” With dual-paned glass, no pellets permeated the gel from 45 feet. Dr. Thornton did not perform tests at any other distance.
In addition to the gelatin testing results, Dr. Thornton also stated other opinions based on the location of the shell casings and particle dispersion. First, he opined that the shots to the door were fired from between forty and fifty feet away, while the shot to the window was fired from twenty feet away. Second, he opined that there were lead pellets in the debris collected from the study. Third, he explained that the bullet 'we’re speaking of is on the small side. It’s intended for small birds.'"
To be clear: It is not cool to shoot at an occupied house. Not cool at all. Even if you're only firing birdshot. Even if you're just pissed off. (And even if, as here, "[a]fter the shooting, he went to his parents’ house, ingested a bottle of pills, and was taken to the hospital." That shows some regret, at least. But still doesn't excuse your conduct. In the slightest.)
Okay. So we're all on board that this guy should be punished. The case is in California state court. He illegally discharged a firearm, he shot at an inhabited dwelling, what he did qualifies as assault (even if he didn't actually intend to hit anyone with the birdshot), and it might even qualify as conduct that endangers the welfare of a child since there was a little kid in the house. All that I get.
So what's the appropriate sentence?
Different people may well have different takes on this. But I must admit that I was surprised -- very surprised -- to see that the guy got thirty one years in prison for the thing. Perhaps I wouldn't have been shocked to see him get a decade in the joint. Though I wouldn't have been surprised to see him get three or four years either. But thirty one years? Wow.
Maybe I just have failed to abandon all hope in concepts like rehabilitation and the like, whereas the state has elected to entirely jettison the concept. But the idea that a person who -- incredibly stupidly and wrongly -- fires some birdshot at a house in an irrational rage is essentially irredeemable, and thus much spend essentially the remainder of his life in prison, conflicts with my gut intuition.
Maybe there was more here I don't know about. Maybe there was a lot more stuff that the opinion leaves out (though I doubt it).
All I can say is that I was very surprised when I got to that portion of the opinion that mentioned that he was sentenced to thirty one years in prison.
I mention the case only because I wanted to get your take on his offenses.
Here's what the guy did:
"Creech and his wife, Reanna, have a four-year-old daughter, Sofia, and a three-year-old son, Zachary. 2 One evening in September 2007, Creech and Reanna had an argument because Creech told Reanna he had obtained a shotgun. Reanna decided to leave him that night. A few weeks later, she took the kids to her father’s house in Napa. Several days later, Creech and Reanna spoke on the phone. She told him the kids were at her father’s and suggested that they talk another time to arrange for Creech to see them.
Later that night, Creech went to Reanna’s father’s house and asked him if he could see the children. Creech’s fatherin-law said “no.” When Reanna returned to her father’s home later that night, she saw Creech waiting there and drove away. He followed her. A highway patrol officer stopped Reanna for “driving 15 miles an hour in a 45.” Reanna, who had been crying, explained to the officer the circumstances with Creech and their kids. At the time she was pulled over, Reanna was on the phone with the sheriff’s department. Creech had contacted the police department and explained that he was trying to get in contact with his children, and that he had been “threatened off [his father-in-law’s] property.” The patrol officer told Reanna that, because Creech was the only custodial parent at her father’s house, she had to go back to her father’s, otherwise Creech would be allowed to take the children. Reanna decided to return to her father’s house.
Creech testified at trial that he was angry with his fatherin-law for not allowing him to see his children. So, he decided to return the following morning to shoot at and damage his house. He grabbed bird shot ammunition because “shooting through things. . . wasn’t [his] intent.”
Late that morning, Reanna, who was at her father’s house, heard a “solid thud.” She looked outside and saw Creech holding a shotgun about fifteen to twenty feet away from the house. Reanna shouted to her stepsister, Jennifer Curry, to grab Sofia. Jennifer saw glass flying everywhere. Jennifer also looked out of a window and saw Creech standing about fifteen to thirty feet away, aiming his shotgun and tracking her and Sofia with the barrel of the gun. Reanna grabbed Zachary and went to the downstairs bathroom, and Jennifer and Sofia joined them. Juliane Rush, Reanna’s stepmother, heard a “very loud pop” from the front of the house. She saw Creech standing about fifteen feet away from the front door. . . .
Officers arrived at the Napa house minutes after the shooting, but Creech had left. They found three shells in front of the house. There were many very small perforations in the front door, and the outer pane of the double-paned window in the upper portion of the door was broken. Both layers of a double-paned window in the study were also broken. . . .
A forensic expert, Dr. John Thornton testified at trial. Among other tests, he performed ballistic gelatin testing “to mimic the behavior expected from human flesh . . . if a human body was shot with that projectile.” He performed these tests “without glass at a distance of 45 feet . . . [his] best approximation of the distance between the cluster of shotgun shells in front of the door and the door.” From this test, he opined that “there would be a minimum of an inch and a half of penetration into flesh.” With dual-paned glass, no pellets permeated the gel from 45 feet. Dr. Thornton did not perform tests at any other distance.
In addition to the gelatin testing results, Dr. Thornton also stated other opinions based on the location of the shell casings and particle dispersion. First, he opined that the shots to the door were fired from between forty and fifty feet away, while the shot to the window was fired from twenty feet away. Second, he opined that there were lead pellets in the debris collected from the study. Third, he explained that the bullet 'we’re speaking of is on the small side. It’s intended for small birds.'"
To be clear: It is not cool to shoot at an occupied house. Not cool at all. Even if you're only firing birdshot. Even if you're just pissed off. (And even if, as here, "[a]fter the shooting, he went to his parents’ house, ingested a bottle of pills, and was taken to the hospital." That shows some regret, at least. But still doesn't excuse your conduct. In the slightest.)
Okay. So we're all on board that this guy should be punished. The case is in California state court. He illegally discharged a firearm, he shot at an inhabited dwelling, what he did qualifies as assault (even if he didn't actually intend to hit anyone with the birdshot), and it might even qualify as conduct that endangers the welfare of a child since there was a little kid in the house. All that I get.
So what's the appropriate sentence?
Different people may well have different takes on this. But I must admit that I was surprised -- very surprised -- to see that the guy got thirty one years in prison for the thing. Perhaps I wouldn't have been shocked to see him get a decade in the joint. Though I wouldn't have been surprised to see him get three or four years either. But thirty one years? Wow.
Maybe I just have failed to abandon all hope in concepts like rehabilitation and the like, whereas the state has elected to entirely jettison the concept. But the idea that a person who -- incredibly stupidly and wrongly -- fires some birdshot at a house in an irrational rage is essentially irredeemable, and thus much spend essentially the remainder of his life in prison, conflicts with my gut intuition.
Maybe there was more here I don't know about. Maybe there was a lot more stuff that the opinion leaves out (though I doubt it).
All I can say is that I was very surprised when I got to that portion of the opinion that mentioned that he was sentenced to thirty one years in prison.
U.S. v. Katakis (9th Cir. - Aug. 31, 2015)
Feel free to hit the "delete" button on your incriminating Microsoft Exchange e-mails. Even if you do so with the intent of keeping those e-mails from the Feds, the Ninth Circuit says that doesn't count as obstruction of justice. Because you haven't "concealed" them; you've simply moved them from one folder (e.g., your inbox) to another (e.g., the "deleted items" folder). That's no different from, say, moving an incriminating document from the top of you desk to a desk drawer.
You may not be entirely off the hook, however. The Ninth Circuit doesn't decide whether hitting the delete button (or moving the e-mails to the "deleted items" folder, which is the same thing) counts as attempted obstruction of justice. The Ninth Circuit similarly doesn't decide whether "double deleting" e-mails -- i.e., moving them to the "deleted items" folder and then "emptying" that folder -- counts as obstruction of justice. So you've still got look out for that.
But if all you do is to move files into the deleted items folder, that ain't going to subject you to non-attempt liability. Mind you: It won't stop those e-mails from being discovered by the government either, since it'll perhaps not shock you to discover that they actually check that folder (and more!) once they seize your computer.
But if all you do is hit the delete button, even with an evil intent, your malicious incompetence may well not count as a substantive federal offense.
Good to know.
You may not be entirely off the hook, however. The Ninth Circuit doesn't decide whether hitting the delete button (or moving the e-mails to the "deleted items" folder, which is the same thing) counts as attempted obstruction of justice. The Ninth Circuit similarly doesn't decide whether "double deleting" e-mails -- i.e., moving them to the "deleted items" folder and then "emptying" that folder -- counts as obstruction of justice. So you've still got look out for that.
But if all you do is to move files into the deleted items folder, that ain't going to subject you to non-attempt liability. Mind you: It won't stop those e-mails from being discovered by the government either, since it'll perhaps not shock you to discover that they actually check that folder (and more!) once they seize your computer.
But if all you do is hit the delete button, even with an evil intent, your malicious incompetence may well not count as a substantive federal offense.
Good to know.
Thursday, August 27, 2015
People v. Romero & Self (Cal. Supreme Court - Aug. 26, 2015)
Sometimes you read these death penalty cases and wonder what it was that led the jury to invoke the death penalty.
Not here.
Just read the first nine pages of the opinion, which recounts the various crimes that the defendants committed during two months in 1992, alongside their subsequent escape attempts from prison in 1994.
Wow. It'd be hard to find a (death-qualified) jury that would not sentence these two to death.
A third defendant is equally culpable. But he testified against the other two. So only gets 51 to life pursuant to a plea deal. Including eligibility for parole. And gets to serve his sentence out of state.
It's good to be the one who flips.
Not here.
Just read the first nine pages of the opinion, which recounts the various crimes that the defendants committed during two months in 1992, alongside their subsequent escape attempts from prison in 1994.
Wow. It'd be hard to find a (death-qualified) jury that would not sentence these two to death.
A third defendant is equally culpable. But he testified against the other two. So only gets 51 to life pursuant to a plea deal. Including eligibility for parole. And gets to serve his sentence out of state.
It's good to be the one who flips.
Wednesday, August 26, 2015
Sternberg v. California State Board of Pharmacy (Cal. Ct. App. - Aug. 26, 2015)
It at first seemed a little harsh to me that the California State Board of Pharmacy revoked Andrew Sternberg's pharmacy license just because he was the pharmacist in charge when someone else stole some drugs from the office. Seemed harsh to the administrative law judge as well, who recommended merely that Mr. Sternberg be publicly reproved.
But, reading on, I then noticed that the Board stayed this revocation, and merely put Mr. Sternberg on probation for three years. Probation: That seems more reasonable.
Still. The guy's being punished for someone else's theft. How's that fair?
But then I read more about the facts. This wasn't just a tiny little theft, or of some insubstantial little drug. "During a two-year period while he supervised the Target pharmacy—September 1, 2006, to August 31, 2008—Imelda Hurtado, a pharmacy technician, stole at least 216,630 tablets of Norco1 from the pharmacy, with an estimated retail value of up to $1.50 per tablet, or $324,945, and street value of up to $5 per tablet, or $1,083,150."
Dude. That's a lot of Norcol. That's a lot of theft. We might well want the supervisor to, well, supervise a little more in order to prevent these drugs from hitting the street.
Then I read more. About precisely how the theft was accomplished. Which, in a way, was a neat little roadmap about how to steal drugs from a pharmacy. But also highlighted the kinds of things that Mr. Sternberg did -- or, more accurately, failed to do -- to prevent such a theft:
Hurtado accomplished this theft as follows: She would place orders for up to 3,000 tablets (six bottles with 500 tablets per bottle) to be delivered to the pharmacy on a day she was scheduled to work. She did this approximately 85 times, as often as three times a week. When orders arrived, she would take the delivery to a work station farthest away from the pharmacist’s station. She would then remove the six bottles, hide them in the store room, and destroy the packing invoice. When the pharmacist on duty took a lunch break, she would go to the store room, put three bottles in her purse, and take them out to her car. Later in the day, when the pharmacist was on a break, she would take the other three bottles to her car in the same manner. Her theft was discovered when Sternberg found a bottle of Norco in the store room. The Target pharmacy normally did not sell Norco . . . .
The wholesaler (‘supplier’) typically delivered the drug orders to the pharmacy between 12:30 p.m. and 1:00 p.m. Section 4059.5 of the Pharmacy Law requires that a pharmacist sign for and receive all dangerous drugs or devices delivered to a pharmacy. [Sternberg] testified that his policy was that ‘everybody that works in the pharmacy knows that the law prevents anybody from signing for deliveries, except a pharmacist.’ [Sternberg] did not explain how he would enforce that policy, nor was there any evidence presented as to how that would be implemented. With respect to receipt of drug deliveries, when [Sternberg] signed for the delivery of dangerous drugs he would sign a ‘delivery log that is supplied by the supplier’; however, that log only disclosed how many containers were being delivered, not what was in the actual containers. He would then count the number of bottles, and give the tote to a pharmacy technician who he assigned to take care of unpacking the drugs, placing appropriate shelf labels on the bottles, and checking the invoice/packing slip inside the box to assure that the supplier delivered what was ordered. After [Sternberg] signed for the drugs, he ‘never’ looked at the invoices being taken out of the delivery container and did not check the invoices against the drugs he received. [Sternberg] admitted that as the Pharmacist-in-Charge he had the ‘discretion’ to examine the invoices, but chose not to do so. The invoices he received were given to a pharmacy technician, who then placed them in a box under a counter. After the box was filled, it was then transferred to a ‘little storage area’ in the pharmacy. The box was not checked regularly by any pharmacists, but ‘occasionally’ [Sternberg] or another pharmacist would look at those invoices, but only ‘for a specific drug that we had to order for somebody to see if it came in or if it didn’t come in.’ As a result, the missing inventory and invoices were only discovered by chance, and not for at least 18 months."
Wow. I think we can all agree that this falls far short from "best practices" at a pharmacy.
So, in the end, I can see why Mr. Sternberg received the discipline he did. If not more.
But, reading on, I then noticed that the Board stayed this revocation, and merely put Mr. Sternberg on probation for three years. Probation: That seems more reasonable.
Still. The guy's being punished for someone else's theft. How's that fair?
But then I read more about the facts. This wasn't just a tiny little theft, or of some insubstantial little drug. "During a two-year period while he supervised the Target pharmacy—September 1, 2006, to August 31, 2008—Imelda Hurtado, a pharmacy technician, stole at least 216,630 tablets of Norco1 from the pharmacy, with an estimated retail value of up to $1.50 per tablet, or $324,945, and street value of up to $5 per tablet, or $1,083,150."
Dude. That's a lot of Norcol. That's a lot of theft. We might well want the supervisor to, well, supervise a little more in order to prevent these drugs from hitting the street.
Then I read more. About precisely how the theft was accomplished. Which, in a way, was a neat little roadmap about how to steal drugs from a pharmacy. But also highlighted the kinds of things that Mr. Sternberg did -- or, more accurately, failed to do -- to prevent such a theft:
Hurtado accomplished this theft as follows: She would place orders for up to 3,000 tablets (six bottles with 500 tablets per bottle) to be delivered to the pharmacy on a day she was scheduled to work. She did this approximately 85 times, as often as three times a week. When orders arrived, she would take the delivery to a work station farthest away from the pharmacist’s station. She would then remove the six bottles, hide them in the store room, and destroy the packing invoice. When the pharmacist on duty took a lunch break, she would go to the store room, put three bottles in her purse, and take them out to her car. Later in the day, when the pharmacist was on a break, she would take the other three bottles to her car in the same manner. Her theft was discovered when Sternberg found a bottle of Norco in the store room. The Target pharmacy normally did not sell Norco . . . .
The wholesaler (‘supplier’) typically delivered the drug orders to the pharmacy between 12:30 p.m. and 1:00 p.m. Section 4059.5 of the Pharmacy Law requires that a pharmacist sign for and receive all dangerous drugs or devices delivered to a pharmacy. [Sternberg] testified that his policy was that ‘everybody that works in the pharmacy knows that the law prevents anybody from signing for deliveries, except a pharmacist.’ [Sternberg] did not explain how he would enforce that policy, nor was there any evidence presented as to how that would be implemented. With respect to receipt of drug deliveries, when [Sternberg] signed for the delivery of dangerous drugs he would sign a ‘delivery log that is supplied by the supplier’; however, that log only disclosed how many containers were being delivered, not what was in the actual containers. He would then count the number of bottles, and give the tote to a pharmacy technician who he assigned to take care of unpacking the drugs, placing appropriate shelf labels on the bottles, and checking the invoice/packing slip inside the box to assure that the supplier delivered what was ordered. After [Sternberg] signed for the drugs, he ‘never’ looked at the invoices being taken out of the delivery container and did not check the invoices against the drugs he received. [Sternberg] admitted that as the Pharmacist-in-Charge he had the ‘discretion’ to examine the invoices, but chose not to do so. The invoices he received were given to a pharmacy technician, who then placed them in a box under a counter. After the box was filled, it was then transferred to a ‘little storage area’ in the pharmacy. The box was not checked regularly by any pharmacists, but ‘occasionally’ [Sternberg] or another pharmacist would look at those invoices, but only ‘for a specific drug that we had to order for somebody to see if it came in or if it didn’t come in.’ As a result, the missing inventory and invoices were only discovered by chance, and not for at least 18 months."
Wow. I think we can all agree that this falls far short from "best practices" at a pharmacy.
So, in the end, I can see why Mr. Sternberg received the discipline he did. If not more.
People v. Toloy (Cal. Ct. App. - Aug. 26, 2015)
Section 290 of the Penal Code requires that when certain people (e.g., sex offenders) are released from jail after serving a sentence of 30 days or more, these people must register their new (post-release) address with the local police department within five working days of their release.
You'd think those statutes are very closely related, right?
But the Court of Appeal holds that the latter statute is "directory, not mandatory". In non-legalese, that means that even if (as here) the warden is required to -- but fails -- to inform the prisoner of his registration obligations, in violation of Section 290.017(a), that person can still be convicted of violating those registration obligations. Even if, as a result of that express statutory directive, the person didn't know about those obligations.
POSTSCRIPT - There may be some dispute about what "not knowing" about these obligations means. The Court of Appeal quoted a prior California Supreme Court case that said that "[A] violation of section 290 requires actual knowledge of the duty to register. A jury may infer knowledge from notice, but notice alone does not necessarily satisfy the willfulness requirement.” So you might take that to mean that actual notice of the statute is required, but that as long as you have knowledge of the statute -- whether from a prior notice, or independent reading of casebooks, or whatever -- it doesn't matter that the mandatory notice under Section 290.017(a) was provided. But, then again, defendant here admitted that "he had initialed a form informing him of that obligation when he reregistered in January 2014, but he maintained that he believed it applied only if he was a transient," and the Court of Appeal didn't seem to think that was a defense, so one might view that as taking a more limited view as to what constitutes sufficient "actual knowledge" to justify a conviction. Maybe defendant was not credible, or maybe that's just not a defense to "actual knowledge". But either way, it's surely better to give the required, mandatory warnings under Section 290.017(a) -- and to say that "actual knowledge" does all the work here is not as clear in this context as it might be in some others.
POSTSCRIPT - There may be some dispute about what "not knowing" about these obligations means. The Court of Appeal quoted a prior California Supreme Court case that said that "[A] violation of section 290 requires actual knowledge of the duty to register. A jury may infer knowledge from notice, but notice alone does not necessarily satisfy the willfulness requirement.” So you might take that to mean that actual notice of the statute is required, but that as long as you have knowledge of the statute -- whether from a prior notice, or independent reading of casebooks, or whatever -- it doesn't matter that the mandatory notice under Section 290.017(a) was provided. But, then again, defendant here admitted that "he had initialed a form informing him of that obligation when he reregistered in January 2014, but he maintained that he believed it applied only if he was a transient," and the Court of Appeal didn't seem to think that was a defense, so one might view that as taking a more limited view as to what constitutes sufficient "actual knowledge" to justify a conviction. Maybe defendant was not credible, or maybe that's just not a defense to "actual knowledge". But either way, it's surely better to give the required, mandatory warnings under Section 290.017(a) -- and to say that "actual knowledge" does all the work here is not as clear in this context as it might be in some others.
Tuesday, August 25, 2015
U.S. v. Sanchez-Gomez (9th Cir. - Aug. 25, 2015)
San Diego is not Los Angeles.
So holds the Ninth Circuit.
Okay, so it's a bit more complicated than that. But that's essentially what the Ninth Circuit holds.
Sure, in 2007, the Ninth Circuit held that the Central District of California could validly shackle all pretrial detainees appearing before a magistrate, without any particularized showing of good cause (e.g., that the particular detainee might be a threat). But the Ninth Circuit says that holding doesn't necessarily mean that the Southern District of California can do a similar thing:
"The policy in Howard [the Ninth Circuit case involving the Central District] authorized only leg shackles, while this policy [in the Southern District] authorizes full five point shackles. The policy in Howard applied only at first appearances, while the policy in the Southern District applies to a wide range of non-jury proceedings. The policy in Howard applied only before magistrate judges; this policy applies to proceedings before both magistrate and district judges."
Plus, as I said, the Southern District isn't the Central District. And Judge Schroeder explains some of these differences, as well as a bit of the backstory about the relevant courtroom in Los Angeles:
"The concerns in Howard were focused on the nature and location of the proceedings. The primary justification given for that policy was a concern for maintaining security in a particular courtroom, a problem peculiar to the Roybal Courthouse in Los Angeles. Howard, 480 F.3d at 1013. We discussed security concerns created by “the Central District’s practice of conducting proceedings in a large courtroom on the third floor of the Roybal Courthouse, in the presence of multiple defendants, where the risks of conflict, violence, or escape are heightened.” Id.
A bit of history is illuminating. The Roybal Courthouse involved in Howard was built several decades earlier, and was originally designed not as a stand-alone courthouse, but as an office building with a few courtrooms. This design is what gave rise to the security problems discussed in Howard and was the result of a feud between the General Services Administration and the District Court for the Central District. After the District Court rejected a proposal to move out of their existing courthouse and into an entirely new one, Congress chose instead to incorporate a few additional courtrooms into a planned office building, which became the Roybal Courthouse. . . . The Roybal Courthouse was thus particularly ill-suited to accommodate modern security concerns.
In this case, the government has not demonstrated that the courthouses in the Southern District pose similar problems for security. The record here indicates the Marshals in the Southern District pointed to problems arising from the existence of three courthouses, ostensibly brought about by the 2012 opening of a new, state-of-the-art courthouse which, unlike Roybal, presumably was designed to accommodate modern security concerns."
In short, San Diego has a shiny new, fancy courthouse with modern security, whereas Los Angeles has a converted office building with a madhouse on the third floor. What you can do in the latter is not necessarily what you can do in the former.
So holds the Ninth Circuit.
Okay, so it's a bit more complicated than that. But that's essentially what the Ninth Circuit holds.
Sure, in 2007, the Ninth Circuit held that the Central District of California could validly shackle all pretrial detainees appearing before a magistrate, without any particularized showing of good cause (e.g., that the particular detainee might be a threat). But the Ninth Circuit says that holding doesn't necessarily mean that the Southern District of California can do a similar thing:
"The policy in Howard [the Ninth Circuit case involving the Central District] authorized only leg shackles, while this policy [in the Southern District] authorizes full five point shackles. The policy in Howard applied only at first appearances, while the policy in the Southern District applies to a wide range of non-jury proceedings. The policy in Howard applied only before magistrate judges; this policy applies to proceedings before both magistrate and district judges."
Plus, as I said, the Southern District isn't the Central District. And Judge Schroeder explains some of these differences, as well as a bit of the backstory about the relevant courtroom in Los Angeles:
"The concerns in Howard were focused on the nature and location of the proceedings. The primary justification given for that policy was a concern for maintaining security in a particular courtroom, a problem peculiar to the Roybal Courthouse in Los Angeles. Howard, 480 F.3d at 1013. We discussed security concerns created by “the Central District’s practice of conducting proceedings in a large courtroom on the third floor of the Roybal Courthouse, in the presence of multiple defendants, where the risks of conflict, violence, or escape are heightened.” Id.
A bit of history is illuminating. The Roybal Courthouse involved in Howard was built several decades earlier, and was originally designed not as a stand-alone courthouse, but as an office building with a few courtrooms. This design is what gave rise to the security problems discussed in Howard and was the result of a feud between the General Services Administration and the District Court for the Central District. After the District Court rejected a proposal to move out of their existing courthouse and into an entirely new one, Congress chose instead to incorporate a few additional courtrooms into a planned office building, which became the Roybal Courthouse. . . . The Roybal Courthouse was thus particularly ill-suited to accommodate modern security concerns.
In this case, the government has not demonstrated that the courthouses in the Southern District pose similar problems for security. The record here indicates the Marshals in the Southern District pointed to problems arising from the existence of three courthouses, ostensibly brought about by the 2012 opening of a new, state-of-the-art courthouse which, unlike Roybal, presumably was designed to accommodate modern security concerns."
In short, San Diego has a shiny new, fancy courthouse with modern security, whereas Los Angeles has a converted office building with a madhouse on the third floor. What you can do in the latter is not necessarily what you can do in the former.
U.S. v. Christensen (9th Cir. - Aug. 25, 2015)
You might expect me to critique the Ninth Circuit for taking nearly 22 months after oral argument to write this opinion.
Nope. Not this time.
This appeal involves the convictions of notorious private investigator Anthony Pellicano and a variety of his associates. Defendants filed fourteen briefs in the Ninth Circuit, a total of over 900 pages. The government's answering brief was nearly 700 (!) pages long. The Ninth Circuit opinion itself caps out at 123 (!!) single-spaced pages. Including a dissent on a material point by Judge Christensen, who's sitting by designation from the district court in Montana. And who, in a neat little coincidence, has the same last name as the lead defendant.
Cranking out 123 pages of published text, plus additional stuff in an accompanying unpublished memorandum disposition, takes time. Twenty-two months, even.
So notwithstanding the fact that several of the district court captions in this appeal begin with "05", I think this is about as timely an opinion as we have any legitimate reason to expect.
Nope. Not this time.
This appeal involves the convictions of notorious private investigator Anthony Pellicano and a variety of his associates. Defendants filed fourteen briefs in the Ninth Circuit, a total of over 900 pages. The government's answering brief was nearly 700 (!) pages long. The Ninth Circuit opinion itself caps out at 123 (!!) single-spaced pages. Including a dissent on a material point by Judge Christensen, who's sitting by designation from the district court in Montana. And who, in a neat little coincidence, has the same last name as the lead defendant.
Cranking out 123 pages of published text, plus additional stuff in an accompanying unpublished memorandum disposition, takes time. Twenty-two months, even.
So notwithstanding the fact that several of the district court captions in this appeal begin with "05", I think this is about as timely an opinion as we have any legitimate reason to expect.
Monday, August 24, 2015
People v. Seumanu (Cal. Supreme Ct. - Aug. 24, 2015)
"Nolan Pamintuan was engaged to marry Rowena Panelo on May 18, 1996.
He spent the evening before, May 17, with friends and family at the rehearsal
dinner at a restaurant in Daly City. Panelo gave him a wedding present that night:
a black Movado watch engraved with their intended wedding date. After dinner,
Pamintuan drove Panelo to her apartment and continued on to Hayward, where he
intended to spend the night at his father‘s apartment. Pamintuan was wearing a
brown Gucci watch, a gold engagement ring, a black leather sport coat, an Old
Navy-brand pea coat, and boots. . . .
That night defendant declared his intention to steal a car in order to commit some robberies, so defendant, Iuli, Palega, and Tautai Seumanu set off to look for a suitable vehicle to steal. They eventually located a van to their liking and Tautai and defendant used a screwdriver to steal it. Back at their family compound in Hayward with the stolen van, the group changed out of their Samoan clothes and donned dark clothes; defendant brought out firearms from the outbuilding. Iuli knew ―something big‖ was going to happen when he saw the guns. Defendant spoke of committing robberies and everyone was ―in on the deal.‖ The foursome left the house in the stolen van and began looking for a robbery victim. . . . After considering and rejecting a few possibilities, the group spotted a potential victim and attempted an armed robbery but the intended victim escaped. When the group reentered the stolen van and drove off, defendant chastised Tautai for the botched robbery. They then observed Nolan Pamintuan parking his car and defendant said: "Let‘s go back and get that guy who just got out of the car." Palega turned the van around.
Defendant, holding a sawed-off shotgun, jumped out of the van with Iuli and confronted the victim. Pamintuan looked shocked and scared and offered defendant the inscribed black Movado watch his fiancée had just given him hours earlier, saying: ―Just take this, that is all I have.‖ Defendant took it and then forced the victim into the van. As they drove off, defendant and Tautai stripped the victim of everything he had, including his boots, sport coat, pea coat, ring, wallet, and watch. Defendant became angry when he discovered Pamintuan was carrying only $3 in cash. The victim offered to withdraw money from the bank and was by this time begging for his life.
They drove to a bank with an automated teller machine and defendant warned Pamintuan that if he tried to escape, defendant would kill him. Tautai and Iuli accompanied Pamintuan to the ATM, where he withdrew $300 and gave it to defendant upon returning to the van. Iuli was worried that the ATM camera had photographed him, Tautai, and the van. The foursome wanted the victim to withdraw more money, and when Pamintuan told them of the daily $300 limit they became angry. Defendant ordered Palega to drive away from the bank and find a dark spot. Defendant and Tautai argued over who would kill the victim, while Palega advised against killing him. Iuli exited the van in an attempt to stop the shooting, seeing no point, as Pamintuan had already given them all of his money. Pamintuan continued to beg for his life. Defendant then shot him in the chest with a single shot from the shotgun. The four then abandoned the stolen van in the neighborhood and went home."
Oh. One more thing. "At 12:15 p.m., police showed photographs to Pamintuan‘s brother, Paul, who identified the shotgun victim as his brother, Nolan. Panelo, the victim‘s intended bride, was told of his murder around 1:30 p.m.; they had planned to marry at 2:00 p.m. that day."
Yeah, you're going to be sentenced to death for that. And the California Supreme Court will unanimously affirm.
That night defendant declared his intention to steal a car in order to commit some robberies, so defendant, Iuli, Palega, and Tautai Seumanu set off to look for a suitable vehicle to steal. They eventually located a van to their liking and Tautai and defendant used a screwdriver to steal it. Back at their family compound in Hayward with the stolen van, the group changed out of their Samoan clothes and donned dark clothes; defendant brought out firearms from the outbuilding. Iuli knew ―something big‖ was going to happen when he saw the guns. Defendant spoke of committing robberies and everyone was ―in on the deal.‖ The foursome left the house in the stolen van and began looking for a robbery victim. . . . After considering and rejecting a few possibilities, the group spotted a potential victim and attempted an armed robbery but the intended victim escaped. When the group reentered the stolen van and drove off, defendant chastised Tautai for the botched robbery. They then observed Nolan Pamintuan parking his car and defendant said: "Let‘s go back and get that guy who just got out of the car." Palega turned the van around.
Defendant, holding a sawed-off shotgun, jumped out of the van with Iuli and confronted the victim. Pamintuan looked shocked and scared and offered defendant the inscribed black Movado watch his fiancée had just given him hours earlier, saying: ―Just take this, that is all I have.‖ Defendant took it and then forced the victim into the van. As they drove off, defendant and Tautai stripped the victim of everything he had, including his boots, sport coat, pea coat, ring, wallet, and watch. Defendant became angry when he discovered Pamintuan was carrying only $3 in cash. The victim offered to withdraw money from the bank and was by this time begging for his life.
They drove to a bank with an automated teller machine and defendant warned Pamintuan that if he tried to escape, defendant would kill him. Tautai and Iuli accompanied Pamintuan to the ATM, where he withdrew $300 and gave it to defendant upon returning to the van. Iuli was worried that the ATM camera had photographed him, Tautai, and the van. The foursome wanted the victim to withdraw more money, and when Pamintuan told them of the daily $300 limit they became angry. Defendant ordered Palega to drive away from the bank and find a dark spot. Defendant and Tautai argued over who would kill the victim, while Palega advised against killing him. Iuli exited the van in an attempt to stop the shooting, seeing no point, as Pamintuan had already given them all of his money. Pamintuan continued to beg for his life. Defendant then shot him in the chest with a single shot from the shotgun. The four then abandoned the stolen van in the neighborhood and went home."
Oh. One more thing. "At 12:15 p.m., police showed photographs to Pamintuan‘s brother, Paul, who identified the shotgun victim as his brother, Nolan. Panelo, the victim‘s intended bride, was told of his murder around 1:30 p.m.; they had planned to marry at 2:00 p.m. that day."
Yeah, you're going to be sentenced to death for that. And the California Supreme Court will unanimously affirm.
Poole v. Orange County Fire Authority (Cal. Supreme Ct. - Aug. 24, 2015)
Justice Cuellar writes a concurrence in an otherwise unanimous case just to make clear his view that "plain" statutory language isn't always necessarily clear. Or dispositive. You've instead got to look at the statute as a whole.
It's five (double-spaced) pages worth reading.
If only because it's from a justice we're just starting to get to know.
It's five (double-spaced) pages worth reading.
If only because it's from a justice we're just starting to get to know.
Friday, August 21, 2015
In Re Marriage of Siegel (Cal. Ct. App. - Aug. 21, 2015)
When a complaint seeks only X, the trial court isn't empowered to give the plaintiff Y.
So, for example, when a complaint seeks only that the ex-husband produce evidence that he has purchased the life insurance required by a marital dissolution agreement, and at the hearing, the ex-husband provides proof of insurance, the trial court can't order that the ex-husband establish and fund a $126,910 trust. That'd violate due process.
This is an obvious point. But one that bears repetition. As well as publication by the Court of Appeal.
Maybe the husband should indeed establish and fund the trust. But plaintiff's got to ask for it first.
So, for example, when a complaint seeks only that the ex-husband produce evidence that he has purchased the life insurance required by a marital dissolution agreement, and at the hearing, the ex-husband provides proof of insurance, the trial court can't order that the ex-husband establish and fund a $126,910 trust. That'd violate due process.
This is an obvious point. But one that bears repetition. As well as publication by the Court of Appeal.
Maybe the husband should indeed establish and fund the trust. But plaintiff's got to ask for it first.
Subscribe to:
Posts (Atom)
