Is HAPPY TRAILS MHP required to publish a Consumer Confidence Report?

Yes. HAPPY TRAILS MHP is a community water system, and federal rules (40 CFR 141 Subpart O) require every community water system to publish a Consumer Confidence Report each year.

When is HAPPY TRAILS MHP’s next Consumer Confidence Report due?

HAPPY TRAILS MHP’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.

What is a Consumer Confidence Report?

A Consumer Confidence Report (CCR) is the annual drinking water quality report that community water systems must provide to the people they serve. It lists the contaminants detected in the system’s water during the year, where the water comes from, and how the results compare with federal limits. EPA’s revised CCR rule takes effect January 1, 2027, and the first reports in the new format are due July 1, 2027.

SABATTUS, ME · Sagadahoc County

HAPPY TRAILS MHP Water System

Consumer Confidence Report status

HAPPY TRAILS MHP must publish a Consumer Confidence Report — the annual drinking water quality report covering calendar year 2026 — by July 1, 2027.

As of August 1, 2026, EPA's federal records show 1 item for HAPPY TRAILS MHP that is open and awaiting resolution. None are health-based violations — open items of this kind are most often monitoring or reporting requirements, not water-safety findings.

Data sourced from the EPA ECHO database (SDWA bulk download), last refreshed August 1, 2026. This is a record-keeping and public-information tool — it does not replace Maine’s official records. Always confirm current status with Maine before making decisions based on this information.

System facts

System ID (PWSID): ME0003377
System type: Community Water System
Population served: 33
Service connections: 12
Ownership: privately owned
Water source: groundwater (wells)

HAPPY TRAILS MHP is one of 536 community water systems in Maine in the 500 or fewer people size category, serving 33 people from groundwater.

As of August 1, 2026, its federal record holds 10 entries between 1992 and 2017, of which 1 remains open; none are health-based.

Of the 10, 7 are monitoring and reporting requirements — the category that accounts for about four in five of all violations in EPA's national dataset — rather than findings about the water itself. The record involves the Total Coliform Rules, the Radionuclides and Revised Rad Rule, and the Public Notice Rule and Revised PN Rule.

Violation history

Monitoring, Additional Routine (RTCR)
—
Revised Total Coliform Rule
October 1, 2017 – October 31, 2017
Resolved
Monitoring, Regular
—
Gross Alpha, Excl. Radon and U
July 1, 2011 – September 30, 2011
Resolved
Public Notification Violation for NPDWR Violation
—
Public Notice
May 6, 2011
Addressed
Public Notification Violation for NPDWR Violation
—
Public Notice
February 14, 2010 – March 26, 2012
Resolved
Monitoring and Reporting (DBP)
—
TTHM
January 1, 2010 – December 10, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Uranium
January 1, 2006 – December 31, 2006
Resolved
Monitoring, Routine Major (TCR)
—
Coliform (TCR)
June 1, 2004 – June 30, 2004
Resolved
Monitoring, Regular
—
CYANIDE
January 1, 2001 – December 31, 2003
Resolved
Monitoring, Routine Major (TCR)
—
Coliform (TCR)
April 1, 1994 – April 30, 1994
Archived
Monitoring, Routine Major (TCR)
—
Coliform (TCR)
June 1, 1992 – June 30, 1992
Resolved

Resolved addressed and confirmed by the stateAddressed corrective action reported, pending final confirmationArchived closed in EPA's records (typically due to age or a data correction)

Period	Violation	Contaminant / rule	Health-based	Status
October 1, 2017 – October 31, 2017	Monitoring, Additional Routine (RTCR)	Revised Total Coliform Rule	—	Resolved
July 1, 2011 – September 30, 2011	Monitoring, Regular	Gross Alpha, Excl. Radon and U	—	Resolved
May 6, 2011	Public Notification Violation for NPDWR Violation	Public Notice	—	Addressed
February 14, 2010 – March 26, 2012	Public Notification Violation for NPDWR Violation	Public Notice	—	Resolved
January 1, 2010 – December 10, 2010	Monitoring and Reporting (DBP)	TTHM	—	Resolved
January 1, 2006 – December 31, 2006	Maximum Contaminant Level Violation, Average	Combined Uranium	Health-based	Resolved
June 1, 2004 – June 30, 2004	Monitoring, Routine Major (TCR)	Coliform (TCR)	—	Resolved
January 1, 2001 – December 31, 2003	Monitoring, Regular	CYANIDE	—	Resolved
April 1, 1994 – April 30, 1994	Monitoring, Routine Major (TCR)	Coliform (TCR)	—	Archived
June 1, 1992 – June 30, 1992	Monitoring, Routine Major (TCR)	Coliform (TCR)	—	Resolved

Resolved addressed and confirmed by the stateAddressed corrective action reported, pending final confirmationArchived closed in EPA's records (typically due to age or a data correction)

Enforcement actions

March 25, 2022State Compliance achieved1 linked violation
March 14, 2022State Formal Notice of Violation issued1 linked violation
February 3, 2022State Formal Notice of Violation issued1 linked violation
January 10, 2022State Compliance achieved1 linked violation
June 28, 2018State Compliance achieved2 linked violations
June 5, 2018State Public Notification received1 linked violation
March 30, 2018State Public Notification requested2 linked violations
March 12, 2018State Compliance achieved1 linked violation
November 28, 2017State Public Notification requested2 linked violations
November 9, 2017State Public Notification requested1 linked violation
November 2, 2017State Compliance achieved3 linked violations
April 18, 2017State Public Notification received2 linked violations
December 1, 2016State Public Notification requested2 linked violations
December 1, 2016State Formal Notice of Violation issued1 linked violation
March 31, 2016State Intentional no-action1 linked violation
July 3, 2012State Public Notification received1 linked violation
May 29, 2012State Bilateral Compliance Agreement signed13 linked violations
March 28, 2012State Compliance achieved3 linked violations
March 27, 2012State Public Notification received1 linked violation
February 17, 2012State Public Notification requested1 linked violation
February 17, 2012State Formal Notice of Violation issued1 linked violation
February 15, 2012State Formal Notice of Violation issued1 linked violation
February 15, 2012State Public Notification requested1 linked violation
February 13, 2012State Administrative/Compliance Order without penalty issued17 linked violations
February 3, 2012State Compliance achieved1 linked violation
December 15, 2011State Compliance achieved1 linked violation
December 2, 2011State Compliance achieved1 linked violation
December 2, 2011State Compliance achieved1 linked violation
November 29, 2011State Public Notification received1 linked violation
November 7, 2011State Compliance achieved2 linked violations
November 7, 2011State Compliance achieved1 linked violation
November 7, 2011State Compliance achievedgeneral compliance action — not tied to a specific violation on record
November 7, 2011State Public Notification requested1 linked violation
November 7, 2011State Formal Notice of Violation issued1 linked violation
November 7, 2011State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
November 7, 2011State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
November 7, 2011State Public Notification requested1 linked violation
November 7, 2011State Formal Notice of Violation issued1 linked violation
September 15, 2011State Intentional no-action4 linked violations
September 15, 2011State Intentional no-actiongeneral compliance action — not tied to a specific violation on record
August 4, 2011State Intentional no-action8 linked violations
May 20, 2011State Formal Notice of Violation issued1 linked violation
May 20, 2011State Public Notification requested1 linked violation
May 11, 2011State Public Notification received2 linked violations
May 5, 2011State Public Notification received3 linked violations
May 3, 2011State Formal Notice of Violation issued1 linked violation
May 3, 2011State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
May 3, 2011State Public Notification requested1 linked violation
May 3, 2011State Public Notification requested1 linked violation
May 3, 2011State Formal Notice of Violation issued1 linked violation
May 3, 2011State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
March 4, 2011State Public Notification received1 linked violation
March 4, 2011State Compliance achieved2 linked violations
December 29, 2010State Formal Notice of Violation issued1 linked violation
December 29, 2010State Public Notification requested1 linked violation
December 10, 2010State Compliance achieved2 linked violations
December 8, 2010State Public Notification requested2 linked violations
December 8, 2010State Formal Notice of Violation issued2 linked violations
August 10, 2010State Public Notification received1 linked violation
August 2, 2010State Public Notification requested1 linked violation
August 2, 2010State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
August 2, 2010State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
August 2, 2010State Formal Notice of Violation issued1 linked violation
August 2, 2010State Formal Notice of Violation issued1 linked violation
August 2, 2010State Public Notification requested1 linked violation
May 5, 2010State Public Notification requested1 linked violation
May 5, 2010State Formal Notice of Violation issued1 linked violation
November 18, 2009State Compliance achieved4 linked violations
August 4, 2009State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
August 4, 2009State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
July 24, 2009State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
July 24, 2009State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
July 23, 2009State Public Notification received2 linked violations
April 28, 2009State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
April 28, 2009State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
April 22, 2009State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
February 25, 2009State Bilateral Compliance Agreement signed6 linked violations
February 20, 2009State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
February 20, 2009State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
February 13, 2009State Public Notification requested1 linked violation
February 13, 2009State Formal Notice of Violation issued1 linked violation
February 11, 2009State Public Notification requested1 linked violation
February 11, 2009State Administrative/Compliance Order without penalty issued8 linked violations
February 11, 2009State Formal Notice of Violation issued1 linked violation
November 3, 2008State Formal Notice of Violation issued1 linked violation
November 3, 2008State Public Notification requested2 linked violations
September 4, 2008State Compliance Meeting conducted5 linked violations
September 3, 2008State Compliance Meeting conducted6 linked violations
August 5, 2008State Formal Notice of Violation issued1 linked violation
August 5, 2008State Public Notification requested1 linked violation
April 24, 2008State Administrative/Compliance Order without penalty issued8 linked violations
February 27, 2008State Public Notification requested1 linked violation
December 6, 2007State Compliance achievedgeneral compliance action — not tied to a specific violation on record
December 6, 2007State Compliance achieved1 linked violation
November 9, 2007State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
November 9, 2007State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
November 9, 2007State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
November 9, 2007State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
April 20, 2007State Compliance achieved3 linked violations
April 20, 2007State Compliance achieved4 linked violations
April 20, 2007State Compliance achieved22 linked violations
April 20, 2007State Compliance achieved9 linked violations
February 6, 2007State Public Notification requested1 linked violation
December 5, 2006State Administrative/Compliance Order without penalty issued48 linked violations
December 5, 2006State Administrative/Compliance Order without penalty issued32 linked violations
November 30, 2006State Bilateral Compliance Agreement signed12 linked violations
October 12, 2006State Public Notification requested2 linked violations
October 12, 2006State Violation/Reminder Notice4 linked violations
May 11, 2006State Public Notification received2 linked violations
May 11, 2006State Compliance achieved4 linked violations
May 11, 2006State Public Notification received2 linked violations
May 11, 2006State Public Notification received4 linked violations
May 11, 2006State Public Notification received3 linked violations
December 27, 2005State Violation/Reminder Notice3 linked violations
October 14, 2005State Violation/Reminder Notice4 linked violations
October 6, 2005State Public Notification received1 linked violation
September 1, 2004State Public Notification received11 linked violations
August 20, 2004State Public Notification requested4 linked violations
February 27, 2004State Public Notification requested1 linked violation
February 27, 2004State Violation/Reminder Notice2 linked violations
February 13, 2004State Formal Notice of Violation issued11 linked violations
July 25, 2003State Public Notification requested8 linked violations
May 21, 2003State Public Notification requested6 linked violations
February 19, 2002State Violation/Reminder Notice4 linked violations
July 25, 1994State Violation/Reminder Notice3 linked violations
September 22, 1993State Public Notification received1 linked violation
September 13, 1993State Compliance achieved2 linked violations
August 27, 1993State Public Notification requested2 linked violations
August 25, 1992State Violation/Reminder Notice2 linked violations
July 20, 1992State Public Notification requested2 linked violations
April 15, 1992State Compliance achieved2 linked violations

Common questions

Is HAPPY TRAILS MHP required to publish a Consumer Confidence Report?: Yes. HAPPY TRAILS MHP is a community water system, and federal rules (40 CFR 141 Subpart O) require every community water system to publish a Consumer Confidence Report each year.
When is HAPPY TRAILS MHP’s next Consumer Confidence Report due?: HAPPY TRAILS MHP’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does HAPPY TRAILS MHP have any open drinking water violations on record?: As of August 1, 2026, EPA's federal records show 1 item for HAPPY TRAILS MHP that is open and awaiting resolution. None are health-based violations — open items of this kind are most often monitoring or reporting requirements, not water-safety findings.
What is a Consumer Confidence Report?: A Consumer Confidence Report (CCR) is the annual drinking water quality report that community water systems must provide to the people they serve. It lists the contaminants detected in the system’s water during the year, where the water comes from, and how the results compare with federal limits. EPA’s revised CCR rule takes effect January 1, 2027, and the first reports in the new format are due July 1, 2027.

Contact

AMES, CHRIS

207-375-8299

SABATTUS, ME 04280