Is NORMAN ACRES SUBDIVISION required to publish a Consumer Confidence Report?

Yes. NORMAN ACRES 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 NORMAN ACRES SUBDIVISION’s next Consumer Confidence Report due?

NORMAN ACRES SUBDIVISION’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.

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.

ROCKVILLE, VA · Culpeper County

NORMAN ACRES SUBDIVISION Water System

Consumer Confidence Report status

NORMAN ACRES 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 NORMAN ACRES 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 Virginia’s official records. Always confirm current status with Virginia before making decisions based on this information.

System facts

System ID (PWSID): VA6047355
System type: Community Water System
Population served: 50
Service connections: 20
Ownership: privately owned
Water source: groundwater (wells)

NORMAN ACRES SUBDIVISION is one of 2,163 community water systems in Virginia in the 500 or fewer people size category, serving 50 people from groundwater.

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

Of the 30, 6 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)
—
TTHM
July 1, 2011 – September 30, 2011
Resolved
Monitoring and Reporting (DBP)
—
Total Haloacetic Acids (HAA5)
July 1, 2011 – September 30, 2011
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2010 – December 31, 2010
Resolved
Maximum Contaminant Level Violation, Monthly (TCR)
Health-based
Coliform (TCR)
September 1, 2010 – September 30, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
July 1, 2010 – September 30, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
April 1, 2010 – June 30, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 2010 – March 31, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2009 – December 31, 2009
Resolved
Consumer Confidence Report Complete Failure to Report
—
Consumer Confidence Rule
July 1, 2009 – June 30, 2010
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 2009 – March 31, 2009
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2008 – December 31, 2008
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
July 1, 2008 – September 30, 2008
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
April 1, 2008 – June 30, 2008
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2007 – December 31, 2007
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
July 1, 2007 – September 30, 2007
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
October 1, 2006 – December 31, 2006
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
April 1, 2005 – June 30, 2005
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 2005 – March 31, 2005
Resolved
Public Notification Violation for NPDWR Violation
—
Public Notice
June 16, 2003 – July 21, 2004
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
April 1, 2003 – June 30, 2003
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
July 1, 2002 – March 31, 2003
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
April 1, 2002 – June 30, 2002
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Combined Radium (-226 and -228)
January 1, 2002 – March 31, 2002
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Gross Alpha, Excl. Radon and U
January 1, 2001 – March 31, 2001
Resolved
Maximum Contaminant Level Violation, Average
Health-based
Gross Alpha, Excl. Radon and U
July 1, 2000 – December 31, 2000
Resolved
Monitoring, Routine Minor (TCR)
—
Coliform (TCR)
December 1, 1992 – December 31, 1992
Archived
Monitoring, Repeat Major (TCR)
—
Coliform (TCR)
November 1, 1992 – November 30, 1992
Archived
Monitoring, Routine Minor (TCR)
—
Coliform (TCR)
October 1, 1992 – October 31, 1992
Archived
Maximum Contaminant Level Violation, Monthly (TCR)
Health-based
Coliform (TCR)
September 1, 1992 – September 30, 1992
Archived
Monitoring, Repeat Major (TCR)
—
Coliform (TCR)
August 1, 1992 – August 31, 1992
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
July 1, 2011 – September 30, 2011	Monitoring and Reporting (DBP)	TTHM	—	Resolved
July 1, 2011 – September 30, 2011	Monitoring and Reporting (DBP)	Total Haloacetic Acids (HAA5)	—	Resolved
October 1, 2010 – December 31, 2010	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
September 1, 2010 – September 30, 2010	Maximum Contaminant Level Violation, Monthly (TCR)	Coliform (TCR)	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 – June 30, 2010	Consumer Confidence Report Complete Failure to Report	Consumer Confidence Rule	—	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
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
October 1, 2006 – December 31, 2006	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
June 16, 2003 – July 21, 2004	Public Notification Violation for NPDWR Violation	Public Notice	—	Resolved
April 1, 2003 – June 30, 2003	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
July 1, 2002 – March 31, 2003	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
April 1, 2002 – June 30, 2002	Maximum Contaminant Level Violation, Average	Combined Radium (-226 and -228)	Health-based	Resolved
January 1, 2002 – March 31, 2002	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
December 1, 1992 – December 31, 1992	Monitoring, Routine Minor (TCR)	Coliform (TCR)	—	Archived
November 1, 1992 – November 30, 1992	Monitoring, Repeat Major (TCR)	Coliform (TCR)	—	Archived
October 1, 1992 – October 31, 1992	Monitoring, Routine Minor (TCR)	Coliform (TCR)	—	Archived
September 1, 1992 – September 30, 1992	Maximum Contaminant Level Violation, Monthly (TCR)	Coliform (TCR)	Health-based	Archived
August 1, 1992 – August 31, 1992	Monitoring, Repeat Major (TCR)	Coliform (TCR)	—	Archived

Resolved addressed and confirmed by the stateArchived closed in EPA's records (typically due to age or a data correction)

Enforcement actions

August 13, 2012State Compliance achieved1 linked violation
August 13, 2012State Compliance achieved1 linked violation
July 12, 2012State Public Notification received2 linked violations
October 24, 2011State Public Notification requested1 linked violation
October 24, 2011State Formal Notice of Violation issued1 linked violation
October 24, 2011State Public Notification requested1 linked violation
October 24, 2011State Formal Notice of Violation issued1 linked violation
June 23, 2011State Public Notification received1 linked violation
February 27, 2011State Compliance achieved1 linked violation
February 27, 2011State Compliance achieved1 linked violation
February 27, 2011State Compliance achieved1 linked violation
February 27, 2011State Compliance achieved1 linked violation
February 27, 2011State Compliance achieved1 linked violation
January 28, 2011State Public Notification received2 linked violations
January 5, 2011State Public Notification requested1 linked violation
January 5, 2011State Public Notification requested2 linked violations
October 18, 2010State Public Notification received1 linked violation
October 13, 2010State Compliance achieved1 linked violation
September 23, 2010State Public Notification received1 linked violation
September 20, 2010State Formal Notice of Violation issued1 linked violation
September 20, 2010State Public Notification requested1 linked violation
August 25, 2010State Formal Notice of Violation issued1 linked violation
August 25, 2010State Public Notification requested1 linked violation
June 30, 2010State Compliance achieved1 linked violation
June 8, 2010State Public Notification received1 linked violation
May 21, 2010State Public Notification requested1 linked violation
May 21, 2010State Formal Notice of Violation issued1 linked violation
February 9, 2010State Public Notification requested1 linked violation
February 9, 2010State Formal Notice of Violation issued1 linked violation
January 27, 2010State Formal Notice of Violation issued1 linked violation
July 12, 2009State Compliance achieved1 linked violation
July 12, 2009State Compliance achieved1 linked violation
July 12, 2009State Compliance achieved1 linked violation
July 12, 2009State Compliance achieved1 linked violation
May 6, 2009State Public Notification received1 linked violation
April 16, 2009State Formal Notice of Violation issued1 linked violation
April 16, 2009State Public Notification requested1 linked violation
February 4, 2009State Public Notification received1 linked violation
January 15, 2009State Formal Notice of Violation issued1 linked violation
January 15, 2009State Public Notification requested1 linked violation
November 7, 2008State Public Notification received1 linked violation
October 15, 2008State Public Notification requested1 linked violation
October 15, 2008State Formal Notice of Violation issued1 linked violation
September 11, 2008State Public Notification received1 linked violation
August 18, 2008State Public Notification requested1 linked violation
August 18, 2008State Formal Notice of Violation issued1 linked violation
March 19, 2008State Formal Notice of Violation issued4 linked violations
January 30, 2008State Compliance achieved2 linked violations
April 24, 2007State Formal Notice of Violation issued4 linked violations
February 8, 2007State Compliance achieved2 linked violations
December 1, 2006State Public Notification requested2 linked violations
July 1, 2005State Compliance achieved3 linked violations
July 21, 2004State Compliance achieved2 linked violations
August 6, 2003State Formal Notice of Violation issued9 linked violations
July 28, 2003State Formal Notice of Violation issued4 linked violations
October 31, 2002State Public Notification requested12 linked violations
June 11, 2002State Formal Notice of Violation issued3 linked violations
June 11, 2002State Public Notification requested4 linked violations
September 24, 2001State Compliance achieved7 linked violations
April 20, 2001State Formal Notice of Violation issued4 linked violations
January 22, 1995State Compliance achieved1 linked violation
July 26, 1990State Public Notification requestedgeneral compliance action — not tied to a specific violation on record

Common questions

Is NORMAN ACRES SUBDIVISION required to publish a Consumer Confidence Report?: Yes. NORMAN ACRES 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 NORMAN ACRES SUBDIVISION’s next Consumer Confidence Report due?: NORMAN ACRES SUBDIVISION’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does NORMAN ACRES SUBDIVISION have any open drinking water violations on record?: As of August 1, 2026, EPA's federal records show no open violations for NORMAN ACRES 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

KRAKIE, ANDREW

804-749-8868

ROCKVILLE, VA 23146