Tri M Co
Terminated WDID 9 37NEC005278 San Marcos, San Diego County Region 9 · San Diego
At a glance
- Permit Evidence: SMARTS record
- Terminated Industrial
- No Exposure Certification (NEC) · Permits and applications
- Location Evidence: facility-reported
- San Marcos, San Diego County
- Region 9 · San Diego · Location · Statewide map
- Receiving water
- San Marcos Creek (as reported by the facility)
- Evidence: candidate, awaiting review Details
- 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
- 2 waterbodies; 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
- 2 inspections · 3 violation records · 1 enforcement action
- 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.14474, -117.15092
- Precision
- 5 decimal places
- Shared point
- 3 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
- 528 E Mission Rd, San Marcos 92069
- Regional Water Board
- 9 — San Diego
HUC12 watershed Evidence: spatial
- San Marcos Creek HUC12 180703030503
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
- No Exposure Certification (NEC)
- Status
- Terminated
- Operator
- Tri M Co
- Primary industry (SIC)
- 3444-Sheet Metal Work
- Application ID
- 218498
- NOI processed
- May 09, 1996
- Termination effective
- Dec 31, 2019
- Last certified
- Jul 03, 2019
- Facility size
- 10 Acres
- Impervious area
- 100 %
Retrieved from SMARTS Oct 20, 2026. Verify against SMARTS before relying on it.
Permit history
| Application | Type | Status | Processed | Terminated | Certified |
|---|---|---|---|---|---|
| 218498 | Industrial | Terminated | May 09, 1996 | Dec 31, 2019 | Jul 03, 2019 |
Every storm water application SMARTS records for this WDID, newest first (1).
Receiving water
- Reported by the facility Evidence: facility-reported
- San Marcos Creek
- Discharges directly / indirectly
- N / Y (as answered in the permit application)
Evidence: not confirmed Evidence: candidate, awaiting review Awaiting review
Receiving-water text as reported by the discharger in SMARTS; no waterbody identification has been confirmed.
Why it is not confirmed (1)
- C1 name is only a prefix of official names
3 official waterbodies share this name; none is assigned without review.
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 |
|---|---|---|---|
| San Marcos Creek, Upper (above San Marcos Lake) CAR9045200020200514036006 | 138 m | listed | 9 |
| San Marcos Creek, unnamed fork at Twin Oaks Valley Road CAR9045300020110812113554 | 960 m | not listed | 0 |
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 | 3 | 3 Violation · 0 Potential (preliminary) · 0 Dismissed | Sep 26, 2001 – Nov 18, 2004 | Oct 21, 2026 | All violations |
| Enforcement actions | 1 | 1 issued · 0 draft · 0 withdrawn, rescinded or superseded | Feb 04, 2005 – Feb 04, 2005 | Oct 21, 2026 | All actions |
| Inspections | 2 | inspections, not findings | Sep 26, 2001 – Nov 18, 2004 | Oct 21, 2026 | All inspections |
| Annual reports | 2 | certified reports (contents not shown) | 2015 – 2016 | Oct 21, 2026 | All reports |
| 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 (8 records, newest first)
| Date | Record | ID | Type or purpose | Status as published | Detail |
|---|---|---|---|---|---|
| Jun 30, 2017 | Annual reports | 879719 | Annual report 2016 | — | |
| Jul 14, 2016 | Annual reports | 842433 | Annual report 2015 | — | |
| Feb 04, 2005 | Enforcement actions | 256401 | NOV (Notice of Violation) | Active | R9-2005-0058 |
| Nov 18, 2004 | Inspections | 336630 | B Type compliance | — | |
| Nov 18, 2004 | Violations | 266646 | Deficient BMP Implementation | Violation | Inspection |
| Sep 26, 2001 | Inspections | 324575 | B Type compliance | — | |
| Sep 26, 2001 | Violations | 202655 | Deficient BMP Implementation | Violation | Inspection |
| Sep 26, 2001 | Violations | 205175 | Deficient BMP Implementation | Violation | Inspection |
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.