Crash Record ID21C5928320

FMCSA crash record in HEYBURN on Dec 31, 2021.

Injury Federal Recordable

What happened

On December 31, 2021, FMCSA recorded an injury crash with one person hurt in HEYBURN, Idaho. The vehicle was operated by CONRAD & BISCHOFF LLC (USDOT 110143). Recorded conditions: 1 / 6 / 6 pavement. FMCSA reference ID21C5928320.

Carrier pattern note

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

Geographic note

This crash is part of an active corridor: 27 crashes occurred in the same city in the past 24 months.

Fatalities

Injuries

Vehicles

Carrier

CONRAD & BISCHOFF LLC

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

4 injury · 5 tow-away

Crashes per 100 power units (24 mo)

0.9

1 crashes · 106 units

Days since prior carrier crash

218

Last on May 27, 2021

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,833 carriers

Geographic context

How this crash sits in its setting.

Within HEYBURN, Idaho, 27 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

SUNRISE EXPRESS INC · 2 reports
TRANSYSTEMS LLC · 2 reports
F M I TRANSPORTATION LLC · 1 reports

Contributing factors

What the responding officer recorded.

Light: 1
Weather: 6
Road surface: 6

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 #:: ID21C5928320
Date:: Dec 31, 2021
Time:: 0956
State:: Idaho
City:: HEYBURN
Fatalities:: 0
Injuries:: 1
Tow-Away:: Yes
HazMat:: No
Vehicles:: 3
Carrier (USDOT):: CONRAD & BISCHOFF LLC (110143)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
3	9	4	4V4N99EH3JN894955	AM5587 (ID)	CONRAD & BISCHOFF LLC	3	Yes

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;2:98:OTHER:Loss of Control;4:17:COLLISION INVOLVING ANIMAL;3:6:NONCOLLISION:EXPLOSION OR FIRE

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Fatalities	Injuries
cr_5111586	Feb 8, 2026	ID	Tow-Away	0	0
cr_4493216	Dec 14, 2022	MT	Injury	0	1
cr_4455338	Oct 28, 2022	ID	Tow-Away	0	0
cr_4408628	Aug 11, 2022	WY	Tow-Away	0	0
cr_4407314	Aug 1, 2022	ID	Tow-Away	0	0
cr_4166153	May 27, 2021	ID	Injury	0	1
cr_4038261	Sep 2, 2020	ID	Tow-Away	0	0
cr_3980423	Apr 4, 2020	ID	Injury	0	1
cr_3928027	Jan 15, 2020	ID	Injury	0	1
cr_3663309	Aug 7, 2018	ID	Fatal	2	1

Related records

Vehicle

2018 VOLVO TRUCK VNL

NHTSA recalls and complaints for this make/model/year.

Carrier

CONRAD & BISCHOFF LLC

USDOT 110143 · 27 crashes · 0 inspections

Vehicle

VIN: 4V4N99EH3JN894955

Decode this VIN for make, model, year, and recall data.

State

Crashes in Idaho

Statewide crash records.

City

Crashes in HEYBURN, 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.