Skip to content

Pinkerton liability

Attribute a U.S. federal conspirator's criminal liability for a co-conspirator's substantive offense when it was committed in furtherance of the conspiracy, within its scope, and reasonably foreseeable.

Version
v1 · 2026-08-30 · History
Domain-specific #
2489
Origin domain
law
Subdomain
united states conspiratorial liability
Aliases
Pinkerton doctrine, Pinkerton rule

Core Idea

Pinkerton liability is a doctrine of United States conspiracy law under which a conspirator may be held liable for a substantive offense committed by another conspirator even without personally committing or aiding that offense, if the offense was undertaken in furtherance of the conspiracy, fell within its scope, and was a reasonably foreseeable consequence of the unlawful agreement. The name derives from Pinkerton v. United States (1946). Its precise availability, elements, instructions, and defenses vary across federal and state jurisdictions.

Scope of Application

The abstraction is literal wherever practitioners can identify the same constitutive roles, apply the same boundary tests, and obtain the same kind of output. The following habitats are uses of Pinkerton liability itself, not metaphors based only on resemblance.

  • Federal conspiracy prosecutions. Relating a participant to substantive offenses committed by co-conspirators.
  • Jury instructions. Separating conspiracy membership, offense proof, and each derivative nexus condition.
  • Withdrawal analysis. Determining the temporal reach of attribution after a participant leaves the agreement.
  • Doctrinal comparison. Contrasting Pinkerton, aiding and abetting, felony murder, and enterprise liability.
  • Legislative analysis. Examining jurisdictions that codify, limit, or reject conspiratorial attribution.
  • Culpability criticism. Assessing tension between agreement-based attribution and personal fault without erasing the positive-law doctrine.

Clarity

A clear account of Pinkerton liability must preserve the recognition invariant stated in the Core Idea rather than rely on the title alone. Identify the jurisdiction and authoritative formulation before listing elements. Prove conspiracy membership and the substantive offense separately from the derivative-attribution nexus. State the timing of membership, offense, termination, and any alleged withdrawal. Do not translate an abstract foreseeability test into advice about a pending case or a person's exposure.

Manages Complexity

Pinkerton liability manages complexity by replacing a diffuse field of observations or possible operations with a bounded role structure: conspiratorial agreement supplies an unlawful common plan supplies the relational basis for derivative attribution.; defendant membership supplies the person to whom liability is attributed must be a legally established participant at the relevant time.; co-conspirator actor supplies another participant commits the charged substantive offense.; substantive offense supplies a completed or attempted crime supplies liability distinct from the agreement itself.; furtherance nexus supplies the act advances, facilitates, conceals, or otherwise serves the conspiracy rather than being purely personal..

Abstract Reasoning

  1. Locate the controlling jurisdiction's cases, statutes, and pattern instructions. 2. Establish the charged conspiracy's objects and the defendant's membership interval. 3. Identify who committed each substantive offense and prove its elements independently. 4. Test whether the offense furthered and fell within the scope of the agreement. 5. Apply the jurisdiction's reasonable-foreseeability formulation to the established facts. 6. Assess termination, withdrawal, and other limiting doctrines at the correct time.

Knowledge Transfer

The strict upward abstraction is Responsibility Attribution. Pinkerton Liability instantiates Responsibility Attribution because it assigns criminal responsibility for an outcome to a person through a rule-governed relation to another actor and a shared unlawful agreement. Within united states conspiratorial liability, the full mechanism transfers literally when the same roles and boundary tests recur. Beyond that domain, only the parent-level skeleton should travel. Reusing the label Pinkerton liability after removing its constitutive vocabulary would hide a change of mechanism behind an analogy. The honest transfer rule is therefore two-stage: recognize the domain-specific pattern first, then lift only the parent relation that remains invariant under a substrate change.

Relationships to Other Abstractions

Local relationship map for Pinkerton liabilityParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Pinkerton liabilityDOMAINPrime abstraction: Responsibility Attribution — is a kind ofResponsibilityAttributionPRIME

Current abstraction Pinkerton liability Domain-specific

Parents (1) — more general patterns this builds on

  • Pinkerton liability is a kind of Responsibility Attribution Prime

    Pinkerton Liability instantiates Responsibility Attribution because it assigns criminal responsibility for an outcome to a person through a rule-governed relation to another actor and a shared unlawful agreement.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

Pinkerton liability sits in a sparse region of the domain-specific corpus (99th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (1565 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08