Crash Record FL8851848102

FMCSA crash record in UNINCORPORATED on Apr 11, 2022.

Tow-Away Federal Recordable

What happened

On April 11, 2022, FMCSA recorded a tow-away crash with no reported injuries in UNINCORPORATED, Florida. The vehicle was operated by CEDAR CREEK LOGGING COMPANY INC (USDOT 2911590). Recorded conditions: 6 / 1 / 1 pavement. Reported by CEDAR CREEK LOGGING COMPANY INC, FMCSA reference FL8851848102.

Carrier pattern note

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

Geographic note

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

Fatalities

Injuries

Vehicles

Carrier

CEDAR CREEK LOGGING COMPANY INC

USDOT 2911590

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 injury · 3 tow-away

Crashes per 100 power units (24 mo)

0.0

0 crashes · 21 units

Days since prior carrier crash

195

Last on Sep 28, 2021

Vs fleet-size peers

above the median

Cohort median 0.0 · 314,961 carriers

Geographic context

How this crash sits in its setting.

Within UNINCORPORATED, Florida, 4,633 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

UNKNOWN · 125 reports
FEDERAL EXPRESS CORPORATION · 36 reports
MIAMI DADE COUNTY FLORIDA · 36 reports

Contributing factors

What the responding officer recorded.

Light: 6
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 #:: FL8851848102
Date:: Apr 11, 2022
Time:: 1800
State:: Florida
City:: UNINCORPORATED
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 1
Carrier (USDOT):: CEDAR CREEK LOGGING COMPANY INC (2911590)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	6	6	1NKWX4TX3NR478582	P72219E (FL)	CEDAR CREEK LOGGING COMPANY INC	3	No

Crash event

Event sequence description.

3:17:COLLISION INVOLVING ANIMAL;1:6:NONCOLLISION:EXPLOSION OR FIRE;2:6:NONCOLLISION:EXPLOSION OR FIRE

Other crashes by this carrier

7 additional crash record(s) on file.

Record	Date	State	Severity	Fatalities	Injuries
cr_4236786	Sep 28, 2021	FL	Tow-Away	0	0
cr_4144793	Apr 13, 2021	AL	Injury	0	3
cr_4134397	Apr 1, 2021	FL	Tow-Away	0	0
cr_3938765	Feb 18, 2020	FL	Fatal	2	0
cr_3671329	Sep 21, 2018	FL	Injury	0	1
cr_3375103	Mar 20, 2017	FL	Injury	0	2
cr_3310293	Nov 21, 2016	FL	Injury	0	1

Carrier booking & risk tools

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

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

Related records

Vehicle

2022 KENWORTH W9 Series

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

Carrier

CEDAR CREEK LOGGING COMPANY INC

USDOT 2911590 · 8 crashes · 51 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 1NKWX4TX3NR478582

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

State

Crashes in Florida

Statewide crash records.

Agency

CEDAR CREEK LOGGING COMPANY INC

Crashes reported by this law-enforcement agency.

City

Crashes in UNINCORPORATED, FL

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.