Universal Waste Systems Inc
Terminated WDID 4 19I018901 Whittier, Los Angeles County Region 4 · Los Angeles
At a glance
- Permit Evidence: SMARTS record
- Terminated Industrial
- Notice of Intent (WDID code I) · Permits and applications
- Location Evidence: facility-reported
- Whittier, Los Angeles County
- Region 4 · Los Angeles · Location · Statewide map
- Identified receiving water on the 2026 303(d) list
- Not established
- Shown only when the reported receiving water is identified and corroborated.
- 2026 Integrated Report waters within 1.0 km Evidence: geographic proximity
- 1 waterbody; 1 on the 2026 303(d) list
- Proximity only; not a discharge pathway · Nearby waterbodies
- Monitoring results Evidence: facility-reported
- None in the current exports
- Compliance and enforcement records Evidence: SMARTS record
- 1 inspection · 8 violation records · 5 enforcement actions
- Counts as published in SMARTS; not a compliance determination · Details
Each label shows where a statement comes from. How to read the labels.
Overview and location
Reported facility location HUC12 watershed Corroborated receiving water 2026 Integrated Report waterbodies nearby
Reported location Evidence: facility-reported
- Coordinates
- 33.91843, -118.04803
- Precision
- 5 decimal places
- Shared point
- 4 permits report this exact point
- Matches application record
- same
Facility location as reported by the discharger in SMARTS; not a discharge point or outfall.
- Facility address
- 13316 Leffingwell, Whittier 90605
- Regional Water Board
- 4 — Los Angeles
HUC12 watershed Evidence: spatial
- La Mirada Creek HUC12 180701060602
The facility's reported location lies within this HUC12 watershed (spatial derivation); it is not a discharge location.
Permits and applications Evidence: SMARTS record
Current permit record
- Permit type
- Industrial
- Application type
- Notice of Intent (WDID code I)
- Status
- Terminated
- Operator
- Universal Waste Systems Inc
- Primary industry (SIC)
- 4953-Refuse Systems
- Application ID
- 191764
- NOI processed
- Jul 21, 2004
- Last certified
- Dec 26, 2025
Retrieved from SMARTS Oct 20, 2026. Verify against SMARTS before relying on it.
Permit history
| Application | Type | Status | Processed | Terminated | Certified |
|---|---|---|---|---|---|
| 191764 | Industrial | Terminated | Jul 21, 2004 | — | Dec 26, 2025 |
Every storm water application SMARTS records for this WDID, newest first (1).
Receiving water
- Reported by the facility Evidence: facility-reported
- —
- Discharges directly / indirectly
- — / Y (as answered in the permit application)
No receiving-water text was reported for this permit.
Impaired waters and TMDLs
Two kinds of information, kept apart: 2026 Integrated Report waterbodies near the reported location (geographic proximity only), and TMDL records that SMARTS lists for this facility. Neither establishes where the facility discharges; see Receiving water for the facility's own statement.
Nearby waterbodies Evidence: geographic proximity
Spatial proximity only; discharge pathway not established. Being near a waterbody does not mean the facility discharges to it.
| Waterbody (2026 Integrated Report) | Distance | 2026 303(d) list | Appendix A decisions |
|---|---|---|---|
| Coyote Creek, North Fork CAR4051501020081117111917 | 912 m | listed | 4 |
Waterbodies within 1.0 km of the reported facility location. Method proximity/1.
SMARTS TMDL records Evidence: SMARTS-reported
No TMDL records for this facility in the SMARTS TMDL export.
Reported monitoring results Evidence: facility-reported
Numeric Action Level (NAL) screening is being independently validated and is not shown. Nothing on this page states whether a result exceeded a NAL.
No industrial monitoring results for this permit are in the current exports.
Compliance and enforcement records Evidence: SMARTS record
These are records as the State Water Board publishes them in SMARTS, with the source's own types and statuses. They are not a compliance determination or rating. A record listed here is not proof of a violation beyond what the source states, and the absence of records does not establish compliance.
| Record type | Records | As published | Dates | Retrieved | List |
|---|---|---|---|---|---|
| Violations | 8 | 8 Violation · 0 Potential (preliminary) · 0 Dismissed | Jul 01, 2005 – Mar 24, 2006 | Oct 21, 2026 | All violations |
| Enforcement actions | 5 | 1 issued · 0 draft · 4 withdrawn, rescinded or superseded | Aug 24, 2005 – Jun 02, 2006 | Oct 21, 2026 | All actions |
| Inspections | 1 | inspections, not findings | Jun 13, 2006 – Jun 13, 2006 | Oct 21, 2026 | All inspections |
| Annual reports | 0 | certified reports (contents not shown) | — | Oct 21, 2026 | |
| Water-quality-based corrective action reports | 0 | reports, by parameter | — | Oct 21, 2026 |
Each record type is counted by its own SMARTS identifier. A violation and the enforcement action that cites it are two records in two lists; they are never added together.
Chronological record history (14 records, newest first)
| Date | Record | ID | Type or purpose | Status as published | Detail |
|---|---|---|---|---|---|
| Jun 13, 2006 | Inspections | 1735892 | Enforcement Follow-up | — | |
| Jun 02, 2006 | Enforcement actions | 305463 | ACL (Administrative Civil Liability) | Historical | R4-2006-0045 |
| Mar 24, 2006 | Violations | 409472 | Deficient Report | Violation | Report |
| Mar 03, 2006 | Enforcement actions | 305460 | NOV (Notice of Violation) | Superceded | NOV |
| Mar 03, 2006 | Violations | 409471 | Deficient BMP Implementation | Violation | Internal Report |
| Dec 16, 2005 | Violations | 409470 | Deficient BMP Implementation | Violation | Internal Report |
| Nov 16, 2005 | Enforcement actions | 305457 | NOV (Notice of Violation) | Superceded | NOV |
| Nov 04, 2005 | Violations | 409467 | Incomplete/Insufficient SWPPP | Violation | Inspection |
| Nov 04, 2005 | Violations | 409468 | Unauthorized NSWD | Violation | Inspection |
| Nov 04, 2005 | Violations | 409469 | Deficient BMP Implementation | Violation | Inspection |
| Oct 17, 2005 | Enforcement actions | 305453 | NOV (Notice of Violation) | Superceded | NOV |
| Aug 24, 2005 | Enforcement actions | 305451 | NTC (Notice to Comply) | Superceded | Notice of Noncompliance |
| Jul 01, 2005 | Violations | 409465 | Late Report | Violation | Internal Report |
| Jul 01, 2005 | Violations | 409473 | Late Report | Violation | Report |
Sources and provenance
| Information | Source | Retrieved or published |
|---|---|---|
| Permit, location, receiving-water text | SMARTS Industrial Application Specific Data | Oct 20, 2026 |
| Permit history | SMARTS Storm Water Applications | Oct 20, 2026 |
| Monitoring results | SMARTS Industrial Parameter Data | Oct 20, 2026 |
| Watershed Boundary Dataset HU2 GeoPackages 15, 16, 18 (WBDHU12) | USGS | 2026-10-22 |
| 2026 California Integrated Report, Appendix A: 2026 303(d) List (final) | SWRCB | 2026-10-22 |
| Final_2026_Rivers_and_Streams + Final_2026_Lakes_and_Reservoirs (FeatureServer 0) | SWRCB GIS | 2026-10-22 |
| SMARTS TMDL requirements | SMARTS | 2026-10-21 |
Relationships computed 2026-10-22 with methods facility_huc12/1, proximity/1, receiving_water/2, tmdl_reference/1, waterbody_huc12_ovl/1, waterbody_huc12_pub/1; proximity threshold 1.0 km.
How to read the evidence labels
- Evidence: SMARTS record Evidence: facility-reported Information as published in SMARTS or reported by the discharger.
- Evidence: identification corroborated The reported receiving-water name identifies one official waterbody and the facility's location is consistent with it. It does not establish a discharge pathway.
- Evidence: candidate, awaiting review Evidence: not confirmed The reported name could match one or more official waterbodies, but no identification has been confirmed; nothing is assigned without review.
- Evidence: spatial Evidence: geographic proximity Derived from the reported location only.
- Evidence: SMARTS-reported Source records whose links to official references are not yet reviewed.
- Evidence: unavailable The information could not be loaded or is not in the sources.
Records are shown as published and are not compliance determinations. How geographic context is derived.