Background
Shortly after midnight on April 20, 2017, Shardel Ragin drove to Tiago’s Bar and Grill in Bridgeport, Connecticut, where eyewitness Tyrelle Noblin entered Ragin’s car and observed a semiautomatic firearm on his lap. Ragin told Noblin that the men leaving the bar “gonna get what they got coming to them,” then reversed toward the victim, Max Antione, and opened fire. Antione was shot while fleeing and pronounced dead at 12:44 a.m. Noblin contacted police a week later and identified Ragin as the shooter.
After an unsuccessful search of Ragin’s home and vehicle failed to locate his cell phone, police obtained a search warrant on May 8, 2017, directing T-Mobile to produce call-identifying information and cell site location information (CSLI) for the period April 20 through May 8, 2017. Because T-Mobile maintains records in Coordinated Universal Time (UTC) rather than Eastern Daylight Time (EDT), it produced data beginning at midnight UTC on April 20—which corresponded to 8:00 p.m. EDT on April 19, four hours before the murder. The records placed Ragin moving toward the bar from 11:43 to 11:52 p.m., showed his phone going dark near the bar between 11:52 p.m. and 1:00 a.m., and then tracked him to the vicinity of an associate’s home before he returned to his own.
Before trial, Ragin moved to suppress the cell phone records on grounds that the warrant lacked probable cause and particularity, was overbroad, and that the extra four hours of data fell outside the warrant’s scope. The trial court denied the motion. The jury convicted Ragin of murder and criminal possession of a pistol, and the court sentenced him to fifty years. He appealed directly to the Connecticut Supreme Court.
The Court’s Holding
The court unanimously affirmed the conviction. On probable cause, it held that the warrant affidavit—detailing Noblin’s eyewitness account, confirming Ragin’s phone number through probation records, and noting that the phone had not been found in the May 6 search—gave the issuing judge a sufficient basis to conclude that Ragin’s call records and location data for the post-murder period would aid both in locating the device and in the investigation and prosecution. No additional nexus between phone use and the crime was required under either the federal or state constitution.
On particularity, the court held that specifying a start date, end date, and year was sufficient to cabin the scope of the request; the warrant was not required to enumerate a time zone. The Bridgeport police and T-Mobile’s New Jersey custodian both operate in EDT, and there was no evidence the officers knew T-Mobile used UTC. The court distinguished its earlier decision in State v. Smith, 344 Conn. 229 (2022), which faulted a warrant for imposing no time parameters at all—a different defect from failing to specify a time zone.
Regarding the extra four hours of UTC data, the court announced a new rule: when a third-party provider enlisted to execute a technical search voluntarily supplies information beyond the warrant’s scope in an area where the defendant retains a legitimate expectation of privacy, the government’s retention and use of that information without a second warrant is subject to constitutional challenge. Nevertheless, the court declined to apply the exclusionary rule. It was not clear the defendant had a cognizable privacy interest in four hours of call-identifying data; his state constitutional argument was inadequately briefed; the police demonstrably had probable cause to seek precisely that data; there was no evidence of deliberate or reckless misconduct; and T-Mobile’s production represented a reasonable response to a facially valid warrant.
Key Takeaways
- A search warrant for cell phone records satisfies the Fourth Amendment’s particularity requirement by specifying numeric start and end dates; it need not designate a time zone when neither the issuing court nor the executing officers had reason to anticipate a UTC/local-time discrepancy.
- Connecticut now recognizes that government retention and use of data a third-party provider voluntarily produces beyond a warrant’s scope—in an area of legitimate privacy expectation—is subject to constitutional challenge and ordinarily requires a second warrant.
- Despite that new rule, the exclusionary rule will not apply where probable cause for the extra data was evident from the warrant itself, police conduct was neither deliberate nor reckless, and suppression would not meaningfully advance Fourth Amendment deterrence.
- The court reaffirmed that the federal and Connecticut probable cause standards are identical for CSLI, declining to find that article first, § 7 of the Connecticut constitution demands a heightened nexus showing.
Why It Matters
The decision is the first Connecticut Supreme Court ruling to address the practical problem of time-zone discrepancies in digital evidence production—a recurring issue as cloud and telecom providers routinely log events in UTC. By holding that a warrant need only supply numeric dates, the court reduces a potential suppression vector for prosecutors while placing the burden on defense counsel to challenge an intentional exploitation of temporal ambiguity rather than an innocent one.
More broadly, the court’s new rule requiring a second warrant before police may retain and use data a third party voluntarily oversupplies marks a meaningful, if limited, extension of digital privacy protections in Connecticut. The carve-out for cases where probable cause was already evident and police acted in good faith, however, means the rule’s practical bite will depend heavily on how courts evaluate the nexus between existing warrant authority and the overproduced data—an issue litigants in future cases will need to develop at the evidentiary hearing stage.