Goat Canyon Sediment Basin

Active WDID 9 37I019905 Imperial Beach, San Diego County Region 9 · San Diego

At a glance

Permit Evidence: SMARTS record
Active Industrial
Notice of Intent (WDID code I) · Permits and applications
Location Evidence: facility-reported
Imperial Beach, San Diego County
Region 9 · San Diego · Location · Statewide map
Receiving water
Goat Canyon Creek (as reported by the facility)
Evidence: not confirmed 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
6 waterbodies; 4 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
0 inspections · 6 violation records · 9 enforcement actions
Counts as published in SMARTS; not a compliance determination · Details
SMARTS TMDL records Evidence: SMARTS-reported
0 records
TMDL records

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

Open this facility on the statewide map

Reported location Evidence: facility-reported

Coordinates
32.57556, -117.12737
Precision
5 decimal places
Shared point
No
Matches application record
same

Facility location as reported by the discharger in SMARTS; not a discharge point or outfall.

Facility address
301 Caspian Way, Imperial Beach 91932
Regional Water Board
9 — San Diego

HUC12 watershed Evidence: spatial

  • Tijuana River-Frontal Pacific Ocean HUC12 180703051304

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
Active
Operator
Tijuana River NERRR
Primary industry (SIC)
1446-Industrial Sand
Application ID
291363
NOI processed
Nov 08, 2005
Last certified
Jul 01, 2015
Facility size
10 Acres

Retrieved from SMARTS Oct 20, 2026. Verify against SMARTS before relying on it.

Permit history

Storm water applications for this WDID, newest first
ApplicationTypeStatusProcessedTerminatedCertified
291363 IndustrialActiveNov 08, 2005 —Jul 01, 2015

Every storm water application SMARTS records for this WDID, newest first (1).

Receiving water

Reported by the facility Evidence: facility-reported
Goat Canyon Creek
Discharges directly / indirectly
N / Y (as answered in the permit application)

Evidence: not confirmed Not matchable to a single waterbody

Receiving-water text as reported by the discharger in SMARTS; no waterbody identification has been confirmed.

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.

Nearest 2026 Integrated Report waterbodies
Waterbody (2026 Integrated Report)Distance2026 303(d) listAppendix A decisions
Tijuana River Estuary CAE911110001999020814303228 m listed10
Pacific Ocean, Tijuana to North Island CAO9101000020200324048177518 m not listed0
Pacific Ocean Shoreline, Tijuana HU, at Cortez Avenue CAC9111100020111027092832523 m listed1
Oneonta Slough CAR9111100020190614038708595 m not listed0
Pacific Ocean Shoreline, Imperial Beach Pier CAC9101000020050918172745762 m listed3
Show 1 more nearby waterbody
More nearby 2026 Integrated Report waterbodies
Waterbody (2026 Integrated Report)Distance2026 303(d) listAppendix A decisions
Pacific Ocean Shoreline, Tijuana HU, at end of Seacoast Drive CAC9111100020090505131259859 m listed1

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.

Compliance and enforcement records by type
Record typeRecordsAs publishedDatesRetrievedList
Violations6 2 Violation · 0 Potential (preliminary) · 4 Dismissed Jul 01, 2009 – Jul 16, 2026 Oct 21, 2026 All violations
Enforcement actions9 9 issued · 0 draft · 0 withdrawn, rescinded or superseded Jul 01, 2009 – Jul 22, 2026 Oct 21, 2026 All actions
Inspections0inspections, not findings — Oct 21, 2026
Annual reports4certified reports (contents not shown) 2015 – 2018 Oct 21, 2026 All reports
Water-quality-based corrective action reports0reports, 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 (19 records, newest first)
Compliance and enforcement records, newest first
DateRecordIDType or purposeStatus as publishedDetail
Jul 22, 2026 Enforcement actions 471063 NOV (Notice of Violation) Active
Jul 16, 2026 Violations 905140 Late Report ViolationReport
Sep 10, 2025 Enforcement actions 463761 NOV (Notice of Violation) Active
Aug 08, 2025 Enforcement actions 457061 NOV (Notice of Violation) Active
Jul 15, 2025 Violations 892532 Late Report ViolationReport
Jul 10, 2019 Annual reports 952596 Annual report 2018 —
Jul 06, 2018 Annual reports 938010 Annual report 2017 —
Jul 13, 2017 Annual reports 877205 Annual report 2016 —
Jul 01, 2016 Annual reports 845739 Annual report 2015 —
Nov 20, 2012 Enforcement actions 410876 2nd NNC - AR (Second Notice of Non-Compliance (annual report)) Historical
Oct 11, 2012 Enforcement actions 410359 1st NNC - AR (First Notice of Non-Compliance (annual report)) Historical
Oct 11, 2012 Enforcement actions 410360 13267 Letter/Order (Water Code section 13267 letter or order) Historical
Jul 02, 2012 Violations 849490 Late Report DismissedReport
Jul 04, 2011 Enforcement actions 406483 NOV (Notice of Violation) HistoricalR9-2011-0092
Jul 01, 2011 Violations 845538 Late Report DismissedReport
Aug 20, 2010 Enforcement actions 402353 1st NNC - AR (First Notice of Non-Compliance (annual report)) Historical
Jul 01, 2010 Violations 842222 Late Report DismissedReport
Jul 01, 2009 Enforcement actions 400341 NOV (Notice of Violation) Historical
Jul 01, 2009 Violations 840189 Late Report DismissedReport

Sources and provenance

Sources behind this page
InformationSourceRetrieved or published
Permit, location, receiving-water textSMARTS Industrial Application Specific DataOct 20, 2026
Permit historySMARTS Storm Water ApplicationsOct 20, 2026
Monitoring resultsSMARTS Industrial Parameter DataOct 20, 2026
Watershed Boundary Dataset HU2 GeoPackages 15, 16, 18 (WBDHU12)USGS2026-10-22
2026 California Integrated Report, Appendix A: 2026 303(d) List (final)SWRCB2026-10-22
Final_2026_Rivers_and_Streams + Final_2026_Lakes_and_Reservoirs (FeatureServer 0)SWRCB GIS2026-10-22
SMARTS TMDL requirementsSMARTS2026-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

Records are shown as published and are not compliance determinations. How geographic context is derived.