Rhino Trucking

Terminated WDID 5F15I024984 Delano, Kern County Region 5F · Central Valley (Fresno)

At a glance

Permit Evidence: SMARTS record
Terminated Industrial
Notice of Intent (WDID code I) · Permits and applications
Location Evidence: facility-reported
Delano, Kern County
Region 5F · Central Valley (Fresno) · Location · Statewide map
Receiving water
Woolomes Lake (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
None
Monitoring results Evidence: facility-reported
None in the current exports
Compliance and enforcement records Evidence: SMARTS record
0 inspections · 1 violation record · 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

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
35.73498, -119.24075
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
1100 Garzoli Ave, Delano 93215
Regional Water Board
5F — Central Valley (Fresno)

HUC12 watershed Evidence: spatial

  • Lake Woollomes HUC12 180300050604

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
Terminated
Operator
Rhino Trucking
Primary industry (SIC)
3273-Ready-Mixed Concrete
Application ID
448427
NOI processed
Jul 31, 2014
Termination effective
Feb 29, 2016
Last certified
Apr 22, 2015
Facility size
1.49 Acres
Impervious area
80 %

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

Permit history

Storm water applications for this WDID, newest first
ApplicationTypeStatusProcessedTerminatedCertified
448427 IndustrialTerminatedJul 31, 2014 Feb 29, 2016Apr 22, 2015

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

Receiving water

Reported by the facility Evidence: facility-reported
Woolomes Lake
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.

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.

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
Violations1 1 Violation · 0 Potential (preliminary) · 0 Dismissed Aug 15, 2015 – Aug 15, 2015 Oct 21, 2026 All violations
Enforcement actions1 1 issued · 0 draft · 0 withdrawn, rescinded or superseded Aug 28, 2015 – Aug 28, 2015 Oct 21, 2026 All actions
Inspections0inspections, not findings — Oct 21, 2026
Annual reports1certified reports (contents not shown) 2015 – 2015 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 (3 records, newest first)
Compliance and enforcement records, newest first
DateRecordIDType or purposeStatus as publishedDetail
Sep 07, 2016 Annual reports 839597 Annual report 2015 —
Aug 28, 2015 Enforcement actions 419889 SEL (Staff Enforcement Letter) Active
Aug 15, 2015 Violations 857663 Late Report ViolationReport

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.