CLARKSDALE, MS · Coahoma County

FARRELL UTILITIES Water System

Inactive system

This water system is marked inactive in EPA’s federal records as of February 10, 2014. It is no longer an operating public water system under this PWSID, and no compliance deadlines — including the 2027 Consumer Confidence Report rule — apply to it.

If you are a resident looking for your current water provider, see water systems in Coahoma County, MS.

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): MS0140006
System type: Community Water System
Population served: 243
Service connections: 91
Ownership: public/private mix
Water source: groundwater (wells)

FARRELL UTILITIES is one of 879 community water systems in Mississippi in the 500 or fewer people size category, formerly serving 243 people from groundwater.

EPA's federal records list this system as inactive in 2014; the record below is historical.

As of August 1, 2026, its federal record holds 46 entries between 1981 and 2013, all of which EPA lists as closed. Nothing has been added since 2013.

Of the 46, 34 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 Public Notice Rule and Revised PN Rule.

Violation history

Public Notification Violation for NPDWR Violation
—
Public Notice
October 1, 2013 – February 10, 2014
Resolved
Maximum Contaminant Level Violation, Average
Health-based
TTHM
July 1, 2013 – September 30, 2013
Resolved
Maximum Contaminant Level Violation, Average
Health-based
TTHM
April 1, 2013 – June 30, 2013
Resolved
Maximum Contaminant Level Violation, Average
Health-based
TTHM
January 1, 2013 – March 31, 2013
Resolved
Maximum Contaminant Level Violation, Average
Health-based
TTHM
October 1, 2012 – December 31, 2012
Resolved
Consumer Confidence Report Complete Failure to Report
—
Consumer Confidence Rule
July 1, 2012 – July 25, 2012
Resolved
Maximum Contaminant Level Violation, Average
Health-based
TTHM
July 1, 2012 – September 30, 2012
Resolved
Consumer Confidence Report Complete Failure to Report
—
Consumer Confidence Rule
July 1, 2011 – July 15, 2011
Resolved
Monitoring, Regular
—
Radium-226
April 1, 2011 – June 30, 2011
Resolved
Monitoring, Regular
—
Radium-228
April 1, 2011 – June 30, 2011
Resolved
Monitoring, Regular
—
Combined Uranium
April 1, 2011 – June 30, 2011
Resolved
Monitoring, Regular
—
Radium-226
January 1, 2011 – March 31, 2011
Resolved
Monitoring, Regular
—
Radium-228
January 1, 2011 – March 31, 2011
Resolved
Monitoring, Regular
—
Combined Uranium
January 1, 2011 – March 31, 2011
Resolved
Monitoring, Regular
—
Radium-226
October 1, 2010 – December 31, 2010
Resolved
Monitoring, Regular
—
Radium-228
October 1, 2010 – December 31, 2010
Resolved
Monitoring, Regular
—
Combined Uranium
October 1, 2010 – December 31, 2010
Resolved
Monitoring, Regular
—
Radium-226
July 1, 2010 – September 30, 2010
Resolved
Monitoring, Regular
—
Radium-228
July 1, 2010 – September 30, 2010
Resolved
Monitoring, Regular
—
Combined Uranium
July 1, 2010 – September 30, 2010
Resolved
Monitoring, Regular
—
Combined Uranium
April 1, 2010 – June 30, 2010
Resolved
Monitoring, Regular
—
Radium-226
April 1, 2010 – June 30, 2010
Resolved
Monitoring, Regular
—
Radium-228
April 1, 2010 – June 30, 2010
Resolved
Monitoring, Regular
—
Radium-228
January 1, 2010 – March 31, 2010
Resolved
Monitoring, Regular
—
Radium-226
January 1, 2010 – March 31, 2010
Resolved
Monitoring, Regular
—
Combined Uranium
January 1, 2010 – March 31, 2010
Resolved
Monitoring, Regular
—
Combined Uranium
October 1, 2009 – December 31, 2009
Resolved
Monitoring, Regular
—
Radium-228
October 1, 2009 – December 31, 2009
Resolved
Monitoring, Regular
—
Radium-226
October 1, 2009 – December 31, 2009
Resolved
Monitoring, Regular
—
Radium-226
July 1, 2009 – September 30, 2009
Resolved
Monitoring, Regular
—
Radium-228
July 1, 2009 – September 30, 2009
Resolved
Monitoring, Regular
—
Combined Uranium
July 1, 2009 – September 30, 2009
Resolved
Monitoring, Regular
—
Radium-226
April 1, 2009 – June 30, 2009
Resolved
Monitoring, Regular
—
Radium-228
April 1, 2009 – June 30, 2009
Resolved
Monitoring, Regular
—
Combined Uranium
April 1, 2009 – June 30, 2009
Resolved
Monitoring, Regular
—
Combined Uranium
January 1, 2009 – March 31, 2009
Resolved
Monitoring, Regular
—
Radium-226
January 1, 2009 – March 31, 2009
Resolved
Monitoring, Regular
—
Radium-228
January 1, 2009 – March 31, 2009
Resolved
Monitoring, Regular
—
Radium-226
October 1, 2008 – December 31, 2008
Resolved
Monitoring, Regular
—
Combined Uranium
October 1, 2008 – December 31, 2008
Resolved
Public Notification Violation for NPDWR Violation
—
Public Notice
October 1, 2008 – July 25, 2012
Resolved
Monitoring, Regular
—
Radium-228
October 1, 2008 – December 31, 2008
Resolved
Monitoring, Regular
—
Combined Radium (-226 and -228)
July 1, 2008 – September 30, 2008
Resolved
Public Notification Violation for NPDWR Violation
—
Public Notice
September 19, 2004 – December 31, 2007
Resolved
Consumer Confidence Report Complete Failure to Report
—
Consumer Confidence Rule
July 1, 2001 – June 19, 2002
Resolved
Notification, Public
—
No contaminant on record
August 1, 1981 – August 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 1, 2013 – February 10, 2014	Public Notification Violation for NPDWR Violation	Public Notice	—	Resolved
July 1, 2013 – September 30, 2013	Maximum Contaminant Level Violation, Average	TTHM	Health-based	Resolved
April 1, 2013 – June 30, 2013	Maximum Contaminant Level Violation, Average	TTHM	Health-based	Resolved
January 1, 2013 – March 31, 2013	Maximum Contaminant Level Violation, Average	TTHM	Health-based	Resolved
October 1, 2012 – December 31, 2012	Maximum Contaminant Level Violation, Average	TTHM	Health-based	Resolved
July 1, 2012 – July 25, 2012	Consumer Confidence Report Complete Failure to Report	Consumer Confidence Rule	—	Resolved
July 1, 2012 – September 30, 2012	Maximum Contaminant Level Violation, Average	TTHM	Health-based	Resolved
July 1, 2011 – July 15, 2011	Consumer Confidence Report Complete Failure to Report	Consumer Confidence Rule	—	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	Combined Uranium	—	Resolved
April 1, 2010 – June 30, 2010	Monitoring, Regular	Radium-226	—	Resolved
April 1, 2010 – June 30, 2010	Monitoring, Regular	Radium-228	—	Resolved
January 1, 2010 – March 31, 2010	Monitoring, Regular	Radium-228	—	Resolved
January 1, 2010 – March 31, 2010	Monitoring, Regular	Radium-226	—	Resolved
January 1, 2010 – March 31, 2010	Monitoring, Regular	Combined Uranium	—	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-226	—	Resolved
July 1, 2009 – September 30, 2009	Monitoring, Regular	Radium-228	—	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	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
October 1, 2008 – December 31, 2008	Monitoring, Regular	Radium-226	—	Resolved
October 1, 2008 – December 31, 2008	Monitoring, Regular	Combined Uranium	—	Resolved
October 1, 2008 – July 25, 2012	Public Notification Violation for NPDWR Violation	Public Notice	—	Resolved
October 1, 2008 – December 31, 2008	Monitoring, Regular	Radium-228	—	Resolved
July 1, 2008 – September 30, 2008	Monitoring, Regular	Combined Radium (-226 and -228)	—	Resolved
September 19, 2004 – December 31, 2007	Public Notification Violation for NPDWR Violation	Public Notice	—	Resolved
July 1, 2001 – June 19, 2002	Consumer Confidence Report Complete Failure to Report	Consumer Confidence Rule	—	Resolved
August 1, 1981 – August 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

June 16, 2014State Compliance achieved1 linked violation
June 16, 2014State Public Notification received3 linked violations
March 27, 2014State Compliance achieved5 linked violations
February 10, 2014State Compliance achieved1 linked violation
November 15, 2013State Public Notification requested1 linked violation
November 15, 2013State Formal Notice of Violation issued1 linked violation
August 15, 2013State Administrative/Compliance Order without penalty issued5 linked violations
August 13, 2013State Formal Notice of Violation issued1 linked violation
August 13, 2013State Public Notification requested1 linked violation
April 18, 2013State Formal Notice of Violation issued1 linked violation
April 18, 2013State Public Notification requested1 linked violation
February 27, 2013State Public Notification received1 linked violation
February 21, 2013State Formal Notice of Violation issued1 linked violation
February 21, 2013State Public Notification requested1 linked violation
November 28, 2012State Public Notification received1 linked violation
November 5, 2012State Public Notification requested1 linked violation
November 5, 2012State Formal Notice of Violation issued1 linked violation
July 25, 2012State Formal Notice of Violation issued2 linked violations
July 25, 2012State Compliance achieved2 linked violations
July 25, 2012State Public Notification received33 linked violations
March 20, 2012State Formal Notice of Violation issued33 linked violations
March 20, 2012State Public Notification requested33 linked violations
December 30, 2011State Compliance achieved55 linked violations
September 27, 2011State Formal Notice of Violation issued1 linked violation
July 15, 2011State Compliance achieved78 linked violations
December 31, 2007State Compliance achieved1 linked violation
June 19, 2002State Compliance achieved3 linked violations
April 18, 1988State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
November 13, 1987State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
October 14, 1987State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
July 17, 1987State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
December 8, 1986State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
October 31, 1985State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
April 15, 1985State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
July 10, 1984State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record
April 10, 1984State Violation/Reminder Notice1 linked violation
November 9, 1983State Violation/Reminder Notice1 linked violation
July 13, 1983State Violation/Reminder Noticegeneral compliance action — not tied to a specific violation on record

Last known contact on file (system is inactive)

THOMAS, LORENZO

662-645-9977

CLARKSDALE, MS 38614