FLORIDA DEP #159 (THE STRIP JOINT)
1761 KELL RD, GULF BREEZE, FL, 32563
No open violations Compliance record — not a listed provider
Facility identity · canonical
- EPA Registry ID
- 110015671799
- RCRA Handler ID(s)
- FLR000098186, FLR000137539
- Generator status
- —
- County
- SANTA ROSA
- EPA Region
- 04
- Active
- —
- NAICS
- 562211 · Hazardous waste treatment & disposal81142
- Coordinates
- 30.400381, -87.008626
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
- Jan 6, 2006
- 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:
| Count | Code | Category | EPA description |
|---|---|---|---|
| 2 | 264.B | TSDF standards (permitted) | Standards for Owners and Operators of HW TSDs: General Facility Standards |
| 2 | 264.C | TSDF standards (permitted) | Standards for Owners and Operators of HW TSDs: Preparedness and Prevention |
| 2 | 264.D | TSDF standards (permitted) | Standards for Owners and Operators of HW TSDs: Contingency Plan and Emergency Procedures |
All violations:
| Determined | Category | Status | Agency |
|---|---|---|---|
| Apr 16, 2003 | TSDF standards (permitted) 264.B · Standards for Owners and Operators of HW TSDs: General Facility Standards | Resolved Oct 27, 2004 | S |
| Apr 16, 2003 | TSDF standards (permitted) 264.B · Standards for Owners and Operators of HW TSDs: General Facility Standards | Resolved Oct 27, 2004 | S |
| Apr 16, 2003 | TSDF standards (permitted) 264.C · Standards for Owners and Operators of HW TSDs: Preparedness and Prevention | Resolved Oct 27, 2004 | S |
| Apr 16, 2003 | TSDF standards (permitted) 264.C · Standards for Owners and Operators of HW TSDs: Preparedness and Prevention | Resolved Oct 27, 2004 | S |
| Apr 16, 2003 | TSDF standards (permitted) 264.D · Standards for Owners and Operators of HW TSDs: Contingency Plan and Emergency Procedures | Resolved Oct 27, 2004 | S |
| Apr 16, 2003 | TSDF standards (permitted) 264.D · Standards for Owners and Operators of HW TSDs: Contingency Plan and Emergency Procedures | Resolved Oct 27, 2004 | S |
Inspection history · canonical · 6 total
| Date | Type | Agency | Outcome |
|---|---|---|---|
| Jan 6, 2006 | COMPLIANCE EVALUATION INSPECTION (CEI) | S | In compliance |
| May 3, 2005 | COMPLIANCE EVALUATION INSPECTION (CEI) | S | In compliance |
| Oct 27, 2004 | NO LONGER A SIGNIFICANT NON-COMPLIER (SNN) | S | In compliance |
| Apr 22, 2003 | CASE DEVELOPMENT INSPECTION (CDI) | S | In compliance |
| Apr 14, 2003 | COMPLIANCE EVALUATION INSPECTION (CEI) | S | Violation found |
| Apr 14, 2003 | SIGNIFICANT NON-COMPLIER (SNY) | S | In compliance |
Related facilities near Gulf Breeze
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.