Skip to main content
TruckCodex
Hubs

Crash Record ID24C6635860

FMCSA crash record in FRUITLAND on Mar 28, 2024.

Injury Federal Recordable

What happened

On March 28, 2024, FMCSA recorded an injury crash with one person hurt in FRUITLAND, Idaho. The vehicle was operated by PAUL TRANSPORTATION INC (USDOT 1082105). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference ID24C6635860.

Carrier pattern note

This is the carrier's 25 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
PAUL TRANSPORTATION INC
USDOT 1082105
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
25
2 fatal · 10 injury
Crashes per 100 power units (24 mo)
8.2
25 crashes · 305 units
Days since prior carrier crash
20
Last on Mar 8, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,045 carriers

Geographic context

How this crash sits in its setting.

Within FRUITLAND, Idaho, 8 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 #:
ID24C6635860
Date:
Mar 28, 2024
Time:
1451
State:
Idaho
City:
FRUITLAND
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No
Vehicles:
2
Carrier (USDOT):
PAUL TRANSPORTATION INC (1082105)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 9 5 1XKYD49X8NJ493978 3FW786 (OK) PAUL TRANSPORTATION INC 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
cmtl0dt1v002bpm66ogjmbw26 Aug 28, 2026 OK Injury 0 1
cr_5115976 Mar 4, 2026 MO Tow-Away 0 0
cr_5099854 Jan 28, 2026 OK Tow-Away 0 0
cr_5059063 Nov 14, 2025 OK Tow-Away 0 0
cr_5073564 Oct 31, 2025 AR Tow-Away 0 0
cr_5053579 Oct 28, 2025 KS Tow-Away 0 0
cr_5044048 Oct 6, 2025 GA Tow-Away 0 0
cr_5026387 Sep 12, 2025 LA Tow-Away 0 0
cr_5028946 Sep 4, 2025 GA Tow-Away 0 0
cr_4991493 Jul 19, 2025 CO Tow-Away 0 0

Carrier booking & risk tools

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

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Carrier
PAUL TRANSPORTATION INC
USDOT 1082105 · 229 crashes · 994 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1XKYD49X8NJ493978
Decode this VIN for make, model, year, and recall data.
State
Crashes in Idaho
Statewide crash records.
City
Crashes in FRUITLAND, ID
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.