K&M Auto Dismantling LLC

Active WDID 4 19I011486 Sun Valley, Los Angeles County Region 4 · Los Angeles

At a glance

Permit Evidence: SMARTS record
Active 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
Tujunga Wash (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
None in the current exports
Compliance and enforcement records Evidence: SMARTS record
3 inspections · 6 violation records · 5 enforcement actions
Counts as published in SMARTS; not a compliance determination · Details
SMARTS TMDL records Evidence: SMARTS-reported
1 record
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.22195, -118.37902
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
8307 Tujunga Ave, 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
Active
Operator
Nerses Sinanyan
Primary industry (SIC)
5015-Motor Vehicle Parts, Used
Application ID
190154
NOI processed
Mar 09, 1995
Last certified
Aug 11, 2017
Facility size
16500 SqFt
Impervious area
100 %

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

Permit history

Storm water applications for this WDID, newest first
ApplicationTypeStatusProcessedTerminatedCertified
190154 IndustrialActiveMar 09, 1995 —Aug 11, 2017

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

Receiving water

Reported by the facility Evidence: facility-reported
Tujunga Wash
Discharges directly / indirectly
N / Y (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

1 official waterbody shares 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

SMARTS TMDL record as reported for this facility; it is not a determination that the TMDL applies to the facility.

TMDL records SMARTS lists for this facility
TMDLWaterbody (as reported)ParameterLimitTypePeriodDueDischarges to TMDL water
Los Angeles River Metals TMDLLos Angeles River and Los Angeles River TributariesLead, Total .094 mg/LNEL instantaneous FINAL2020-07-01Y

1 record. Links between these records and specific TMDL projects or listed waterbodies have not been reviewed and are not shown.

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
Violations6 6 Violation · 0 Potential (preliminary) · 0 Dismissed Jan 14, 2002 – May 15, 2025 Oct 21, 2026 All violations
Enforcement actions5 5 issued · 0 draft · 0 withdrawn, rescinded or superseded Mar 01, 2002 – May 15, 2025 Oct 21, 2026 All actions
Inspections3inspections, not findings Jan 14, 2002 – Feb 01, 2023 Oct 21, 2026 All inspections
Annual reports10certified 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 (24 records, newest first)
Compliance and enforcement records, newest first
DateRecordIDType or purposeStatus as publishedDetail
Jul 14, 2026 Annual reports 1334339 Annual report 2025 —
Jul 14, 2025 Annual reports 1293115 Annual report 2024 —
May 15, 2025 Enforcement actions 456047 NOV (Notice of Violation) Active
May 15, 2025 Violations 891332 Failure to Notify ViolationReport
Dec 12, 2023 Enforcement actions 452465 NOV (Notice of Violation) Active
Jun 23, 2023 Annual reports 1188074 Annual report 2022 —
Jun 14, 2023 Enforcement actions 449941 NOV (Notice of Violation) Historical
Jun 14, 2023 Violations 885108 Late Report ViolationReport
Mar 24, 2023 Violations 887565 Deficient BMP Implementation ViolationInspection
Feb 01, 2023 Inspections 2062761 B Type compliance FinalizedAdditional Info Required
Sep 08, 2022 Annual reports 1111353 Annual report 2021 —
Nov 10, 2021 Annual reports 1067301 Annual report 2020 —
Jul 14, 2020 Annual reports 984473 Annual report 2019 —
Aug 22, 2018 Annual reports 937391 Annual report 2017 —
Jul 31, 2018 Annual reports 951980 Annual report 2018 —
Aug 14, 2017 Annual reports 876550 Annual report 2016 —
Aug 08, 2016 Annual reports 840836 Annual report 2015 —
Dec 28, 2015 Enforcement actions 422231 1st NNC - AR (First Notice of Non-Compliance (annual report)) Historical
Aug 15, 2015 Violations 859484 Late Report ViolationReport
Feb 19, 2003 Inspections 1733062 B Type compliance —
Mar 01, 2002 Enforcement actions 241516 NTC (Notice to Comply) HistoricalUNKNOWN
Jan 14, 2002 Inspections 1733061 B Type compliance —
Jan 14, 2002 Violations 204746 Deficient BMP Implementation ViolationInspection
Jan 14, 2002 Violations 204747 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.