Portola Class III Landfill

Active WDID 5R32I015203 Portola, Plumas 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
Portola, Plumas County
Region 5R · Central Valley (Redding) · Location · Statewide map
Receiving water
Feather 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
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
9 inspections · 10 violation records · 14 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
39.822742, -120.448392
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
Meadow, Portola 96122
Regional Water Board
5R — Central Valley (Redding)

HUC12 watershed Evidence: spatial

  • Humbug Creek-Middle Fork Feather River HUC12 180201230404

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
Portola City
Primary industry (SIC)
1446-Industrial Sand
Application ID
197301
NOI processed
Jul 01, 1999
Last certified
Jun 01, 2015

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

Permit history

Storm water applications for this WDID, newest first
ApplicationTypeStatusProcessedTerminatedCertified
197301 IndustrialActiveJul 01, 1999 —Jun 01, 2015

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

Receiving water

Reported by the facility Evidence: facility-reported
Feather 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

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

Nearest 2026 Integrated Report waterbodies
Waterbody (2026 Integrated Report)Distance2026 303(d) listAppendix A decisions
Feather River, Middle Fork (Sierra Valley to Lake Oroville, Butte and Plumas Counties) CAR5183305020020610143011538 m listed4

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
Violations10 10 Violation · 0 Potential (preliminary) · 0 Dismissed Jul 01, 2002 – Jul 16, 2026 Oct 21, 2026 All violations
Enforcement actions14 14 issued · 0 draft · 0 withdrawn, rescinded or superseded Aug 14, 2002 – Jul 22, 2026 Oct 21, 2026 All actions
Inspections9inspections, not findings Oct 10, 2006 – Jun 28, 2017 Oct 21, 2026 All inspections
Annual reports11certified reports (contents not shown) 2015 – 2025 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 (44 records, newest first)
Compliance and enforcement records, newest first
DateRecordIDType or purposeStatus as publishedDetail
Jul 27, 2026 Annual reports 1334458 Annual report 2025 —
Jul 22, 2026 Enforcement actions 470584 NOV (Notice of Violation) Active
Jul 16, 2026 Violations 904661 Late Report ViolationReport
Feb 18, 2026 Annual reports 1111502 Annual report 2021 —
Aug 19, 2025 Annual reports 1242263 Annual report 2023 —
Aug 19, 2025 Annual reports 1293240 Annual report 2024 —
Aug 08, 2025 Enforcement actions 457036 NOV (Notice of Violation) Active
Jul 15, 2025 Violations 892507 Late Report ViolationReport
Jul 09, 2024 Annual reports 1188218 Annual report 2022 —
Jul 13, 2021 Annual reports 1067461 Annual report 2020 —
Jul 06, 2020 Annual reports 984645 Annual report 2019 —
Jul 17, 2019 Annual reports 952155 Annual report 2018 —
Jul 12, 2018 Annual reports 937568 Annual report 2017 —
Jul 11, 2017 Annual reports 876737 Annual report 2016 —
Jun 28, 2017 Inspections 2034425 B Type compliance —No Further Action
Nov 02, 2016 Annual reports 845201 Annual report 2015 —
Sep 16, 2016 Enforcement actions 424119 2nd NNC - AR (Second Notice of Non-Compliance (annual report)) Historical
Aug 15, 2016 Enforcement actions 423704 1st NNC - AR (First Notice of Non-Compliance (annual report)) Historical
Jul 16, 2016 Violations 860870 Late Report ViolationReport
Oct 22, 2015 Inspections 2030141 B Type compliance —No Further Action
Mar 09, 2015 Inspections 2025037 B Type compliance —Follow-up Inspection Needed
Mar 04, 2013 Inspections 2018252 B Type compliance —Follow-up Inspection Needed
Oct 26, 2012 Enforcement actions 410635 SEL (Staff Enforcement Letter) Historical
Oct 20, 2010 Inspections 2009488 B Type compliance —No Further Action
Dec 15, 2009 Enforcement actions 401526 SEL (Staff Enforcement Letter) Historical

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.