LEVELLAND, TX · Hockley County
CITY OF LEVELLAND Water System
Consumer Confidence Report status
CITY OF LEVELLAND 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 CITY OF LEVELLAND.
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 Texas’s official records. Always confirm current status with Texas before making decisions based on this information.
System facts
- System ID (PWSID)
- TX1100002
- System type
- Community Water System
- Population served
- 12,652
- Service connections
- 5,826
- Ownership
- local government
- Water source
- surface water (rivers, lakes, or reservoirs)
CITY OF LEVELLAND is one of 385 community water systems in Texas in the 10,001 to 100,000 people size category, serving 12,652 people from surface water.
As of August 1, 2026, its federal record holds 20 entries between 1993 and 2025, all of which EPA lists as closed.
Of the 20, 10 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, the Public Notice Rule and Revised PN Rule, and the Total Coliform Rules.
Violation history
Lead Consumer Notice
—Lead and Copper Rule
December 30, 2025 – March 25, 2026
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
May 1, 2025 – June 16, 2025
ResolvedLSL Reporting
—LEAD AND COPPER RULE REVISIONS
October 17, 2024 – June 16, 2025
ResolvedLSL Inventory
Health-basedLEAD AND COPPER RULE REVISIONS
October 17, 2024 – June 16, 2025
ResolvedLead Consumer Notice
—Lead and Copper Rule
December 30, 2017 – April 18, 2018
ResolvedLead Consumer Notice
—Lead and Copper Rule
December 30, 2016 – January 24, 2017
ResolvedFollow-up Or Routine LCR Tap M/R
—Lead and Copper Rule
October 1, 2016 – October 6, 2017
ResolvedMonitoring, Source Water (GWR)
—E. COLI
December 1, 2013 – May 1, 2018
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
July 1, 2013 – July 31, 2013
ResolvedMonitoring, Routine Minor (TCR)
—Coliform (TCR)
June 1, 2013 – June 30, 2013
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
May 6, 2013 – June 26, 2013
ResolvedMonitoring, Source Water (GWR)
—E. COLI
November 1, 2012 – March 4, 2013
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
January 10, 2012 – February 26, 2012
ResolvedMonitoring, Routine Minor (TCR)
—Coliform (TCR)
September 1, 2011 – September 30, 2011
ResolvedMonitoring, Source Water (GWR)
—E. COLI
July 1, 2011 – January 19, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
October 1, 2008 – December 31, 2008
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
September 25, 2008 – February 20, 2014
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
August 21, 2008 – February 20, 2014
ResolvedMaximum Contaminant Level Violation, Average
Health-basedFluoride
July 1, 2008 – September 30, 2008
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
July 1, 1993 – July 31, 1993
Archived
Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| December 30, 2025 – March 25, 2026 | Lead Consumer Notice | Lead and Copper Rule | — | Resolved |
| May 1, 2025 – June 16, 2025 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| October 17, 2024 – June 16, 2025 | LSL Reporting | LEAD AND COPPER RULE REVISIONS | — | Resolved |
| October 17, 2024 – June 16, 2025 | LSL Inventory | LEAD AND COPPER RULE REVISIONS | Health-based | Resolved |
| December 30, 2017 – April 18, 2018 | Lead Consumer Notice | Lead and Copper Rule | — | Resolved |
| December 30, 2016 – January 24, 2017 | Lead Consumer Notice | Lead and Copper Rule | — | Resolved |
| October 1, 2016 – October 6, 2017 | Follow-up Or Routine LCR Tap M/R | Lead and Copper Rule | — | Resolved |
| December 1, 2013 – May 1, 2018 | Monitoring, Source Water (GWR) | E. COLI | — | Resolved |
| July 1, 2013 – July 31, 2013 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Resolved |
| June 1, 2013 – June 30, 2013 | Monitoring, Routine Minor (TCR) | Coliform (TCR) | — | Resolved |
| May 6, 2013 – June 26, 2013 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| November 1, 2012 – March 4, 2013 | Monitoring, Source Water (GWR) | E. COLI | — | Resolved |
| January 10, 2012 – February 26, 2012 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| September 1, 2011 – September 30, 2011 | Monitoring, Routine Minor (TCR) | Coliform (TCR) | — | Resolved |
| July 1, 2011 – January 19, 2012 | Monitoring, Source Water (GWR) | E. COLI | — | Resolved |
| October 1, 2008 – December 31, 2008 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| September 25, 2008 – February 20, 2014 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| August 21, 2008 – February 20, 2014 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| July 1, 2008 – September 30, 2008 | Maximum Contaminant Level Violation, Average | Fluoride | Health-based | Resolved |
| July 1, 1993 – July 31, 1993 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Archived |
Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
Enforcement actions
- March 25, 2026State Compliance achieved1 linked violation
- February 23, 2026State Violation/Reminder Notice1 linked violation
- June 16, 2025State Compliance achieved1 linked violation
- June 16, 2025State Public Notification received1 linked violation
- June 16, 2025State Compliance achieved2 linked violations
- June 16, 2025State Compliance achieved1 linked violation
- June 16, 2025State Public Notification received1 linked violation
- May 28, 2025State Violation/Reminder Notice1 linked violation
- March 31, 2025State Public Notification requested1 linked violation
- March 31, 2025State Public Notification requested1 linked violation
- March 31, 2025State Violation/Reminder Notice1 linked violation
- March 31, 2025State Violation/Reminder Notice1 linked violation
- May 1, 2018State Compliance achieved1 linked violation
- April 18, 2018State Compliance achieved1 linked violation
- February 15, 2018State Violation/Reminder Notice1 linked violation
- October 6, 2017State Compliance achieved1 linked violation
- January 24, 2017State Compliance achieved1 linked violation
- January 24, 2017State Public Notification received1 linked violation
- January 13, 2017State Violation/Reminder Notice1 linked violation
- October 31, 2016State Public Notification requested1 linked violation
- October 31, 2016State Violation/Reminder Notice1 linked violation
- January 22, 2016State Compliance achieved1 linked violation
- December 11, 2015State Compliance achievedgeneral compliance action — not tied to a specific violation on record
- December 8, 2015State Public Notification received1 linked violation
- October 30, 2015State Violation/Reminder Notice1 linked violation
- October 30, 2015State Public Notification requested1 linked violation
- June 9, 2014State Public Notification received1 linked violation
- March 7, 2014State Public Notification requested1 linked violation
- March 7, 2014State Violation/Reminder Notice1 linked violation
- February 20, 2014State Intentional no-action1 linked violation
- February 20, 2014State Intentional no-action1 linked violation
- February 18, 2014State Public Notification received1 linked violation
- December 3, 2013State Compliance achieved1 linked violation
- November 13, 2013State Violation/Reminder Notice1 linked violation
- November 13, 2013State Public Notification requested1 linked violation
- October 8, 2013State Public Notification received1 linked violation
- September 1, 2013State Compliance achieved2 linked violations
- August 27, 2013State Public Notification received1 linked violation
- August 27, 2013State Compliance achieved2 linked violations
- August 8, 2013State Violation/Reminder Notice1 linked violation
- August 8, 2013State Public Notification requested1 linked violation
- July 31, 2013State Violation/Reminder Notice1 linked violation
- July 31, 2013State Public Notification requested2 linked violations
- July 9, 2013State Public Notification received1 linked violation
- June 26, 2013State Compliance achieved2 linked violations
- June 21, 2013State Violation/Reminder Notice1 linked violation
- March 4, 2013State Compliance achieved1 linked violation
- February 4, 2013State Public Notification requested1 linked violation
- February 4, 2013State Violation/Reminder Notice1 linked violation
- March 6, 2012State Public Notification received1 linked violation
- February 26, 2012State Compliance achieved1 linked violation
- January 27, 2012State Violation/Reminder Notice1 linked violation
- January 19, 2012State Compliance achieved1 linked violation
- November 3, 2011State Violation/Reminder Notice1 linked violation
- November 3, 2011State Public Notification requested1 linked violation
- November 1, 2011State Compliance achieved1 linked violation
- October 18, 2011State Public Notification received1 linked violation
- August 25, 2011State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- August 25, 2011State Public Notification requested1 linked violation
- December 22, 2010State Formal Notice of Violation issued6 linked violations
- June 26, 2009State Public Notification requested1 linked violation
- June 26, 2009State Violation/Reminder Notice1 linked violation
- December 12, 2008State Public Notification received1 linked violation
- October 29, 2008State Violation/Reminder Notice1 linked violation
- October 29, 2008State Public Notification requested1 linked violation
Common questions
Is CITY OF LEVELLAND required to publish a Consumer Confidence Report?
- Yes. CITY OF LEVELLAND 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 CITY OF LEVELLAND’s next Consumer Confidence Report due?
- CITY OF LEVELLAND’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does CITY OF LEVELLAND have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for CITY OF LEVELLAND.
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
BUXKEMPER, BREANN
806-894-0113
LEVELLAND, TX 79336-1010