Public water system record
CSA 70 W-3 Hacienda
Serves Morongo Valley, San Bernardino County, CA · 611 people served
Federal records show 37 health-based violations and no monitoring/reporting issues for CSA 70 W-3 Hacienda in the last ten years. The most serious issue in this window was a Combined Uranium violation that EPA lists as archived, not resolved.
System profile
Source water
Groundwater
ZIP
92415
EPA system ID
CA3600114
- Health-based violations, last 10 years
- 37
- Resolved
- 0
- Unresolved
- 0
- Archived by EPA
- 37
- Any acute record
- No
- Monitoring issues, last 10 years
- 0
Key facts
- CSA 70 W-3 Hacienda draws water from 2 wells.
- Most recent formal enforcement: compliance order (no penalty) by California, December 2018.
- Record on file since 1980, with 20 health-based violations before October 19, 2016.
- Lead pipe inventory: 0 lead and 64 unknown out of 165 service lines.
Check whether CSA 70 W-3 Hacienda serves your address
Health-based violations
Since October 2016Violation data reflects EPA records through March 2026. For the most current status, visit the EPA ECHO database.
| Contaminant | Rule family | Start date | Status | Acute |
|---|---|---|---|---|
|
Combined Uranium
Contaminant limit exceeded
|
340 | Oct 1, 2025 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Jul 1, 2025 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Apr 1, 2025 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Jan 1, 2025 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Oct 1, 2024 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Jul 1, 2024 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Apr 1, 2024 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Jan 1, 2024 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Oct 1, 2023 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Jul 1, 2023 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Apr 1, 2023 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Jan 1, 2023 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Oct 1, 2022 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Jul 1, 2022 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Apr 1, 2022 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Jan 1, 2022 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Oct 1, 2021 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Jul 1, 2021 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Apr 1, 2021 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Jan 1, 2021 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Oct 1, 2020 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Jul 1, 2020 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Apr 1, 2020 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Jan 1, 2020 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Oct 1, 2019 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Jul 1, 2019 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Apr 1, 2019 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Jan 1, 2019 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Oct 1, 2018 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Jul 1, 2018 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Apr 1, 2018 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Jan 1, 2018 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Oct 1, 2017 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Jul 1, 2017 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Apr 1, 2017 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Jan 1, 2017 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
|
Combined Uranium
Contaminant limit exceeded
|
340 | Oct 1, 2016 |
Archived
Violation period ended. EPA no longer counts it toward current compliance, but no fix was formally recorded.
|
No |
Full record since 1980
EPA's records for CSA 70 W-3 Hacienda go back to 1980. Before October 19, 2016 they list 20 health-based violations (1 resolved, 19 archived by EPA without a recorded fix) and 3 monitoring or reporting violations.
| Violations that began in | Health-based | Monitoring and reporting |
|---|---|---|
| 1980s | 0 | 2 |
| 1990s | 0 | 1 |
| 2010 to October 18, 2016 | 20 | 0 |
| October 19, 2016 to 2019 | 12 | 0 |
| 2020s | 24 | 0 |
Most recent health-based violation before October 19, 2016: Combined Uranium, began October 2016, Archived.
Show all 20 health-based violations before October 19, 2016
| Contaminant | Start date | Status |
|---|---|---|
|
Combined Uranium
Contaminant limit exceeded
|
Oct 1, 2016 | Archived |
|
Combined Uranium
Contaminant limit exceeded
|
Jul 1, 2016 | Archived |
|
Combined Uranium
Contaminant limit exceeded
|
Apr 1, 2016 | Archived |
|
Combined Uranium
Contaminant limit exceeded
|
Jan 1, 2016 | Archived |
|
Combined Uranium
Contaminant limit exceeded
|
Oct 1, 2015 | Archived |
|
Combined Uranium
Contaminant limit exceeded
|
Jul 1, 2015 | Archived |
|
Combined Uranium
Contaminant limit exceeded
|
Apr 1, 2015 | Archived |
|
Combined Uranium
Contaminant limit exceeded
|
Jan 1, 2015 | Archived |
|
Combined Uranium
Contaminant limit exceeded
|
Oct 1, 2014 | Archived |
|
Combined Uranium
Contaminant limit exceeded
|
Jul 1, 2014 | Archived |
|
Combined Uranium
Contaminant limit exceeded
|
Apr 1, 2014 | Archived |
|
Combined Uranium
Contaminant limit exceeded
|
Jan 1, 2014 | Archived |
|
Combined Uranium
Contaminant limit exceeded
|
Oct 1, 2013 | Archived |
|
Combined Uranium
Contaminant limit exceeded
|
Jul 1, 2013 | Archived |
|
Combined Uranium
Contaminant limit exceeded
|
Apr 1, 2013 | Archived |
|
Combined Uranium
Contaminant limit exceeded
|
Jan 1, 2013 | Archived |
|
Combined Uranium
Contaminant limit exceeded
|
Oct 1, 2012 | Archived |
|
Combined Uranium
Contaminant limit exceeded
|
Jul 1, 2012 | Archived |
|
Combined Uranium
Contaminant limit exceeded
|
Apr 1, 2012 | Resolved |
|
Combined Uranium
Contaminant limit exceeded
|
Jan 1, 2012 | Archived |
Enforcement actions
California regulators took 4 formal enforcement actions against CSA 70 W-3 Hacienda between 2011 and 2018. The most recent was a compliance order (no penalty) in December 2018.
| Date | By | Action | Violations covered |
|---|---|---|---|
| Dec 28, 2018 | California | Compliance order (no penalty) | 28 violations (28 health-based): Combined Uranium |
| Jun 20, 2017 | California | Compliance order (no penalty) | 7 violations (7 health-based): Combined Uranium |
| Sep 19, 2012 | California | Compliance order (no penalty) | 1 violation (1 health-based): Combined Uranium |
| Nov 22, 2011 | California | Compliance order (no penalty) | 20 violations (20 health-based): Combined Uranium |
What the violations mean
Combined Uranium
37 incidentsTest results for Combined Uranium were above the federal limit (a maximum contaminant level violation).
The utility had to notify customers about each of these violations.
Where the water comes from
CSA 70 W-3 Hacienda draws water from 2 wells.
Annual water quality report
CSA 70 W-3 Hacienda must give its customers an annual water quality report (Consumer Confidence Report) by July 1, with the levels its tests found in the previous year.
Where the state allows it, systems serving fewer than 10,000 people may publish the report in a local newspaper or news site instead of mailing it, and must provide a copy on request.
Find a posted report with EPA's Consumer Confidence Report search
Testing your own water
To test the water at your tap, or a private well this record does not cover, use a laboratory certified for drinking water by California.
Certified drinking water labs by state EPA guidance for private wells