Raytheon Vision Systems

Terminated WDID 3 42I018513 Lompoc, Santa Barbara County Region 3 · Central Coast

At a glance

Permit Evidence: SMARTS record
Terminated Industrial
Notice of Intent (WDID code I) · Permits and applications
Location Evidence: facility-reported
Lompoc, Santa Barbara County
Region 3 · Central Coast · Location · Statewide map
Receiving water
Santa Ynez 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
4 distinct results, 1 reporting year (2016 to 2016)
Most recent sample Feb 17, 2017 · Monitoring
Compliance and enforcement records Evidence: SMARTS record
0 inspections · 1 violation record · 0 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
34.66357, -120.46056
Precision
5 decimal places
Shared point
2 permits report this exact point
Matches application record
same

Facility location as reported by the discharger in SMARTS; not a discharge point or outfall.

Facility address
425 Commerce Ct, Lompoc 93436
Regional Water Board
3 — Central Coast

HUC12 watershed Evidence: spatial

  • San Miguelito Creek-Santa Ynez River HUC12 180600100703

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
Raytheon
Primary industry (SIC)
3812-Search, Detection, Navigation, Guidance, Aeronautical, and Nautical Systems and Instruments
Application ID
186235
NOI processed
Dec 15, 2003
Termination effective
Mar 13, 2019
Last certified
Mar 04, 2019
Facility size
3 Acres

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

Permit history

Storm water applications for this WDID, newest first
ApplicationTypeStatusProcessedTerminatedCertified
186235 IndustrialTerminatedDec 15, 2003 Mar 13, 2019Mar 04, 2019

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

Receiving water

Reported by the facility Evidence: facility-reported
Santa Ynez River
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

3 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
Santa Ynez River (Cachuma Lake to below city of Lompoc) CAR3141005019980827094226448 m listed8

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.

4 distinct measurements across 4 parameters, most recent sample Feb 17, 2017.

By reporting year

Distinct results by reporting year
Reporting year (July–June)Distinct resultsParametersWith several versionsFirst sampleLast sample
201644 0 Feb 17, 2017Feb 17, 2017

By parameter

Distinct results by parameter
ParameterUnitsMeasurementsBelow detectionFirst sampleLast sampleResults
Electrical Conductivity @ 25 Deg. Cumhos/cm1 0Feb 17, 2017Feb 17, 2017 Results
Oil and Greasemg/L1 0Feb 17, 2017Feb 17, 2017 Results
pHSU1 0Feb 17, 2017Feb 17, 2017 Results
Total Suspended Solids (TSS)mg/L1 0Feb 17, 2017Feb 17, 2017 Results

All results (4 distinct rows)

Reported monitoring results, newest first
Sample dateParameterResultUnitsLocation typeEventMethodReportVersions
Feb 17, 2017 Electrical Conductivity @ 25 Deg. C 19.8 umhos/cm Effluent Qualifying Storm Event E120.1 928636
Feb 17, 2017 Oil and Grease 1.9 mg/L Effluent Qualifying Storm Event E1664A 928636
Feb 17, 2017 pH 7.05 SU Effluent Qualifying Storm Event pH_Field 928636
Feb 17, 2017 Total Suspended Solids (TSS) 23 mg/L Effluent Qualifying Storm Event A2540D 928636

Results are shown exactly as reported by the discharger. Identical rows repeated in the State's export are shown once. Where the export contains different versions of the same sample and parameter, each version is listed and flagged. Details.

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 Jul 01, 2004 – Jul 01, 2004 Oct 21, 2026 All violations
Enforcement actions0 0 issued · 0 draft · 0 withdrawn, rescinded or superseded — Oct 21, 2026
Inspections0inspections, not findings — Oct 21, 2026
Annual reports4certified reports (contents not shown) 2015 – 2018 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 (5 records, newest first)
Compliance and enforcement records, newest first
DateRecordIDType or purposeStatus as publishedDetail
Jul 11, 2019 Annual reports 954374 Annual report 2018 —
Jul 11, 2018 Annual reports 939792 Annual report 2017 —
Jun 22, 2017 Annual reports 879078 Annual report 2016 —
Jul 15, 2016 Annual reports 846812 Annual report 2015 —
Jul 01, 2004 Violations 263337 Deficient Report 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.