COURTLAND, MS · Panola County
POPE-COURTLAND WATER ASSN Water System
Consumer Confidence Report status
POPE-COURTLAND WATER ASSN 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 POPE-COURTLAND WATER ASSN.
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)
- MS0540017
- System type
- Community Water System
- Population served
- 977
- Service connections
- 370
- Ownership
- public/private mix
- Water source
- groundwater (wells)
POPE-COURTLAND WATER ASSN is one of 794 community water systems in Mississippi in the 501 to 3,300 people size category, serving 977 people from groundwater.
As of August 1, 2026, its federal record holds 20 entries between 2009 and 2012, all of which EPA lists as closed. Nothing has been added since 2012.
All 20 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.
Violation history
Monitoring, Regular
—Radium-226
July 1, 2012 – September 30, 2012
ResolvedMonitoring, Regular
—Radium-226
April 1, 2012 – June 30, 2012
ResolvedMonitoring, Regular
—Radium-226
January 1, 2012 – March 31, 2012
ResolvedMonitoring, Regular
—Radium-228
January 1, 2012 – March 31, 2012
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-226
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Radium-228
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Radium-228
October 1, 2010 – December 31, 2010
ResolvedMonitoring, Regular
—Radium-228
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2010 – June 30, 2010
ResolvedMonitoring, Regular
—Radium-228
January 1, 2010 – March 31, 2010
ResolvedMonitoring, Regular
—Radium-226
October 1, 2009 – December 31, 2009
ResolvedMonitoring, Regular
—Radium-228
October 1, 2009 – December 31, 2009
ResolvedMonitoring, Regular
—Radium-228
July 1, 2009 – September 30, 2009
ResolvedMonitoring, Regular
—Combined Uranium
April 1, 2009 – June 30, 2009
ResolvedMonitoring, Regular
—Combined Uranium
January 1, 2009 – March 31, 2009
ResolvedMonitoring, Regular
—Radium-226
January 1, 2009 – March 31, 2009
ResolvedMonitoring, Regular
—Radium-228
January 1, 2009 – March 31, 2009
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| July 1, 2012 – September 30, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| April 1, 2012 – June 30, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2012 – March 31, 2012 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2012 – March 31, 2012 | Monitoring, Regular | Radium-228 | — | 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 |
| 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 | Radium-228 | — | Resolved |
| April 1, 2010 – June 30, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| April 1, 2010 – June 30, 2010 | Monitoring, Regular | Combined Uranium | — | Resolved |
| January 1, 2010 – March 31, 2010 | Monitoring, Regular | Radium-228 | — | Resolved |
| October 1, 2009 – December 31, 2009 | Monitoring, Regular | Radium-226 | — | Resolved |
| October 1, 2009 – December 31, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
| July 1, 2009 – September 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 | Combined Uranium | — | Resolved |
| January 1, 2009 – March 31, 2009 | Monitoring, Regular | Radium-226 | — | Resolved |
| January 1, 2009 – March 31, 2009 | Monitoring, Regular | Radium-228 | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- June 10, 2013State Public Notification received28 linked violations
- September 30, 2012State Compliance achieved12 linked violations
- September 30, 2012State Compliance achieved15 linked violations
- September 30, 2012State Compliance achieved8 linked violations
- September 30, 2012State Compliance achieved9 linked violations
- September 30, 2012State Compliance achieved11 linked violations
- September 30, 2012State Compliance achieved11 linked violations
- September 30, 2012State Compliance achieved10 linked violations
- September 30, 2012State Compliance achieved6 linked violations
- September 30, 2012State Compliance achieved11 linked violations
- September 30, 2012State Compliance achieved29 linked violations
- September 30, 2012State Compliance achieved9 linked violations
- September 30, 2012State Compliance achieved35 linked violations
- September 30, 2012State Compliance achieved36 linked violations
- September 30, 2012State Compliance achieved60 linked violations
- July 2, 2012State Compliance achieved7 linked violations
- March 20, 2012State Formal Notice of Violation issued83 linked violations
- March 20, 2012State Public Notification requested82 linked violations
- September 27, 1985State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- August 12, 1982State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
- November 13, 1981State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
Common questions
Is POPE-COURTLAND WATER ASSN required to publish a Consumer Confidence Report?
- Yes. POPE-COURTLAND WATER ASSN 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 POPE-COURTLAND WATER ASSN’s next Consumer Confidence Report due?
- POPE-COURTLAND WATER ASSN’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does POPE-COURTLAND WATER ASSN have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for POPE-COURTLAND WATER ASSN.
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
FORD, JOHN H
662-561-1009
COURTLAND, MS 38620