Crash Record PA806864700X

FMCSA crash record in Pennsylvania on Jun 20, 2018.

Tow-Away

What happened

On June 20, 2018, FMCSA recorded a tow-away crash with no reported injuries in Pennsylvania. The vehicle was operated by STALLION LOGISTICS LLC (USDOT 2367945). FMCSA reference PA806864700X.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
Carrier
STALLION LOGISTICS LLC
Vehicle Type
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
5
1 injury · 5 tow-away
Crashes per 100 power units (24 mo)
100.0
2 crashes · 2 units
Days since prior carrier crash
478
Last on Feb 27, 2017
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,561,123 carriers

Geographic context

How this crash sits in its setting.

Within Pennsylvania, 12,713 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Crash details

Key facts from the FMCSA crash record.

Report #:
PA806864700X
Date:
Jun 20, 2018
Time:
1652
State:
Pennsylvania
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No

Other crashes by this carrier

9 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5053363 Oct 16, 2025 NY Injury 0 2
cr_4900568 Oct 24, 2024 MD Injury 0 1
cr_4723752 Jan 9, 2024 NJ Injury 0 1
cr_4383252 Jul 5, 2022 NC Injury 0 4
cr_4027736 Aug 27, 2020 MI Tow-Away 0 0
cr_3375396 Feb 27, 2017 OH Tow-Away 0 0
cr_3358926 Jan 26, 2017 PA Injury 0 1
cr_3341139 Dec 27, 2016 VA Tow-Away 0 0
cr_3282914 Aug 20, 2016 KY Tow-Away 0 0

Related records

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.