Is COVENTRY FIRE DISTRICT 1 required to publish a Consumer Confidence Report?

Yes. COVENTRY FIRE DISTRICT 1 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 COVENTRY FIRE DISTRICT 1’s next Consumer Confidence Report due?

COVENTRY FIRE DISTRICT 1’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.

COVENTRY, VT · Orleans County

COVENTRY FIRE DISTRICT 1 Water System

Consumer Confidence Report status

COVENTRY FIRE DISTRICT 1 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 COVENTRY FIRE DISTRICT 1.

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 Vermont’s official records. Always confirm current status with Vermont before making decisions based on this information.

System facts

System ID (PWSID): VT0005191
System type: Community Water System
Population served: 251
Service connections: 70
Ownership: local government
Water source: groundwater (wells)

COVENTRY FIRE DISTRICT 1 is one of 498 community water systems in Vermont in the 500 or fewer people size category, serving 251 people from groundwater.

As of August 1, 2026, its federal record holds 39 entries between 1992 and 2021, all of which EPA lists as closed. Nothing has been added since 2021.

Of the 39, 33 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 Stage 1 Disinfectants and Disinfection Byproducts Rule.

Violation history

Monitoring, Regular
—
Arsenic
October 1, 2021 – December 31, 2021
Resolved
Consumer Confidence Report Complete Failure to Report
—
Consumer Confidence Rule
July 1, 2020 – June 28, 2021
Resolved
Monitoring, Routine (RTCR)
—
Revised Total Coliform Rule
February 1, 2020 – February 29, 2020
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
January 1, 2020 – March 31, 2020
Resolved
Monitoring, Regular
—
Arsenic
July 1, 2018 – September 30, 2018
Resolved
Monitoring, Routine (RTCR)
—
Revised Total Coliform Rule
May 1, 2018 – May 31, 2018
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
April 1, 2018 – June 30, 2018
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
July 1, 2016 – September 30, 2016
Resolved
Monitoring, Regular
—
Arsenic
January 1, 2016 – March 31, 2016
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
January 1, 2015 – March 31, 2015
Resolved
Monitoring, Routine Major (TCR)
—
Coliform (TCR)
January 1, 2015 – January 31, 2015
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
July 1, 2014 – September 30, 2014
Resolved
Monitoring, Routine Major (TCR)
—
Coliform (TCR)
November 1, 2013 – November 30, 2013
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
October 1, 2013 – December 31, 2013
Resolved
Monitoring, Regular
—
Arsenic
October 1, 2012 – December 31, 2012
Resolved
Monitoring and Reporting (DBP)
—
Total Haloacetic Acids (HAA5)
July 1, 2012 – September 30, 2012
Resolved
Monitoring and Reporting (DBP)
—
TTHM
July 1, 2012 – September 30, 2012
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
October 1, 2011 – December 31, 2011
Resolved
Monitoring, Routine Minor (TCR)
—
Coliform (TCR)
October 1, 2011 – October 31, 2011
Resolved
Follow-up Or Routine LCR Tap M/R
—
Lead and Copper Rule
October 1, 2011 – June 23, 2015
Resolved
Monitoring, Repeat Major (TCR)
—
Coliform (TCR)
September 1, 2011 – September 30, 2011
Resolved
Monitoring and Reporting (DBP)
—
Chlorine
July 1, 2011 – September 30, 2011
Resolved
Monitoring, Routine Major (TCR)
—
Coliform (TCR)
November 1, 2010 – November 30, 2010
Resolved
Monitoring, Routine Major (TCR)
—
Coliform (TCR)
June 1, 2008 – June 30, 2008
Resolved
Monitoring, Repeat Minor (TCR)
—
Coliform (TCR)
October 1, 2007 – October 31, 2007
Resolved
Monitoring, Regular
—
Nitrate
January 1, 2007 – March 31, 2007
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
January 1, 2007 – March 31, 2007
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
October 1, 2006 – December 31, 2006
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
July 1, 2006 – September 30, 2006
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Arsenic
April 1, 2006 – June 30, 2006
Resolved
Monitoring, Regular
—
Cadmium
July 1, 2001 – September 30, 2001
Resolved
Monitoring, Regular
—
Thallium, Total
July 1, 2001 – September 30, 2001
Resolved
Monitoring, Regular
—
Nickel
July 1, 2001 – September 30, 2001
Resolved
Monitoring, Regular
—
Mercury
July 1, 2001 – September 30, 2001
Resolved
Monitoring, Routine Major (TCR)
—
Coliform (TCR)
December 1, 1997 – December 31, 1997
Resolved
Monitoring, Routine Major (TCR)
—
Coliform (TCR)
September 1, 1996 – September 30, 1996
Resolved
Monitoring, Routine Major (TCR)
—
Coliform (TCR)
November 1, 1992 – November 30, 1992
Resolved
Monitoring, Routine Major (TCR)
—
Coliform (TCR)
September 1, 1992 – September 30, 1992
Resolved
Monitoring, Routine Major (TCR)
—
Coliform (TCR)
May 1, 1992 – May 31, 1992
Resolved

Resolved addressed and confirmed by the state

Period	Violation	Contaminant / rule	Health-based	Status
October 1, 2021 – December 31, 2021	Monitoring, Regular	Arsenic	—	Resolved
July 1, 2020 – June 28, 2021	Consumer Confidence Report Complete Failure to Report	Consumer Confidence Rule	—	Resolved
February 1, 2020 – February 29, 2020	Monitoring, Routine (RTCR)	Revised Total Coliform Rule	—	Resolved
January 1, 2020 – March 31, 2020	Monitoring and Reporting (DBP)	Chlorine	—	Resolved
July 1, 2018 – September 30, 2018	Monitoring, Regular	Arsenic	—	Resolved
May 1, 2018 – May 31, 2018	Monitoring, Routine (RTCR)	Revised Total Coliform Rule	—	Resolved
April 1, 2018 – June 30, 2018	Monitoring and Reporting (DBP)	Chlorine	—	Resolved
July 1, 2016 – September 30, 2016	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
January 1, 2016 – March 31, 2016	Monitoring, Regular	Arsenic	—	Resolved
January 1, 2015 – March 31, 2015	Monitoring and Reporting (DBP)	Chlorine	—	Resolved
January 1, 2015 – January 31, 2015	Monitoring, Routine Major (TCR)	Coliform (TCR)	—	Resolved
July 1, 2014 – September 30, 2014	Monitoring and Reporting (DBP)	Chlorine	—	Resolved
November 1, 2013 – November 30, 2013	Monitoring, Routine Major (TCR)	Coliform (TCR)	—	Resolved
October 1, 2013 – December 31, 2013	Monitoring and Reporting (DBP)	Chlorine	—	Resolved
October 1, 2012 – December 31, 2012	Monitoring, Regular	Arsenic	—	Resolved
July 1, 2012 – September 30, 2012	Monitoring and Reporting (DBP)	Total Haloacetic Acids (HAA5)	—	Resolved
July 1, 2012 – September 30, 2012	Monitoring and Reporting (DBP)	TTHM	—	Resolved
October 1, 2011 – December 31, 2011	Monitoring and Reporting (DBP)	Chlorine	—	Resolved
October 1, 2011 – October 31, 2011	Monitoring, Routine Minor (TCR)	Coliform (TCR)	—	Resolved
October 1, 2011 – June 23, 2015	Follow-up Or Routine LCR Tap M/R	Lead and Copper Rule	—	Resolved
September 1, 2011 – September 30, 2011	Monitoring, Repeat Major (TCR)	Coliform (TCR)	—	Resolved
July 1, 2011 – September 30, 2011	Monitoring and Reporting (DBP)	Chlorine	—	Resolved
November 1, 2010 – November 30, 2010	Monitoring, Routine Major (TCR)	Coliform (TCR)	—	Resolved
June 1, 2008 – June 30, 2008	Monitoring, Routine Major (TCR)	Coliform (TCR)	—	Resolved
October 1, 2007 – October 31, 2007	Monitoring, Repeat Minor (TCR)	Coliform (TCR)	—	Resolved
January 1, 2007 – March 31, 2007	Monitoring, Regular	Nitrate	—	Resolved
January 1, 2007 – March 31, 2007	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
October 1, 2006 – December 31, 2006	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2006 – September 30, 2006	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
April 1, 2006 – June 30, 2006	Maximum Contaminant Level Violation, Average	Arsenic	Health-based	Resolved
July 1, 2001 – September 30, 2001	Monitoring, Regular	Cadmium	—	Resolved
July 1, 2001 – September 30, 2001	Monitoring, Regular	Thallium, Total	—	Resolved
July 1, 2001 – September 30, 2001	Monitoring, Regular	Nickel	—	Resolved
July 1, 2001 – September 30, 2001	Monitoring, Regular	Mercury	—	Resolved
December 1, 1997 – December 31, 1997	Monitoring, Routine Major (TCR)	Coliform (TCR)	—	Resolved
September 1, 1996 – September 30, 1996	Monitoring, Routine Major (TCR)	Coliform (TCR)	—	Resolved
November 1, 1992 – November 30, 1992	Monitoring, Routine Major (TCR)	Coliform (TCR)	—	Resolved
September 1, 1992 – September 30, 1992	Monitoring, Routine Major (TCR)	Coliform (TCR)	—	Resolved
May 1, 1992 – May 31, 1992	Monitoring, Routine Major (TCR)	Coliform (TCR)	—	Resolved

Resolved addressed and confirmed by the state

Enforcement actions

March 4, 2022State Public Notification requested3 linked violations
November 12, 2021State Compliance achieved1 linked violation
June 28, 2021State Public Notification received1 linked violation
June 28, 2021State Compliance achieved2 linked violations
June 28, 2021State Public Notification received1 linked violation
April 16, 2021State Technical Assistance Visit1 linked violation
April 16, 2021State Formal Notice of Violation issued2 linked violations
February 5, 2021State Compliance achieved1 linked violation
November 23, 2020State Public Notification requested1 linked violation
November 23, 2020State Formal Notice of Violation issued1 linked violation
November 20, 2020State Formal Notice of Violation issued2 linked violations
November 20, 2020State Public Notification requested1 linked violation
February 4, 2020State Compliance achieved1 linked violation
September 4, 2019State Compliance achieved1 linked violation
September 3, 2019State Compliance achieved1 linked violation
September 3, 2019State Compliance achievedgeneral compliance action — not tied to a specific violation on record
September 3, 2019State Compliance achieved18 linked violations
September 3, 2019State Compliance achieved1 linked violation
June 24, 2019State Public Notification received1 linked violation
June 24, 2019State Public Notification received1 linked violation
February 12, 2019State Compliance achieved1 linked violation
January 4, 2019State Public Notification received1 linked violation
December 19, 2018State Compliance achieved1 linked violation
November 14, 2018State Formal Notice of Violation issued1 linked violation
November 14, 2018State Public Notification requested1 linked violation
November 14, 2018State Technical Assistance Visit1 linked violation
July 19, 2018State Formal Notice of Violation issued1 linked violation
July 19, 2018State Formal Notice of Violation issued1 linked violation
July 19, 2018State Public Notification requested1 linked violation
July 19, 2018State Public Notification requested1 linked violation
June 30, 2017State Public Notification received1 linked violation
September 19, 2016State Public Notification received2 linked violations
September 19, 2016State Public Notification received1 linked violation
September 19, 2016State Public Notification received3 linked violations
September 19, 2016State Public Notification received3 linked violations
August 23, 2016State Public Notification requested1 linked violation
August 23, 2016State Technical Assistance Visit1 linked violation
August 23, 2016State Formal Notice of Violation issued1 linked violation
July 26, 2016State Compliance achieved1 linked violation
May 24, 2016State Formal Notice of Violation issued1 linked violation
May 24, 2016State Public Notification requested1 linked violation
May 24, 2016State Technical Assistance Visit1 linked violation
May 16, 2016State Public Notification received1 linked violation
May 16, 2016State Public Notification received1 linked violation
June 23, 2015State Compliance achieved8 linked violations
May 14, 2015State Public Notification received1 linked violation
March 16, 2015State Public Notification requested1 linked violation
March 16, 2015State Public Notification requested1 linked violation
March 16, 2015State Formal Notice of Violation issued1 linked violation
March 16, 2015State Formal Notice of Violation issued1 linked violation
October 7, 2014State Public Notification requested1 linked violation
October 7, 2014State Formal Notice of Violation issued1 linked violation
August 8, 2014State Compliance achieved1 linked violation
August 8, 2014State Compliance achieved1 linked violation
June 27, 2014State Public Notification received1 linked violation
June 27, 2014State Public Notification received1 linked violation
December 26, 2013State Formal Notice of Violation issued1 linked violation
December 26, 2013State Formal Notice of Violation issued1 linked violation
December 26, 2013State Public Notification requested1 linked violation
December 26, 2013State Public Notification requested1 linked violation
June 27, 2013State Public Notification received2 linked violations
June 27, 2013State Public Notification received1 linked violation
February 26, 2013State Public Notification requested1 linked violation
February 26, 2013State Technical Assistance Visit1 linked violation
February 26, 2013State Formal Notice of Violation issued1 linked violation
February 11, 2013State Compliance achieved2 linked violations
February 11, 2013State Compliance achieved3 linked violations
December 13, 2012State Technical Assistance Visit2 linked violations
December 13, 2012State Formal Notice of Violation issued2 linked violations
December 13, 2012State Public Notification requested2 linked violations
June 13, 2012State Public Notification received1 linked violation
June 13, 2012State Public Notification received1 linked violation
June 13, 2012State Public Notification received1 linked violation
June 13, 2012State Public Notification received1 linked violation
June 13, 2012State Public Notification received1 linked violation
February 21, 2012State Public Notification requested1 linked violation
February 21, 2012State Technical Assistance Visit1 linked violation
February 21, 2012State Formal Notice of Violation issued1 linked violation
February 2, 2012State Public Notification requested1 linked violation
February 2, 2012State Public Notification requested1 linked violation
February 2, 2012State Formal Notice of Violation issued1 linked violation
February 2, 2012State Formal Notice of Violation issued1 linked violation
January 4, 2012State Formal Notice of Violation issued1 linked violation
January 4, 2012State Public Notification requested1 linked violation
December 30, 2011State Public Notification requested1 linked violation
December 30, 2011State Formal Notice of Violation issued1 linked violation
December 29, 2010State Formal Notice of Violation issued1 linked violation
May 20, 2010State Public Notification received1 linked violation
September 1, 2009State Formal Notice of Violation issued1 linked violation
September 1, 2009State Public Notification requested1 linked violation
July 28, 2008State Public Notification received1 linked violation
July 28, 2008State Public Notification received1 linked violation
July 22, 2008State Formal Notice of Violation issued1 linked violation
July 22, 2008State Public Notification requested1 linked violation
January 14, 2008State Public Notification received1 linked violation
December 31, 2007State Formal Notice of Violation issued1 linked violation
December 31, 2007State Public Notification requested1 linked violation
November 27, 2007State Formal Notice of Violation issued1 linked violation
November 27, 2007State Public Notification requested1 linked violation
July 2, 2007State Public Notification received1 linked violation
June 11, 2007State Formal Notice of Violation issued1 linked violation
June 11, 2007State Public Notification requested1 linked violation
June 5, 2007State Formal Notice of Violation issued1 linked violation
June 5, 2007State Public Notification requested2 linked violations
January 12, 2007State Public Notification requested1 linked violation
November 13, 2006State Public Notification requested1 linked violation
November 13, 2006State Formal Notice of Violation issued1 linked violation
October 19, 2006State Public Notification requested1 linked violation
August 10, 2006State Formal Notice of Violation issued1 linked violation
June 8, 2006State Formal Notice of Violation issued1 linked violation
June 8, 2006State Public Notification requested1 linked violation
November 28, 2001State Public Notification received11 linked violations
November 26, 2001State Compliance achieved11 linked violations
November 19, 2001State Formal Notice of Violation issued22 linked violations
January 1, 1999State Public Notification requested1 linked violation
January 1, 1999State Formal Notice of Violation issued1 linked violation
July 2, 1998State Public Notification received1 linked violation
June 1, 1998State Violation/Reminder Notice1 linked violation
June 1, 1998State Public Notification requested1 linked violation
January 1, 1998State Public Notification requested1 linked violation
January 1, 1998State Violation/Reminder Notice1 linked violation
December 31, 1996State Public Notification requested1 linked violation
December 31, 1996State Violation/Reminder Notice1 linked violation
December 31, 1996State Public Notification requested1 linked violation
December 31, 1996State Violation/Reminder Notice1 linked violation
October 1, 1996State Public Notification requested1 linked violation
October 1, 1996State Public Notification requested2 linked violations
October 1, 1996State Violation/Reminder Notice2 linked violations
October 1, 1996State Violation/Reminder Notice1 linked violation
January 31, 1994State Administrative/Compliance Order with penalty issued2 linked violations
January 31, 1994State Administrative/Compliance Order with penalty issued3 linked violations
December 7, 1993State Compliance Meeting conducted4 linked violations
August 1, 1993State Violation/Reminder Notice1 linked violation
August 1, 1993State Public Notification requested1 linked violation
January 1, 1993State Public Notification requested1 linked violation
January 1, 1993State Violation/Reminder Notice1 linked violation
December 1, 1992State Public Notification requested1 linked violation
December 1, 1992State Violation/Reminder Notice1 linked violation
October 1, 1992State Violation/Reminder Notice2 linked violations
October 1, 1992State Violation/Reminder Notice1 linked violation
June 1, 1992State Public Notification requested3 linked violations
April 1, 1992State Violation/Reminder Notice1 linked violation
April 1, 1992State Public Notification requested2 linked violations
December 1, 1991State Public Notification requested2 linked violations
October 1, 1991State Public Notification requested2 linked violations
October 1, 1991State Public Notification requested4 linked violations
July 1, 1991State Violation/Reminder Notice3 linked violations
July 1, 1991State Public Notification received2 linked violations
March 1, 1991State Public Notification requested3 linked violations
October 1, 1990State Public Notification requested1 linked violation
January 1, 1900State Formal Notice of Violation issued1 linked violation

Common questions

Is COVENTRY FIRE DISTRICT 1 required to publish a Consumer Confidence Report?: Yes. COVENTRY FIRE DISTRICT 1 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 COVENTRY FIRE DISTRICT 1’s next Consumer Confidence Report due?: COVENTRY FIRE DISTRICT 1’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does COVENTRY FIRE DISTRICT 1 have any open drinking water violations on record?: As of August 1, 2026, EPA's federal records show no open violations for COVENTRY FIRE DISTRICT 1.
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

GERVAIS, DOMINIQUE

802-624-3044

COVENTRY, VT 05825