Skip to main content
TruckCodex
Hubs

Crash Record PA506318200X

FMCSA crash record in ROBINSON TOWNSHIP on Jul 14, 2025.

Tow-Away Federal Recordable

What happened

On July 14, 2025, FMCSA recorded a tow-away crash with no reported injuries in ROBINSON TOWNSHIP, Pennsylvania. The vehicle was operated by MID-EAST TRUCK & TRACTOR SERVICE INC (USDOT 212190). Recorded conditions: 1 / 1 / 2 pavement. Reported by MID-EAST TRUCK & TRACTOR SERVICE, FMCSA reference PA506318200X.

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
1
Carrier
MID-EAST TRUCK & TRACTOR SERVICE INC
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)
4.2
2 crashes · 48 units
Days since prior carrier crash
1,040
Last on Sep 8, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 314,646 carriers

Geographic context

How this crash sits in its setting.

Within ROBINSON TOWNSHIP, Pennsylvania, 45 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
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 #:
PA506318200X
Date:
Jul 14, 2025
Time:
1252
State:
Pennsylvania
City:
ROBINSON TOWNSHIP
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
MID-EAST TRUCK & TRACTOR SERVICE INC (212190)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 5 3 2NP2HM6X3KM264745 PKK4589 (OH) MID-EAST TRUCK & TRACTOR SERVICE 2 No

Crash event

Event sequence description.

1:17:COLLISION INVOLVING ANIMAL

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5076817 Dec 6, 2025 OH Tow-Away 0 0
cr_4420475 Sep 8, 2022 OH Fatal 1 2
cr_4127054 Mar 23, 2021 WV Tow-Away 0 0
cr_4006181 Jul 17, 2020 OH Tow-Away 0 0
cr_4026390 Jun 30, 2020 IL Tow-Away 0 0
cr_3814504 May 30, 2019 OH Injury 0 1
cr_3680156 Oct 15, 2018 OH Tow-Away 0 0
cr_3607775 Jun 1, 2018 IL Injury 0 1
cr_3591981 May 7, 2018 OH Tow-Away 0 0
cr_3409801 May 20, 2017 OH Injury 0 1

Related records

Vehicle
2019 PETERBILT 337
NHTSA recalls and complaints for this make/model/year.
Recall
22V277000
STEERING:CRITICAL FASTENERS
Recall
21V391000
FUEL SYSTEM, DIESEL:FUEL INJECTION SYSTEM:FUEL RAIL
Recall
20V199000
ELECTRONIC STABILITY CONTROL (ESC)
Carrier
MID-EAST TRUCK & TRACTOR SERVICE INC
USDOT 212190 · 37 crashes · 37 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 2NP2HM6X3KM264745
Decode this VIN for make, model, year, and recall data.
State
Crashes in Pennsylvania
Statewide crash records.
Agency
MID-EAST TRUCK & TRACTOR SERVICE
Crashes reported by this law-enforcement agency.
City
Crashes in ROBINSON 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.