BANGOR, ME · Piscataquis County
COVERED BRIDGE APARTMENTS Water System
Consumer Confidence Report status
COVERED BRIDGE APARTMENTS 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 COVERED BRIDGE APARTMENTS.
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)
- ME0094501
- System type
- Community Water System
- Population served
- 25
- Service connections
- 10
- Ownership
- privately owned
- Water source
- groundwater (wells)
COVERED BRIDGE APARTMENTS is one of 536 community water systems in Maine in the 500 or fewer people size category, serving 25 people from groundwater.
As of August 1, 2026, its federal record holds 10 entries between 2009 and 2025, all of which EPA lists as closed.
Of the 10, 1 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, the Total Coliform Rules, and the Public Notice Rule and Revised PN Rule.
Violation history
Public Notification Violation for NPDWR Violation
—Public Notice
April 23, 2025 – June 19, 2025
ResolvedMonitoring, Regular
—Arsenic
January 1, 2025 – March 31, 2025
ResolvedConsumer Confidence Report Complete Failure to Report
—Consumer Confidence Rule
July 1, 2022 – August 1, 2022
ResolvedPublic Education
Health-basedLead and Copper Rule
March 2, 2020 – September 22, 2020
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
July 1, 2012 – July 31, 2012
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
January 16, 2012 – July 5, 2012
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
January 1, 2012 – January 31, 2012
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
December 1, 2011 – December 31, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
April 1, 2010 – June 30, 2010
ResolvedMaximum Contaminant Level Violation, Average
Health-basedArsenic
October 1, 2009 – December 31, 2009
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| April 23, 2025 – June 19, 2025 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| January 1, 2025 – March 31, 2025 | Monitoring, Regular | Arsenic | — | Resolved |
| July 1, 2022 – August 1, 2022 | Consumer Confidence Report Complete Failure to Report | Consumer Confidence Rule | — | Resolved |
| March 2, 2020 – September 22, 2020 | Public Education | Lead and Copper Rule | Health-based | Resolved |
| July 1, 2012 – July 31, 2012 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| January 16, 2012 – July 5, 2012 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| January 1, 2012 – January 31, 2012 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| December 1, 2011 – December 31, 2011 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| April 1, 2010 – June 30, 2010 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
| October 1, 2009 – December 31, 2009 | Maximum Contaminant Level Violation, Average | Arsenic | Health-based | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- July 21, 2025State Formal Notice of Violation issued1 linked violation
- June 24, 2025State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- June 17, 2025State Public Notification received1 linked violation
- May 29, 2025State Public Notification received1 linked violation
- May 29, 2025State Public Notification requested1 linked violation
- May 13, 2025State Formal Notice of Violation issued1 linked violation
- May 13, 2025State Public Notification requested1 linked violation
- April 15, 2025State Compliance achieved1 linked violation
- March 23, 2025State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- March 23, 2025State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- July 3, 2024State Compliance achieved1 linked violation
- March 14, 2024State Formal Notice of Violation issued1 linked violation
- March 13, 2023State Formal Notice of Violation issued1 linked violation
- August 1, 2022State Public Notification received2 linked violations
- March 9, 2022State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- March 9, 2022State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- March 9, 2022State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- March 9, 2022State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- June 7, 2021State Formal Notice of Violation issued1 linked violation
- June 7, 2021State Formal Notice of Violation issued1 linked violation
- September 22, 2020State Compliance achieved1 linked violation
- July 1, 2020State Compliance achieved1 linked violation
- March 6, 2020State Formal Notice of Violation issued1 linked violation
- March 5, 2020State Compliance achieved1 linked violation
- January 7, 2016State Intentional no-action4 linked violations
- November 10, 2015State Compliance achieved1 linked violation
- March 23, 2015State Formal Notice of Violation issued1 linked violation
- August 28, 2013State Public Notification received1 linked violation
- March 22, 2013State Compliance achieved1 linked violation
- February 26, 2013State Public Notification requested1 linked violation
- February 26, 2013State Formal Notice of Violation issued1 linked violation
- September 5, 2012State Compliance achieved1 linked violation
- August 17, 2012State Public Notification received1 linked violation
- August 6, 2012State Public Notification requested1 linked violation
- August 6, 2012State Formal Notice of Violation issued1 linked violation
- July 5, 2012State Public Notification received2 linked violations
- July 5, 2012State Compliance achieved2 linked violations
- June 29, 2012State Public Notification requested1 linked violation
- June 28, 2012State Public Notification requested1 linked violation
- May 30, 2012State Formal Notice of Violation issued1 linked violation
- May 29, 2012State Formal Notice of Violation issued1 linked violation
- February 14, 2012State Compliance achieved3 linked violations
- January 20, 2012State Public Notification requested1 linked violation
- January 20, 2012State Formal Notice of Violation issued1 linked violation
- December 16, 2011State Formal Notice of Violation issued2 linked violations
- December 16, 2011State Public Notification requested1 linked violation
- November 22, 2011State Public Notification received1 linked violation
- November 14, 2011State Formal Notice of Violation issued2 linked violations
- November 14, 2011State Public Notification requested1 linked violation
- December 7, 2010State Formal Notice of Violation issued1 linked violation
- August 17, 2010State Public Notification requested1 linked violation
- August 17, 2010State Formal Notice of Violation issued3 linked violations
- July 1, 2010State Public Notification requested2 linked violations
- July 1, 2010State Public Notification requested2 linked violations
- July 1, 2010State Public Notification requested2 linked violations
- December 2, 2009State Formal Notice of Violation issued2 linked violations
- December 2, 2009State Public Notification requested2 linked violations
- December 2, 2009State Public Notification requested2 linked violations
- March 24, 2009State Formal Notice of Violation issued2 linked violations
Common questions
Is COVERED BRIDGE APARTMENTS required to publish a Consumer Confidence Report?
- Yes. COVERED BRIDGE APARTMENTS 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 COVERED BRIDGE APARTMENTS’s next Consumer Confidence Report due?
- COVERED BRIDGE APARTMENTS’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does COVERED BRIDGE APARTMENTS have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for COVERED BRIDGE APARTMENTS.
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
GAGNON, LEE
207-265-4006
BANGOR, ME 04402