TruckCodex

Crash Record OR2023410030

FMCSA crash record in 6.82 E LITTLE VALLEY on Aug 23, 2023.

Fatal HazMat Federal Recordable

What happened

On August 23, 2023, FMCSA recorded a fatal crash that resulted in one death in 6.82 E LITTLE VALLEY, Oregon. The vehicle was operated by BYBEE TRANSPORT INC (USDOT 238387). Recorded conditions: 1 / 9 / 9 pavement. Reported by BYBEE TRANSPORT INC, FMCSA reference OR2023410030.

Fatalities
1
Injuries
0
Vehicles
2
Carrier
BYBEE TRANSPORT INC
Vehicle Type
Truck
Severity
Fatal

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1
1 fatal · 0 injury
Crashes per 100 power units (24 mo)
0.0
0 crashes · 5 units
Days since prior carrier crash
1,261
Last on Mar 10, 2020
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,494,995 carriers

Contributing factors

What the responding officer recorded.

Light
1
Weather
9
Road surface
9

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 #:
OR2023410030
Date:
Aug 23, 2023
Time:
1220
State:
Oregon
City:
6.82 E LITTLE VALLEY
Fatalities:
1
Injuries:
0
Tow-Away:
Yes
HazMat:
Yes
Vehicles:
2
Carrier (USDOT):
BYBEE TRANSPORT INC (238387)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 4 1XPHD49X5DD213781 YAHA141 (OR) BYBEE TRANSPORT INC 3 No

Hazardous Materials Involved

This crash involved a vehicle carrying hazardous materials. No hazardous material release was reported.

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;2:6:NONCOLLISION:EXPLOSION OR FIRE

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_3953771 Mar 10, 2020 OR Tow-Away 0 0
cr_3862444 Sep 26, 2019 OR Tow-Away 0 0
cr_3657305 Sep 5, 2018 WA Tow-Away 0 0
cr_3566510 Mar 9, 2018 ID Injury 0 1
cr_3522656 Dec 30, 2017 OR Tow-Away 0 0
cr_3503903 Nov 25, 2017 IL Tow-Away 0 0
cr_3394073 May 7, 2017 TN Injury 0 1
cr_3381733 Feb 28, 2017 NE Tow-Away 0 0
cr_3127435 Nov 1, 2015 AL Injury 0 1
cr_3116741 Aug 14, 2015 OR Tow-Away 0 0

Related records

Carrier
BYBEE TRANSPORT INC
USDOT 238387 · 36 crashes · 5 inspections
Vehicle
VIN: 1XPHD49X5DD213781
Decode this VIN for make, model, year, and recall data.
State
Crashes in Oregon
Statewide crash records.
Agency
BYBEE TRANSPORT INC
Crashes reported by this law-enforcement agency.
City
Crashes in 6.82 E LITTLE VALLEY, OR
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.

How to evaluate a carrier's crash record

  1. Look at frequency, not any single crash. A single crash record rarely tells you anything decisive about a carrier. Pull the carrier's full multi-year crash list and look at the rate over time — clusters and trends matter more than any one event.
  2. Calculate crashes per power unit when data is available. Divide the 24-month crash count by the carrier's reported power units. A rate of one crash per power unit per year is high; a rate of one crash per ten power units per year is closer to industry baseline. Skip this step when power_units is missing or zero — the rate is meaningless without it.
  3. Filter for fault-attributed crashes. FMCSA crash records do not flag fault. To distinguish preventable from non-preventable, check whether the carrier requested a Preventability Determination through DataQs and what FMCSA ruled. Only the preventable crashes are a clean signal of carrier or driver behavior.
  4. Compare against fleet-size peers. Crash counts cannot be compared directly between fleets of different sizes. Use the SMS Crash Indicator percentile, or compare the carrier's crashes-per-power-unit rate against the median for its fleet-size cohort. A 50-truck carrier with 4 crashes in 24 months looks very different from a 5-truck carrier with the same count.
  5. Cross-reference with the SMS BASIC Crash Indicator. FMCSA's Safety Measurement System publishes a Crash Indicator percentile when the carrier has enough crashes and exposure to score. A score in the 65th percentile or higher triggers federal intervention thresholds. Always sanity-check raw crash counts against the percentile before drawing conclusions.

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.

Data sources & freshness

TruckCodex aggregates official public-sector datasets. See the Source registry for dataset-level coverage and the Freshness log for last-import timestamps.

FMCSA

Census, SAFER, SMS, Licensing & Insurance (L&I), roadside inspections, crashes, and authority history.

Refreshed daily.
NHTSA

Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).

Refreshed daily.
EIA

Retail diesel and gasoline price history and state fuel-tax tables.

Refreshed weekly.
Transport Canada

Cross-border carrier registry and Canadian recall campaigns where applicable.

Refreshed weekly.

TruckCodex is an independent aggregator; it is not affiliated with FMCSA, NHTSA, EIA, or Transport Canada. Always verify compliance-critical information directly with the originating agency.