State v. McCloud

34 P.3d 699, 177 Or. App. 511, 2001 Ore. App. LEXIS 1630
CourtCourt of Appeals of Oregon
DecidedOctober 31, 2001
Docket000849967; A112227
StatusPublished
Cited by6 cases

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

Bluebook
State v. McCloud, 34 P.3d 699, 177 Or. App. 511, 2001 Ore. App. LEXIS 1630 (Or. Ct. App. 2001).

Opinion

*513 HASELTON, P. J.

Defendant appeals his convictions on two counts of third-degree sexual abuse. ORS 163.415. He argues that the trial court erred in entering two convictions rather than merging the two counts and' entering a single conviction pursuant to ORS 161.067. As explained below, we agree that the trial court erred in failing to merge the convictions. We therefore reverse the convictions and remand for merger of the convictions and for resentencing.

The relevant facts are not in dispute. Defendant was charged with two counts of third-degree sexual abuse committed on or about August 16,2000. One of the counts alleged that defendant subjected the victim to nonconsensual sexual contact by touching her breast, and the other alleged that defendant subjected the victim to nonconsensual sexual contact by touching her vaginal area. Evidence at trial demonstrated that the victim entered defendant’s room at the residential hotel where both were living. Defendant was viewing pornography and told the victim that he wanted to engage in various sexual acts with her as depicted in the pornography. The victim declined. Defendant then kissed the victim and touched her breasts and vaginal area over her objections. The victim pushed defendant away, left the room, and reported the incident to police, who arrested defendant later that evening.

Defendant was convicted of two counts of third-degree sexual abuse after a trial to the court. ORS 163.415. 1 Defendant argued that the convictions should merge, given the provisions of ORS 161.067(3). 2 The trial court agreed that *514 ORS 161.067(3) applied, because there had not been a separation in time between the two violations of the statute sufficient to afford defendant an opportunity to renounce his criminal intent. The trial court concluded, however, that the statute did not require it to merge defendant’s convictions, but required it to merge only defendant’s sentences. It therefore entered separate convictions on each count of third-degree sexual abuse.

On appeal, defendant argues that the trial court erred in concluding that ORS 161.067 did not require merger of the convictions but required only “sentence merger.” We agree.

Surprisingly, although ORS 161.067 was enacted almost 15 years ago, no reported decision has explicitly addressed the question whether the phrase “separately punishable offenses” is meant to address situations in which separate convictions should be entered, or merely to address situations in which separate convictions may be punished separately, i.e., not concurrently. Defendant takes the former view, and the state takes the latter. The case law applying this statute implicitly supports defendant’s view: In many cases, this court and the Supreme Court have interpreted ORS 161.067 and its virtually identical counterpart, former ORS 161.062, 3 as applying to merger of convictions, not sentences.

*515 In State v. Crotsley, 308 Or 272, 779 P2d 600 (1989), the court noted that ORS 161.062, ORS 161.067, relating to merger, and ORS 137.123, relating to consecutive sentencing, had been enacted in response to case law concerning when “a single criminal episode provides grounds for multiple convictions and sentences.” Although the issue in Crotsley involved the first subsection of ORS 161.062 (and ORS 161.067) rather than the third subsection, both subsections use the same term, “separately punishable offenses.” The issue, as framed by the court, was whether “separate * * * convictions and sentences may be imposed” under the circumstances presented there. Crotsley, 308 Or at 276 (emphasis added). See also State v. Barrett, 331 Or 27, 10 P3d 901 (2000) (similarly treating former ORS 161.062 as pertaining to merger of convictions).

Our court, like the Supreme Court, has on numerous occasions determined when convictions should merge under ORS 161.067 and ORS 161.062. Recently, in State v. Schwartz, 173 Or App 301, 319, 21 P3d 1128 (2001), we held that a defendant’s “convictions * * * do not merge [under ORS 161.067(3)], because the acts that formed the basis for each violation were separated by a ‘sufficient pause’ in defendant’s criminal conduct to afford him the opportunity to renounce criminal intent.” (Emphasis added.) Similarly, in State v. Lucio-Camargo, 172 Or App 298, 310, 18 P3d 467 (2001), we treated ORS 167.067(3) as relating to requirements for when “separate convictions * * * can be entered]” (Emphasis added.) See also State v. Gilbertson, 110 Or App 152, 156-57, 822 P2d 716 (1991), rev den 313 Or 211 (1992) (court did not *516 err in refusing to merge convictions, where defendant had opportunity to renounce criminal intent between crimes). 4

Despite those decisions implicitly recognizing that ORS 161.067

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

Related

State v. Parkins
211 P.3d 262 (Oregon Supreme Court, 2009)
State v. Yong
205 P.3d 63 (Court of Appeals of Oregon, 2009)
State v. Lucio-Camargo
62 P.3d 811 (Court of Appeals of Oregon, 2003)
State v. McCloud
56 P.3d 962 (Court of Appeals of Oregon, 2002)

Cite This Page — Counsel Stack

Bluebook (online)
34 P.3d 699, 177 Or. App. 511, 2001 Ore. App. LEXIS 1630, Counsel Stack Legal Research, https://law.counselstack.com/opinion/state-v-mccloud-orctapp-2001.