City of Red Bluff
Active WDID 5R52I000539 Red Bluff, Tehama County Region 5R · Central Valley (Redding)
At a glance
- Permit Evidence: SMARTS record
- Active Industrial
- Notice of Intent (WDID code I) · Permits and applications
- Location Evidence: facility-reported
- Red Bluff, Tehama County
- Region 5R · Central Valley (Redding) · Location · Statewide map
- Receiving water
- Sacramento 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
- Monitoring results Evidence: facility-reported
- 47 distinct results, 4 reporting years (2015 to 2018)
- Most recent sample Nov 27, 2018 · Monitoring
- Compliance and enforcement records Evidence: SMARTS record
- 2 inspections · 7 violation records · 6 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
- 40.156893, -122.250701
- Precision
- 6 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
- 1800 Airport Blvd, Red Bluff 96080
- Regional Water Board
- 5R — Central Valley (Redding)
HUC12 watershed Evidence: spatial
- Lower Reeds Creek HUC12 180201550202
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
- City of Red Bluff
- Primary industry (SIC)
- 4581-Airports, Flying Fields, and Airport Terminal Services
- Application ID
- 197678
- NOI processed
- Mar 16, 1992
- Last certified
- Nov 21, 2025
- Facility size
- 505 Acres
Retrieved from SMARTS Oct 20, 2026. Verify against SMARTS before relying on it.
Permit history
| Application | Type | Status | Processed | Terminated | Certified |
|---|---|---|---|---|---|
| 197678 | Industrial | Active | Mar 16, 1992 | — | Nov 21, 2025 |
Every storm water application SMARTS records for this WDID, newest first (1).
Receiving water
- Reported by the facility Evidence: facility-reported
- Sacramento River
- Discharges directly / indirectly
- Y / N (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
7 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.
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.
47 distinct measurements across 3 parameters, most recent sample Nov 27, 2018.
By reporting year
| Reporting year (July–June) | Distinct results | Parameters | With several versions | First sample | Last sample |
|---|---|---|---|---|---|
| 2018 | 8 | 2 | 0 | Nov 27, 2018 | Nov 27, 2018 |
| 2017 | 9 | 3 | 0 | Jan 18, 2018 | Jan 18, 2018 |
| 2016 | 18 | 3 | 0 | Oct 24, 2016 | Feb 02, 2017 |
| 2015 | 12 | 3 | 0 | Jan 04, 2016 | Jan 04, 2016 |
By parameter
| Parameter | Units | Measurements | Below detection | First sample | Last sample | Results |
|---|---|---|---|---|---|---|
| Oil and Grease | mg/L | 17 | 16 | Jan 04, 2016 | Nov 27, 2018 | Results |
| Total Suspended Solids (TSS) | mg/L | 17 | 0 | Jan 04, 2016 | Nov 27, 2018 | Results |
| pH | SU | 13 | 0 | Jan 04, 2016 | Jan 18, 2018 | Results |
All results (47 distinct rows)
| Sample date | Parameter | Result | Units | Location type | Event | Method | Report | Versions |
|---|---|---|---|---|---|---|---|---|
| Nov 27, 2018 | Oil and Grease | ND | mg/L | Effluent | Qualifying Storm Event | A5220B | 1033768 | |
| Nov 27, 2018 | Oil and Grease | ND | mg/L | Effluent | Qualifying Storm Event | A5220B | 1033768 | |
| Nov 27, 2018 | Oil and Grease | ND | mg/L | Effluent | Qualifying Storm Event | A5220B | 1033768 | |
| Nov 27, 2018 | Oil and Grease | ND | mg/L | Effluent | Qualifying Storm Event | A5220B | 1033768 | |
| Nov 27, 2018 | Total Suspended Solids (TSS) | 6 | mg/L | Effluent | Qualifying Storm Event | A2540D | 1033768 | |
| Nov 27, 2018 | Total Suspended Solids (TSS) | 5.8 | mg/L | Effluent | Qualifying Storm Event | A2540D | 1033768 | |
| Nov 27, 2018 | Total Suspended Solids (TSS) | 3 | mg/L | Effluent | Qualifying Storm Event | A2540D | 1033768 | |
| Nov 27, 2018 | Total Suspended Solids (TSS) | 5 | mg/L | Effluent | Qualifying Storm Event | A2540D | 1033768 | |
| Jan 18, 2018 | Oil and Grease | ND | mg/L | Effluent | Qualifying Storm Event | E1664A | 992724 | |
| Jan 18, 2018 | Oil and Grease | ND | mg/L | Effluent | Qualifying Storm Event | E1664A | 992724 | |
| Jan 18, 2018 | Oil and Grease | ND | mg/L | Effluent | Qualifying Storm Event | E1664A | 992724 | |
| Jan 18, 2018 | pH | 7.8 | SU | Effluent | Qualifying Storm Event | pH_Field | 992724 | |
| Jan 18, 2018 | pH | 8.2 | SU | Effluent | Qualifying Storm Event | pH_Field | 992724 | |
| Jan 18, 2018 | pH | 8.1 | SU | Effluent | Qualifying Storm Event | pH_Field | 992724 | |
| Jan 18, 2018 | Total Suspended Solids (TSS) | 7 | mg/L | Effluent | Qualifying Storm Event | A2540D | 992724 | |
| Jan 18, 2018 | Total Suspended Solids (TSS) | 9.5 | mg/L | Effluent | Qualifying Storm Event | A2540D | 992724 | |
| Jan 18, 2018 | Total Suspended Solids (TSS) | 13 | mg/L | Effluent | Qualifying Storm Event | A2540D | 992724 | |
| Feb 02, 2017 | Oil and Grease | ND | mg/L | Effluent | Qualifying Storm Event | E1664A | 925652 | |
| Feb 02, 2017 | Oil and Grease | ND | mg/L | Effluent | Qualifying Storm Event | E1664A | 925652 | |
| Feb 02, 2017 | Oil and Grease | ND | mg/L | Effluent | Qualifying Storm Event | E1664A | 925652 | |
| Feb 02, 2017 | Oil and Grease | ND | mg/L | Effluent | Qualifying Storm Event | E1664A | 925652 | |
| Feb 02, 2017 | pH | 8.67 | SU | Effluent | Qualifying Storm Event | pH_Field | 925652 | |
| Feb 02, 2017 | pH | 8.34 | SU | Effluent | Qualifying Storm Event | pH_Field | 925652 | |
| Feb 02, 2017 | pH | 7.83 | SU | Effluent | Qualifying Storm Event | pH_Field | 925652 | |
| Feb 02, 2017 | pH | 7.32 | SU | Effluent | Qualifying Storm Event | pH_Field | 925652 | |
| Feb 02, 2017 | Total Suspended Solids (TSS) | 1 | mg/L | Effluent | Qualifying Storm Event | A2540D | 925652 | |
| Feb 02, 2017 | Total Suspended Solids (TSS) | 16 | mg/L | Effluent | Qualifying Storm Event | A2540D | 925652 | |
| Feb 02, 2017 | Total Suspended Solids (TSS) | 1 | mg/L | Effluent | Qualifying Storm Event | A2540D | 925652 | |
| Feb 02, 2017 | Total Suspended Solids (TSS) | 3 | mg/L | Effluent | Qualifying Storm Event | A2540D | 925652 | |
| Oct 24, 2016 | Oil and Grease | ND | mg/L | Effluent | Qualifying Storm Event | E1664A | 908639 | |
| Oct 24, 2016 | Oil and Grease | ND | mg/L | Effluent | Qualifying Storm Event | E1664A | 908639 | |
| Oct 24, 2016 | pH | 8.8 | SU | Effluent | Qualifying Storm Event | pH_Field | 908639 | |
| Oct 24, 2016 | pH | 8.07 | SU | Effluent | Qualifying Storm Event | pH_Field | 908639 | |
| Oct 24, 2016 | Total Suspended Solids (TSS) | 17 | mg/L | Effluent | Qualifying Storm Event | A2540D | 908639 | |
| Oct 24, 2016 | Total Suspended Solids (TSS) | 19 | mg/L | Effluent | Qualifying Storm Event | A2540D | 908639 | |
| Jan 04, 2016 | Oil and Grease | ND | mg/L | Effluent | Qualifying Storm Event | E1664A | 906272 | |
| Jan 04, 2016 | Oil and Grease | ND | mg/L | Effluent | Qualifying Storm Event | E1664A | 906272 | |
| Jan 04, 2016 | Oil and Grease | ND | mg/L | Effluent | Qualifying Storm Event | E1664A | 906272 | |
| Jan 04, 2016 | Oil and Grease | 1.6 | mg/L | Effluent | Qualifying Storm Event | E1664A | 906272 | |
| Jan 04, 2016 | pH | 9.01 | SU | Effluent | Qualifying Storm Event | pH_Field | 906272 | |
| Jan 04, 2016 | pH | 8.41 | SU | Effluent | Qualifying Storm Event | pH_Field | 906272 | |
| Jan 04, 2016 | pH | 7.16 | SU | Effluent | Qualifying Storm Event | pH_Field | 906272 | |
| Jan 04, 2016 | pH | 7.14 | SU | Effluent | Qualifying Storm Event | pH_Field | 906272 | |
| Jan 04, 2016 | Total Suspended Solids (TSS) | 14 | mg/L | Effluent | Qualifying Storm Event | A2540D | 906272 | |
| Jan 04, 2016 | Total Suspended Solids (TSS) | 78 | mg/L | Effluent | Qualifying Storm Event | A2540D | 906272 | |
| Jan 04, 2016 | Total Suspended Solids (TSS) | 9.8 | mg/L | Effluent | Qualifying Storm Event | A2540D | 906272 | |
| Jan 04, 2016 | Total Suspended Solids (TSS) | 10 | mg/L | Effluent | Qualifying Storm Event | A2540D | 906272 |
Results are shown exactly as reported by the discharger. Identical rows repeated in the State's export are shown once. Where the export contains different versions of the same sample and parameter, each version is listed and flagged. Details.
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 | 7 | 7 Violation · 0 Potential (preliminary) · 0 Dismissed | Jun 30, 1998 – Jul 15, 2025 | Oct 21, 2026 | All violations |
| Enforcement actions | 6 | 6 issued · 0 draft · 0 withdrawn, rescinded or superseded | Aug 14, 2002 – Aug 08, 2025 | Oct 21, 2026 | All actions |
| Inspections | 2 | inspections, not findings | Aug 07, 2002 – Mar 23, 2005 | Oct 21, 2026 | All inspections |
| Annual reports | 7 | certified reports (contents not shown) | 2015 – 2025 | 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 (22 records, newest first)
| Date | Record | ID | Type or purpose | Status as published | Detail |
|---|---|---|---|---|---|
| May 19, 2026 | Annual reports | 1069478 | Annual report 2020 | — | |
| May 19, 2026 | Annual reports | 1336008 | Annual report 2025 | — | |
| Aug 19, 2025 | Annual reports | 1294850 | Annual report 2024 | — | |
| Aug 08, 2025 | Enforcement actions | 457161 | NOV (Notice of Violation) | Active | |
| Jul 15, 2025 | Violations | 892632 | Late Report | Violation | Report |
| Jul 18, 2019 | Annual reports | 954383 | Annual report 2018 | — | |
| Jul 24, 2018 | Annual reports | 939801 | Annual report 2017 | — | |
| Feb 15, 2018 | Annual reports | 879089 | Annual report 2016 | — | |
| Jul 12, 2016 | Annual reports | 845901 | Annual report 2015 | — | |
| Oct 26, 2012 | Enforcement actions | 410609 | SEL (Staff Enforcement Letter) | Historical | |
| Jul 01, 2012 | Violations | 849688 | Deficient Report | Violation | Report |
| Dec 15, 2009 | Enforcement actions | 401527 | SEL (Staff Enforcement Letter) | Historical | |
| Mar 23, 2005 | Inspections | 1217661 | B Type compliance | — | No Further Action |
| Aug 20, 2004 | Enforcement actions | 253344 | SEL (Staff Enforcement Letter) | Historical | |
| Jul 01, 2004 | Violations | 262145 | Deficient BMP Implementation | Violation | Inspection |
| Aug 23, 2002 | Enforcement actions | 248472 | SEL (Staff Enforcement Letter) | Historical | |
| Aug 14, 2002 | Enforcement actions | 248556 | NNC (Notice of Non-Compliance) | Historical | |
| Aug 07, 2002 | Inspections | 326426 | B Type compliance | — | |
| Jul 01, 2002 | Violations | 220663 | Deficient BMP Implementation | Violation | Inspection |
| Jul 01, 2002 | Violations | 220845 | Deficient Report | Violation | Inspection |
| Jul 02, 1999 | Violations | 167304 | Deficient Report | Violation | Inspection |
| Jun 30, 1998 | Violations | 136671 | Late Report | Violation | Internal 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.