Skip to main content
TruckCodex
Hubs

Crash Record PA300672900X

FMCSA crash record in RICHLAND TOWNSHIP on Jan 18, 2023.

Tow-Away Federal Recordable

What happened

On January 18, 2023, FMCSA recorded a tow-away crash with no reported injuries in RICHLAND TOWNSHIP, Pennsylvania. The vehicle was operated by YANKO BROS TRUCKING INC (USDOT 851762). Recorded conditions: 1 / 2 / 2 pavement. Reported by YANKO BROS TRUCKING INC, FMCSA reference PA300672900X.

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
1
Carrier
YANKO BROS TRUCKING INC
USDOT 851762
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1
0 injury · 1 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 3 units
Days since prior carrier crash
2,729
Last on Jul 30, 2015
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,579,684 carriers

Geographic context

How this crash sits in its setting.

Within RICHLAND TOWNSHIP, Pennsylvania, 47 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
2
Road surface
2

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 #:
PA300672900X
Date:
Jan 18, 2023
Time:
0824
State:
Pennsylvania
City:
RICHLAND TOWNSHIP
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
YANKO BROS TRUCKING INC (851762)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 — 6 1FVHALCKX6DV92494 ZJR7061 (PA) YANKO BROS TRUCKING INC 3 No

Crash event

Event sequence description.

1:18:COLLISION INVOLVING FIXED OBJECT;2:17:COLLISION INVOLVING ANIMAL

Other crashes by this carrier

8 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4545108 Apr 11, 2023 PA Tow-Away 0 0
cr_3113899 Jul 30, 2015 PA Tow-Away 0 0
cr_2728900 Jul 9, 2013 PA Injury 0 1
cr_1917434 Oct 4, 2007 PA Injury 0 1
cr_1739725 Dec 8, 2006 PA Injury 0 1
cr_1698779 Aug 15, 2006 PA Injury 0 1
cr_1249900 May 22, 2003 PA Tow-Away 0 0
cr_283954 Mar 26, 2001 PA Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Vehicle
2006 FREIGHTLINER FLD120
NHTSA recalls and complaints for this make/model/year.
Recall
07V530000
TRAILER HITCHES:FIFTH WHEEL ASSEMBLY
Recall
07V302000
SERVICE BRAKES, AIR:SUPPLY:CHECK VALVE
Carrier
YANKO BROS TRUCKING INC
USDOT 851762 · 9 crashes · 3 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1FVHALCKX6DV92494
Decode this VIN for make, model, year, and recall data.
State
Crashes in Pennsylvania
Statewide crash records.
Agency
YANKO BROS TRUCKING INC
Crashes reported by this law-enforcement agency.
City
Crashes in RICHLAND 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.