105,313Records 71,083Employers 85,290Hospitalizations 27,770Amputations 2015-01-01 2025-10-31
Safety Incidents OSHA Severe Injury Reports · 2015–2025

Phoenix Dewatering, Inc.

Federal OSHA safety record across 2 records in FLORIDA.

Federal OSHA records for Phoenix Dewatering, Inc. include 2 Severe Injury Reports, 0 Form 300/301 injury filings, and 0 OSHA inspections, spanning FLORIDA, with incidents dated between and . Aggregated from three OSHA data feeds; per-record detail and source citations are linked below.

Compliance History Report Phoenix Dewatering, Inc.'s full severe-injury history, benchmarked against its sector and the national average — one portable, citable document.
Get the report →
Ongoing Severe-Injury Monitor A private watch page for Phoenix Dewatering, Inc., refreshed daily as new federal OSHA severe injuries are published — with full history and benchmark. $99/mo, cancel anytime.
Start monitoring →

SIR2 records Injuries0 records Inspections0 records

Date range to

Most recent 2 of 2 reports for this employer.

Phoenix Dewatering, Inc.

EventInjured by slipping or swinging object held by injured worker

Amputation

Phoenix Dewatering, Inc.

EventFall on same level due to tripping on uneven surface

Hospitalized

No ITA Form 300/301 injury filings recorded for this employer.

No OSHA inspections recorded for this employer.

No OSHA citations recorded for this employer.

Name as filed with OSHA
Phoenix Dewatering, Inc.
States with records
FL
1 record
3873 E STATE ROAD 46, SANFORD, FLORIDA 32771
1 record
4225 SOUTH ATLANTIC AVENUE, NEW SMYRNA BEACH, FLORIDA 32168
NEW SMYRNA BEACH, FL
1 record
SANFORD, FL
1 record
NAICS 237110
NAICS 238220

This profile aggregates federal OSHA records from three published feeds: OSHA Severe Injury Reports, the ITA Establishment-Specific Injury and Illness Data (Form 300/301), and the U.S. Department of Labor Open Data API (OSHA inspections). Records are matched to this employer by normalized name; small variations in spelling, punctuation, and capitalization collapse to one profile, while materially different legal entities (e.g. parent vs. subsidiary with distinct hyphenated names) remain separate.