Willie James Clements, Jr. v. Commonwealth of Virginia

Court of Appeals of Virginia·Decided August 11, 2026·No. 2032244·Published

Opinion

COURT OF APPEALS OF VIRGINIA Record No. 2032-24-4

WILLIE JAMES CLEMENTS, JR.

v.

COMMONWEALTH OF VIRGINIA

Present: Judges O’Brien, Chaney and Callins Argued at Alexandria, Virginia Opinion Issued August 11, 2026

FROM THE CIRCUIT COURT OF ARLINGTON COUNTY Daniel S. Fiore, II, Judge

Kelsey Bulger, Deputy Appellate Counsel (Virginia Indigent Defense Commission, on briefs), for appellant.

Nassir Aboreden, Deputy Commonwealth’s Attorney (Parisa Dehghani-Tafti, Commonwealth’s Attorney; Abhimanyu Mehta, Deputy Commonwealth’s Attorney, on brief), for appellee.

Amici Curiae: Electronic Frontier Foundation, American Civil Liberties Union, and American Civil Liberties Union of Virginia (Matthew William Callahan; Andrew Gellis Crocker, on brief), for appellant.

PUBLISHED OPINION BY

JUDGE DOMINIQUE A. CALLINS

Perhaps it reduces to a matter about a smartphone. But in an era where the average American walks around with the “privacies of life” in their pocket, Riley v. California, 573 U.S. 373, 403 (2014) (quoting Boyd v. United States, 116 U.S. 616, 630 (1886)), this case raises significant questions about the balance between public safety and the constitutional right to privacy, including the extent to which law enforcement may leverage the former against the latter. As the U.S. Supreme Court has noted, “[t]he fact that technology now allows an individual to carry such information in his hand does not make the information any less worthy of the protection for which the Founders fought.” Id. “[T]he government’s unrestrained power

to assemble data” from nothing more than the keystrokes a citizen makes on their smartphone charts new territory in the possibilities of law enforcement investigations. United States v. Jones, 565 U.S. 400, 416 (2012) (Sotomayor, J., concurring).

That these questions loom over the jurisprudential horizon is not, however, determinative of the controversy presented here. Willie James Clements, Jr., appeals his conviction for leaving the scene of an accident and aggravated malicious wounding. Arlington police officers obtained a reverse-keyword search warrant to compel Google to identify Clements’s Google account and, ultimately, Clements himself. Clements argues the trial court erred in failing to suppress the evidence from a keyword-search warrant and in failing to grant his motion to strike the Commonwealth’s evidence as to causation. Moreover, Clements contends that, as an initial matter, the trial judge should have recused himself from the suppression hearing. We hold that the trial judge had no obligation to recuse himself after having signed the search warrant, that the exclusionary rule’s good-faith exception allows admission of evidence from the search, and that the causation finding was not plainly wrong or without evidentiary support. Thus, we affirm the trial court’s judgment.

BACKGROUND1

Around 2:20 a.m. on May 15, 2022, video footage outside an Arlington bar showed M.K.

holding her phone and “stumbling” about after ordering a rideshare to take her home. M.K. later testified that it had “been a long day” and that she “had a couple drinks.” A vehicle matching the description of her rideshare arrived, but a dark SUV with no front tag pulled up behind it.

1 We review the evidence in the light most favorable to the prevailing party in the trial court—here, the Commonwealth. Fary v. Commonwealth, 77 Va. App. 331, 341 (2023) (en banc); Cantrell v. Commonwealth, 65 Va. App. 53, 56 (2015). Further, we unseal facts found in the sealed record only to the extent we must discuss them. Brown v. Va. State Bar ex rel. Sixth Dist. Comm., 302 Va. 234, 240 n.2 (2023). And we refer to the survivor by initials to protect her privacy. Poole v. Commonwealth, 73 Va. App. 357, 360 n.1 (2021).

Instead of getting into the rideshare,2 M.K. tried opening the rear door of the dark SUV and eventually got into the front passenger seat. As the SUV was driving around fifty miles per hour, an eyewitness traveling near the car saw “something [get] thrown out of the car.” When they slowed near the object, they realized it was a woman, and surveillance footage from the street confirmed a person had fallen from the moving car. The SUV never returned to the scene.

When the police began searching for the SUV driver, they obtained M.K.’s cell phone location data, because they suspected her missing cell phone remained in the car after the suspect pushed her out. Historical cell-site location data led to a neighborhood in Maryland, where police found a “Black Chevrolet Traverse, [with] no front tag,” matching the description of the suspect’s vehicle. Police identified Clements as the suspect after finding the vehicle registered in his name.

M.K. had been pushed out of the SUV only half a mile from her home, and M.K.’s cellphone data “indicate[d] that the phone traveled . . . past [her] residence” before crossing the intersection where the incident occurred. With no evidence indicating the suspect knew M.K. and based on her appearing “extremely intoxicated” in the bar surveillance footage, police reasoned that in order to drive past M.K.’s home, the suspect would have searched her address in a “navigation system” to get directions to her home. On this premise, the police secured a keyword-search warrant3 for any Google account that searched M.K.’s address in Google the night of the incident. Specifically, the warrant authorized the collection of any accounts that on

2 According to the rideshare records, M.K.’s ride was canceled, and no pickup occurred.

3 “Reverse-keyword warrants operate differently than traditional warrants. With traditional warrants, investigators first identify a suspect or suspects, then obtain a warrant to search them or their property for evidence.” People v. Seymour, 536 P.3d 1260, 1268 (Colo. 2023). “However, reverse-keyword warrants start with a potentially incriminating piece of evidence—a search term like the address where the alleged [crime] occurred—then request a list of users implicated by that evidence.” Id.

May 15, 2022, from 2:15 a.m. to 3:15 a.m., searched M.K.’s address, or “any reasonable derivatives.” The warrant resulted in only one Google account that searched for her address at 2:22 a.m. on that date. After securing a second search warrant for the account’s information and the phone number associated with it, the police confirmed that the account was associated with Clements.4 In addition to M.K.’s address, Clements’s search history also included, “Arlington VA News, Police, Woman Jumps out of Vehicle,” and “Any suspect in Arlington VA News, Police, Woman Jumps out of Vehicle.”

A grand jury indicted Clements for leaving the scene of an accident and aggravated malicious wounding. Prior to trial, Clements moved to suppress the evidence discovered through the keyword-search warrant, arguing he had a reasonable expectation of privacy over what he searched. Clements also moved to recuse the trial judge from the case because he was the same judge who granted and signed the keyword-search warrant. In his motion, Clements compared the trial judge presiding over both proceedings to a “motion to reconsider,” noting that, unlike such a motion “where the court listens to an issue again with additional information,” his “motion to suppress brings into question the original ruling” and asks the court to “come to a different conclusion than [it] did previously.” The judge denied Clements’s motions, declining to recuse himself and finding probable cause supported the keyword-search warrant.

Clements moved to strike at the close of the Commonwealth’s case and again at the close of all evidence, arguing that the evidence was insufficient to prove causation, but the court denied both motions. The jury convicted Clements of leaving the scene of an accident resulting in injury to a person and aggravated malicious wounding. The trial court denied Clements’s motion to set aside the jury verdict. This appeal followed.

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

Willie James Clements, Jr. v. Commonwealth of Virginia, (Va. Ct. App. 2026).

Willie James Clements, Jr. v. Commonwealth of Virginia (Willie James Clements, Jr. v. Commonwealth of Virginia) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related

Boyd v. United States
116 U.S. 616 (Supreme Court, 1886)
Siler v. Louisville & Nashville Railroad
213 U.S. 175 (Supreme Court, 1909)
United States v. Di Re
332 U.S. 581 (Supreme Court, 1948)
Brinegar v. United States
338 U.S. 160 (Supreme Court, 1949)
Mapp v. Ohio
367 U.S. 643 (Supreme Court, 1961)
Stanford v. Texas
379 U.S. 476 (Supreme Court, 1965)
Coolidge v. New Hampshire
403 U.S. 443 (Supreme Court, 1971)
Ward v. Village of Monroeville
409 U.S. 57 (Supreme Court, 1972)
Stone v. Powell
428 U.S. 465 (Supreme Court, 1976)
Zurcher v. Stanford Daily
436 U.S. 547 (Supreme Court, 1978)
United States v. Leon
468 U.S. 897 (Supreme Court, 1984)
Maryland v. Garrison
480 U.S. 79 (Supreme Court, 1987)
Illinois v. Krull
480 U.S. 340 (Supreme Court, 1987)
Arizona v. Evans
514 U.S. 1 (Supreme Court, 1995)
Ornelas v. United States
517 U.S. 690 (Supreme Court, 1996)
United States v. Grubbs
547 U.S. 90 (Supreme Court, 2006)
Herring v. United States
555 U.S. 135 (Supreme Court, 2009)
Kentucky v. King
131 S. Ct. 1849 (Supreme Court, 2011)