State v. Azure

2005 MT 328, 125 P.3d 1116, 329 Mont. 536, 2005 Mont. LEXIS 512
CourtMontana Supreme Court
DecidedDecember 20, 2005
Docket04-603
StatusPublished
Cited by16 cases

This text of 2005 MT 328 (State v. Azure) is published on Counsel Stack Legal Research, covering Montana Supreme Court primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
State v. Azure, 2005 MT 328, 125 P.3d 1116, 329 Mont. 536, 2005 Mont. LEXIS 512 (Mo. 2005).

Opinion

JUSTICE COTTER

delivered the Opinion of the Court.

¶1 Following a four-day jury trial in January 2004, Donald Azure (Azure) was convicted by unanimous verdict of felony deliberate homicide and felony criminal endangerment. He appeals on the grounds that the jury was impaneled improperly and that the District Court gave an erroneous jury instruction for the charge of criminal endangerment. We affirm.

ISSUES

¶2 A restatement of the issues on appeal is:

¶3 Was Azure’s jury venire improperly impaneled?

¶4 Did the District Court correctly instruct the jury on the elements of criminal endangerment?

FACTUAL AND PROCEDURAL BACKGROUND

¶5 Azure was charged with deliberate homicide, attempted deliberate homicide and criminal mischief on February 27,1997. He was tried in October 1997, and convicted of deliberate homicide, mitigated attempted deliberate homicide and criminal mischief. We affirmed his conviction in 2002. The underlying facts pertinent to Azure’s original charges and earlier trial have been detailed in State v. Azure, 2002 MT 22, 308 Mont. 201, 41 P.3d 899, and will not be repeated here.

¶6 In February 2003, Azure petitioned for postconviction relief claiming that the jury selection process of his 1997 trial violated his constitutional rights. The District Court granted Azure’s Petition in November 2003. On December 9, 2003, the State filed an Amended Information charging Azure with deliberate homicide and felony criminal endangerment. In preparation for the January 12,2004, jury trial, the Cascade County Clerk of Court (clerk) began compiling the jury pool. On January 9, 2004, Azure challenged the panel, arguing it *540 had not been drawn randomly, as required by statute. The District Court heard the matter on January 12, 2004, and denied Azure’s challenge. The trial commenced on the same day, and Azure was convicted on January 15, 2004. The court sentenced him on March 3, 2004, imposing the same sentence it had imposed six years earlier, i.e., one hundred (100) years to Montana State Prison (MSP) for deliberate homicide, with an additional ten (10) years for the use of a dangerous weapon in the commission of the crime, and ten (10) years to MSP for criminal endangerment, with an additional two (2) years for the use of a dangerous weapon. The sentences total one hundred twenty-two (122) years and run consecutively. Azure filed a timely appeal.

STANDARD OF REVIEW

¶7 The District Court’s decision to deny Azure’s challenge to the composition of the jury was a conclusion of law. Our standard of review for a district court’s conclusions of law is plenary and we must determine whether the court’s conclusions are correct as a matter of law. State v. Bingman, 2002 MT 350, ¶ 55, 313 Mont. 376, ¶ 55, 61 P.3d 153, ¶ 55 (citation omitted).

¶8 We review jury instructions to determine whether the instructions as a whole fully and fairly instruct the jury on the applicable law. A district court has broad discretion in formulating jury instructions, and our standard of review is whether the court abused that discretion. State v. Meyer, 2005 MT 215, ¶ 14, 328 Mont. 247, ¶ 14, 119 P.3d 1214, ¶ 14.

DISCUSSION

¶9 Was Azure’s jury venire improperly impaneled ?

¶10 Azure’s jury venire was compiled by combining three separate jury panels that had been randomly selected by computer from the list of Cascade County registered voters. These panels were called for trials scheduled to occur around the same time as Azure’s trial. When these other trials did not take place, the jury panels were held over and ultimately assigned to Azure’s trial. Panels one and two each originally consisted of seventy persons. Panel three originally consisted of thirty-five persons. Prior to being assigned to Azure’s trial, these panels were reduced to forty-six, forty-seven, and twenty-four persons respectively as a result of some jurors being excused by the clerk’s office or the judge for legitimate reasons. Additionally, ten people were eliminated for failure to contact the clerk after the summons was mailed to them and the clerk was subsequently unable to reach them.

*541 ¶11 Panel one was initially assigned to Azure’s trial. However, the District Court notified the clerk several days before the trial that it wanted at least eighty prospective jurors in this case. To accommodate this request, the clerk’s office added the twenty-four names from panel three to the forty-six names on panel one. This created a pool of seventy people. The clerk then added the first twenty-one names from panel two. However, because panel two had previously been alphabetized, the selected surnames began with the letters A through K, and the names beginning with the remaining letters of the alphabet were eliminated. Subsequently, one person from panel two was excused, leaving the District Court with ninety potential jurors from which to choose. These ninety names were placed in a box for additional random selection, and the first twenty-seven names selected comprised the venire for the jury and one alternate.

¶12 Azure’s complaint on appeal arises from the manner in which panel two was split. He maintains that it was error to alphabetize this fist and then select only the first twenty-one persons based upon the first letter of their last names. He posits that once the list was put in alphabetical order and then not used in its entirety, it ceased to be random. He further asserts that when this list was combined with the other panels, the overall jury pool was tainted, he was denied a fair cross-section jury panel, and he is entitled to a new trial.

¶13 Section 3-15-503(l)(b), MCA (1995), upon which Azure relies, states:

If the drawing of jurors is conducted by means of a computerized database, it must be conducted by use of a computerized random selection process that the judges of the district court of the county have approved in writing as satisfactorily fulfilling the requirements for the drawing of trial juries. [Emphasis added.]

¶14 Azure complains his jury panel was not “randomly” selected. Using the ordinary meaning of the term “random,” i.e., lacking a specific plan or pattern, 1 it could be argued that once the list was alphabetized, it was no longer random. However, to prevail, Azure must prove that the selection process was not random. This he has failed to do. Mere alphabetization of a randomly selected list of names and elimination of some of those names based exclusively on where they fall in the alphabet does not taint the random selection process. As a result, we conclude Azure’s jury selection process did not violate *542 § 3-15-503(l)(b), MCA (1995).

¶15 Without substantive analysis, Azure relies on State v. Taylor (1975), 168 Mont. 142, 542 P.2d 100, and Taylor v. Louisiana (1975), 419 U.S. 522, 95 S.Ct.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

State v. P. Green
2025 MT 52N (Montana Supreme Court, 2025)
State v. B. Hamernick
2023 MT 249 (Montana Supreme Court, 2023)
State v. P. Smith
2023 MT 34N (Montana Supreme Court, 2023)
State v. S. Ragner
2022 MT 211 (Montana Supreme Court, 2022)
State v. S. Tracy
2022 MT 207N (Montana Supreme Court, 2022)
State v. G. Deveraux
2022 MT 130 (Montana Supreme Court, 2022)
State v. Secrease
2021 MT 212 (Montana Supreme Court, 2021)
State v. M. Collins
2021 MT 10N (Montana Supreme Court, 2021)
State v. B. Bagnell
2020 MT 234N (Montana Supreme Court, 2020)
State v. Ilk
2018 MT 186 (Montana Supreme Court, 2018)
State v. Kalem Johnston
2010 MT 152 (Montana Supreme Court, 2010)
State v. Johnston
2010 MT 152 (Montana Supreme Court, 2010)
Bloomer v. State
2009 WY 77 (Wyoming Supreme Court, 2009)
State v. Hausauer
2006 MT 336 (Montana Supreme Court, 2006)

Cite This Page — Counsel Stack

Bluebook (online)
2005 MT 328, 125 P.3d 1116, 329 Mont. 536, 2005 Mont. LEXIS 512, Counsel Stack Legal Research, https://law.counselstack.com/opinion/state-v-azure-mont-2005.