LOVINGSTON, VA · Nelson County
NCSA - LOVINGSTON Water System
Consumer Confidence Report status
NCSA - LOVINGSTON 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 NCSA - LOVINGSTON.
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)
- VA2125325
- System type
- Community Water System
- Population served
- 2,493
- Service connections
- 408
- Ownership
- local government
- Water source
- surface water (rivers, lakes, or reservoirs)
NCSA - LOVINGSTON is one of 391 community water systems in Virginia in the 501 to 3,300 people size category, serving 2,493 people from surface water.
As of August 1, 2026, its federal record holds 1 entry in 2023, all of which EPA lists as closed. Nothing has been added since 2023.
All 1 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 inorganic chemicals.
Violation history
Monitoring, Regular
—Nickel
January 1, 2023 – December 31, 2025
Archived
Archived closed in EPA's records (typically due to age or a data correction)
| Period | Violation | Contaminant / rule | Health-based | Status |
|---|---|---|---|---|
| January 1, 2023 – December 31, 2025 | Monitoring, Regular | Nickel | — | Archived |
Archived closed in EPA's records (typically due to age or a data correction)
Enforcement actions
- February 10, 2026State Formal Notice of Violation issued3 linked violations
- February 10, 2026State Public Notification requested1 linked violation
- February 10, 2026State Formal Notice of Violation issued1 linked violation
- February 10, 2026State Public Notification requested10 linked violations
- February 10, 2026State Formal Notice of Violation issued10 linked violations
- February 10, 2026State Formal Notice of Violation issued10 linked violations
- February 10, 2026State Public Notification requested10 linked violations
- February 10, 2026State Formal Notice of Violation issuedgeneral compliance action — not tied to a specific violation on record
- February 10, 2026State Public Notification requestedgeneral compliance action — not tied to a specific violation on record
- February 10, 2026State Public Notification requested1 linked violation
- February 10, 2026State Public Notification requested1 linked violation
- February 10, 2026State Formal Notice of Violation issued1 linked violation
- February 10, 2026State Public Notification requested12 linked violations
- February 10, 2026State Formal Notice of Violation issued10 linked violations
- February 10, 2026State Public Notification requested11 linked violations
- February 10, 2026State Formal Notice of Violation issued12 linked violations
- February 10, 2026State Formal Notice of Violation issued2 linked violations
- February 10, 2026State Public Notification requested23 linked violations
- February 10, 2026State Formal Notice of Violation issued22 linked violations
- February 10, 2026State Public Notification requested2 linked violations
- February 10, 2026State Formal Notice of Violation issued3 linked violations
- February 10, 2026State Public Notification requested1 linked violation
- January 27, 2026State Public Notification requested3 linked violations
- January 27, 2026State Formal Notice of Violation issued3 linked violations
- December 20, 2025State Compliance achieved16 linked violations
- September 24, 2025State Compliance achieved41 linked violations
- September 2, 2025State Formal Notice of Violation issued6 linked violations
- September 2, 2025State Public Notification requested23 linked violations
- September 2, 2025State Formal Notice of Violation issued23 linked violations
- May 21, 2025State Compliance achieved4 linked violations
- February 18, 2025State Compliance achieved7 linked violations
- January 29, 2025State Public Notification requested6 linked violations
- January 28, 2025State Formal Notice of Violation issued1 linked violation
- January 28, 2025State Public Notification requested3 linked violations
- January 24, 2025State Compliance achieved2 linked violations
- November 14, 2024State Compliance achieved3 linked violations
- September 26, 2024State Public Notification requested7 linked violations
- July 17, 2024State Compliance achieved4 linked violations
- July 3, 2024State Public Notification received4 linked violations
- June 1, 2024State Compliance achieved5 linked violations
- December 14, 2022State Compliance achieved1 linked violation
- April 19, 2022State Public Notification received1 linked violation
- January 26, 2022State Public Notification requested1 linked violation
- January 26, 2022State Formal Notice of Violation issued1 linked violation
- April 17, 2020State Public Notification received2 linked violations
- April 17, 2020State Public Notification received1 linked violation
- April 17, 2020State Public Notification received10 linked violations
- April 17, 2020State Public Notification received1 linked violation
- April 17, 2020State Public Notification received21 linked violations
- April 17, 2020State Public Notification received13 linked violations
- April 17, 2020State Public Notification received6 linked violations
- April 17, 2020State Public Notification received3 linked violations
- April 17, 2020State Public Notification received2 linked violations
- January 22, 2020State Public Notification requested1 linked violation
- January 22, 2020State Public Notification requested21 linked violations
- January 22, 2020State Formal Notice of Violation issued21 linked violations
- January 22, 2020State Formal Notice of Violation issued11 linked violations
- January 22, 2020State Public Notification requested11 linked violations
- January 22, 2020State Formal Notice of Violation issued2 linked violations
- January 22, 2020State Public Notification requested3 linked violations
- January 22, 2020State Formal Notice of Violation issued3 linked violations
- January 22, 2020State Public Notification requested2 linked violations
- January 22, 2020State Public Notification requested13 linked violations
- January 22, 2020State Formal Notice of Violation issued13 linked violations
- January 22, 2020State Formal Notice of Violation issued2 linked violations
- January 22, 2020State Public Notification requested6 linked violations
- January 22, 2020State Formal Notice of Violation issued6 linked violations
- January 22, 2020State Public Notification requested2 linked violations
- January 22, 2020State Public Notification requested2 linked violations
- January 22, 2020State Formal Notice of Violation issued2 linked violations
- January 10, 2020State Compliance achieved2 linked violations
- January 10, 2020State Compliance achieved3 linked violations
- January 10, 2020State Compliance achieved3 linked violations
- January 10, 2020State Compliance achieved13 linked violations
- January 10, 2020State Compliance achieved6 linked violations
- January 8, 2020State Compliance achieved10 linked violations
- January 8, 2020State Compliance achieved1 linked violation
- January 8, 2020State Compliance achieved21 linked violations
- January 8, 2020State Compliance achieved1 linked violation
- December 26, 2019State Public Notification requested2 linked violations
- June 23, 2017State Public Notification received2 linked violations
- September 28, 2016State Public Notification requested2 linked violations
- August 22, 2016State Public Notification received5 linked violations
- July 26, 2016State Public Notification requested3 linked violations
- August 22, 2013State Public Notification requested3 linked violations
- July 19, 2013State Public Notification received3 linked violations
- July 11, 2013State Public Notification requested2 linked violations
- January 17, 2007State Formal Notice of Violation issued3 linked violations
- January 8, 2007State Formal Notice of Violation issued3 linked violations
Common questions
Is NCSA - LOVINGSTON required to publish a Consumer Confidence Report?
- Yes. NCSA - LOVINGSTON 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 NCSA - LOVINGSTON’s next Consumer Confidence Report due?
- NCSA - LOVINGSTON’s next Consumer Confidence Report is due by July 1, 2027. The report covers calendar year 2026.
Does NCSA - LOVINGSTON have any open drinking water violations on record?
- As of August 1, 2026, EPA's federal records show no open violations for NCSA - LOVINGSTON.
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
MILLER, GEORGE T. JR.
434-263-5341
LOVINGSTON, VA 22949