Skip to main content
TruckCodex
Hubs

Crash Record FL7101013302

FMCSA crash record in Florida on Mar 21, 2002.

Tow-Away

What happened

On March 21, 2002, FMCSA recorded a tow-away crash with no reported injuries in Florida. The vehicle was operated by SUN STATE INTERNATIONAL TRUCKS LLC (USDOT 345923). FMCSA reference FL7101013302.

Fatalities
0
Injuries
0
Vehicles
—
Carrier
USDOT 345923
Vehicle Type
—
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
2
1 injury · 2 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 36 units
Days since prior carrier crash
205
Last on Aug 28, 2001
Vs fleet-size peers
above the median
Cohort median 0.0 · 316,148 carriers

Geographic context

How this crash sits in its setting.

Within Florida, 10,139 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 #:
FL7101013302
Date:
Mar 21, 2002
Time:
0800
State:
Florida
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4195387 Jun 23, 2021 TX Tow-Away 0 0
cr_3980799 May 16, 2020 FL Injury 0 4
cr_3929292 Feb 4, 2020 FL Injury 0 2
cr_3651410 Aug 24, 2018 DC Injury 0 1
cr_3602432 May 21, 2018 FL Tow-Away 0 0
cr_3385988 Apr 8, 2017 FL Tow-Away 0 0
cr_2869220 May 20, 2014 FL Tow-Away 0 0
cr_2854005 Apr 19, 2014 FL Tow-Away 0 0
cr_2638408 Nov 30, 2012 FL Injury 0 1
cr_2638533 Nov 15, 2012 FL Injury 0 2

Carrier booking & risk tools

Check booking and risk signals for USDOT 345923 — 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.