VIDALIA, GA · Toombs County
PETROSS SUBDIVISION Water System
Consumer Confidence Report status
PETROSS SUBDIVISION 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 PETROSS SUBDIVISION.
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 Georgia’s official records. Always confirm current status with Georgia before making decisions based on this information.
System facts
- System ID (PWSID)
- GA2790015
- System type
- Community Water System
- Population served
- 151
- Service connections
- 58
- Ownership
- privately owned
- Water source
- groundwater (wells)
PETROSS SUBDIVISION is one of 2,261 community water systems in Georgia in the 500 or fewer people size category, serving 151 people from groundwater.
As of August 1, 2026, its federal record holds 27 entries between 1995 and 2025, all of which EPA lists as closed.
Of the 27, 11 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 and volatile organic chemicals.
Violation history
Maximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2025 – September 30, 2025
ArchivedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
January 1, 2025 – March 31, 2025
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
October 1, 2024 – December 31, 2024
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
April 1, 2024 – June 30, 2024
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2024 – June 30, 2024
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2023 – September 30, 2023
ResolvedMonitoring, Regular
—Gross Alpha, Excl. Radon and U
July 1, 2023 – September 30, 2023
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
July 1, 2023 – September 30, 2023
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2023 – March 31, 2023
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2017 – December 31, 2017
ResolvedMonitoring, Regular
—Gross Alpha, Excl. Radon and U
January 1, 2016 – March 31, 2016
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2016 – March 31, 2016
ResolvedMonitoring, Regular
—Combined Radium (-226 and -228)
January 1, 2016 – March 31, 2016
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2015 – September 30, 2015
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2015 – June 30, 2015
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2015 – March 31, 2015
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
July 1, 2014 – September 30, 2014
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
April 1, 2014 – June 30, 2014
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2014 – June 30, 2014
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
January 1, 2014 – March 31, 2014
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2014 – March 31, 2014
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
April 1, 2012 – June 30, 2012
ArchivedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2010 – September 30, 2010
ArchivedMonitoring, Regular
—1,1,2-Trichloroethane
January 1, 1995 – December 31, 1995
ResolvedMonitoring, Regular
—p-Dichlorobenzene
January 1, 1995 – December 31, 1995
ResolvedMonitoring, Regular
—Toluene
January 1, 1995 – December 31, 1995
ResolvedMonitoring, Regular
—Trichloroethylene
January 1, 1995 – December 31, 1995
Resolved
Archived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| July 1, 2025 – September 30, 2025 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Archived |
| January 1, 2025 – March 31, 2025 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| October 1, 2024 – December 31, 2024 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| April 1, 2024 – June 30, 2024 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| April 1, 2024 – June 30, 2024 | Monitoring, Regular | Combined Uranium | — | Resolved |
| July 1, 2023 – September 30, 2023 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2023 – September 30, 2023 | Monitoring, Regular | Gross Alpha, Excl. Radon and U | — | Resolved |
| July 1, 2023 – September 30, 2023 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| January 1, 2023 – March 31, 2023 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2017 – December 31, 2017 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2016 – March 31, 2016 | Monitoring, Regular | Gross Alpha, Excl. Radon and U | — | Resolved |
| January 1, 2016 – March 31, 2016 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2016 – March 31, 2016 | Monitoring, Regular | Combined Radium (-226 and -228) | — | Resolved |
| July 1, 2015 – September 30, 2015 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2015 – June 30, 2015 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2015 – March 31, 2015 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2014 – September 30, 2014 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| April 1, 2014 – June 30, 2014 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| April 1, 2014 – June 30, 2014 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2014 – March 31, 2014 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| January 1, 2014 – March 31, 2014 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2012 – June 30, 2012 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Archived |
| July 1, 2010 – September 30, 2010 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Archived |
| January 1, 1995 – December 31, 1995 | Monitoring, Regular | 1,1,2-Trichloroethane | — | Resolved |
| January 1, 1995 – December 31, 1995 | Monitoring, Regular | p-Dichlorobenzene | — | Resolved |
| January 1, 1995 – December 31, 1995 | Monitoring, Regular | Toluene | — | Resolved |
| January 1, 1995 – December 31, 1995 | Monitoring, Regular | Trichloroethylene | — | Resolved |
Archived closed in EPA's records (typically due to age or a data correction)Resolved addressed and confirmed by the state
Enforcement actions
- July 25, 2025State Public Notification received1 linked violation
- July 15, 2025State Public Notification requested1 linked violation
- July 15, 2025State Violation/Reminder Notice1 linked violation
- March 28, 2025State Public Notification received1 linked violation
- March 19, 2025State Violation/Reminder Notice1 linked violation
- March 19, 2025State Public Notification requested1 linked violation
- August 22, 2024State Compliance achieved1 linked violation
- August 1, 2024State Public Notification received3 linked violations
- July 24, 2024State Violation/Reminder Notice3 linked violations
- July 24, 2024State Public Notification requested3 linked violations
- July 14, 2024State Compliance achieved3 linked violations
- February 13, 2024State Public Notification received1 linked violation
- January 24, 2024State Violation/Reminder Notice1 linked violation
- January 24, 2024State Public Notification requested1 linked violation
- December 21, 2023State Violation/Reminder Notice1 linked violation
- December 21, 2023State Public Notification requested1 linked violation
- October 26, 2023State Public Notification received3 linked violations
- October 19, 2023State Violation/Reminder Notice3 linked violations
- October 19, 2023State Public Notification requested3 linked violations
- October 18, 2023State Compliance achieved7 linked violations
- October 5, 2023State Public Notification received1 linked violation
- September 19, 2023State Public Notification requested1 linked violation
- September 19, 2023State Violation/Reminder Notice1 linked violation
- June 28, 2023State Public Notification received1 linked violation
- June 6, 2023State Public Notification requested1 linked violation
- June 6, 2023State Violation/Reminder Notice1 linked violation
- March 23, 2023State Public Notification received1 linked violation
- February 21, 2023State Violation/Reminder Notice1 linked violation
- February 21, 2023State Public Notification requested1 linked violation
- March 24, 2020State Compliance achieved1 linked violation
- March 24, 2020State Public Notification received26 linked violations
- March 9, 2020State Public Notification requested2 linked violations
- March 9, 2020State Violation/Reminder Notice2 linked violations
- February 13, 2018State Compliance achieved1 linked violation
- June 14, 2017State Public Notification requested3 linked violations
- June 14, 2017State Violation/Reminder Notice3 linked violations
- August 15, 2016State Compliance achieved10 linked violations
- May 17, 2016State Compliance achieved3 linked violations
- February 25, 2015State Compliance achieved4 linked violations
- December 30, 2013State Administrative/Compliance Order with penalty issued31 linked violations
- August 24, 2012State Public Notification received2 linked violations
- August 22, 2012State Intentional no-action2 linked violations
- July 30, 2012State Public Notification requested3 linked violations
- July 30, 2012State Violation/Reminder Notice3 linked violations
- January 26, 2012State Violation/Reminder Notice2 linked violations
- November 1, 2011State Public Notification received2 linked violations
- October 31, 2011State Violation/Reminder Notice1 linked violation
- October 31, 2011State Public Notification requested1 linked violation
- September 13, 2011State Public Notification requested1 linked violation
- June 23, 2011State Public Notification received3 linked violations
- April 4, 2011State Violation/Reminder Notice3 linked violations
- July 27, 2010State Bilateral Compliance Agreement signed8 linked violations
- May 19, 2010State Public Notification requested2 linked violations
- May 19, 2010State Violation/Reminder Notice3 linked violations
- November 16, 2009State Public Notification requested2 linked violations
- April 4, 2007State Violation/Reminder Notice2 linked violations
- October 18, 2005State Bilateral Compliance Agreement signed4 linked violations
- October 18, 2005State Public Notification received4 linked violations
- April 29, 2005State Violation/Reminder Notice3 linked violations
- September 21, 2004State Violation/Reminder Notice2 linked violations
- September 21, 2004State Public Notification requested2 linked violations
- November 13, 2003State Violation/Reminder Notice1 linked violation
- July 15, 2003State Violation/Reminder Notice2 linked violations
- December 1, 2001Federal Compliance achieved42 linked violations
Common questions
Is PETROSS SUBDIVISION required to publish a Consumer Confidence Report?
- Yes. PETROSS SUBDIVISION 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 PETROSS SUBDIVISION’s next Consumer Confidence Report due?
- PETROSS SUBDIVISION’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does PETROSS SUBDIVISION have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for PETROSS SUBDIVISION.
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
MOBLEY, BILLY
912-532-2195
VIDALIA, GA 30474