When Absolute Liability Is Allowed

When Absolute Liability Is Allowed

The culpability baseline gives way in one provision, § 2.05(1), whose lead-in states that the culpability requirements of §§ 2.01 and 2.02 do not apply to the categories it lists.¹ Two categories follow, and together they form a single rule with two gates. The first gate covers offenses that constitute violations, and it closes again where the requirement involved is included in the definition of the offense or where the court determines that applying it is consistent with effective enforcement of the law defining the offense. The second gate covers offenses defined by statutes other than the Code, and it opens only insofar as a legislative purpose to impose absolute liability for the offense, or for any material element of it, plainly appears.² Every instance of absolute liability the Code tolerates must pass through one of these two gates, so the question for any offense is which gate, if either, it fits.

The gates are narrow because each fences absolute liability in at a different point. A violation carries a sanction below that of a true crime, so a defendant whose fault was never proved is not condemned as a criminal. A non-Code statute may define a serious offense, and there the safeguard is a demand for a clear statement. A court may not infer absolute liability from silence or careless drafting, and a legislature that wants the result must make the choice visibly and answer for its moral cost. That demand follows from the baseline itself, which already reads silence about mental state to require fault. Because the gates work by different mechanisms, each gate carries its own limit. The exceptions written into the first gate, a mental state in the offense definition or culpability consistent with effective enforcement, have no counterpart in the second. The plain-purpose requirement of the second likewise does not govern the first. The next two subsections take the gates in turn, beginning with offenses classified as violations.

Offenses Classified as Violations

The first gate in § 2.05(1) opens for offenses that constitute violations. As to those offenses, the culpability requirements of §§ 2.01 and 2.02 do not apply, unless the requirement involved is included in the definition of the offense or the court determines that its application is consistent with effective enforcement of the law defining the offense.⁴ The gate is defined by classification. What matters is the grade and sanction the legislature attached to the offense, whatever the seriousness of the underlying conduct. The text has two parts: a category (violations) and two overrides that can close the gate again. A reader who remembers only the category will treat every violation as strict, which is the mistake the overrides exist to prevent. This gate also concerns offenses that are already violations. A different mechanism, taken up in the next major section, reduces a non-Code offense to a violation when a conviction rests on absolute liability.⁵

The Code gives the word violation a specific meaning, and the sanction supplies it. An offense is a violation when imprisonment, even for a day, is not an available sentence.⁶ Violations are not crimes, they do not carry the collateral consequences that follow a criminal conviction, and they may be punished only by a suspended sentence, a fine, or another civil penalty.⁷ They also give rise to no disability or legal disadvantage of the kind that attaches to a criminal conviction.⁸ A legislature that places an offense in this grade has therefore already decided that the offender will not be treated as a criminal.

That sanction ceiling explains why the Code is willing to lift culpability here. The central objection to strict liability, developed later in this chapter, is that it subjects a morally blameless actor to the stigma of a criminal conviction.⁹ A violation removes the thing the objection targets, because there is no prison term, no criminal label, and no disability to inflict on someone who may have done nothing wrong. What the State keeps is a cheap way to enforce minor rules in areas where proving fault is difficult or where prosecutions are numerous.¹⁰ The fine-only profile also suits corporate defendants, which cannot be imprisoned, and the Code's provision on corporate liability lists violations among the offenses for which a corporation may be convicted.¹¹

The same ceiling marks what this gate does not reach. In Garnett v. State a Maryland court read a second-degree rape statute as defining a strict liability offense that allows no mistake-of-age defense.¹² The statute made the offense a felony punishable by up to twenty years in prison.¹³ An offense with that penalty cannot be a violation, because a violation never authorizes imprisonment, so the first gate could never supply its strictness. For a statute defined outside the Code, strictness of that gravity would have to clear the second gate, which is the subject of the next subsection.

The two overrides follow the same logic as the category. The first closes the gate when the requirement involved is included in the definition of the offense. A legislature that writes knowingly or recklessly into an offense has made fault part of the wrong, and the violation label does not undo that choice. The second closes the gate when the court determines that applying the requirement is consistent with effective enforcement of the law defining the offense.¹⁴ Enforcement convenience is the justification for dropping culpability from violations, so where requiring culpability would not hamper enforcement, nothing remains to justify dropping it and the baseline governs again. Students lose this issue when they treat every violation as automatically strict.

The first step is a threshold about the sanction, while the last two depend on the particular offense's text and enforcement needs. Skipping to the overrides for an offense that carries a prison term wastes effort, because that offense can become strict only through the second gate, which asks whether a legislative purpose to impose absolute liability plainly appears.

Plain Legislative Purpose

The second gate in § 2.05(1) opens for offenses defined by statutes other than the Code. It lifts the culpability requirements of §§ 2.01 and 2.02 only insofar as a legislative purpose to impose absolute liability for the offense, or for any material element of it, plainly appears.¹⁶ What separates this gate from the violations gate is the question it asks. The violations gate classifies an offense by its sanction, so it cannot reach a statute that authorizes imprisonment. The plain-purpose gate classifies by source and then asks about legislative intent, so it can reach a non-Code statute of any seriousness, including a felony. An offense that the Code itself defines never passes through this gate, and it can become strict only as a violation. The inquiry therefore runs in two stages: first whether the statute is defined outside the Code, and then whether a purpose to impose absolute liability on the element in dispute plainly appears.

The word plainly makes this a clear-statement requirement, and its force shows most clearly against the baseline the Code sets for silent statutes. When a statute says nothing about mental state, the Code presumes that its culpability requirements apply and reads in purpose, knowledge, or recklessness.¹⁷ Silence therefore cannot double as the legislative purpose, because the baseline has already given silence a meaning, and that meaning is fault. In United States v. Cordoba-Hincapie the court described § 2.05 as the Code's sole and narrow exception to its insistence on mens rea and emphasized that a legislative intent to impose strict liability must "plainly appear."¹⁸

The standard also explains itself by what it prevents. Absolute liability removes the only filter that keeps a blameless actor out of the criminal system, so the Code insists that the choice be made visibly. A court that inferred strictness from careless drafting, or from its own guess about what the legislature would have wanted, would be making that choice for the legislature, and no legislator would answer to voters for it. Requiring the purpose to appear plainly leaves the decision, and its moral cost, with the body that is accountable for it. Courts applying other doctrines show a similar caution: in Morissette v. United States the Court cautioned against assuming that a legislature, without clear expression, intends to abolish intent as an ingredient of serious crimes.¹⁹ The same opinion traces how courts came to read silent regulatory statutes as dispensing with intent where penalties are small and a conviction does little damage to reputation.²⁰ Those features show why a legislature might choose strictness, but they do not show that a particular legislature did, and § 2.05(1)(b) requires that second showing. Students lose this issue when they treat silence about mental state as proof of a purpose to impose absolute liability.

Plain purpose can appear in a statute's wording and in its legislative history, and Garnett v. State shows both at work. Maryland's second-degree rape statute reached a perpetrator at least four years older than a victim under 14 and made the offense a felony punishable by up to twenty years in prison.²¹ The defendant was a 20-year-old with an I.Q. of 52, and the victim was 13.²² The court concluded that the plain language of the statute, viewed in its entirety, together with the legislative history of its creation, made it a strict liability offense that does not require the State to prove mens rea and allows no mistake-of-age defense.²³ The court recognized that the Model Penal Code generally rejects strict criminal liability.²⁴ That recognition did not change the reading, because the Code is a model that binds a jurisdiction only to the extent the jurisdiction enacts it, and the court's task was to find what its own legislature had chosen. For this gate, the case shows the kind of evidence that satisfies the standard, namely text and history pointing toward strictness. The twenty-year penalty also shows that the severity of the sanction is no precondition at this gate. In a jurisdiction that has adopted the Code, a conviction resting on that strictness would carry a consequence taken up in the next major section, because § 2.05(2)(a) reduces a non-Code offense to a violation when a conviction is based on absolute liability as to a material element.²⁵

An express clause is the plainest way for the purpose to appear. The child-solicitation statute in State v. Moser covers a child defined as 15 years of age or younger and states that "mistake as to age is not a defense."²⁶ Once a legislature writes that sentence, the purpose to make age an absolute-liability element is beyond dispute. An adult's belief that the other person was older then gives no defense on that element, because a mistake excuses only by negating a mental state the offense requires, and none is required here.²⁷ Strictness on age depends on what the legislature chose. Some states have softened statutory rape laws that once treated the victim's age as strict by allowing a defense when the defendant shows a reasonable belief that the partner was of age.²⁸

The statutory phrases "insofar as" and "any material element thereof" make the plain-purpose inquiry an element-by-element one.²⁹ A legislature may therefore decide that one element, such as the victim's age or a quantity threshold, carries absolute liability while every other element keeps the ordinary culpability requirement. Allowing the choice at that fine a grain keeps the strictness as narrow as the purpose behind it. A statute that is plainly strict about one element does not become strict about the act, the identity of the substance, or any other element merely because the legislature spoke to one of them.

The two scenarios differ only in whether the legislature spoke. Where it did, the weight element is strict and the plant-identity element is not, because the gate lifts the baseline only as far as the purpose reaches.³⁰ Where it did not, the Code's presumption of culpability governs the weight element, and a mistake that negates the required mental state defeats the charge.³¹

The third step is where most disputes are decided, because the first two are matters of classification and the fourth follows mechanically from the third. A statute that spells out its strictness, as the child-solicitation provision does, ends the inquiry at once. A statute that is merely quiet leaves the baseline in place, however regulatory it looks and however sensible strictness might seem.