Skip to main content
TruckCodex
Hubs

Crash Record PA506201700X

FMCSA crash record in SUSQUEHANNA TOWNSHIP on Jul 3, 2025.

Tow-Away Federal Recordable

What happened

On July 3, 2025, FMCSA recorded a tow-away crash with no reported injuries in SUSQUEHANNA TOWNSHIP, Pennsylvania. The vehicle was operated by FAF LLC (USDOT 728630). Recorded conditions: 1 / 1 / 1 pavement. Reported by FAF LLC, FMCSA reference PA506201700X.

Carrier pattern note

This is the carrier's 148 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: 35 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
0
Vehicles
2
Carrier
FAF LLC
USDOT 728630
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
148
7 fatal · 38 injury
Crashes per 100 power units (24 mo)
5.7
98 crashes · 1,729 units
Days since prior carrier crash
7
Last on Jun 26, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,878 carriers

Geographic context

How this crash sits in its setting.

Within SUSQUEHANNA TOWNSHIP, Pennsylvania, 35 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 #:
PA506201700X
Date:
Jul 3, 2025
Time:
1408
State:
Pennsylvania
City:
SUSQUEHANNA TOWNSHIP
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
FAF LLC (728630)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 13 3AKJHLDV7RSUZ8288 3632592 (IN) FAF 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
cmqkg78ck00kdp8fy786yxlwe Jun 10, 2026 OH Tow-Away 0 0
cmokyirjv002pnv1d7ndwybz3 Apr 23, 2026 PA Tow-Away 0 0
cr_5118901 Mar 12, 2026 WY Tow-Away 0 0
cr_5115377 Mar 5, 2026 AR Tow-Away 0 0
cr_5118388 Mar 4, 2026 LA Injury 0 1
cr_5120846 Mar 4, 2026 TX Tow-Away 0 0
cr_5112765 Feb 11, 2026 GA Injury 0 1
cr_5112286 Feb 6, 2026 TX Tow-Away 0 0
cr_5096291 Jan 29, 2026 TN Tow-Away 0 0
cr_5099787 Jan 29, 2026 OK Injury 0 3

Carrier booking & risk tools

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

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

Related records

Carrier
FAF LLC
USDOT 728630 · 1,515 crashes · 3,682 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Insurance
Insurance-lapse watch · HIGH
BMC-91 filing instability signal for this carrier.
HIGH
Vehicle
VIN: 3AKJHLDV7RSUZ8288
Decode this VIN for make, model, year, and recall data.
State
Crashes in Pennsylvania
Statewide crash records.
Agency
FAF LLC
Crashes reported by this law-enforcement agency.
City
Crashes in SUSQUEHANNA 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.