Skip to main content
TruckCodex
Hubs

Crash Record FL0554024404

FMCSA crash record in Florida on Jun 3, 2004.

Injury

What happened

On June 3, 2004, FMCSA recorded an injury crash with one person hurt in Florida. The vehicle was operated by WEEKLEY ASPHALT PAVING INC (USDOT 968071). FMCSA reference FL0554024404.

Fatalities
0
Injuries
1
Vehicles
—
Carrier
USDOT 968071
Vehicle Type
—
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
3
1 fatal · 2 injury
Crashes per 100 power units (24 mo)
0.0
0 crashes · 95 units
Days since prior carrier crash
560
Last on Nov 21, 2002
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,419 carriers

Geographic context

How this crash sits in its setting.

Within Florida, 9,533 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Crash details

Key facts from the FMCSA crash record.

Report #:
FL0554024404
Date:
Jun 3, 2004
Time:
1200
State:
Florida
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4811060 Sep 12, 2024 FL Tow-Away 0 0
cr_4728560 Mar 19, 2024 FL Injury 0 1
cr_4693284 Feb 1, 2024 FL Tow-Away 0 0
cr_4681292 Jan 2, 2024 FL Injury 0 2
cr_4610270 Aug 21, 2023 FL Injury 0 1
cr_4540822 Apr 2, 2023 FL Tow-Away 0 0
cr_4367612 Feb 9, 2022 FL Tow-Away 0 0
cr_4215508 Aug 26, 2021 FL Tow-Away 0 0
cr_4088519 Jan 6, 2021 FL Injury 0 1
cr_4043497 Oct 5, 2020 FL Tow-Away 0 0

Carrier booking & risk tools

Check booking and risk signals for USDOT 968071 — tools open pre-filled.

Related records

Frequently asked questions about FMCSA crash records

What does this crash report tell me about the carrier? ▾
An individual FMCSA crash record tells you that a commercial vehicle operated by this carrier was involved in a reportable crash on the date listed, along with the severity (fatalities / injuries / tow-away) and the responding agency. A single crash record does not tell you whether the carrier was at fault, whether the driver was cited, or how the crash affected the carrier's safety scores. To evaluate the carrier, compare the full multi-year crash history against the carrier's fleet size, miles driven, and cohort peers.
Was this crash the carrier's fault? ▾
FMCSA crash records do not assign fault. Fault attribution requires reviewing the police report, any litigation outcome, and FMCSA's preventability determination if one was requested. If you need a fault determination, request the underlying state police crash report (PAR) — the carrier or its insurer can pull this through standard channels.
How does this crash affect the carrier's safety scores? ▾
Crash records feed FMCSA's Crash Indicator BASIC inside the Safety Measurement System (SMS). Each FMCSA-reportable crash counts for two years from the crash date and is weighted by severity (fatal / injury / tow-only). The Crash Indicator score is normalized against the carrier's power-unit count and exposure, so larger fleets need more crashes to score the same percentile as smaller ones. Non-reportable crashes do not enter the score.
Will this crash show up on the carrier's CSA SMS scores? ▾
If the federal_recordable flag on this record is true, yes — it will appear in the carrier's Crash Indicator BASIC for two years from the crash date. Crashes flagged state-only (state_recordable) are visible on the public crash file but do not enter the federal score.
How do I check the carrier's full crash history? ▾
Click through to the carrier profile (the USDOT link near the top of this page). The carrier's profile lists every crash on file, severity counts, and links into the SMS detail when an MC docket is on record. You can also visit FMCSA's SAFER and SMS portals directly using the carrier's USDOT number.
What if details look wrong — how do I correct an FMCSA crash record? ▾
FMCSA's DataQs system handles corrections to crash records. Either the carrier or an interested third party can file a Request for Data Review (RDR) with supporting documentation (police report, court records, witness statements). Corrections are processed by the originating state agency and propagate to the federal file within roughly 60–120 days when accepted.