This case presents the question of whether alleged building code violations by a contractor, based on the construction work of a subcontractor, should be classified as a strict liability offense that does not require a mens rea element. The facts in this case are undisputed. Carriage Homes was a Minnesota corporation that engaged in multi-family residential and land-development projects.
See State v. Arkell,
Beginning in 1997, appellant worked with the City of Austin, Minnesota on a new development titled “Southwinds Development.” The development consists of a 7-acre parcel of land with 38 residential units. The Austin City Council approved appellant’s development plan on June 16, 1997. Appellant signed the Development Agreement on behalf of Carriage Homes. Appellant was involved in the planning of the Southwinds project to a point where he personally spoke with the Austin planning director and appeared at city council meetings. Construction work on Southwinds was subcontracted to several outside companies. The development was substantially completed in 1998. Id.
In July and August of 1999, and in June 2001, Craig Hoium, the community development director for the City of Austin, wrote a series of letters to appellant regarding grading, water drainage and roofing problems at the Southwinds Development. 1 Hoium further spoke with the construction supervisor of Southwinds, and other construction managers, but never directly spoke with appellant. Regarding the grading issue, exhibits at trial showed that elevations of certain homes were below grade, causing water to run toward structures. Following snowmelt or during rain conditions, some water pooling occurs in the driveways of certain residential units. After Carriage Homes was notified of the grading problem, it worked to a certain degree to fix the problem. The city inspectors allege that Carriage Homes did not do enough, as drainage issues remain.
Ulland Brothers, a local subcontractor based in Austin, performed the grading on the Southwinds Development. In doing so, Ulland Brothers attempted to implement plans drawn by B.R.W. Engineering, another independent subcontractor. B.R.W. prepared the engineering report, and Ulland performed the grading. 2 Appellant has no involvement or ownership in those entities other than the hiring of them as independent subcontractors. Appellant claims that he had no control over grading or drainage issues because he subcontracted all of those types of construction projects. He further claims that he has no education or experience in engineering.
On May 30, 2001, the state charged Carriage Homes and appellant with three misdemeanor counts each, alleging violations of the Uniform Building Code and thereby both an ordinance violation and a violation
The court of appeals affirmed without oral argument. It concluded that Minn. Stat. § 16B.69, which imposes misdemean- or liability for a violation of the State Building Code, is a public welfare statute.
Arkell,
I.
Minnesota Statutes § 16B.69 states: “A violation of the [building] code is a misdemeanor.” Appellant argues that he did not intend to violate the building code, and thought that subcontractors would take care of all regulatory issues. The district court and the court of appeals both concluded appellant’s intent to be irrelevant because they held Minn.Stat. 16B.69 to be a public welfare statute that requires strict liability.
Statutory construction is a legal determination reviewed under a de novo standard.
See In re A.A.E.,
As we previously recognized, the United States Supreme Court has noted that statutes “concerning ‘public welfare’ or ‘regulatory offenses,’ which typically ‘regulate potentially harmful or injurious items,’ are not subject to a presumption requiring proof of a mens rea to establish
The Supreme Court has recognized public welfare offenses in limited circumstances.
Staples,
In
Staples,
the defendant was convicted of possessing an illegal firearm.
Id.
at 600,
We have not previously dealt with the question of strict liability in relation to a building code. Generally, the distinction between strict liability crimes and those requiring a mens rea has been recognized in both our case law and statutes. In
State v. Florine,
In
State v. Loge,
Unlike the open bottle law in Loge, the building code does not have separate sections that include words, such ,as “knowingly,” which are indicative of intent. The legislature also provides for an appeals process for violations of the building code, where a person “aggrieved by the final decision of any municipality as to the application of the code * * * may, within 180 days of the decision, appeal to the commissioner.” Minn.Stat. § 16B.67 (2002). A provision that allows for appeals of such administrative decisions points toward possible ambiguity in building code requirements and enforcement that are subject to varied interpretation. These aspects raise questions as to whether it could have been intended as a strict liability statute. In Loge, we noted a particularly strong public policy rationale in finding strict liability. The same rationale does not exist in the present matter, where construction projects are regulated by building code enforcement officers and proof of an intentional violation is not insurmountable.
Strict liability statutes are generally disfavored, and legislative intent to impose strict criminal liability must be clear.
In re C.R.M.,
[Ljocal building officials have considerable discretion in enforcing and interpreting building code provisions, and this can lead to variation across and within municipalities. * * * Building officials also have considerable discretion in howthey interpret unclear or ambiguous portions of the code. 7
Importantly, and as an initial matter, we note that unlike other statutes which have been interpreted to impose strict liability such as hand grenades and chemical substances, the legislature has not even imposed the state building code on a statewide basis, which may lead to uneven, disparate enforcement of the state building code.
The present matter illustrates the difficult and varying levels of enforcement of a building code. It was not until 1999, after completion of the project, that the city cited improper grading and began sending letters to Carriage Homes. The complaint alleges a time frame for the violation as “[b]etween July 20, 2000, and April 11, 2001.” 8 It remains unclear as to the exact nature of the offense with which Arkell is being charged. The city appears to alternate between, on the one hand charging Arkell with a plain violation of the building code and, on the other hand, a failure to correct the violation once it was cited. Carriage Homes received development approval at various steps, and only a year after completion of construction was the company notified of problems (they were notified by four grading-related letters that were not admitted into evidence). These problems were vaguely described as “grading difficulties” that the drainage situation is not completed and “not all of it” flows correctly. There were no precise measurements introduced, and these letters outlining the complaint were relied upon to charge criminal violations. 9 In the end, appellant was charged with a crime, apparently because he failed to correct a violation after a significant amount of time had passed between construction and citation.
Further, appellant’s corporation did not perform the work that resulted in a building code violation. Instead, it relied on subcontractors and engineers to do their jobs correctly, while employing its own project managers for general supervision.
Arkell,
Given the facts of this case and the nature of building code violations, it is erroneous to classify appellant’s alleged crime as a strict liability offense. We therefore reverse the court of appeals’ decision to classify Minn.Stat. § 16B.69 as a public welfare or strict liability statute. In light of our conclusion that Minn.Stat. § 16B.69 is not a public welfare statute, we need not address the issue of Arkell’s liability under the responsible corporate offi
Reversed.
Notes
. The letters sent by inspectors to Carriage Homes regarding improper grading were not admitted into evidence and are not part of the record before the court.
. Charges were not brought against the subcontractors.
. The building code has been selectively adopted by certain cities in Minnesota. The City of Austin has incorporated the State Building Code into its ordinances. See Austin, Minn., City Code § 4.01 (1999). Violation of the State Building Code constitutes a misdemeanor. See Minn.Stat. § 16B.69.
. The restitution request amounts to $238,565.
.The court of appeals held that Minn.Stat. § 16B.69 is a public welfare statute because it “regulates activities that pervasively affect human health and safety because the State Building Code protects the public's health, safety, and welfare.”
Arkell,
. The district court sentenced Arkell to 90 days in jail and a $1,000 fine, with 80 days stayed if Arkell paid restitution and met other conditions. The possibility of imprisonment as a result of a building code violation, and the moral condemnation attached, should be carefully considered when assessing whether the building code is a strict liability statute.
See Strong,
. Office of the Legislative Auditor, State of Minnesota, Program Evaluation Report: Affordable Housing, Report No. 01-03 at 44 (2001), available at http://www.auditor.leg.state.mn.us/ped/pedrep/0103all.pdf (visited December 11, 2003).
. According to the complaint dated May 29, 2001, ''[b]etween July 20, 2000, and April 11, 2001, Defendants have not provided adequate draining, and as a result, have not allowed for proper storm water drainage through the common area.”
.We are also concerned that there appears to be an effort to replace civil proceedings by attaching a monetary restitution punishment in lieu of 80 days in jail where a traditional civil remedy was evidently not even sought.
