Apollo European Auto Parts

Terminated WDID 4 19I011033 Sun Valley, Los Angeles County Region 4 · Los Angeles

At a glance

Permit Evidence: SMARTS record
Terminated Industrial
Notice of Intent (WDID code I) · Permits and applications
Location Evidence: facility-reported
Sun Valley, Los Angeles County
Region 4 · Los Angeles · Location · Statewide map
Receiving water
Not reported
No identification to check. 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
3 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
34.2012, -118.36808
Precision
4 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
10901 Sherman Way, Sun Valley 91352
Regional Water Board
4 — Los Angeles

HUC12 watershed Evidence: spatial

  • Tujunga Wash-Los Angeles River HUC12 180701050208

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
Berghoudian, Avedis
Primary industry (SIC)
5015-Motor Vehicle Parts, Used
Application ID
190061
NOI processed
Jun 09, 1994
Termination effective
Jun 12, 2008
Last certified
—
Facility size
99600 SqFt
Impervious area
13 %

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

Permit history

Storm water applications for this WDID, newest first
ApplicationTypeStatusProcessedTerminatedCertified
190061 IndustrialTerminatedJun 09, 1994 Jun 12, 2008—

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

Receiving water

Reported by the facility Evidence: facility-reported
—
Discharges directly / indirectly
— / — (as answered in the permit application)

No receiving-water text was reported for this permit.

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 01, 2002 – Aug 01, 2002 Oct 21, 2026 All violations
Enforcement actions1 1 issued · 0 draft · 0 withdrawn, rescinded or superseded Aug 09, 2002 – Aug 09, 2002 Oct 21, 2026 All actions
Inspections3inspections, not findings Aug 01, 2002 – Aug 28, 2008 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 (5 records, newest first)
Compliance and enforcement records, newest first
DateRecordIDType or purposeStatus as publishedDetail
Aug 28, 2008 Inspections 1734124 NOT —
Sep 10, 2002 Inspections 1734125 Enforcement Follow-up —
Aug 09, 2002 Enforcement actions 247493 NOV (Notice of Violation) HistoricalNOV
Aug 01, 2002 Inspections 1734126 B Type compliance —
Aug 01, 2002 Violations 217940 Deficient BMP Implementation ViolationInspection

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.