OCEAN SPRINGS, MS · Jackson County
COLONIAL ESTATES # 3 Water System
Consumer Confidence Report status
COLONIAL ESTATES # 3 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 COLONIAL ESTATES # 3.
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 Mississippi’s official records. Always confirm current status with Mississippi before making decisions based on this information.
System facts
- System ID (PWSID)
- MS0300064
- System type
- Community Water System
- Population served
- 140
- Service connections
- 53
- Ownership
- privately owned
- Water source
- groundwater (wells)
COLONIAL ESTATES # 3 is one of 879 community water systems in Mississippi in the 500 or fewer people size category, serving 140 people from groundwater.
As of August 1, 2026, its federal record holds 41 entries between 1981 and 2024, all of which EPA lists as closed.
Of the 41, 37 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 Lead and Copper Rule, and the Stage 1 Disinfectants and Disinfection Byproducts Rule.
Violation history
LSL Inventory
Health-basedLEAD AND COPPER RULE REVISIONS
October 17, 2024 – February 6, 2025
ResolvedLSL Reporting
—LEAD AND COPPER RULE REVISIONS
October 17, 2024 – February 6, 2025
ResolvedMonitoring and Reporting (DBP)
—Chlorine
April 1, 2022 – June 30, 2022
ResolvedMonitoring, Routine (RTCR)
—Revised Total Coliform Rule
April 1, 2022 – April 30, 2022
ResolvedMonitoring, Routine (RTCR)
—Revised Total Coliform Rule
June 1, 2016 – June 30, 2016
ResolvedMonitoring and Reporting (DBP)
—Chlorine
April 1, 2016 – June 30, 2016
ResolvedFailure To Address Deficiency
Health-basedGroundwater Rule
September 1, 2013 – January 17, 2020
ResolvedMonitoring, Regular
—Radium-226
April 1, 2011 – June 30, 2011
ResolvedMonitoring, Regular
—Radium-228
April 1, 2011 – June 30, 2011
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2011 – June 30, 2011
ResolvedMonitoring, Regular
—Radium-226
January 1, 2011 – March 31, 2011
ResolvedMonitoring, Regular
—Radium-228
January 1, 2011 – March 31, 2011
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2011 – March 31, 2011
ResolvedMonitoring, Regular
—Radium-226
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Radium-228
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Radium-226
July 1, 2010 – September 30, 2010
ResolvedMonitoring, Regular
—Radium-228
July 1, 2010 – September 30, 2010
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2010 – September 30, 2010
ResolvedMonitoring, Regular
—Radium-228
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Radium-226
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2010 – March 31, 2010
ResolvedMonitoring, Regular
—Radium-228
January 1, 2010 – March 31, 2010
ResolvedMonitoring, Regular
—Radium-226
January 1, 2010 – March 31, 2010
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2009 – December 31, 2009
ResolvedMonitoring, Regular
—Radium-228
October 1, 2009 – December 31, 2009
ResolvedMonitoring, Regular
—Radium-226
October 1, 2009 – December 31, 2009
ResolvedMonitoring, Regular
—Radium-228
July 1, 2009 – September 30, 2009
ResolvedMonitoring, Regular
—Radium-226
July 1, 2009 – September 30, 2009
ResolvedMonitoring, Regular
—Combined Uranium
July 1, 2009 – September 30, 2009
ResolvedMonitoring, Regular
—Radium-226
April 1, 2009 – June 30, 2009
ResolvedMonitoring, Regular
—Radium-228
April 1, 2009 – June 30, 2009
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2009 – June 30, 2009
ResolvedMonitoring, Regular
—Radium-228
January 1, 2009 – March 31, 2009
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2009 – March 31, 2009
ResolvedMonitoring, Regular
—Radium-226
January 1, 2009 – March 31, 2009
ResolvedMonitoring, Regular
—Combined Uranium
October 1, 2008 – December 31, 2008
ResolvedPublic Notification Violation for NPDWR Violation
—Public Notice
October 1, 2008 – June 28, 2012
ResolvedMonitoring, Regular
—Radium-228
October 1, 2008 – December 31, 2008
ResolvedNotification, Public
—No contaminant on record
July 1, 1981 – July 31, 1981
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 |
|---|---|---|---|---|
| October 17, 2024 – February 6, 2025 | LSL Inventory | LEAD AND COPPER RULE REVISIONS | Health-based | Resolved |
| October 17, 2024 – February 6, 2025 | LSL Reporting | LEAD AND COPPER RULE REVISIONS | — | Resolved |
| April 1, 2022 – June 30, 2022 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| April 1, 2022 – April 30, 2022 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| June 1, 2016 – June 30, 2016 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| April 1, 2016 – June 30, 2016 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| September 1, 2013 – January 17, 2020 | Failure To Address Deficiency | Groundwater Rule | Health-based | Resolved |
| April 1, 2011 – June 30, 2011 | Monitoring, Regular | Radium-226 | — | Resolved |
| April 1, 2011 – June 30, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2011 – June 30, 2011 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2011 – March 31, 2011 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2010 – December 31, 2010 | Monitoring, Regular | Combined Uranium | — | Resolved |
| July 1, 2010 – September 30, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2010 – September 30, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| July 1, 2010 – September 30, 2010 | Monitoring, Regular | Combined Uranium | — | Resolved |
| April 1, 2010 – June 30, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2010 – June 30, 2010 | Monitoring, Regular | Combined Uranium | — | Resolved |
| April 1, 2010 – June 30, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2010 – March 31, 2010 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2010 – March 31, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2010 – March 31, 2010 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2009 – December 31, 2009 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2009 – December 31, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2009 – December 31, 2009 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2009 – September 30, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| July 1, 2009 – September 30, 2009 | Monitoring, Regular | Radium-226 | — | Resolved |
| July 1, 2009 – September 30, 2009 | Monitoring, Regular | Combined Uranium | — | Resolved |
| April 1, 2009 – June 30, 2009 | Monitoring, Regular | Radium-226 | — | Resolved |
| April 1, 2009 – June 30, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2009 – June 30, 2009 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2009 – March 31, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| January 1, 2009 – March 31, 2009 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2009 – March 31, 2009 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2008 – December 31, 2008 | Monitoring, Regular | Combined Uranium | — | Resolved |
| October 1, 2008 – June 28, 2012 | Public Notification Violation for NPDWR Violation | Public Notice | — | Resolved |
| October 1, 2008 – December 31, 2008 | Monitoring, Regular | Radium-228 | — | Resolved |
| July 1, 1981 – July 31, 1981 | Notification, Public | — | — | Archived |
Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
Enforcement actions
- February 26, 2025State Violation/Reminder Notice1 linked violation
- February 26, 2025State Violation/Reminder Notice1 linked violation
- February 6, 2025State Compliance achieved2 linked violations
- September 30, 2022State Compliance achieved1 linked violation
- May 25, 2022State Public Notification requested2 linked violations
- May 12, 2022State Public Notification requested2 linked violations
- May 9, 2022State Compliance achieved2 linked violations
- January 17, 2020State Compliance achieved2 linked violations
- September 13, 2019State Public Notification requested2 linked violations
- April 25, 2017State Public Notification received2 linked violations
- September 13, 2013State Formal Notice of Violation issued2 linked violations
- June 28, 2012State Public Notification received37 linked violations
- March 20, 2012State Public Notification requested37 linked violations
- May 18, 1987State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- December 3, 1986State Public Notification receivedgeneral compliance action — not tied to a specific violation on record
- October 14, 1986State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- November 1, 1985State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- August 13, 1981State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
Common questions
Is COLONIAL ESTATES # 3 required to publish a Consumer Confidence Report?
- Yes. COLONIAL ESTATES # 3 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 COLONIAL ESTATES # 3’s next Consumer Confidence Report due?
- COLONIAL ESTATES # 3’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does COLONIAL ESTATES # 3 have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for COLONIAL ESTATES # 3.
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
AGAR, BEVERLY
228-238-1082
OCEAN SPRINGS, MS 39564