Skip to main content
TruckCodex
Hubs

Crash Record PA406365900X

FMCSA crash record in ARMAGH TOWNSHIP on Jul 16, 2024.

Injury Federal Recordable

What happened

On July 16, 2024, FMCSA recorded an injury crash with one person hurt in ARMAGH TOWNSHIP, Pennsylvania. The vehicle was operated by TIGER TRUCKING LLC (USDOT 3563906). Recorded conditions: 2 / 1 / 1 pavement. Reported by TIGER TRUCKING LLC, FMCSA reference PA406365900X.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
1
Carrier
TIGER TRUCKING LLC
USDOT 3563906
Vehicle Type
Truck
Severity
Injury

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)
14.3
2 crashes · 14 units
Days since prior carrier crash
42
Last on Jun 4, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 314,932 carriers

Geographic context

How this crash sits in its setting.

Within ARMAGH TOWNSHIP, Pennsylvania, 5 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
2
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 #:
PA406365900X
Date:
Jul 16, 2024
Time:
2052
State:
Pennsylvania
City:
ARMAGH TOWNSHIP
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
TIGER TRUCKING LLC (3563906)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3AKJHHDR9KSKG4641 Z085898 (UT) TIGER TRUCKING LLC 3 No

Crash event

Event sequence description.

1:18:COLLISION INVOLVING FIXED OBJECT

Other crashes by this carrier

9 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4889527 Feb 5, 2025 OR Injury 0 1
cr_4889792 Nov 4, 2024 NM Tow-Away 0 0
cr_4787029 Jul 24, 2024 WA Tow-Away 0 0
cr_4763227 Jun 4, 2024 WA Tow-Away 0 0
cr_4743767 Apr 5, 2024 TX Tow-Away 0 0
cr_4717396 Mar 13, 2024 WY Tow-Away 0 0
cr_4663468 Nov 24, 2023 WY Tow-Away 0 0
cr_4343525 Apr 12, 2022 MT Tow-Away 0 0
cr_4287432 Jan 5, 2022 MT Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Vehicle
2019 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
23V105000
STEERING:LINKAGES:DRAG:LINK:CONNECTION
Recall
23V073000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
22V919000
TIRES
Carrier
TIGER TRUCKING LLC
USDOT 3563906 · 10 crashes · 0 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3AKJHHDR9KSKG4641
Decode this VIN for make, model, year, and recall data.
State
Crashes in Pennsylvania
Statewide crash records.
Agency
TIGER TRUCKING LLC
Crashes reported by this law-enforcement agency.
City
Crashes in ARMAGH 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.