Ojo Sarco Mdwca

PWSID: NM3556821

System Details

Population Served225
Service Connections75
Water SourceGroundwater
System TypeCommunity Water System
OwnerLocal Government
StatusActive
CityOjo Sarco
Zip Code87521

Areas Served

  • Ojo Sarco, Rio Arriba County

Lead & Copper Testing

ContaminantLevelEPA Action LevelStatus
Lead (90th percentile)0.0016 mg/L0.015 mg/LBelow Action Level

Violation History (51 total)

ContaminantViolationDateHealth-BasedStatus
2023-10-01Returned to Compliance
2023-10-01Returned to Compliance
2022-07-01Returned to Compliance
2022-07-01Returned to Compliance
2022-07-01Returned to Compliance
2019-07-01Returned to Compliance
2019-07-01Returned to Compliance
2018-03-08Returned to Compliance
2018-03-08Returned to Compliance
2018-03-08Returned to Compliance
2018-03-08Returned to Compliance
2017-07-09Returned to Compliance
2017-07-09Returned to Compliance
2017-01-01 MajorReturned to Compliance
2017-01-01 MajorReturned to Compliance
2016-12-01 MajorReturned to Compliance
2016-12-01 MajorReturned to Compliance
2016-11-01 MajorReturned to Compliance
2016-11-01 MajorReturned to Compliance
2016-10-01 MajorReturned to Compliance
2016-10-01 MajorReturned to Compliance
2016-10-01Returned to Compliance
2016-10-01Returned to Compliance
2016-09-01 MajorReturned to Compliance
2016-09-01 MajorReturned to Compliance
2016-08-01 MajorReturned to Compliance
2016-08-01 MajorReturned to Compliance
2016-07-01 MajorReturned to Compliance
2016-07-01 MajorReturned to Compliance
2016-06-02Returned to Compliance
2016-06-02Returned to Compliance
2016-06-01 MajorReturned to Compliance
2016-06-01 MajorReturned to Compliance
2015-07-01Returned to Compliance
2015-07-01Returned to Compliance
2015-01-23YesReturned to Compliance
2015-01-23YesReturned to Compliance
2015-01-23YesReturned to Compliance
2015-01-23YesReturned to Compliance
2015-01-23YesReturned to Compliance
2015-01-23YesReturned to Compliance
2014-10-28YesReturned to Compliance
2014-10-28YesReturned to Compliance
2014-10-28YesReturned to Compliance
2014-10-28YesReturned to Compliance
2014-10-28YesReturned to Compliance
2014-10-28YesReturned to Compliance
2013-10-01Returned to Compliance
2011-07-01Returned to Compliance
2010-07-01Returned to Compliance

Showing 50 of 51 historical violations.