Is BYARS required to publish a Consumer Confidence Report?

Yes. BYARS 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 BYARS’s next Consumer Confidence Report due?

BYARS’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.

BYARS, OK · McClain County

BYARS Water System

Consumer Confidence Report status

BYARS 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 BYARS.

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

System facts

System ID (PWSID): OK2004709
System type: Community Water System
Population served: 275
Service connections: 160
Ownership: local government
Water source: groundwater (wells)

BYARS is one of 1,277 community water systems in Oklahoma in the 500 or fewer people size category, serving 275 people from groundwater.

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

All 5 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 Lead and Copper Rule, inorganic chemicals, and synthetic organic chemicals.

Violation history

Monitoring, Regular
—
Cadmium
January 1, 2014 – December 31, 2016
Resolved
Monitoring, Regular
—
Picloram
January 1, 2005 – December 31, 2007
Resolved
Follow-up Or Routine LCR Tap M/R
—
Lead and Copper Rule
October 1, 2000 – October 3, 2003
Resolved
Follow-up Or Routine LCR Tap M/R
—
Lead and Copper Rule
October 1, 1998 – October 3, 2003
Resolved
Monitoring, Routine Major (TCR)
—
Coliform (TCR)
December 1, 1996 – December 31, 1996
Resolved

Resolved addressed and confirmed by the state

Period	Violation	Contaminant / rule	Health-based	Status
January 1, 2014 – December 31, 2016	Monitoring, Regular	Cadmium	—	Resolved
January 1, 2005 – December 31, 2007	Monitoring, Regular	Picloram	—	Resolved
October 1, 2000 – October 3, 2003	Follow-up Or Routine LCR Tap M/R	Lead and Copper Rule	—	Resolved
October 1, 1998 – October 3, 2003	Follow-up Or Routine LCR Tap M/R	Lead and Copper Rule	—	Resolved
December 1, 1996 – December 31, 1996	Monitoring, Routine Major (TCR)	Coliform (TCR)	—	Resolved

Resolved addressed and confirmed by the state

Enforcement actions

October 3, 2019State Public Notification received1 linked violation
October 3, 2019State Public Notification received1 linked violation
October 3, 2019State Public Notification received1 linked violation
October 3, 2019State Public Notification received1 linked violation
October 3, 2019State Public Notification received1 linked violation
October 3, 2019State Public Notification received1 linked violation
October 3, 2019State Public Notification received1 linked violation
October 3, 2019State Public Notification received1 linked violation
October 3, 2019State Public Notification received1 linked violation
October 3, 2019State Public Notification received1 linked violation
May 16, 2017State Compliance achieved10 linked violations
April 20, 2017State Public Notification requested10 linked violations
April 20, 2017State Violation/Reminder Notice10 linked violations
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achieved1 linked violation
August 4, 2016State Compliance achieved1 linked violation
August 4, 2016State Compliance achieved1 linked violation
August 4, 2016State Compliance achieved1 linked violation
August 4, 2016State Compliance achieved1 linked violation
August 4, 2016State Compliance achieved1 linked violation
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
August 4, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
January 2, 2014State Public Notification received1 linked violation
December 18, 2013State Violation/Reminder Notice1 linked violation
December 18, 2013State Public Notification requested1 linked violation
October 31, 2013State Compliance achieved1 linked violation
August 9, 2010State Compliance achieved1 linked violation
February 8, 2010State Public Notification received1 linked violation
January 27, 2010State Violation/Reminder Notice1 linked violation
January 27, 2010State Public Notification requested1 linked violation
September 11, 2009State Compliance achieved3 linked violations
September 11, 2009State Public Notification received3 linked violations
August 28, 2008State Administrative/Compliance Order with penalty issued3 linked violations
August 28, 2008State Public Notification requested3 linked violations
October 16, 2006State Public Notification received2 linked violations
February 23, 2004State Violation/Reminder Notice3 linked violations
February 23, 2004State Public Notification requested5 linked violations
October 3, 2003State Compliance achieved3 linked violations
July 30, 2001State Administrative/Compliance Order with penalty issued2 linked violations
October 10, 1991State Compliance achievedgeneral compliance action — not tied to a specific violation on record
October 1, 1991State Administrative/Compliance Order without penalty issued1 linked violation
August 15, 1991State Boil Water Order1 linked violation

Common questions

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

BYARS

405-783-4255

BYARS, OK 74831