State v. Bernini

207 P.3d 789, 220 Ariz. 536, 553 Ariz. Adv. Rep. 12, 2009 Ariz. App. LEXIS 80
CourtCourt of Appeals of Arizona
DecidedApril 7, 2009
Docket2 CA-SA 2008-0078
StatusPublished
Cited by8 cases

This text of 207 P.3d 789 (State v. Bernini) is published on Counsel Stack Legal Research, covering Court of Appeals of Arizona primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
State v. Bernini, 207 P.3d 789, 220 Ariz. 536, 553 Ariz. Adv. Rep. 12, 2009 Ariz. App. LEXIS 80 (Ark. Ct. App. 2009).

Opinion

OPINION

ESPINOSA, Judge.

¶ 1 This special action by the state arises from consolidated cases in which real parties in interest, Erica Daughters-White and twenty-four other defendants charged with driving with an alcohol concentration of .08 or more have sought production of the software configuration (“source code”) of the In-toxilyzer 8000, the breath-testing equipment currently used by the Tucson Police Department. Defendants argued that they had a “substantial need” for the source code in preparing their defenses; that the source code was “material and information not otherwise covered” in the disclosure required by Rule 15. 1, Ariz. R.Crim. P.; and that they were “unable ... without undue hardship to obtain the substantial equivalent by other means.”

¶ 2 On September 10, 2008, after a two-day evidentiary hearing, the respondent judge ordered that CMI, a Kentucky corporation that manufactures the Intoxilyzer equipment and owns the source code, produce the requested material. The respondent also ruled as follows:

The Court finds that the source code for the Intoxilyzer 8000 is not within the possession or control of the Pima County Attorney[’]s Office, any law enforcement agency, or any other person that has participated in the investigation that is under the direction or control of the Pima County AttorneyL’Js Office, and therefore declines to find that the State has a Rule 15.1 obligation to produce the programming language or software utilized by CMI in its Intoxilyzer 8000 machines. The Court further finds that while a defendant is entitled to any evidence[] “that potentially could rebut the state’s prima facie showing” that an Intoxilyzer was operating correctly and is entitled to attack the [IJntoxilyzer’s reliability before a jury, such information is not Brady material. [ 1 ]

¶ 3 Nevertheless, at a subsequent hearing on defendants’ “Request for Remedies,” 2 the *538 respondent judge ordered the state to obtain the source code from CMI and provide it to defendants. She also ordered the state to serve a CMI representative in Kentucky with an order to show cause why CMI should not be held in contempt. The respondent reasoned that, even though she had found the information was not in the possession or control of the state, “there is an obligation on the State to disclose material that’s not in its possession under Rule 15 if the State has better access” to information defendants have specifically requested but have not obtained, despite their good-faith efforts. '

Discussion

¶ 4 The state has petitioned this court for special action relief, asking that we “revers[e] the trial court’s orders that CMI disclose the Source Code to Defendants, that the State obtain the Source Code from CMI, and that the State serve the order to show cause” on CMI. After filing its petition, the state wrote to CMI requesting disclosure of the source code and apparently had the respondent judge’s orders served on a representative of CMI. In addition, the state sought enforcement of those orders in a Kentucky eoux’t. The record reflects the Kentucky court quashed the orders, finding the Intoxilyzer 8000 source code subject to pi’o-teetion as a trade secret. CMI subsequently stated it would produce the source code px-o-vided all parties agreed to a protective order and signed a nondisclosure agreement.

¶ 5 The state then unsuccessfully moved the respondent judge to reconsider her order requiring the state to obtain and produce the source code. On January 12, 2009, the respondent concluded she lacked jui’isdiction to require the out-of-state coi’poration to comply with her oi’dei’s and vacated her September 2008 order directing CMI to disclose the source code. And as noted above, the state had already sexwed CMI with the x-espon-dent’s order to show cause. Thus, the state’s l’equest that we vacate the respondent’s orders requiring CMI to disclose the source code and requiring the state to serve CMI with an order to show cause is moot.

¶ 6 One issue remains, however: whether the respondent judge abused her discretion in ordering the state to obtain the source code from CMI and disclose it to defendants. We accept jui’isdiction of this issue because the state has no equally plain, speedy, or adequate remedy by appeal to challenge the respondent’s order compelling discovery, see Twin City Fire Ins. Co. v. Burke, 204 Ariz. 251, ¶ 3, 63 P.3d 282, 283 (2003), and because the issue is one of statewide impox’tance, see Martin v. Reinstein, 195 Ariz. 293, ¶ 10, 987 P.2d 779, 786-87 (App.1999).

¶ 7 We will not disturb a ti’ial court’s x’uling on discovexy and disclosure matters absent an abuse of discretion, and we defer to the trial coui’t’s factual findings as long as they are supported by reasonable evidence. Twin City, 204 Ariz. 251, ¶ 10, 63 P.3d at 284-85; see also Ariz. R.P. Spec. Actions 3.

¶ 8 Reasonable evidence supported the respondent judge’s findings that the state has no independent obligation under Rule 15.1 to produce CMI’s source code for the Intoxilyzer 8000, because, based upon the record concerning the Pima County Attorney’s Office and the Tucson Police Department, the state has neither possession of the source code nor control over CMI. See Ariz. R.Crim. P. 15.1(b), (f). We find no evidence, however, to suppoi’t the respondent’s finding that the state has better access than defendants to CMI’s source code and is therefore obligated to produce it. Indeed, the state attempted to have CMI pi’oduce the source code, which CMI x’efused to do without pi’otective conditions it sought to impose.

¶ 9 As our supreme coui’t has explained, “Genei’ally, ‘[t]he [Sjtate cannot be held to disclose material that it does not possess.’ ” State v. Armstrong, 208 Ariz. 345, ¶ 55, 93 P.3d 1061, 1072 (2004), quoting State v. McDaniel, 136 Ariz. 188, 195, 665 P.2d 70, 77 (1983) (alterations in Armstrong ). Accordingly,

the state has an obligation under Rule 15.1 to disclose material information not in its possession or under its conti’ol only if (1) the state has better access to the information; (2) the defense shows that it has *539 made a good faith effort to obtain the information without success; and (3) the information has been specifically requested by the defendant.

State v. Rienhardt, 190 Ariz. 579, 585-86, 951 P.2d 454, 460-61 (1997) (“fact that the prosecution is in a better position to secure a witness’s cooperation” does not “mean that the witness is under the prosecution’s control”). We therefore conclude the respondent abused her discretion in ordering the state to obtain and disclose the CMI source code.

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

Related

State v. Hudson
Court of Appeals of Arizona, 2020
State v. Brown
Court of Appeals of Arizona, 2019
Magnotta v. Serra
Court of Appeals of Arizona, 2018
Dlr v. O'Neil
Court of Appeals of Arizona, 2017
State v. Huerta
224 P.3d 240 (Court of Appeals of Arizona, 2010)
State of Arizona v. Alexander Joel Huerta
Court of Appeals of Arizona, 2010
State v. Bernini
218 P.3d 1064 (Court of Appeals of Arizona, 2009)

Cite This Page — Counsel Stack

Bluebook (online)
207 P.3d 789, 220 Ariz. 536, 553 Ariz. Adv. Rep. 12, 2009 Ariz. App. LEXIS 80, Counsel Stack Legal Research, https://law.counselstack.com/opinion/state-v-bernini-arizctapp-2009.