New Minnesota Supreme Court Justice Dave Stras: An End to the Pawlenty Four?

Tomorrow Justice David Stras begins his new job as Minnesota Supreme Court Justice. I thought it appropriate to present my view of the makeup of the court and how the change may affect the court’s direction.

The defense bar (and those for whom we fight) has endured for the last four years the “Pawlenty Four” (“P4”) – a bloc of conservative justices carrying the majority and appointed by the lame-duck governor. Until recently, the P4 took the majority in several close cases. In a number of cases, including State v. Netland (2009), Laase v. 2007 Chevrolet Tahoe, and State v. Peck (2009), the minority wrote particularly scathing dissents.

Last month the Minnesota Supreme Court voted 4-3 in Governor Pawlenty’s unallotment case. The governor lost when retiring Chief Justice Magnuson seemingly switched sides and went against the governor. This could have indicated a “shift” in the Chief Justice’s stance, and provided some hope that the Court would perhaps return to a less activist role in Minnesota. Unfortunately, Chief Justice Magnuson had announced he was retiring earlier this year.

After the unallotment case, the governor named Justice Magnuson’s replacement. He elevated Justice Gildea – who wrote the unallotment dissent – to Chief Justice, and appointed David Stras to fill the new vacancy. Professor Stras, a young law school professor, had written an Amicus Curiae (“Friend of the court”) supporting Pawlenty in the unallotment case. 

Most court observers believe Pawlenty’s new appointments will have no effect on the court’s conservative majority. William Mitchell College of Law Professor Peter Knapp believes the appointments signal "no dramatic change in direction of the court." Pawlenty's picks keep high court tilting right. New justice and chief sided with governor's solo-handed budget cuts, the DFL points out. (Star Tribune).

I don't agree.

Professor Stras served as law clerk to conservative U.S. Supreme Court Justice Clarence Thomas and serves on the executive committee of the conservative Federalist Society.

Stras said he believes “the role of judges is a limited one, safeguarding liberty and protecting the rights of all citizens.” Reporters asked whether he shares Thomas’s philosophy of the law. Stras called Thomas ‘my mentor. ... But we have differences in our approach.’”

Reporters and court observers questioned how to interpret Stras’ comment. Stras suggested that review of his “scholarly papers” may provide some insight.

So that’s exactly what I did.

Stras said he is particularly proud of an article he spent years researching, challenging former U.S. Supreme Court Justice Pierce Butler's reputation as a one-dimensional conservative by citing his pro-defendant rulings.  So that’s where I started.

In Pierce Butler: A Supreme Technician, Vanderbilt Law Review, vol 62 (2009), Stras characterizes Butler as having “surprisingly pro-defendant criminal rights positions.” P. 697. In attempting to debunk Butler’s reputation as conservative, he portrays Butler’s views as “liberal” in criminal cases but conservative on economic issues. See FN183. He thoughtfully explains that Butler broadly construed the Fourth Amendment, in defense of individual liberties. P. 722, and applies this same ideology to defendant’s Sixth Amendment rights. P. 723.

Stras noted that “Justice Butler was a ‘stickler for the rights of criminals,’” citing Chief Justice Hughes. P. 723. After analyzing this article, Stras’ thesis is clear: He makes a scholarly case that carefully debunks Justice Butler’s reputation as conservative when it comes to criminal law issues.

One quote is particularly telling:

As a Supreme Court Justice, Butler’s jurisprudence was deceptively nuanced. Those who categorize him merely as one of the so-called “Four Horsemen of the Apocalypse” fail to give him credit for the intricacy and sophistication with which he approached constitutional questions. To be sure, Butler often took positions that were “favorable toward constitutional protection of economic liberties through judicial restriction of government action.” But it is far too simplistic to assert, as some commentators have, that Butler was the “epitome of ultra-conservativism” or that he was “insensitive to matters of civil liberties.” To the extent that labels are helpful in describing Butler, previous commentators have largely mischaracterized his jurisprudence by widely labeling him as a “conservative.” For example, Butler took stereotypically libertarian (or even liberal) positions in cases involving the Fourth Amendment and the rights of criminal defendants.

P. 717-18 (footnotes omitted).

Does this mean that Stras, despite being appointed to act as a “conservative” justice on a “conservative” court, may actually be a wild card? Is it possible that the P4 could suddenly become the “P3" and end up dissenting in upcoming cases penned by Stras himself? It’s too soon to tell, but based on my research, I don’t see Stras as the type of justice who would indubitably fall in line with the other Pawlenty appointees.

Tags: ,

How Can the State Charge You With Two DWIs For the Same Incident?

Anyone will be upset after being arrested for DWI. They are usually put in handcuffs, transported in the back of a squad car to a nearby (or not-so nearby) police station, and then told to submit a sample of blood (ouch) urine (embarrassing) or breath (inaccurate). After that, many are thrown in jail; others post as much as $12,000 in bail, while others need to find a ride home and a way to get their car out of an impound lot.

After this incident has robbed them of their dignity, many are then even more shocked to discover that they are being charged with not one crime, but two, based off of this arrest. While this seems illegal, it’s actually common, and a good defense attorney can work this to your advantage.

There are two types of DWI Crimes in Minnesota: 1) “driving while impaired” and 2) “per se intoxication.” There is only one real difference between these two crimes, and that is what type of evidence the State can use to prove guilt.

Driving while impaired means just that: the State must prove beyond a reasonable doubt that you were impaired by alcohol or drugs while you were driving. The type of evidence in this type of case ranges from performance on field sobriety tests to the arresting officer’s “opinion” of your level of impairment to the reason the police office stopped your vehicle. Note that for this type of offense, it’s not necessary to prove an alcohol concentration above a .08 - sometimes a driver’s alcohol test result isn’t even relevant.

Per se intoxication, on the other hand, doesn’t mean that a driver was a danger to anyone on the road. In fact, someone who is per se intoxicated might not even feel the effects of what they drank. Instead, per se intoxication just means that someone’s alcohol concentration was at or above .08, as measured anytime within two hours of driving. You can perform perfectly on a field sobriety test and enunciate every word flawlessly, and still be guilty of per se intoxication - if the State has a test result that “proves” you were above a .08.

Back in the day, the only offense drivers could be charged with was “driving while impaired.” These are the types of drivers that can be the most dangerous. However, in close cases, they are also the types of drivers that are hardest for a prosecutor to convict.

Because it can be hard to convict an otherwise safe driver of driving while impaired, the legislature chose to pass a per se law and create a level of alcohol concentration that automatically renders someone “drunk.” This use of “science” makes it far easier for prosecutors to get convictions. Obviously, any prosecutor would rather just flash a test result in front of a jury, say “this number is higher than .08," and get a conviction, than actually prove that someone was impaired!

Of course, these per se laws were both a blessing and a curse for prosecutors. A blessing, because now it’s so much easier to convict people who otherwise do not appear impaired - just look at the test result! However, it’s also a curse, because if they don’t have a test result to rely on, most prosecutors won’t even bother to litigate a driving while impaired case.

That’s where we come in: we often gear our defensive strategy towards getting that test result suppressed, which forces the prosecutor to try their case the “old fashioned” way. Whether that test result is an example of junk science, flawed logic, or the secretive workings of the incomprehensible Intoxilyzer 5000 breath test machine, if there is a way for us to get it suppressed, we will get it suppressed. And without a test result, the vast majority of prosecutors will lose interest in gaining a conviction, and seriously consider settlement or dismissal.

You can feel stone sober and still commit the crime of driving while per se intoxicated. Winning your case means hiring an attorney who knows every possible way to attack the State’s best evidence - a test result - and get it suppressed. If you’ve been charged with driving while impaired, driving while over a .08, or both, contact Ramsay Law Office as soon as possible. We’ll carefully explain the legal process to you and answer your questions.

 

Like Plugging A Leaking Oil Well A Mile Below the Gulf, Onerous Conditions Delay Source Code Review

Earlier this year Judge Abrams issued his case management order for the review of the Minnesota Intoxilyzer 5000. Among other deadlines, he set July 1 as the due date to provide the government with our experts’ report of our source code review.

Last week the source code coalition brought a motion to extend the timelines set by the court. We asked for a three month extension given the circumstances. The Court responded by extending these timelines by a little more than one month. I can’t help but compare this deadline with the current fiasco in the Gulf of Mexico.

While I’m not our president’s number one fan, I empathize with his position. He did not cause the BP oil spill in the Gulf of Mexico, but many look to him to stop the oil and limit the scope of this disaster. Given a choice, I’m sure that everyone would prefer that this oil leak was just offshore, instead of under 5,000 feet of water, and that those responsible for causing the problem would solve it themselves before anyone innocent is harmed.

Likewise, it was the state and CMI who have repeatedly dragged their feet and interfered with our software review. It was the state and CMI that mandated that we travel to Kentucky to review the software, instead of reviewing it from established computer forensics laboratories. Yet, Judge Abrams is expected to speed this whole review process along, meaning that we are expected to inspect, analyze and present a full report in less than two months! I feel like we are trying to plug a leaking oil well miles below the surface of the gulf - and what’s worse, it’s a leak that we warned everyone about years ago!

“Need for Speed?”

This six week extension of the deadline for our experts to finish their report is already causing serious problems, and simply isn’t enough time to properly analyze a complex piece of ancient software. What makes this “need for speed” especially odd is the fact that the State has been dragging its feet for years on any issues regarding the source code!

I “led the charge” against the Intoxilyzer, and was one of the first attorneys in Minnesota to ask the state to produce the source code. This was back in 2006 - over four years ago - and sadly, I have a number of cases that have been consolidated dating all the way back to then.

The Minnesota Supreme Court issued Underdahl I in 2007, holding that Minnesota owned the source code and the state is required to provide it. As early as then, the state acknowledged it could sue CMI for access to the source code, but it did nothing until March, 2008. It was then, over two years after I made my first request, that the state filed a law suit against CMI. And even then, while the state outwardly claimed that it was suing to obtain the software, it was obvious the suit was primarily designed to keep it from us.

With barely a shot fired in the litigation, the state secretly (and hastily!) settled a second time with CMI in June, 2009. We objected to this settlement - we claimed that it rendered source code review too costly, too time consuming, and too inefficient. Nevertheless, Federal Judge Frank approved the settlement over our objection on July 16, 2009. Thus, over three years from the first request for the source code, the state finally crafted a half-cocked method of analyzing this problematic software.

Unfortunately (but not unexpectedly) this interesting settlement was simply the starting point for more and more delay . . .

Relying upon the terms of the settlement reached between the State and CMI, the breath test machine’s manufacturer delayed analysis of the software for months. It boasted about how it would provide a “hard copy” of the source code . . . and then it blacked out large portions of the material throughout the book.

Our experts had to cancel flights to Owensboro, Kentucky on several occasions.  We were forced to bring motions in federal court to get greater access to the code, made agreements which CMI breached, and had to bring even more motions. All of this occurred months and months after the State had reached its secretive settlement with CMI, and years after the State was first asked to disclose the source code.

10,000 Leagues Under the Sea

Our experts finally - finally! - got access for the first time on May 11, 2010. Since then, they have worked diligently to get the job done, despite onerous conditions. They must perform review at CMI’s headquarters in Kentucky, under the constant supervision of CMI security. Hours are limited to Monday to Friday, 8:30-4:30. Each day, ½ hour is wasted for “check-in.” Additional time is wasted setting up and tearing down their equipment. Although it sounds like an exaggeration, our experts (who otherwise spend their time reviewing software on behalf of such clients as the U.S. Navy) assure us that these work conditions make no sense, and that their job has gone from a simple analysis to one that is more like capping an oil leak at the bottom of the ocean - a new, strange, and incredibly difficult experience.

This is the history behind our request for an additional three months to analyze the source code and issue a report. It is a history full of delay tactics, hidden agendas and double-speak. Yet here, now that we’ve finally pushed the State long enough and hard enough to actually provide us with some access to the source code, they are objecting to our request for more time, saying we’ve had plenty!

We are at a critical stage. After almost half a decade of motions, arguments and appeals, we are finally on the threshold of proving what we’ve always known to be the case: there are serious problems with the Intoxilyzer 5000 that is used in Minnesota. Drivers and their families have the right to ensure the black box accuser works as designed. Otherwise, we will blindly trust this Intoxilyzer and risk more erroneous convictions.

The State did everything it could to prevent us from reviewing this software. Then it was CMI’s turn to prevent analysis of the source code. Now, due to overly-restrictive scheduling orders (prompted by the State) our careful analysis is being rushed to a sudden conclusion. It almost seems like the State is being rewarded for dragging its feet for so long.

It may be time to reconsider consolidation....

Source Code Update

Judge Abrams has issued an Order in regard to the request for amended schedule.  Deadlines have been extended.  The order can be viewed below:

 

 

 

 

 

Also, included is the PDF Version.