BYARS, OK · McClain County
BYARS Water System
Current status
No open violations on record as of July 4, 2026.
This system's next federally required Consumer Confidence Report is due July 1, 2027, under the EPA's revised reporting rule.
Data sourced from the EPA ECHO database (SDWA bulk download), last refreshed July 4, 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)
Violation history
Monitoring, Regular
—Mercury
January 1, 2014 – December 31, 2016
ResolvedMonitoring, Regular
—Antimony, Total
January 1, 2014 – December 31, 2016
ResolvedMonitoring, Regular
—Atrazine
January 1, 2005 – December 31, 2007
ResolvedFollow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
October 1, 2000 – October 3, 2003
ResolvedFollow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
October 1, 1999 – October 3, 2003
ResolvedMaximum Contaminant Level Violation, Acute (TCR)
Health-basedColiform (TCR)
August 1, 1901 – August 31, 1901
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2014 – December 31, 2016 | Monitoring, Regular | Mercury | — | Resolved |
| January 1, 2014 – December 31, 2016 | Monitoring, Regular | Antimony, Total | — | Resolved |
| January 1, 2005 – December 31, 2007 | Monitoring, Regular | Atrazine | — | Resolved |
| October 1, 2000 – October 3, 2003 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Resolved |
| October 1, 1999 – October 3, 2003 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Resolved |
| August 1, 1901 – August 31, 1901 | Maximum Contaminant Level Violation, Acute (TCR) | Coliform (TCR) | Health-based | 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 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
- 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 Public Notification requested1 linked violation
- January 27, 2010State Violation/Reminder Notice1 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 18, 2006State Compliance achieved2 linked violations
- October 16, 2006State Public Notification received2 linked violations
- October 3, 2003State Compliance achieved3 linked violations
- July 30, 2001State Administrative/Compliance Order with penalty issued2 linked violations
Contact
BYARS
405-783-4255
BYARS, OK 74831