SAYRE, OK · Beckham County
SAYRE 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)
- OK2000508
- System type
- Community Water System
- Population served
- 4,375
- Service connections
- 1,667
- Ownership
- local government
- Water source
- groundwater (wells)
Violation history
Follow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
January 1, 2010 – August 11, 2010
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2010 – August 11, 2010 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- July 26, 2016State Compliance achieved1 linked violation
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achieved1 linked violation
- July 26, 2016State Compliance achieved1 linked violation
- July 26, 2016State Compliance achieved1 linked violation
- July 26, 2016State Compliance achieved1 linked violation
- July 26, 2016State Compliance achieved1 linked violation
- July 26, 2016State Compliance achieved1 linked violation
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- July 26, 2016State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- August 11, 2010State Compliance achieved1 linked violation
- March 5, 2010State Compliance achieved1 linked violation
- March 2, 2010State Public Notification received1 linked violation
- February 26, 2010State Public Notification received1 linked violation
- February 25, 2010State Violation/Reminder Notice1 linked violation
- February 8, 2010State Public Notification requested1 linked violation
- February 8, 2010State Administrative/Compliance Order with penalty issued1 linked violation
- January 27, 2010State Public Notification requested1 linked violation
- January 27, 2010State Violation/Reminder Notice1 linked violation
- February 13, 2004State Public Notification received3 linked violations
- October 2, 2003State Public Notification received1 linked violation
- September 25, 2003State Violation/Reminder Notice1 linked violation
- September 25, 2003State Public Notification requested1 linked violation
Contact
SAYRE
580-928-2260
SAYRE, OK 73662