Microsemi Corp

Terminated WDID 8 30I003479 Garden Grove, Orange County Region 8 · Santa Ana

At a glance

Permit Evidence: SMARTS record
Terminated Industrial
Notice of Intent (WDID code I) · Permits and applications
Location Evidence: facility-reported
Garden Grove, Orange County
Region 8 · Santa Ana · Location · Statewide map
Receiving water
City of Garden Grove Storm Sewer (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
6 inspections · 19 violation records · 25 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
33.79362, -118.00809
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
11652 Markon Dr, Garden Grove 92841
Regional Water Board
8 — Santa Ana

HUC12 watershed Evidence: spatial

  • Anaheim Bay HUC12 180702010001

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
Microsemi Corp
Primary industry (SIC)
3674-Semiconductors and Related Devices
Application ID
208372
NOI processed
Apr 03, 1992
Termination effective
Sep 15, 2017
Last certified
Jun 29, 2015
Facility size
29400 SqFt

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

Permit history

Storm water applications for this WDID, newest first
ApplicationTypeStatusProcessedTerminatedCertified
208372 IndustrialTerminatedApr 03, 1992 Sep 15, 2017Jun 29, 2015

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

Receiving water

Reported by the facility Evidence: facility-reported
City of Garden Grove Storm Sewer
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
Violations19 19 Violation · 0 Potential (preliminary) · 0 Dismissed Jul 02, 1999 – Jul 16, 2016 Oct 21, 2026 All violations
Enforcement actions25 25 issued · 0 draft · 0 withdrawn, rescinded or superseded Jul 17, 2001 – Aug 01, 2016 Oct 21, 2026 All actions
Inspections6inspections, not findings Jun 28, 2001 – Oct 11, 2017 Oct 21, 2026 All inspections
Annual reports2certified reports (contents not shown) 2015 – 2016 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 (52 records, newest first)
Compliance and enforcement records, newest first
DateRecordIDType or purposeStatus as publishedDetail
Oct 11, 2017 Inspections 2035116 NOT —No Further Action
Jul 21, 2017 Annual reports 876613 Annual report 2016 —
Aug 14, 2016 Annual reports 845983 Annual report 2015 —
Aug 01, 2016 Enforcement actions 423564 1st NNC - AR (First Notice of Non-Compliance (annual report)) Historical
Jul 16, 2016 Violations 860728 Late Report ViolationReport
Aug 29, 2014 Enforcement actions 416240 2nd NNC - AR (Second Notice of Non-Compliance (annual report)) Historical
Jul 31, 2014 Enforcement actions 416111 1st NNC - AR (First Notice of Non-Compliance (annual report)) Historical
Jul 02, 2014 Violations 854536 Late Report ViolationReport
Jul 31, 2013 Enforcement actions 412770 1st NNC - AR (First Notice of Non-Compliance (annual report)) Historical
Jul 02, 2013 Violations 851520 Late Report ViolationReport
Jul 31, 2012 Enforcement actions 409468 1st NNC - AR (First Notice of Non-Compliance (annual report)) Historical
Jul 02, 2012 Violations 848650 Late Report ViolationReport
Jul 30, 2010 Enforcement actions 402176 1st NNC - AR (First Notice of Non-Compliance (annual report)) Historical
Jul 02, 2010 Violations 842045 Late Report ViolationReport
Apr 23, 2010 Inspections 2005173 B Type compliance —No Further Action
Apr 23, 2010 Violations 841660 Deficient BMP Implementation ViolationInspection
Sep 22, 2009 Inspections 2000000 Inspection from Vehicle —No Further Action
Aug 28, 2009 Enforcement actions 370945 2nd NNC - AR (Second Notice of Non-Compliance (annual report)) Historical
Jul 30, 2009 Enforcement actions 370943 1st NNC - AR (First Notice of Non-Compliance (annual report)) Historical
Jul 02, 2009 Violations 837547 Late Report ViolationReport
Aug 01, 2008 Enforcement actions 350304 1st NNC - AR (First Notice of Non-Compliance (annual report)) Historical
Jul 02, 2008 Violations 779325 Late Report ViolationReport
Aug 31, 2007 Enforcement actions 331959 2nd NNC - AR (Second Notice of Non-Compliance (annual report)) Historical
Aug 01, 2007 Enforcement actions 297938 1st NNC - AR (First Notice of Non-Compliance (annual report)) Historical
Jul 02, 2007 Violations 612298 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.