Fort Craig Rest Area East Side
PWSID: NM3590128
This system has no unresolved violations. The most recent violation on record was 2024-04-03.
Violation trend: 0.4 per year over the last 5 years.
System Details
| Population Served | 300 |
| Service Connections | 2 |
| Water Source | Groundwater |
| System Type | Transient Non-Community |
| Owner | State |
| Status | Active |
| City | Las Cruces |
| EPA ZIP on File | 88005 |
Areas Served
- San Antonio, Socorro County
Violation History (2 total)
| Contaminant | Violation | Date | Health-Based | Status |
|---|---|---|---|---|
| 0700 | TT | 2024-04-03 | Yes | Returned to Compliance |
| 0700 | TT | 2024-04-03 | Yes | Returned to Compliance |
Understanding This Water System's Record
Fort Craig Rest Area East Side is a transient non-community water system that draws from groundwater sources and serves a population of 300 in Las Cruces, New Mexico. This page shows its complete compliance history as reported to the EPA's Safe Drinking Water Information System (SDWIS), the federal database that tracks every public water system in the United States.
What Do These Violations Mean?
Health-based violations mean the system exceeded an EPA maximum contaminant level (MCL) or failed to provide required treatment. These indicate potential health risks from contaminants like lead, arsenic, bacteria, nitrates, or disinfection byproducts. Non-health-based violations involve monitoring, reporting, or procedural requirements — the system missed a testing deadline or failed to notify customers, but contaminant levels were not necessarily unsafe.
What Should You Do?
Your water utility is required to publish an annual Consumer Confidence Report (CCR) that details test results and any violations. If your system has active health-based violations, consider a certified water filter rated for the specific contaminants involved. The contaminant guides on this site explain health risks and filter options for common pollutants. For the most current results, contact your water utility directly — EPA data can lag weeks or months behind real-time testing.