BLACK HAWK, SD · Lawrence County
VALHALLA ADDITION Water System
Consumer Confidence Report status
VALHALLA ADDITION 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 VALHALLA ADDITION.
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 South Dakota’s official records. Always confirm current status with South Dakota before making decisions based on this information.
System facts
- System ID (PWSID)
- SD4602211
- System type
- Community Water System
- Population served
- 38
- Service connections
- 15
- Ownership
- privately owned
- Water source
- groundwater (wells)
VALHALLA ADDITION is one of 583 community water systems in South Dakota in the 500 or fewer people size category, serving 38 people from groundwater.
As of August 1, 2026, its federal record holds 16 entries between 2002 and 2003, all of which EPA lists as closed. Nothing has been added since 2003.
All 16 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 synthetic organic chemicals.
Violation history
Monitoring, Regular
—Diquat
April 1, 2003 – June 30, 2003
ResolvedMonitoring, Regular
—Endrin
April 1, 2003 – June 30, 2003
ResolvedMonitoring, Regular
—Simazine
April 1, 2003 – June 30, 2003
ResolvedMonitoring, Regular
—OXAMYL
April 1, 2003 – June 30, 2003
ResolvedMonitoring, Regular
—2,4,5-TP
April 1, 2003 – June 30, 2003
ResolvedMonitoring, Regular
—1,2-DIBROMO-3-CHLOROPROPANE
April 1, 2003 – June 30, 2003
ResolvedMonitoring, Regular
—ETHYLENE DIBROMIDE
April 1, 2003 – June 30, 2003
ResolvedMonitoring, Regular
—Endothall
April 1, 2003 – June 30, 2003
ResolvedMonitoring, Regular
—LASSO
April 1, 2003 – June 30, 2003
ResolvedMonitoring, Regular
—Benzo(a)pyrene
January 1, 2003 – March 30, 2003
ResolvedMonitoring, Regular
—Heptachlor epoxide
January 1, 2003 – March 30, 2003
ResolvedMonitoring, Regular
—Atrazine
January 1, 2003 – March 30, 2003
ResolvedMonitoring, Regular
—2,4,5-TP
January 1, 2003 – March 30, 2003
ResolvedMonitoring, Regular
—Picloram
January 1, 2003 – March 30, 2003
ResolvedMonitoring, Regular
—ETHYLENE DIBROMIDE
October 1, 2002 – December 31, 2002
ResolvedMonitoring, Regular
—Heptachlor epoxide
October 1, 2002 – December 31, 2002
Resolved
Resolved addressed and confirmed by the state
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| April 1, 2003 – June 30, 2003 | Monitoring, Regular | Diquat | — | Resolved |
| April 1, 2003 – June 30, 2003 | Monitoring, Regular | Endrin | — | Resolved |
| April 1, 2003 – June 30, 2003 | Monitoring, Regular | Simazine | — | Resolved |
| April 1, 2003 – June 30, 2003 | Monitoring, Regular | OXAMYL | — | Resolved |
| April 1, 2003 – June 30, 2003 | Monitoring, Regular | 2,4,5-TP | — | Resolved |
| April 1, 2003 – June 30, 2003 | Monitoring, Regular | 1,2-DIBROMO-3-CHLOROPROPANE | — | Resolved |
| April 1, 2003 – June 30, 2003 | Monitoring, Regular | ETHYLENE DIBROMIDE | — | Resolved |
| April 1, 2003 – June 30, 2003 | Monitoring, Regular | Endothall | — | Resolved |
| April 1, 2003 – June 30, 2003 | Monitoring, Regular | LASSO | — | Resolved |
| January 1, 2003 – March 30, 2003 | Monitoring, Regular | Benzo(a)pyrene | — | Resolved |
| January 1, 2003 – March 30, 2003 | Monitoring, Regular | Heptachlor epoxide | — | Resolved |
| January 1, 2003 – March 30, 2003 | Monitoring, Regular | Atrazine | — | Resolved |
| January 1, 2003 – March 30, 2003 | Monitoring, Regular | 2,4,5-TP | — | Resolved |
| January 1, 2003 – March 30, 2003 | Monitoring, Regular | Picloram | — | Resolved |
| October 1, 2002 – December 31, 2002 | Monitoring, Regular | ETHYLENE DIBROMIDE | — | Resolved |
| October 1, 2002 – December 31, 2002 | Monitoring, Regular | Heptachlor epoxide | — | Resolved |
Resolved addressed and confirmed by the state
Enforcement actions
- September 1, 2003State Compliance achieved6 linked violations
- September 1, 2003State Compliance achieved7 linked violations
- September 1, 2003State Compliance achieved4 linked violations
- September 1, 2003State Compliance achieved24 linked violations
- September 1, 2003State Compliance achieved6 linked violations
- September 1, 2003State Compliance achieved2 linked violations
- September 1, 2003State Compliance achieved3 linked violations
- September 1, 2003State Compliance achieved2 linked violations
- September 1, 2003State Compliance achieved18 linked violations
- September 1, 2003State Compliance achieved4 linked violations
- September 1, 2003State Compliance achieved5 linked violations
- September 1, 2003State Compliance achieved29 linked violations
- September 1, 2003State Compliance achieved6 linked violations
- September 1, 2003State Compliance achieved21 linked violations
- September 1, 2003State Compliance achieved12 linked violations
- September 1, 2003State Compliance achieved3 linked violations
- September 1, 2003State Compliance achieved8 linked violations
- September 1, 2003State Compliance achieved5 linked violations
- September 1, 2003State Compliance achieved3 linked violations
- September 1, 2003State Compliance achieved2 linked violations
- September 1, 2003State Compliance achieved4 linked violations
- September 1, 2003State Compliance achieved7 linked violations
- September 1, 2003State Compliance achieved6 linked violations
- September 1, 2003State Compliance achieved6 linked violations
- August 28, 2003State Public Notification requested7 linked violations
- June 13, 2003State Public Notification requested58 linked violations
- June 13, 2003State Public Notification requested19 linked violations
- June 13, 2003State Public Notification requested66 linked violations
- June 13, 2003State Public Notification requested14 linked violations
- June 13, 2003State Public Notification requested15 linked violations
- April 1, 2002State Compliance achieved167 linked violations
Common questions
Is VALHALLA ADDITION required to publish a Consumer Confidence Report?
- Yes. VALHALLA ADDITION 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 VALHALLA ADDITION’s next Consumer Confidence Report due?
- VALHALLA ADDITION’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does VALHALLA ADDITION have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for VALHALLA ADDITION.
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
VALHALLA ADDITION
6057864366
BLACK HAWK, SD 57718