State v. Leino
Annotate this Case
Download PDF
FILED: February 15, 2012 IN THE COURT OF APPEALS OF THE STATE OF OREGON STATE OF OREGON, Plaintiff-Respondent, v. JACOB CHARLES LEINO, aka Jacob C. Leino, Defendant-Appellant. Multnomah County Circuit Court 080733445 A141398 Youlee Y. You, Judge. Argued and submitted on December 16, 2010. Ernest G. Lannet, Senior Deputy Defender, argued the cause for appellant. With him on the brief was Peter Gartlan, Chief Defender, Office of Public Defense Services. Erika L. Hadlock, Senior Assistant Attorney General, argued the cause for respondent. With her on the brief were John R. Kroger, Attorney General, and David B. Thompson, Interim Solicitor General. Before Schuman, Presiding Judge, and Brewer, Chief Judge, and Wollheim, Judge.* BREWER, C. J. Affirmed. *Brewer, C. J., vice Rosenblum, S. J. 1 BREWER, C. J. 2 Defendant appeals his convictions for unlawful possession of cocaine, ORS 3 475.884, and unlawful possession of methamphetamine, ORS 475.894. He assigns error 4 to the denial of his motion to suppress. He argues that the police officer's observations 5 leading to the search that produced evidence of drugs were made during an unlawful 6 extension of an initially lawful traffic stop. We review the trial court's denial of the 7 motion to suppress for errors of law. State v. Chambers, 226 Or App 363, 365, 203 P3d 8 337 (2009). We conclude that the stop was not unlawfully extended, and therefore 9 affirm. 10 The pertinent facts are not in dispute. Around 3:00 a.m. on July 3, 2008, 11 Portland Police Officer Thurman observed defendant riding a bicycle without a headlight, 12 a traffic violation under ORS 815.280(2)(c). Defendant rode the bicycle into a garage, 13 and Thurman called to defendant from the street to come and talk to Thurman. Thurman 14 told defendant the reason for the stop and asked for his identification, and defendant 15 handed him his Oregon driver's license. Thurman proceeded to call in defendant's 16 identifying information to the police dispatch. While Thurman was speaking with the 17 dispatcher, he noticed that defendant was fidgety and asked defendant to keep his hands 18 in view. Defendant raised his hands, and, at that point, Thurman observed that defendant 19 was carrying a knife clipped to the front pocket of his pants. Thurman asked if he could 20 search defendant, and defendant consented to a search, which revealed drugs in addition 21 to the knife. At around the time Thurman was conducting the search, dispatch responded 1 1 that defendant was "clear and valid." 2 Defendant moved to suppress the knife, the drugs, and incriminating 3 statements that he made after he was arrested, arguing that he was stopped in violation of 4 Article I, Section 9, of the Oregon Constitution, because he had been unlawfully detained 5 before Thurman saw the knife, when Thurman had called dispatch.1 At the suppression 6 hearing, Thurman testified that he had taken defendant's identification "to issue a citation, 7 essentially. As he did give me the [identification] then, of course, I ran his information 8 through our service net." When asked if he was running defendant's name through the 9 system for a "records check," Thurman replied that he was. He indicated that it was 10 "standard procedure" to check a person for warrants in the course of a traffic stop. 11 Defendant argued that, after he had provided Thurman with his identification, Thurman 12 had all the information he needed to issue defendant a citation for the bicycle violation, 13 and that he impermissibly extended the stop by calling defendant's identification in to the 14 dispatcher. The trial court, relying on State v. Smith, 73 Or App 287, 292, 298 P2d 973 15 (1985), concluded that "the request for consent was conducted during an unavoidable lull; 16 that is, the warrant check that the officer was conducting," and denied defendant's motion 17 to suppress. Defendant was then tried to the court on stipulated facts, reserving the right 18 to appeal, and he was convicted. 19 On appeal, defendant argues that Thurman ran his information to check for 1 Article I, section 9, provides, in part, "No law shall violate the right of the people to be secure in their persons, houses, papers, and effects, against unreasonable search, or seizure." 2 1 outstanding warrants, which he contends was not reasonably necessary to the 2 investigation of a routine, bicycle-related, traffic violation. Conducting a warrant check, 3 according to defendant, was equivalent to a criminal investigation without reasonable 4 suspicion, and thus unlawfully extended the duration of the stop. Defendant argues that 5 Thurman's request for consent and subsequent search of defendant's person occurred 6 while that unlawful stop was ongoing. Therefore, he contends, the trial court erred in 7 denying his motion to suppress. 8 As pertinent here, the state replies that an officer does not impermissibly 9 extend a traffic stop by conducting a records and warrant check, because a records check 10 can establish whether the identification provided to the officer is valid. The state further 11 notes that there is no evidence that the performance of a "warrant check" at the same time 12 as the "records check" takes any additional time and, thus, even assuming that checking 13 for warrants alone might impermissibly extend a stop, a "records check" does not. The 14 state relies on numerous cases from this court that indicate, at least implicitly, that 15 records and warrant checks are permissible in the course of a traffic stop. 16 As an initial matter, we agree with the state that the proper framing of the 17 issue is whether a records check that includes a warrant check impermissibly extends a 18 stop. As noted, the evidence showed that it was standard procedure for Thurman to run a 19 "records check" and a "warrant check" before issuing a traffic citation.2 Thus, to the 2 We note that the record does not establish precisely what that process entails, other than the officer calling the stopped person's identifying information in to a "service net," and, as in this case, receiving a response of "clear" and "valid." 3 1 extent that defendant is suggesting that, by calling defendant's information in to the 2 "service net," Thurman began an impermissible "criminal investigation [into] whether 3 defendant was a fugitive from justice," we do not agree that the record establishes that 4 that was what Thurman was doing. Rather, the record reflects that Thurman followed a 5 standard procedure that involves performing a records and warrant check whenever a 6 traffic citation is issued. Thus, the issue is whether, in the course of investigating a 7 bicycle traffic violation, the officer unlawfully extended the stop by running such a check 8 on defendant before issuing the citation. 9 As the state notes, on numerous occasions we have indicated that running a 10 records or warrant check is permissible in the course of a traffic stop. As explained 11 below, although much of our case law is implicit rather than explicit on this point, we 12 agree with the state that conducting such a check before issuing a citation did not 13 impermissibly extend or expand the scope of the stop in this case. 14 15 16 17 18 19 20 21 22 Under Article I, section 9, "[p]olice authority to perform a traffic stop arises out of the facts that created probable cause to believe that there has been unlawful, noncriminal activity, viz., a traffic infraction. Police authority to detain a motorist dissipates when the investigation reasonably related to that traffic infraction, the identification of persons, and the issuance of a citation (if any) is completed or reasonably should be completed. Other or further conduct by the police, beyond that reasonably related to the traffic violation, must be justified on some basis other than the traffic violation." 23 State v. Rodgers/Kirkeby, 347 Or 610, 623, 227 P3d 695 (2010). As we concluded in 24 State v. Amaya, 176 Or App 35, 47, 29 P3d 1177 (2001), aff'd on other grounds, 336 Or 25 616, 89 P3d 1163 (2004), Article I, section 9, also is not implicated if an inquiry 4 1 unrelated to a traffic stop occurs during a routine stop but does not delay it, that is, if it 2 occurs during an "unavoidable lull" in the investigation. Thus, for example, questioning 3 that transforms an encounter from a routine traffic stop into a criminal investigation is not 4 unlawful if it occurs while an officer is lawfully and expeditiously conducting the traffic 5 stop, and it does not result in an extension of that initial stop. State v. Gomes, 236 Or 6 App 364, 372, 236 P3d 841 (2010). Accordingly, the precise question in this case is 7 whether Thurman observed defendant's knife in the course of lawfully conducting the 8 stop for a bicycle traffic violation while calling defendant's identifying information in to 9 the dispatcher, or whether, as defendant contends, calling in defendant's identifying 10 information to the dispatcher was not "reasonably related to that traffic violation, the 11 identification of persons, and the issuance of a citation." Rogers/Kirkeby, 347 Or at 623. 12 Operating a bicycle without a light in the circumstances at issue in this case 13 is a traffic violation, ORS 815.280, and a police officer "[m]ay stop and detain a person 14 for a traffic violation for the purposes of investigation reasonably related to the traffic 15 violation, identification and issuance of citation." ORS 810.410(3)(b); accord, 16 Rogers/Kirkeby, 347 Or at 623 (identifying scope of lawful traffic stop accordingly). In 17 addition, we note that Rogers/Kirkeby itself provides strong support for the conclusion 18 that this type of check is permissibly within the scope of a traffic stop. There, the 19 defendant Rogers had been stopped for a traffic violation and had provided the officer 20 with his license and registration, but was unable to provide proof of insurance. 347 Or at 21 613. The officer had "returned to his patrol car and radioed a request for a records 5 1 check," which "had come back clear, and [the officer] therefore had a sufficient basis 2 only to issue defendant a traffic citation." Id. at 614. Rather than issue the citation, 3 however, the officer questioned the defendant about items in the vehicle. The court 4 concluded that the stop had been unlawfully extended because, when the officer "returned 5 to defendant's driver-side window, he had all the information necessary to issue 6 defendant a citation and end defendant's limited detention." Id. at 626. At that point, the 7 officer "had completed the investigation reasonably related to the traffic infraction and 8 issuance of the citation." Id. Implicit in the court's conclusion is that, before that point, 9 the stop was lawful. That is, the stop became unlawful after the officer had run the check 10 and it had "come back clear." Id. at 614. 11 Additionally, in numerous cases, we have indicated that an officer's action 12 in contacting dispatch with a defendant's identifying information is within the scope of a 13 lawful traffic stop. See, e.g., State v. Hampton, 247 Or App 147, 153 n 5, ___ P3d ___ 14 (2011) (explicitly rejecting argument that officer unlawfully extended a stop by asking 15 for the defendant's registration, noting that "asking a defendant for his license, 16 registration, and insurance is routine behavior for an officer conducting a traffic stop"); 17 State v. Klein, 234 Or App 523, 531, 228 P3d 714 (2010) (officer "had the information 18 that he needed to conclude the traffic stop when he returned to speak with defendant after 19 completing the warrant check"); State v. Amador, 230 Or App 1, 8, 213 P3d 846 (2009), 20 rev den, 347 Or 533 (2010) (officer's question about drugs and weapons did not 21 impermissibly expand scope of traffic stop because "the officer had only just obtained 6 1 defendant's identification and thus did not yet have all the information necessary to issue 2 a citation"); State v. Huggett, 228 Or App 569, 574-75, 209 P3d 385 (2009), rev 3 dismissed, 348 Or 71 (2010) ("Nothing in the record indicates that, at the time [the 4 officer] requested defendant's consent to search his person, he was awaiting the results of 5 a records check, was waiting for defendant to provide him with items needed to continue 6 the traffic stop, or was engaging in any other step related to the investigation of the traffic 7 offense or the issuance of a citation for that offense."); Smith, 73 Or App at 292 (a check 8 "to confirm identification and to check for outstanding warrants is a procedure that 9 commonly accompanies traffic stops" and does not exceed the lawful basis for the stop); 10 State v. Perry, 39 Or App 37, 42, 591 P2d 379 (1979) (after officer "had a check by radio 11 and discovered no criminal record of any outstanding process for defendant, further 12 detention of defendant and his family was not justified"). 13 To the extent that defendant suggests that, even if a "records" check is 14 permissible, a "warrant" check is not, we disagree that any such distinction is possible on 15 this record. Neither the parties nor the trial court drew any legal distinction between a 16 records check and a warrant check. Nor have we or the Supreme Court done so in any 17 previous decision. Moreover, the record does not establish a factual basis for any such 18 distinction. The trial court specifically found, and the record supports the finding, that 19 the officer "asked the defendant for identification to issue a citation," and he received a 20 response from dispatch within a very few minutes. There is no indication that the 21 dispatcher required additional time to check for "warrants." Cf. Smith, 73 Or App at 292 7 1 ("A warrant check may become unreasonable under ORS 131.615(2) if, for instance, it 2 takes an inordinately long time to complete.") Thus, this case affords us no occasion to 3 decide whether a warrant check that significantly delays the issuance of a citation would 4 impermissibly extend a lawful traffic stop. 5 Finally, we reject defendant's suggestion that, because this case involves the 6 stop of a bicycle rather than a motor vehicle, no check of any sort was permissible. It is 7 true that an officer stopping a motor vehicle may have more to check than the stopped 8 person's identification; for example, the cases cited above generally indicate that a check 9 in a motor vehicle stop involves a check of a vehicle's registration and insurance 10 coverage. However, that does not change the nature of the inquiry under ORS 810.410 11 and Article I, section 9, concerning whether "the investigation reasonably [is] related to 12 that traffic infraction, the identification of persons, and the issuance of a citation[.]" 13 Rogers/Kirkeby, 347 Or at 623. 14 We conclude that, in the course of a lawful traffic stop, an officer's act of 15 contacting dispatch with a person's identifying information is reasonably related to the 16 identification of the person and the issuance of the citation. Determining that a defendant 17 is, in fact, the person he or she claims to be is reasonably related to the identification of 18 the person and the issuance of the citation. See, e.g., State v. Hebrard, 244 Or App 594, 19 596, 260 P3d 759 (2011) (officer who called in a defendant's name and date of birth to 20 dispatch received a response of "unable to locate"); State v. Backstrand, 231 Or App 621, 21 624, 220 P3d 748 (2009) (officer called dispatch "in order to ensure that the identification 8 1 cards were genuine," explaining, "[w]hen somebody has a fake ID, if we run it, it comes 2 back unable to locate."); State v. Chrisco, 223 Or App 380, 383, 196 P3d 10 (2008) 3 (dispatch informed officer that the defendant gave a date of birth that did not match the 4 date of birth of the name given). 5 In sum, the trial court correctly concluded that the officer's act of contacting 6 dispatch with identifying information about defendant, who was lawfully stopped, was 7 permissibly related to "the identification of [a person] and the issuance of a citation." 8 Rodgers/Kirkeby, 347 Or at 623. 9 Affirmed. 9
Some case metadata and case summaries were written with the help of AI, which can produce inaccuracies. You should read the full case before relying on it for legal research purposes.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
