Skip to main content
TruckCodex
Hubs

Crash Record PA206448900X

FMCSA crash record in PHILADELPHIA CITY on Jul 12, 2022.

Injury Federal Recordable

What happened

On July 12, 2022, FMCSA recorded an injury crash with one person hurt in PHILADELPHIA CITY, Pennsylvania. The vehicle was operated by CHEESEMAN LLC (USDOT 120612). Recorded conditions: 1 / 1 / 1 pavement. Reported by CHEESEMAN LLC, FMCSA reference PA206448900X.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
CHEESEMAN LLC
USDOT 120612
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
24
1 fatal · 8 injury
Crashes per 100 power units (24 mo)
1.1
21 crashes · 1,949 units
Days since prior carrier crash
40
Last on Jun 2, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,875 carriers

Geographic context

How this crash sits in its setting.

Within PHILADELPHIA CITY, Pennsylvania, 538 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 #:
PA206448900X
Date:
Jul 12, 2022
Time:
1120
State:
Pennsylvania
City:
PHILADELPHIA CITY
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
CHEESEMAN LLC (120612)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3HSDZAPR8MN086406 3018663 (IN) CHEESEMAN LLC 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
cmpupuhvd001nmok7ln5bq0rk May 26, 2026 NC Tow-Away 0 0
cr_5125379 Mar 14, 2026 TX Tow-Away 0 0
cr_5117538 Feb 12, 2026 MI Tow-Away 0 0
cr_5109042 Jan 27, 2026 OH Tow-Away 0 0
cr_5092671 Jan 24, 2026 KY Injury 0 1
cr_5069176 Dec 9, 2025 MN Tow-Away 0 0
cr_5074967 Nov 3, 2025 IN Injury 0 1
cr_5055919 Nov 3, 2025 WI Tow-Away 0 0
cr_5075702 Sep 4, 2025 MA Injury 0 1
cr_5004691 Aug 4, 2025 OH Injury 0 1

Carrier booking & risk tools

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

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

Related records

Vehicle
2021 INTERNATIONAL LT625
NHTSA recalls and complaints for this make/model/year.
Carrier
CHEESEMAN LLC
USDOT 120612 · 320 crashes · 894 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3HSDZAPR8MN086406
Decode this VIN for make, model, year, and recall data.
State
Crashes in Pennsylvania
Statewide crash records.
Agency
CHEESEMAN LLC
Crashes reported by this law-enforcement agency.
City
Crashes in PHILADELPHIA CITY, 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.