TruckCodex
Hubs

Crash Record OH0216062776

FMCSA crash record in FREEDOM (TOWNSHIP OF) on Apr 13, 2021.

Injury Federal Recordable

What happened

On April 13, 2021, FMCSA recorded an injury crash with one person hurt in FREEDOM (TOWNSHIP OF), Ohio. The vehicle was operated by BASIN TRANSPORTATION LLC (USDOT 2559935). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference OH0216062776.

Carrier pattern note

This is the carrier's 12 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 51–500 power units.

Fatalities
0
Injuries
1
Vehicles
2
Carrier
BASIN TRANSPORTATION LLC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
12
4 injury · 11 tow-away
Crashes per 100 power units (24 mo)
3.2
3 crashes · 95 units
Days since prior carrier crash
28
Last on Mar 16, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,632 carriers

Geographic context

How this crash sits in its setting.

Within FREEDOM (TOWNSHIP OF), Ohio, 23 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Contributing factors

What the responding officer recorded.

Light
1
Weather
1
Road surface
1

Conditions are mixed. The data does not assign causation; this section reports only what was recorded by the responding officer.

Crash details

Key facts from the FMCSA crash record.

Report #:
OH0216062776
Date:
Apr 13, 2021
Time:
1418
State:
Ohio
City:
FREEDOM (TOWNSHIP OF)
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
BASIN TRANSPORTATION LLC (2559935)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 9 12 1XPCD49X3KD606640 3CK121 (OK) BASIN TRANSPORTATION LLC 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4846166 Oct 4, 2024 IL Tow-Away 0 0
cr_4809576 Sep 17, 2024 AL Injury 0 1
cr_4808272 Sep 10, 2024 LA Tow-Away 0 0
cr_4806879 Aug 15, 2024 TX Injury 0 2
cr_4732509 Mar 19, 2024 NM Tow-Away 0 0
cr_4695288 Jan 25, 2024 TX Tow-Away 0 0
cr_4665742 Dec 4, 2023 SD Tow-Away 0 0
cr_4648221 Oct 28, 2023 AR Tow-Away 0 0
cr_4632540 Aug 18, 2023 OK Injury 0 1
cr_4586533 Jun 26, 2023 WY Tow-Away 0 0

Related records

Carrier
BASIN TRANSPORTATION LLC
USDOT 2559935 · 49 crashes · 481 inspections
Vehicle
VIN: 1XPCD49X3KD606640
Decode this VIN for make, model, year, and recall data.
State
Crashes in Ohio
Statewide crash records.
City
Crashes in FREEDOM (TOWNSHIP OF), OH
All crashes on file for this city.
Index
All Crash Records
Browse FMCSA commercial vehicle crash records.
Database
Roadside Inspections
Inspection history and violation details.
Database
NHTSA Recalls
Active recall campaigns.

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.