Eel River Sawmills Redcrest

Terminated WDID 1 12I005226 Redcrest, Humboldt County Region 1 · North Coast

At a glance

Permit Evidence: SMARTS record
Terminated Industrial
Notice of Intent (WDID code I) · Permits and applications
Location Evidence: facility-reported
Redcrest, Humboldt County
Region 1 · North Coast · Location
Receiving water
Eel River (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
None (no usable location)
Monitoring results Evidence: facility-reported
None in the current exports
Compliance and enforcement records Evidence: SMARTS record
4 inspections · 2 violation records · 1 enforcement action
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

No usable coordinates in the permit record (missing).

Reported location Evidence: facility-reported

Not located: missing.

Facility address
26011 Avenue Of The Giants, Redcrest 95569
Regional Water Board
1 — North Coast

HUC12 watershed Evidence: spatial

No HUC12 assignment (the facility has no usable reported location, or it lies outside the loaded watersheds).

Permits and applications Evidence: SMARTS record

Current permit record

Permit type
Industrial
Application type
Notice of Intent (WDID code I)
Status
Terminated
Operator
Eel River Sawmills
Primary industry (SIC)
2421-Sawmills and Planing Mills, General
Application ID
178285
NOI processed
Apr 09, 1992
Last certified
—
Facility size
21 Acres

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

Permit history

No application records for this WDID in the general applications export.

Receiving water

Reported by the facility Evidence: facility-reported
Eel River
Discharges directly / indirectly
— / — (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

10 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.

No 2026 Integrated Report waterbody lies within the proximity threshold of the reported location (no usable location).

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
Violations2 2 Violation · 0 Potential (preliminary) · 0 Dismissed Aug 30, 1999 – Sep 23, 1999 Oct 21, 2026 All violations
Enforcement actions1 1 issued · 0 draft · 0 withdrawn, rescinded or superseded Aug 30, 1999 – Aug 30, 1999 Oct 21, 2026 All actions
Inspections4inspections, not findings Nov 19, 1993 – Dec 16, 2005 Oct 21, 2026 All inspections
Annual reports0certified reports (contents not shown) — Oct 21, 2026
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 (7 records, newest first)
Compliance and enforcement records, newest first
DateRecordIDType or purposeStatus as publishedDetail
Dec 16, 2005 Inspections 940857 B Type compliance —No Further Action
Oct 31, 2001 Inspections 318429 B Type compliance —
Sep 23, 1999 Violations 140537 Deficient BMP Implementation ViolationInspection
Aug 30, 1999 Enforcement actions 224527 13267 Letter/Order (Water Code section 13267 letter or order) HistoricalUNKNOWN
Aug 30, 1999 Violations 139438 Deficient BMP Implementation ViolationReport
Mar 26, 1999 Inspections 318428 B Type compliance —
Nov 19, 1993 Inspections 318427 Inspection from Vehicle —

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.