BETHESDA, VA · Culpeper County
BAILEYS MOBILE HOME PARK Water System
Consumer Confidence Report status
BAILEYS MOBILE HOME PARK 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 BAILEYS MOBILE HOME PARK.
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 Virginia’s official records. Always confirm current status with Virginia before making decisions based on this information.
System facts
- System ID (PWSID)
- VA6047015
- System type
- Community Water System
- Population served
- 84
- Service connections
- 28
- Ownership
- privately owned
- Water source
- groundwater (wells)
BAILEYS MOBILE HOME PARK is one of 2,163 community water systems in Virginia in the 500 or fewer people size category, serving 84 people from groundwater.
As of August 1, 2026, its federal record holds 49 entries between 1991 and 2025, all of which EPA lists as closed.
Of the 49, 3 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 Total Coliform Rules, and the Stage 1 Disinfectants and Disinfection Byproducts Rule.
Violation history
Monitoring and Reporting (DBP)
—Chlorine
November 1, 2025 – November 30, 2025
ResolvedMonitoring, Routine (RTCR)
—Revised Total Coliform Rule
November 1, 2025 – November 30, 2025
ResolvedLead Consumer Notice
—Lead and Copper Rule
September 26, 2019 – November 10, 2019
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2013 – September 30, 2013
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2013 – June 30, 2013
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2013 – March 31, 2013
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2012 – December 31, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2012 – September 30, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2012 – June 30, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2012 – March 31, 2012
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2011 – December 31, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2011 – September 30, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2011 – June 30, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2011 – March 31, 2011
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2010 – December 31, 2010
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2010 – September 30, 2010
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2010 – June 30, 2010
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-basedCombined Radium (-226 and -228)
July 1, 2009 – September 30, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2009 – June 30, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2009 – March 31, 2009
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2008 – December 31, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2008 – September 30, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2008 – June 30, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2008 – March 31, 2008
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2007 – December 31, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2007 – September 30, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2007 – June 30, 2007
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2006 – September 30, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2006 – June 30, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2006 – March 31, 2006
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2005 – December 31, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2005 – September 30, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2005 – June 30, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2005 – March 31, 2005
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
October 1, 2004 – December 31, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2004 – September 30, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2004 – June 30, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2004 – March 31, 2004
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2003 – September 30, 2003
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
April 1, 2003 – June 30, 2003
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2003 – March 31, 2003
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2002 – December 31, 2002
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
January 1, 2001 – December 31, 2001
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
January 1, 2001 – March 31, 2001
ResolvedMaximum Contaminant Level Violation, Average
Health-basedGross Alpha, Excl. Radon and U
July 1, 2000 – December 31, 2000
ResolvedMaximum Contaminant Level Violation, Average
Health-basedCombined Radium (-226 and -228)
July 1, 2000 – December 31, 2000
ResolvedMaximum Contaminant Level Violation, Monthly (TCR)
Health-basedColiform (TCR)
June 1, 1991 – June 30, 1991
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 |
|---|---|---|---|---|
| November 1, 2025 – November 30, 2025 | Monitoring and Reporting (DBP) | Chlorine | — | Resolved |
| November 1, 2025 – November 30, 2025 | Monitoring, Routine (RTCR) | Revised Total Coliform Rule | — | Resolved |
| September 26, 2019 – November 10, 2019 | Lead Consumer Notice | Lead and Copper Rule | — | Resolved |
| July 1, 2013 – September 30, 2013 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2013 – June 30, 2013 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2013 – March 31, 2013 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2012 – December 31, 2012 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2012 – September 30, 2012 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2012 – June 30, 2012 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2012 – March 31, 2012 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2011 – December 31, 2011 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2011 – September 30, 2011 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2011 – June 30, 2011 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2011 – March 31, 2011 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2010 – December 31, 2010 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2010 – September 30, 2010 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2010 – June 30, 2010 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | 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 |
| July 1, 2009 – September 30, 2009 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2009 – June 30, 2009 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2009 – March 31, 2009 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2008 – December 31, 2008 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2008 – September 30, 2008 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2008 – June 30, 2008 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2008 – March 31, 2008 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2007 – December 31, 2007 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2007 – September 30, 2007 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2007 – June 30, 2007 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2006 – September 30, 2006 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2006 – June 30, 2006 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2006 – March 31, 2006 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2005 – December 31, 2005 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2005 – September 30, 2005 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2005 – June 30, 2005 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2005 – March 31, 2005 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| October 1, 2004 – December 31, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2004 – September 30, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2004 – June 30, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2004 – March 31, 2004 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| July 1, 2003 – September 30, 2003 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| April 1, 2003 – June 30, 2003 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2003 – March 31, 2003 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2002 – December 31, 2002 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2001 – December 31, 2001 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| January 1, 2001 – March 31, 2001 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| July 1, 2000 – December 31, 2000 | Maximum Contaminant Level Violation, Average | Gross Alpha, Excl. Radon and U | Health-based | Resolved |
| July 1, 2000 – December 31, 2000 | Maximum Contaminant Level Violation, Average | Combined Radium (-226 and -228) | Health-based | Resolved |
| June 1, 1991 – June 30, 1991 | Maximum Contaminant Level Violation, Monthly (TCR) | Coliform (TCR) | Health-based | Archived |
Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)
Enforcement actions
- December 30, 2025State Compliance achieved7 linked violations
- December 11, 2025State Formal Notice of Violation issued11 linked violations
- July 17, 2014Federal Compliance achieved17 linked violations
- November 4, 2013State Public Notification received3 linked violations
- October 16, 2013State Formal Notice of Violation issued4 linked violations
- October 9, 2013State Compliance achieved1 linked violation
- October 9, 2013State Compliance achieved1 linked violation
- October 9, 2013State Compliance achieved1 linked violation
- October 9, 2013State Compliance achieved1 linked violation
- October 9, 2013State Compliance achieved1 linked violation
- October 9, 2013State Compliance achieved1 linked violation
- October 9, 2013State Compliance achieved28 linked violations
- October 9, 2013State Compliance achieved1 linked violation
- October 9, 2013State Compliance achieved1 linked violation
- October 9, 2013State Compliance achieved1 linked violation
- October 9, 2013State Compliance achieved1 linked violation
- October 9, 2013State Compliance achieved1 linked violation
- October 9, 2013State Compliance achieved1 linked violation
- October 9, 2013State Compliance achieved1 linked violation
- October 9, 2013State Compliance achieved1 linked violation
- October 9, 2013State Compliance achieved1 linked violation
- October 9, 2013State Compliance achieved1 linked violation
- October 9, 2013State Compliance achieved1 linked violation
- October 9, 2013State Compliance achieved1 linked violation
- June 24, 2013State Formal Notice of Violation issued1 linked violation
- June 24, 2013State Public Notification requested1 linked violation
- April 18, 2013State Public Notification received1 linked violation
- February 19, 2013State Public Notification received1 linked violation
- January 28, 2013State Formal Notice of Violation issued1 linked violation
- January 28, 2013State Public Notification requested1 linked violation
- October 15, 2012State Public Notification received1 linked violation
- September 7, 2012State Public Notification requested1 linked violation
- September 7, 2012State Formal Notice of Violation issued1 linked violation
- August 14, 2012State Public Notification requested1 linked violation
- August 14, 2012State Formal Notice of Violation issued1 linked violation
- January 30, 2012State Public Notification received1 linked violation
- December 21, 2011State Public Notification requested1 linked violation
- December 21, 2011State Formal Notice of Violation issued1 linked violation
- November 9, 2011State Public Notification received1 linked violation
- October 26, 2011State Public Notification requested1 linked violation
- October 26, 2011State Formal Notice of Violation issued1 linked violation
- September 2, 2011State Public Notification received1 linked violation
- August 2, 2011State Formal Notice of Violation issued1 linked violation
- August 2, 2011State Public Notification requested1 linked violation
- July 11, 2011State Public Notification received1 linked violation
- June 3, 2011State Public Notification received1 linked violation
- June 1, 2011State Formal Notice of Violation issued1 linked violation
- June 1, 2011State Public Notification requested1 linked violation
- May 27, 2011State Public Notification requested1 linked violation
- February 9, 2011State Public Notification received2 linked violations
- January 5, 2011State Public Notification requested1 linked violation
- January 5, 2011State Formal Notice of Violation issued1 linked violation
- January 5, 2011State Public Notification requested1 linked violation
- January 5, 2011State Formal Notice of Violation issued1 linked violation
- September 27, 2010State Public Notification received2 linked violations
- August 25, 2010State Public Notification requested1 linked violation
- August 25, 2010State Formal Notice of Violation issued1 linked violation
- May 10, 2010State Formal Notice of Violation issued1 linked violation
- May 10, 2010State Public Notification requested1 linked violation
- February 9, 2010State Formal Notice of Violation issued1 linked violation
- September 30, 2009State Public Notification received1 linked violation
- September 22, 2009State Public Notification requested1 linked violation
- September 22, 2009State Formal Notice of Violation issued1 linked violation
- July 16, 2009State Public Notification requested1 linked violation
- July 16, 2009State Formal Notice of Violation issued1 linked violation
- July 12, 2009State Public Notification received1 linked violation
- April 16, 2009State Public Notification requested1 linked violation
- April 16, 2009State Formal Notice of Violation issued1 linked violation
- February 4, 2009State Public Notification received1 linked violation
- January 15, 2009State Public Notification requested1 linked violation
- January 15, 2009State Formal Notice of Violation issued1 linked violation
- October 2, 2008State Public Notification received1 linked violation
- September 23, 2008State Public Notification requested1 linked violation
- September 23, 2008State Formal Notice of Violation issued1 linked violation
- August 15, 2008State Public Notification received1 linked violation
- July 17, 2008State Public Notification requested1 linked violation
- July 17, 2008State Formal Notice of Violation issued1 linked violation
- May 8, 2008State Public Notification received2 linked violations
- April 11, 2008State Formal Notice of Violation issued4 linked violations
- November 13, 2007State Public Notification requested4 linked violations
- December 14, 2006State Formal Notice of Violation issued5 linked violations
- December 14, 2006State Public Notification requested5 linked violations
- March 27, 2006State Public Notification received21 linked violations
- March 20, 2006State Public Notification requested4 linked violations
- October 24, 2005State Formal Notice of Violation issued6 linked violations
- June 29, 2005State Public Notification received5 linked violations
- June 22, 2005State Public Notification requested5 linked violations
- April 10, 2005State Public Notification received5 linked violations
- March 1, 2005State Formal Notice of Violation issued4 linked violations
- September 14, 2004State Compliance achieved2 linked violations
- February 10, 2004State Public Notification requested11 linked violations
- June 6, 2003State Public Notification received4 linked violations
- June 24, 2002State Public Notification received5 linked violations
- June 11, 2002State Formal Notice of Violation issued4 linked violations
- August 31, 2000State Public Notification requested3 linked violations
- April 20, 2000State Public Notification requested74 linked violations
- September 30, 1991Federal issued Formal Notice of Violationgeneral compliance action — not tied to a specific violation on record
Common questions
Is BAILEYS MOBILE HOME PARK required to publish a Consumer Confidence Report?
- Yes. BAILEYS MOBILE HOME PARK 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 BAILEYS MOBILE HOME PARK’s next Consumer Confidence Report due?
- BAILEYS MOBILE HOME PARK’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does BAILEYS MOBILE HOME PARK have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for BAILEYS MOBILE HOME PARK.
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
FISHKIND, SCOTT
Phone not on record
BETHESDA, MD 20814