TruckCodex
Hubs

Crash Record PA302477000X

FMCSA crash record in ROARING BROOK TOWNSHIP on Mar 17, 2023.

Tow-Away Federal Recordable

What happened

On March 17, 2023, FMCSA recorded a tow-away crash with no reported injuries in ROARING BROOK TOWNSHIP, Pennsylvania. The vehicle was operated by CAL-CLEVE LIMITED (USDOT 205915). Recorded conditions: 2 / 1 / 1 pavement. Reported by DOT-LINE TRANSPORTATION, FMCSA reference PA302477000X.

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
0
Vehicles
1
Carrier
CAL-CLEVE LIMITED
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
12
1 fatal · 1 injury
Crashes per 100 power units (24 mo)
12.9
15 crashes · 116 units
Days since prior carrier crash
57
Last on Jan 19, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,672 carriers

Geographic context

How this crash sits in its setting.

Within ROARING BROOK TOWNSHIP, Pennsylvania, 12 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
2
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 #:
PA302477000X
Date:
Mar 17, 2023
Time:
0200
State:
Pennsylvania
City:
ROARING BROOK TOWNSHIP
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
CAL-CLEVE LIMITED (205915)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3AKJHHDR1NSNA4964 3GC (OK) DOT-LINE TRANSPORTATION 3 No

Crash event

Event sequence description.

1:18:COLLISION INVOLVING FIXED OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5105399 Feb 4, 2026 AZ Injury 0 2
cr_5094909 Jan 22, 2026 OK Tow-Away 0 0
cr_5069373 Nov 20, 2025 MO Injury 0 2
cr_5034138 Sep 25, 2025 OK Tow-Away 0 0
cr_5014204 Aug 9, 2025 TX Tow-Away 0 0
cr_4991247 Jul 11, 2025 CA Tow-Away 0 0
cr_4955162 Jun 6, 2025 MS Tow-Away 0 0
cr_4990357 Jun 4, 2025 CA Tow-Away 0 0
cr_4947953 Apr 26, 2025 MO Injury 0 1
cr_4882525 Jan 10, 2025 MO Injury 0 2

Related records

Carrier
CAL-CLEVE LIMITED
USDOT 205915 · 208 crashes · 428 inspections
Vehicle
VIN: 3AKJHHDR1NSNA4964
Decode this VIN for make, model, year, and recall data.
State
Crashes in Pennsylvania
Statewide crash records.
Agency
DOT-LINE TRANSPORTATION
Crashes reported by this law-enforcement agency.
City
Crashes in ROARING BROOK TOWNSHIP, PA
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.