Shield Public Safety Training · Police Technology Case Law Center

United States v. Thorne

No. 23-3054 (D.C. Cir. Mar. 17, 2026)

The D.C. Circuit decision applying good faith to a cell-site-simulator warrant challenged under Rule 41(b)’s territorial venue limits.

CourtU.S. Court of Appeals, D.C. Circuit
DecisionMarch 17, 2026
Opinion AuthorJudge Florence Y. Pan
Separate OpinionSenior Judge Judith W. Rogers
Target202-area-code cellphone
TechnologiesGPS ping and cell-site simulator
Issuing CourtD.C. magistrate judge
ExecutionBaltimore, Maryland
Rule at IssueFederal Rule 41(b)
Merits QuestionReserved
Core HoldingGood-faith exception applied
DispositionConvictions affirmed

Executive Summary

The Case in One Paragraph

After searching Linwood Thorne’s suspected D.C. residence and Maryland business, officers obtained an arrest warrant and sought to locate him through two associated cellphones. A D.C. magistrate judge issued GPS-ping and cell-site-simulator warrants for both numbers. Provider ping data placed Thorne’s 202-area-code phone in Baltimore, and a simulator deployed in Maryland pinpointed it at an apartment where officers arrested him. Thorne argued that the simulator warrant violated Federal Rule of Criminal Procedure 41(b) because the affidavit did not establish that the phone was within the District of Columbia when the D.C. judge issued the warrant. The D.C. Circuit affirmed denial of suppression without deciding what level of certainty Rule 41(b) requires or whether the warrant was valid. It held that the officers reasonably relied on the judicial warrant, adequately presented the venue issue, and engaged in no deliberate, reckless, or grossly negligent conduct. The opinion suggested—but expressly did not decide—that probable cause may be the proper Rule 41(b) standard and explained that probable cause can exist simultaneously in more than one adjoining district.

Core RuleEven assuming a cell-site-simulator warrant violated Rule 41(b)’s territorial requirements, evidence need not be suppressed when officers presented the venue facts to a neutral judge and relied on the issued warrant in objectively reasonable good faith.

Key Holdings at a Glance

Good Faith Decided the AppealThe court assumed a Rule 41(b) defect and held suppression unwarranted.
Merits Were ReservedThe court did not decide whether the issuing judge needed probable cause that the phone was inside D.C.
Officers Presented Venue FactsThe affidavit identified Thorne’s D.C. residence, his continued phone use, and Rule 41(b)(2).
Movement Outside the DistrictRule 41(b)(2) can cover property inside the district when issued but later moved outside it.
No Facial InvalidityThe target was mobile and the affidavit supplied a factual basis for possible D.C. location.
Multiple Probable LocationsProbable cause is below 50 percent and may support fair probabilities in more than one district.

Interstate Drug and Firearms Investigation

In 2018, the FBI, ATF, and Metropolitan Police Department investigated Omar Elbakkoush for drug and firearms trafficking across D.C., Maryland, and Virginia. Controlled purchases led agents to suspect Thorne was Elbakkoush’s heroin supplier.

Surveillance indicated that Thorne likely lived with his girlfriend at a Foote Street home in northeast D.C. and owned an auto body shop, Dou’ Perfect, in Clinton, Maryland. Search warrants executed at both locations produced large quantities of marijuana, heroin, fentanyl, firearms, drug equipment, and documents associated with Thorne.

After Thorne was indicted and an arrest warrant issued, officers attempted to locate him. Negotiations for voluntary surrender through attorneys did not succeed, so the Marshals Service, ATF, and FBI turned to his cellular devices.

The Maryland and D.C. Phone Numbers

Agents associated two numbers with Thorne. A 301-area-code number was tied to his Maryland auto body shop and confirmed by his girlfriend. A 202-area-code number came to investigators through an attorney attempting to arrange Thorne’s surrender.

Officers applied for a GPS-ping warrant and a cell-site-simulator warrant for each number. The Maryland-area-code phone was turned off and did not produce useful location results. The 202 number remained active.

Area Codes Are Weak Location EvidenceA phone number’s area code may support context, but number portability and ordinary mobility mean it cannot establish current physical location by itself.

GPS Pings and Cell-Site-Simulator Precision

The opinion carefully distinguished the two methods. A GPS-ping warrant directs the carrier to cause the phone to report coordinates and transmit the result to law enforcement. In the court’s description, pinging provided a location within roughly 500 to 1,000 meters.

A cell-site simulator mimics a tower, induces nearby devices to connect, receives identifying and directional information, and can be focused on the target phone. Continuous signal-strength and direction analysis can come close to the device’s exact location.

Ping results placed Thorne’s 202 phone in Baltimore. Officers then deployed the simulator in Maryland and pinpointed the phone at a Linden Avenue apartment, where they arrested him.

MethodOperatorFunction in Thorne
GPS pingCarrier acting under warrantPlaced phone in a broader Baltimore area
Cell-site simulatorLaw enforcement equipmentPinpointed the target apartment
Arrest warrantExecuting officersAuthorized Thorne’s apprehension
Phone-content warrantLater forensic searchAuthorized review of seized phone contents

Rule 41(b)’s Territorial Limits

Rule 41(b)(1) generally authorizes a magistrate judge to issue a warrant for a person or property located within the district. Rule 41(b)(2) also permits a warrant for property that is within the district when issued but may move outside the district before execution.

The D.C. application stated there was reason to believe the target phone was currently somewhere in the District because Thorne lived at the Foote Street address and continued using the device. It expressly invoked Rule 41(b)(2) for later location outside D.C.

Thorne argued that the judge needed probable cause—not merely reason to believe—that the phone was inside D.C. at issuance. Because evidence also connected him to Maryland, he maintained that the D.C. judge lacked territorial authority and the warrant was void from the outset.

Venue Is a Warrant ElementState the issuing court’s territorial basis expressly, identify facts showing where the mobile target is at issuance, and address expected movement and execution outside the district.

The District Court’s Reason-to-Believe Standard

The district court treated the Rule 41(b) issue as one of first impression and held that a “reason to believe” standard governed whether the phone was located within D.C. It found that Thorne’s D.C. residence and the phone’s 202 area code supplied that basis.

The district court rejected a probable-cause standard in part because evidence pointed toward both D.C. and Maryland. It feared that requiring probable cause would make a warrant unavailable in either jurisdiction when officers were trying to discover the phone’s location.

It also ruled alternatively that good faith would defeat suppression even if the warrant violated Rule 41(b). The D.C. Circuit affirmed solely on that alternative ground.

Why the Good-Faith Exception Applied

Under United States v. Leon, exclusion ordinarily does not deter police misconduct when officers objectively and reasonably rely on a warrant issued by a neutral judge.

The investigators did not conceal the venue problem. Their affidavit cited Rule 41(b)(2), stated why they believed the phone might be in D.C., explained Thorne’s D.C. residence, and noted his continued use of the device. The magistrate judge implicitly resolved her authority by issuing the warrant.

The appellate court found no deliberate, reckless, or grossly negligent conduct. The proper degree of certainty was novel and unsettled, and officers were entitled to submit that legal question to the magistrate judge. Any error was attributable to the issuing court, so suppression would add little deterrence.

Remedy, Not PermissionThorne protects objectively reasonable historical reliance. It does not authorize investigators to disregard territorial limits or draft venue allegations vaguely in future warrants.

Probable Cause Can Exist in More Than One District

Although it reserved the governing Rule 41(b) standard, the panel criticized part of the district court’s reasoning. Probable cause requires only a fair probability, is not a high bar, and demands less than 50-percent certainty.

Thus, the evidence could establish probable cause that the phone was in D.C. because Thorne resided there and also probable cause that it was in Maryland because he operated a business there. Those conclusions are not mathematically or legally inconsistent.

The court suggested there may be good reason to use the familiar, practical probable-cause standard for Rule 41(b), but explicitly left the question for another case.

Reserved QuestionDo not cite Thorne as holding that probable cause is definitively required—or definitively unnecessary—to establish Rule 41(b) territorial location.

Why the Warrant Was Not Facially Void

Thorne argued that a jurisdictionally defective warrant is void from the beginning and cannot support good faith. The court rejected that categorical argument.

Unlike warrants that openly targeted a fixed object or premises known to be outside the issuing district, this warrant concerned a mobile phone whose location was uncertain. The application offered facts supporting D.C. location and did not reveal an obvious territorial contradiction on its face.

Rule 41(b) also lacks the statutory suppression command found in some communications laws. The court held that good faith can apply to an alleged Rule 41(b) violation and joined the approach of other federal circuits.

The Court Did Not Decide Whether Simulator Use Is a Search

The government noted that the Fourth Amendment status of simulator use remained open in the circuit but did not argue that no warrant was required. The appellate court therefore did not decide the issue.

The case proceeded on an issued probable-cause simulator warrant. Its holding concerns venue and remedy—not whether investigators could have used the technique without judicial authorization.

Citation WarningThorne is not a no-search holding. It is a good-faith decision involving an expressly obtained cell-site-simulator warrant.

Judge Rogers’s Separate Opinion

Senior Judge Rogers joined the holding that the good-faith exception required affirmance. She declined to join the panel’s additional discussion of the unresolved Rule 41(b) standard.

Her separate opinion reinforces the limited nature of the binding result: good faith disposed of the appeal, and extended commentary about venue probability was unnecessary to judgment.

Precedential DisciplineSeparate the court’s holding from observations about an unresolved issue. Training and warrant drafting should not convert dicta into a settled rule.

Current Significance

Thorne is a current appellate reminder that sophisticated warrants have both substantive and territorial requirements. Probable cause connecting a suspect to a phone does not automatically establish which judge has authority to issue the warrant.

Investigations in metropolitan border areas must account for ordinary movement among districts. Agencies should consider parallel or coordinated applications, appropriate federal statutory authority, mobile-property provisions, and early consultation with prosecutors.

The opinion also confirms the importance of separating GPS-ping process, simulator authority, arrest authority, premises entry, seizure, and phone-content searches. Thorne’s investigators obtained distinct warrants for those stages.

Current Practice RuleUse simulator-specific probable-cause warrants that establish both investigative nexus and territorial authority, disclose uncertainty candidly, and plan lawful execution if the phone crosses district lines.

Practical Guidance for Agencies

Address Venue DirectlyIdentify the rule or statute giving the issuing judge territorial authority.
Establish Current LocationUse recent facts—not just an area code or historical address—to support district location.
Plan for MovementExplain why the phone may cross boundaries and which provision permits continued execution.
Separate TechniquesObtain clear authority for provider pings and direct simulator use.
Coordinate JurisdictionsConsult prosecutors and partner agencies before deployment across district lines.
Preserve the TimelineRecord issuance time, location evidence, pings, border crossing, deployment, and arrest.

Territorial Simulator Warrant Checklist

  1. Identify the offense, target, phone, provider, and all known device identifiers.
  2. Establish probable cause connecting the target to the device and investigative objective.
  3. State the issuing court’s territorial authority and governing provision.
  4. Provide current facts supporting the phone’s location when the warrant issues.
  5. Explain expected movement and authority for execution outside the district.
  6. Separate provider pinging from direct simulator operation.
  7. Define precision, duration, geography, deployment settings, and stopping events.
  8. Address homes, non-target devices, content limits, minimization, and deletion.
  9. Require logs and a return identifying where and how execution occurred.
  10. Seek renewed or parallel authority when material territorial facts change.

Cross-Border Operations Checklist

  1. Confirm issuance time, target identifiers, territorial basis, and expiration.
  2. Record the phone’s best-known location at the moment of issuance.
  3. Separate carrier ping results from simulator-derived information.
  4. Document each district entered and the legal basis for continued execution.
  5. Coordinate local agencies, prosecutors, supervisors, and technical operators.
  6. Pause before premises entry and confirm separate authority.
  7. Stop when the target is found, objective achieved, or authority ends.
  8. Preserve configuration, location, timing, readings, and operational decisions.
  9. Report deviations and obtain supplemental authority when required.
  10. Complete judicial returns, discovery, audit, and after-action review.

Litigation and Discovery Checklist

  1. Obtain every ping warrant, simulator warrant, affidavit, return, and arrest warrant.
  2. Build a time-and-location chronology from issuance through execution.
  3. Identify the precise territorial rule, statutory authority, and issuing judge’s jurisdiction.
  4. Test facts supporting device location at issuance—not only later ping results.
  5. Separate probable cause for the crime from probable cause or belief about venue.
  6. Determine whether the warrant was facially defective or presented an unsettled legal issue.
  7. Analyze the merits of any Rule 41 violation separately from good faith and prejudice.
  8. Distinguish binding holding from the panel’s reserved-standard discussion.
  9. Review protected-place entry, seizures, and later content warrants separately.
  10. Apply any superseding rule amendments and current circuit authority.

Frequently Asked Questions

What did United States v. Thorne hold?

The D.C. Circuit held that suppression was unwarranted because officers relied in good faith on a judicially issued cell-site-simulator warrant.

What was wrong with the warrant according to Thorne?

He argued that the D.C. magistrate lacked Rule 41(b) authority because the affidavit did not adequately establish that his phone was inside D.C. when the warrant issued.

Where was the phone ultimately located?

Provider pinging placed it in Baltimore, and a simulator pinpointed it at a Linden Avenue apartment.

Did the court decide the warrant was valid?

No. It assumed a possible Rule 41(b) error and resolved the appeal through good faith.

Did the court require probable cause for territorial location?

No definitive holding was issued. The panel suggested probable cause may be appropriate but reserved the question.

Can probable cause point to two districts?

Yes. The court explained that a fair probability can exist in more than one location because probable cause requires less than 50-percent certainty.

Did Thorne hold simulator use is not a search?

No. The government did not rely on that argument, and the court did not reach it.

Why did Judge Rogers write separately?

She agreed that good faith controlled but did not join the majority’s additional discussion of the unresolved Rule 41(b) standard.

Primary Authorities and Current Law

United States v. Thorne, No. 23-3054 (D.C. Cir. Mar. 17, 2026)
D.C. Circuit opinion affirming through good faith while reserving the Rule 41(b) standard.
Read United States v. Thorne
United States v. Thorne, 548 F. Supp. 3d 70 (D.D.C. 2021)
District-court opinion finding Rule 41 compliance and alternatively applying good faith.
Read the district-court decision
Federal Rule of Criminal Procedure 41
Federal warrant rule governing territorial authority and specified categories of searches.
Read Rule 41
United States v. Leon, 468 U.S. 897 (1984)
Supreme Court decision establishing the objective good-faith exception.
Read United States v. Leon
United States v. Magruder, 126 F.4th 671 (D.C. Cir. 2025)
D.C. Circuit decision applying good faith to an analogous alleged jurisdictional defect in cellular-location process.
Read United States v. Magruder

Final Assessment

United States v. Thorne is a good-faith decision with a forward-looking venue lesson. Investigators did many things correctly: they obtained simulator-specific warrants, identified the territorial issue, supplied current facts, and sought judicial resolution rather than acting unilaterally.

The opinion nevertheless leaves the governing Rule 41(b) standard open. Its observation that probable cause may exist simultaneously in D.C. and Maryland provides useful drafting guidance for mobile targets in adjoining jurisdictions, but it is not a definitive holding on the standard.

Shield Practice RuleFor mobile-phone tracking across borders, obtain technique-specific probable-cause authority; establish the target-device nexus and current territorial facts; cite the issuing court’s jurisdiction; explain anticipated movement; coordinate parallel jurisdictions when needed; separate pings, simulator use, arrest, entry, seizure, and content searches; preserve a precise execution timeline; and treat good faith as a retrospective remedy—not a substitute for venue planning.

Shield Public Safety Training · Police Technology Case Law Center

This monograph is provided for training and general informational purposes. It is not legal advice and does not replace review of the complete opinions, current statutes, court rules, controlling federal and state authority, provider requirements, agency policy, technical documentation, or consultation with prosecutors and agency counsel.

© 2026 Shield Public Safety Training. All rights reserved. Reviewed August 30, 2026.