TRI PRODUCTS INC

5649 PECK RD, ARCADIA, CA, 91006
No open violations Compliance record — not a listed provider
Compliance record, not a business listing. This facility is a hazardous-waste generator (it produces regulated waste as part of an unrelated business), not a waste-management vendor — it isn't eligible to be claimed or listed. Data below is shown for compliance transparency, sourced from EPA ECHO & RCRAInfo.

Facility identity · canonical

EPA Registry ID
110033623728
RCRA Handler ID(s)
CAR000190363
Generator status
—
County
LOS ANGELES
EPA Region
09
Active
Yes
NAICS
33411
Coordinates
34.10422, -118.00809
Compliance summary · canonical · EPA source pulled Aug 11, 2026 · summary recalculated Aug 26, 2026
3-year compliance history Not in the compliance universe for any of the last 12 quarters
Not in universe In violation Significant non-compliance
Significant non-complier
No
Last inspection
Feb 8, 2011
Inspections (5 yr)
—
Informal actions (5 yr)
—
Formal actions (5 yr)
—
Total penalties
—
Permits & authorizations · canonical
No permits on record.
Violations · canonical · 6 total, 0 open
3 distinct violation categories on record:
CountCodeCategoryEPA description
4 XXS State-specific requirement (broader than federal) State Statutory or Regulatory requirements that are broader-in-scope than the federal RCRA requirements
1 262.A Generator standards Standards Applicable to Generators of HW: General
1 273.A Universal waste Standards for Universal Waste Management: General
All violations:
DeterminedCategoryStatusAgency
Jan 19, 2011
Generator standards
262.A · Standards Applicable to Generators of HW: General
Resolved Feb 8, 2011 S
Jan 19, 2011
State-specific requirement (broader than federal)
XXS · State Statutory or Regulatory requirements that are broader-in-scope than the federal RCRA requirements
Resolved Feb 8, 2011 S
Jan 10, 2010
Universal waste
273.A · Standards for Universal Waste Management: General
Resolved Jan 29, 2010 S
Jan 10, 2010
State-specific requirement (broader than federal)
XXS · State Statutory or Regulatory requirements that are broader-in-scope than the federal RCRA requirements
Resolved Jan 29, 2010 S
May 29, 2009
State-specific requirement (broader than federal)
XXS · State Statutory or Regulatory requirements that are broader-in-scope than the federal RCRA requirements
Resolved May 29, 2009 S
May 29, 2009
State-specific requirement (broader than federal)
XXS · State Statutory or Regulatory requirements that are broader-in-scope than the federal RCRA requirements
Resolved Sep 14, 2009 S
Inspection history · canonical · 6 total
DateTypeAgencyOutcome
Feb 8, 2011 NO LONGER A SIGNIFICANT NON-COMPLIER (SNN) S In compliance
Jan 19, 2011 FOCUSED COMPLIANCE INSPECTION (FCI) S Violation found
Jan 19, 2011 SIGNIFICANT NON-COMPLIER (SNY) S In compliance
Jan 10, 2010 FOCUSED COMPLIANCE INSPECTION (FCI) S Violation found
May 29, 2009 FOCUSED COMPLIANCE INSPECTION (FCI) S Violation found
Apr 30, 2008 FOCUSED COMPLIANCE INSPECTION (FCI) S In compliance

Data sources

EPA ECHO — this facility's detailed report — facility, compliance summary, permits, evaluations & violations
RCRAInfo evaluation and violation records for this facility are integrated into the ECHO report linked above — RCRAInfo's own public search doesn't offer a stable per-facility link. General source: EPA ECHO, EPA RCRAInfo.
Compliance, permit, and location data come straight from EPA and can't be edited. Contact info and description come from the business's claimed listing, if any. This profile is not an official regulatory determination.
EPA ECHO Exporter
Source snapshot pulled Aug 11, 2026 · batch 20260811T113837Z
EPA RCRAInfo (ECHO download)
Source snapshot pulled Aug 11, 2026 · batch 20260811T113837Z
Two different dates can appear on this page, and both are correct but mean different things: "Source snapshot pulled" above is when we last pulled that source's raw data — this is the date to check for source currency. "Recalculated" on the compliance summary is when we last recomputed that summary from the data on hand, which can land on a later date than the source pull itself — a later recalculation date does NOT mean the underlying source has data through that date.