Orogrande Mdwca

PWSID: NM3513919

System Details

Population Served92
Service Connections34
Water SourceGroundwater Purchased
System TypeCommunity Water System
OwnerLocal Government
StatusActive
CityOrogrande
Zip Code88342

Areas Served

  • Orogrande, Otero County

Lead & Copper Testing

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

Violation History (47 total)

ContaminantViolationDateHealth-BasedStatus
2022-12-01 MajorReturned to Compliance
2022-12-01 MajorReturned to Compliance
2020-11-18Returned to Compliance
2020-01-01 MajorReturned to Compliance
2020-01-01 MajorAcknowledged
2018-10-01Returned to Compliance
2017-07-07Returned to Compliance
2017-04-01 MajorReturned to Compliance
2016-08-01 MajorReturned to Compliance
2016-08-01 MajorReturned to Compliance
2016-07-01Returned to Compliance
2016-01-01 MajorReturned to Compliance
2016-01-01 MajorReturned to Compliance
2015-06-07YesReturned to Compliance
2015-03-12YesReturned to Compliance
2014-10-01 MajorReturned to Compliance
2014-09-01 MajorReturned to Compliance
2014-04-04Returned to Compliance
2014-01-01 MajorReturned to Compliance
2014-01-01 MajorReturned to Compliance
2013-07-01Returned to Compliance
2013-04-25Returned to Compliance
2013-01-01Returned to Compliance
2012-01-01Returned to Compliance
2011-07-01Returned to Compliance
2011-01-01Returned to Compliance
2010-07-01Returned to Compliance
2010-07-01Returned to Compliance
2010-01-01Returned to Compliance
2009-07-01Returned to Compliance
2009-07-01Returned to Compliance
2009-07-01Returned to Compliance
2009-01-01Returned to Compliance
2008-07-01Returned to Compliance
2008-07-01Returned to Compliance
2008-07-01Returned to Compliance
2008-06-28Returned to Compliance
2008-01-01Returned to Compliance
2007-07-01Returned to Compliance
2007-01-01Returned to Compliance
2006-07-01Returned to Compliance
2006-07-01Returned to Compliance
2006-07-01Returned to Compliance
2006-01-01Returned to Compliance
2005-07-01Returned to Compliance
2005-07-01Returned to Compliance
2005-07-01Returned to Compliance