WESTBROOK, ME · Cumberland County
322 ROOSEVELT TRAIL Water System
Consumer Confidence Report status
322 ROOSEVELT TRAIL 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 no open violations for 322 ROOSEVELT TRAIL.
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)
- ME0004228
- System type
- Community Water System
- Population served
- 46
- Service connections
- 1
- Ownership
- privately owned
- Water source
- groundwater (wells)
322 ROOSEVELT TRAIL is one of 536 community water systems in Maine in the 500 or fewer people size category, serving 46 people from groundwater.
As of August 1, 2026, its federal record holds 3 entries between 1998 and 2016, all of which EPA lists as closed. Nothing has been added since 2016.
All 3 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 inorganic chemicals.
Violation history
Monitoring, Regular
—Nitrate
April 1, 2016 – June 30, 2016
ResolvedMonitoring, Regular
—Nitrate
April 1, 2006 – June 30, 2006
ResolvedMonitoring, Regular
—Nitrate
April 1, 1998 – June 30, 1998
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| April 1, 2016 – June 30, 2016 | Monitoring, Regular | Nitrate | — | Resolved |
| April 1, 2006 – June 30, 2006 | Monitoring, Regular | Nitrate | — | Resolved |
| April 1, 1998 – June 30, 1998 | Monitoring, Regular | Nitrate | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- March 25, 2026State Public Notification received3 linked violations
- March 6, 2026State Formal Notice of Violation issued1 linked violation
- March 6, 2026State Public Notification requested1 linked violation
- March 6, 2026State Formal Notice of Violation issued1 linked violation
- March 6, 2026State Formal Notice of Violation issued1 linked violation
- March 6, 2026State Public Notification requested1 linked violation
- March 6, 2026State Public Notification requested1 linked violation
- October 27, 2023State Public Notification received1 linked violation
- October 27, 2023State Compliance achieved1 linked violation
- October 23, 2023State Formal Notice of Violation issued1 linked violation
- May 9, 2023State Formal Notice of Violation issued1 linked violation
- May 9, 2023State Public Notification requested1 linked violation
- April 27, 2023State Compliance achieved1 linked violation
- February 22, 2023State Public Notification received1 linked violation
- February 14, 2023State Formal Notice of Violation issued1 linked violation
- February 14, 2023State Public Notification requested1 linked violation
- December 29, 2022State Compliance achieved1 linked violation
- May 17, 2022State Public Notification received1 linked violation
- May 5, 2022State Public Notification requested1 linked violation
- May 5, 2022State Formal Notice of Violation issued1 linked violation
- March 9, 2022State Compliance achieved2 linked violations
- May 12, 2021State Intentional no-action1 linked violation
- April 12, 2021State Compliance achieved2 linked violations
- February 25, 2021State Public Notification received2 linked violations
- January 29, 2021State Compliance Meeting conducted1 linked violation
- January 29, 2021State Public Notification requested1 linked violation
- January 29, 2021State Technical Assistance Visit1 linked violation
- January 29, 2021State Formal Notice of Violation issued1 linked violation
- January 29, 2021State Compliance Meeting conducted1 linked violation
- January 29, 2021State Public Notification requested1 linked violation
- January 29, 2021State Technical Assistance Visit1 linked violation
- January 29, 2021State Formal Notice of Violation issued1 linked violation
- July 16, 2020State Public Notification received1 linked violation
- July 14, 2020State Compliance achieved1 linked violation
- July 1, 2020State Formal Notice of Violation issued1 linked violation
- April 13, 2020State Formal Notice of Violation issued1 linked violation
- March 25, 2020State Compliance achieved1 linked violation
- July 9, 2019State Public Notification received3 linked violations
- July 1, 2019State Public Notification requested3 linked violations
- July 1, 2019State Formal Notice of Violation issued1 linked violation
- June 11, 2019State Compliance achieved1 linked violation
- May 29, 2019State Formal Notice of Violation issued1 linked violation
- April 1, 2019State Public Notification requested3 linked violations
- April 1, 2019State Formal Notice of Violation issued1 linked violation
- March 27, 2019State Compliance achieved6 linked violations
- March 18, 2019State Public Notification requested1 linked violation
- March 18, 2019State Formal Notice of Violation issued1 linked violation
- December 17, 2018State Public Notification received1 linked violation
- December 4, 2018State Formal Notice of Violation issued1 linked violation
- December 4, 2018State Public Notification requested1 linked violation
- November 2, 2017State Public Notification received1 linked violation
- November 1, 2017State Public Notification received1 linked violation
- October 26, 2017State Public Notification requested1 linked violation
- October 26, 2017State Formal Notice of Violation issued1 linked violation
- October 26, 2017State Formal Notice of Violation issued1 linked violation
- October 24, 2017State Compliance achieved3 linked violations
- August 10, 2017State Public Notification received1 linked violation
- August 3, 2017State Public Notification requested1 linked violation
- August 3, 2017State Formal Notice of Violation issued1 linked violation
- August 3, 2017State Public Notification requested1 linked violation
- August 3, 2017State Formal Notice of Violation issued1 linked violation
- August 2, 2017State Public Notification requested1 linked violation
- August 2, 2017State Formal Notice of Violation issued1 linked violation
- August 1, 2017State Compliance achieved1 linked violation
- August 1, 2017State Compliance achieved2 linked violations
- May 30, 2017State Intentional no-action1 linked violation
- May 30, 2017State Intentional no-action1 linked violation
- May 30, 2017State Intentional no-action1 linked violation
- May 30, 2017State Intentional no-action1 linked violation
- May 30, 2017State Intentional no-action1 linked violation
- May 30, 2017State Intentional no-action1 linked violation
- December 7, 2016State Compliance achieved1 linked violation
- November 16, 2016State Formal Notice of Violation issued1 linked violation
- August 29, 2016State Public Notification received2 linked violations
- August 22, 2016State Compliance achieved2 linked violations
- August 17, 2016State Formal Notice of Violation issued1 linked violation
- August 17, 2016State Public Notification requested1 linked violation
- August 17, 2016State Formal Notice of Violation issued1 linked violation
- August 17, 2016State Public Notification requested1 linked violation
- April 28, 2015State Public Notification received4 linked violations
- April 21, 2015State Compliance achieved2 linked violations
- April 9, 2015State Formal Notice of Violation issued1 linked violation
- April 9, 2015State Formal Notice of Violation issued1 linked violation
- March 3, 2015State Compliance achieved2 linked violations
- February 9, 2015State Public Notification requested1 linked violation
- February 9, 2015State Formal Notice of Violation issued1 linked violation
- February 9, 2015State Formal Notice of Violation issued1 linked violation
- December 8, 2014State Public Notification received1 linked violation
- November 21, 2014State Formal Notice of Violation issued1 linked violation
- November 21, 2014State Public Notification requested1 linked violation
- October 10, 2014State Compliance achieved1 linked violation
- September 30, 2014State Formal Notice of Violation issued1 linked violation
- September 30, 2014State Public Notification requested1 linked violation
- September 24, 2014State Compliance achieved2 linked violations
- September 17, 2014State Public Notification received1 linked violation
- September 3, 2014State Formal Notice of Violation issued1 linked violation
- September 3, 2014State Public Notification requested1 linked violation
- August 8, 2014State Public Notification requested1 linked violation
- August 8, 2014State Formal Notice of Violation issued1 linked violation
- July 7, 2014State Compliance achieved1 linked violation
- March 7, 2014State Public Notification received2 linked violations
- March 4, 2014State Compliance achieved1 linked violation
- February 24, 2014State Formal Notice of Violation issued1 linked violation
- January 8, 2013State Compliance achieved1 linked violation
- December 4, 2012State Public Notification requested1 linked violation
- December 4, 2012State Formal Notice of Violation issued1 linked violation
- September 16, 2011State Intentional no-action5 linked violations
- September 6, 2011State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- August 26, 2011State Intentional no-action11 linked violations
- August 15, 2011State Compliance achieved2 linked violations
- November 18, 2009State Public Notification requested1 linked violation
- November 18, 2009State Public Notification requested2 linked violations
- November 18, 2009State Formal Notice of Violation issued1 linked violation
- March 12, 2007State Public Notification requested3 linked violations
- November 6, 2006State Public Notification requested1 linked violation
- November 6, 2006State Violation/Reminder Notice1 linked violation
- September 29, 2006State Violation/Reminder Notice1 linked violation
- September 29, 2006State Public Notification requested1 linked violation
- September 22, 2006State Public Notification requested1 linked violation
- January 27, 2006State Public Notification received5 linked violations
- January 27, 2006State Public Notification received3 linked violations
- December 28, 2005State Public Notification requested31 linked violations
- July 7, 2005State Compliance achieved6 linked violations
- February 15, 2005State Violation/Reminder Notice4 linked violations
- February 15, 2005State Public Notification requested24 linked violations
- February 4, 2005State Violation/Reminder Notice3 linked violations
- August 15, 2003State Compliance achieved13 linked violations
- May 19, 2003State Public Notification received3 linked violations
- September 27, 2002State Public Notification received1 linked violation
- September 25, 2002State Violation/Reminder Notice3 linked violations
- September 25, 2002State Technical Assistance Visit4 linked violations
- September 25, 2002State Boil Water Order2 linked violations
- September 25, 2002State Public Notification requested2 linked violations
- March 7, 2002State Public Notification requested2 linked violations
- March 7, 2002State Violation/Reminder Notice2 linked violations
- March 30, 1994State Violation/Reminder Notice2 linked violations
- March 15, 1994State Public Notification requested2 linked violations
Common questions
Is 322 ROOSEVELT TRAIL required to publish a Consumer Confidence Report?
- Yes. 322 ROOSEVELT TRAIL 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 322 ROOSEVELT TRAIL’s next Consumer Confidence Report due?
- 322 ROOSEVELT TRAIL’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does 322 ROOSEVELT TRAIL have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for 322 ROOSEVELT TRAIL.
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
COLE, MARC
207-591-0365
WESTBROOK, ME 04029