STEPHENVILLE, TX · Erath County
PIGEON ROAD ESTATES Water System
Consumer Confidence Report status
PIGEON ROAD ESTATES 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 PIGEON ROAD ESTATES.
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)
- TX0720027
- System type
- Community Water System
- Population served
- 114
- Service connections
- 38
- Ownership
- privately owned
- Water source
- groundwater (wells)
PIGEON ROAD ESTATES is one of 4,188 community water systems in Texas in the 500 or fewer people size category, serving 114 people from groundwater.
As of August 1, 2026, its federal record holds 28 entries between 2004 and 2024, all of which EPA lists as closed.
Of the 28, 14 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 Radionuclides and Revised Rad Rule, the Stage 1 Disinfectants and Disinfection Byproducts Rule, and the Total Coliform Rules.
Violation history
Monitoring, Routine (RTCR)
—Revised Total Coliform Rule
May 1, 2024 – May 31, 2024
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
November 22, 2019 – January 2, 2019
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
April 1, 2018 – June 30, 2018
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Uranium
October 1, 2017 – December 31, 2017
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
October 1, 2017 – December 31, 2017
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Uranium
July 1, 2017 – September 30, 2017
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
April 1, 2017 – June 30, 2017
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Uranium
January 1, 2017 – March 31, 2017
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2017 – March 31, 2017
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
January 1, 2017 – March 31, 2017
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
January 1, 2016 – March 31, 2016
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2010 – March 31, 2010
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2009 – December 31, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
October 1, 2009 – December 31, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Uranium
October 1, 2009 – December 31, 2009
ResolvedMonitoring and Reporting (DBP)
—Chlorine
January 1, 2007 – March 31, 2007
ResolvedMonitoring and Reporting (DBP)
—Chlorine
October 1, 2006 – December 31, 2006
ResolvedMonitoring and Reporting (DBP)
—Chlorine
July 1, 2006 – September 30, 2006
ResolvedMonitoring and Reporting (DBP)
—Chlorine
April 1, 2006 – June 30, 2006
ResolvedMonitoring and Reporting (DBP)
—Chlorine
January 1, 2006 – March 31, 2006
ResolvedMonitoring and Reporting (DBP)
—Chlorine
October 1, 2005 – December 31, 2005
ResolvedMonitoring and Reporting (DBP)
—Chlorine
July 1, 2005 – September 30, 2005
ResolvedMonitoring and Reporting (DBP)
—Chlorine
April 1, 2005 – June 30, 2005
ResolvedMonitoring and Reporting (DBP)
—Chlorine
January 1, 2005 – March 31, 2005
ResolvedMonitoring and Reporting (DBP)
—Chlorine
October 1, 2004 – December 31, 2004
ResolvedMonitoring and Reporting (DBP)
—Chlorine
July 1, 2004 – September 30, 2004
ResolvedMonitoring and Reporting (DBP)
—Chlorine
April 1, 2004 – June 30, 2004
ResolvedMonitoring and Reporting (DBP)
—Chlorine
January 1, 2004 – March 31, 2004
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| May 1, 2024 – May 31, 2024 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| November 22, 2019 – January 2, 2019 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| April 1, 2018 – June 30, 2018 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| October 1, 2017 – December 31, 2017 | Maximum Contaminant Level Violation, Average | Combined Uranium | Health-based | Resolved |
| October 1, 2017 – December 31, 2017 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| July 1, 2017 – September 30, 2017 | Maximum Contaminant Level Violation, Average | Combined Uranium | Health-based | Resolved |
| April 1, 2017 – June 30, 2017 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| January 1, 2017 – March 31, 2017 | Maximum Contaminant Level Violation, Average | Combined Uranium | Health-based | Resolved |
| January 1, 2017 – March 31, 2017 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2017 – March 31, 2017 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| January 1, 2016 – March 31, 2016 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| January 1, 2010 – March 31, 2010 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2009 – December 31, 2009 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2009 – December 31, 2009 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| October 1, 2009 – December 31, 2009 | Maximum Contaminant Level Violation, Average | Combined Uranium | Health-based | Resolved |
| January 1, 2007 – March 31, 2007 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| October 1, 2006 – December 31, 2006 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| July 1, 2006 – September 30, 2006 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| April 1, 2006 – June 30, 2006 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| January 1, 2006 – March 31, 2006 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| October 1, 2005 – December 31, 2005 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| July 1, 2005 – September 30, 2005 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| April 1, 2005 – June 30, 2005 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| January 1, 2005 – March 31, 2005 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| October 1, 2004 – December 31, 2004 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| July 1, 2004 – September 30, 2004 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| April 1, 2004 – June 30, 2004 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| January 1, 2004 – March 31, 2004 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- July 30, 2024State Public Notification received4 linked violations
- July 11, 2024State Compliance achieved4 linked violations
- July 25, 2019State Compliance achieved4 linked violations
- April 23, 2019State Compliance achieved4 linked violations
- April 23, 2019State Compliance achieved4 linked violations
- April 23, 2019State Compliance achieved5 linked violations
- April 23, 2019State Compliance achieved4 linked violations
- April 23, 2019State Compliance achieved4 linked violations
- April 23, 2019State Compliance achieved4 linked violations
- January 3, 2019State Public Notification requested4 linked violations
- September 26, 2018State Administrative/Compliance Order without penalty issued11 linked violations
- September 26, 2018State Public Notification received3 linked violations
- August 9, 2018State Violation/Reminder Notice1 linked violation
- August 9, 2018State Public Notification requested1 linked violation
- July 12, 2018State Compliance achieved5 linked violations
- July 10, 2018State Violation/Reminder Notice1 linked violation
- July 10, 2018State Public Notification requested1 linked violation
- July 5, 2018State Compliance achieved5 linked violations
- May 10, 2018State Public Notification received1 linked violation
- May 10, 2018State Public Notification received1 linked violation
- May 10, 2018State Public Notification received1 linked violation
- April 13, 2018State Public Notification requested1 linked violation
- April 13, 2018State Violation/Reminder Notice1 linked violation
- April 9, 2018State Public Notification received1 linked violation
- April 3, 2018State Public Notification requested1 linked violation
- April 3, 2018State Violation/Reminder Notice1 linked violation
- April 3, 2018State Public Notification requested1 linked violation
- April 3, 2018State Violation/Reminder Notice1 linked violation
- February 28, 2018State Public Notification requested1 linked violation
- February 28, 2018State Violation/Reminder Notice1 linked violation
- December 21, 2017State Public Notification received2 linked violations
- December 21, 2017State Public Notification received1 linked violation
- October 26, 2017State Public Notification requested1 linked violation
- October 26, 2017State Public Notification requested4 linked violations
- October 26, 2017State Violation/Reminder Notice1 linked violation
- October 20, 2017State Public Notification received4 linked violations
- October 13, 2017State Formal Notice of Violation issued6 linked violations
- September 13, 2017State Violation/Reminder Notice2 linked violations
- September 12, 2017State Public Notification requested2 linked violations
- September 12, 2017State Public Notification requested2 linked violations
- June 5, 2017State Public Notification received2 linked violations
- May 4, 2017State Public Notification requested2 linked violations
- May 4, 2017State Public Notification requested2 linked violations
- May 4, 2017State Public Notification requested4 linked violations
- January 27, 2017State Public Notification received4 linked violations
- December 28, 2016State Public Notification requested3 linked violations
- December 28, 2016State Violation/Reminder Notice2 linked violations
- December 28, 2016State Violation/Reminder Notice1 linked violation
- November 16, 2016State Public Notification requested1 linked violation
- November 16, 2016State Violation/Reminder Notice1 linked violation
- November 3, 2016State Public Notification received1 linked violation
- September 28, 2016State Public Notification requested2 linked violations
- July 15, 2016State Violation/Reminder Notice4 linked violations
- March 7, 2016State Public Notification requested1 linked violation
- March 7, 2016State Violation/Reminder Notice1 linked violation
- August 10, 2015State Administrative/Compliance Order without penalty issued15 linked violations
- April 21, 2015State Compliance achieved12 linked violations
- December 19, 2014State Formal Notice of Violation issued3 linked violations
- December 16, 2014State Public Notification requested2 linked violations
- December 16, 2014State Violation/Reminder Notice1 linked violation
- September 22, 2014State Public Notification received2 linked violations
- September 22, 2014State Public Notification received3 linked violations
- August 26, 2014State Public Notification requested1 linked violation
- June 3, 2014State Public Notification requested2 linked violations
- November 22, 2011State Public Notification received2 linked violations
- November 18, 2011State Violation/Reminder Notice1 linked violation
- November 18, 2011State Public Notification requested1 linked violation
- November 18, 2011State Violation/Reminder Notice1 linked violation
- November 18, 2011State Public Notification requested1 linked violation
- April 11, 2011State Formal Notice of Violation issued7 linked violations
- March 31, 2011State Public Notification requested3 linked violations
- March 31, 2011State Violation/Reminder Notice4 linked violations
- January 24, 2011State Compliance achieved13 linked violations
- January 3, 2011State Public Notification received3 linked violations
- May 11, 2010State Violation/Reminder Notice1 linked violation
- May 11, 2010State Public Notification requested4 linked violations
- May 11, 2010State Violation/Reminder Notice1 linked violation
- May 11, 2010State Public Notification requested4 linked violations
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Public Notification requested1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
- July 19, 2007State Violation/Reminder Notice1 linked violation
Common questions
Is PIGEON ROAD ESTATES required to publish a Consumer Confidence Report?
- Yes. PIGEON ROAD ESTATES 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 PIGEON ROAD ESTATES’s next Consumer Confidence Report due?
- PIGEON ROAD ESTATES’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does PIGEON ROAD ESTATES have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for PIGEON ROAD ESTATES.
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
AARDAL, GARY, C
254-965-5924
STEPHENVILLE, TX 76401-0001