Today, the court of appeals decided State v. Baker. Baker explains when a trial judge is required to make findings of fact when hearing a motion to suppress, and it raises what I think is an interesting search and seizure issue.
The facts were as follows. An officer was on patrol near a nursing facility where several minor crimes had recently been committed. He saw the defendant walking in the area at 11:00 p.m., and stopped him (or stopped to talk to him — more on this later). In part because the defendant was “fidgety” and smelled of alcohol, the officer decided to frisk him. The defendant had a gun in his pants, and the officer charged him with carrying a concealed weapon and with being a felon in possession of a firearm. The defendant moved to suppress. Both the officer and the defendant testified at the suppression hearing. The motion was denied, the defendant was convicted, and he appealed.
The court of appeals held that the trial judge erred in failing to make findings of fact and conclusions of law in violation of G.S. 15A-977(f). The court explained that a judge is excused from making findings only if (1) there is no material conflict in the evidence, and (2) the judge explains the reason for his decision clearly from the bench. In such a case, proper findings are implicit in the court’s ruling. If either condition is not met, however, the failure to make findings “is fatal to the validity of [the court’s] ruling and constitutes reversible error.”
Applying this standard to the case at bar, the court first noted that it had never previously reversed a trial judge for failing to make findings of fact in the face of conflicting evidence. It determined that a material conflict exists when “evidence presented by one party controverts evidence presented by an opposing party such that the outcome of the matter to be decided is likely to be affected.” (As an aside, I don’t see why it matters which party presents the evidence. If, for example, the state calls two officers to testify, and the officers contradict one another on an important point, it seems to me that there is a material conflict, even if the defendant doesn’t present any evidence.) The court found that standard to be satisfied, because the parties’ evidence conflicted about the number of officers who were present on the scene, a factor that could be relevant to whether the interaction was a “stop” or a consensual encounter.
The court’s procedural clarification of when findings are required is helpful. But, as I suggested at the beginning of this post, I think the substantive issue in this case is even more interesting. Here’s the heart of it: “Defendant argues that he was seized . . . when [the officer] activated his blue lights [which he did as he pulled his car directly behind the defendant]. The State contends that defendant was free to leave until the time the gun was found.” As far as I can tell from the opinion, the officer did not activate his siren. He explained that he turned on his lights “to notify other motorists of the presence of his patrol vehicle,” which apparently protruded into the road to some extent, not as a way of compelling the defendant to stop.
The court didn’t conclusively resolve the significance of the blue lights. That isn’t surprising, given that it remanded the case for further findings. It did state that “[t]he activation of blue lights on a police vehicle has been included among factors for consideration to determine when a seizure occurs.” My initial reaction was that the use of blue lights is conclusive, not merely a “factor[] for consideration.” Only police vehicles may be equipped with blue lights. G.S. 20-130.1(c). Motorists are required by law to pull over when an officer activates his blue lights and siren. G.S. 20-157. At least when a reasonable person would believe that the officer’s activation of his blue lights is directed at him, it seemed to me that the use of blue lights constitutes a show of authority. If the person stops, the interaction is a seizure. Cf. Brower v. County of Inyo, 489 U.S. 593 (1989) (characterizing “flashing lights and continuing pursuit” as a show of authority). See generally 4 Wayne R. LaFave, Search and Seizure § 9.4(a) (discussing what constitutes a show of authority). But the Fourth Circuit held that the use of blue lights does not always constitute a show of authority with respect to pedestrians in an interesting unpublished case. The dissent in United States v. Williams, 2000 WL 718395 (4th Cir. June 5, 2000), argued that “[a] reasonable person is certain to understand that when he is approached directly by a police cruiser with flashing red and blue lights, the officer is making a display of authority, not giving a safety warning.” But the majority noted that a pedestrian, unlike a motorist, is not required to stop in response to blue lights. Therefore, it concluded, when a pedestrian does stop upon seeing blue lights, he does so consensually. I admit that I’m not fully persuaded by Williams, but the issue does seem to be meatier than I initially believed. I would be very interested to hear readers’ analyses of it.
I do not see how a police cruiser blue-lighting a lone pedestrian along the side of the road at 11 o’clock at night can be anything but a seizure. No one would feel free to just carry on their way under these circumstances. If the officer was truly concerned about obstructing the roadway, I wonder if he could have parked elsewhere, as this was not an immediate emergency and caught up with Mr. Baker on foot? I wonder how straight the officer kept his face when testifying the blue lights were a “safety warning” as opposed to a show of authority.
Of course the blue lights are a show of authority and a seizure. We all know that if the person didn’t stop then the officer would charge him with Resist/Delay/Obstruct for not heeding them.
Frankly, it’s absolutely incredulous (and I believe disingenuous) to argue otherwise. Yet, I’m not surprised to hear that the prosecution and the Court have indulged such ludicrous “logic”. It’s tough to not get jaded by it.
The attorney general made the same argument in State v. Haislip during oral arguments. The court was not impressed with the position
That’s impressive mind-reading to know whether or not the court was impressed with a particular argument. Any clerk fresh out of law school, though, can tell you that the judges and justices are not so transparent and that it’s a fool’s errand to make predictions based on panel-members’ statements or demeanor.
JD
The Ct. of Appeals opinion in Haislip was issued over three years ago. It expressly rejected the State’s argument. So it doesn’t take a mind reader to know what the panel was thinking, just a reader.
I also thought it was disingenuous for the state to argue that the person was free to leave after the officer turned on the blue lights. It is hard to believe that if the suspect had run or walked away quickly, he would not have been “placed on the ground.”
Dan, the mind-reading goes to the Supreme Court’s view of the State’s argument. Les indicated the Court’s opinion during oral arguments, and per the June 6, 2007 calendar, the case was not orally argued in the Court of Appeals.
At least Les signs his name to his posts. It does not take a “mind-reader” to know whose words they are, nor to understand that “JD” can conveniently throw barbs without ever personally answering for them.