TruckCodex
Hubs

Crash Record PA210567500X

FMCSA crash record in TINICUM UPPER TOWNSHIP on Sep 16, 2022.

Fatal Federal Recordable

What happened

On September 16, 2022, FMCSA recorded a fatal crash that resulted in one death in TINICUM UPPER TOWNSHIP, Pennsylvania. The vehicle was operated by ALLAN MYERS TRANSPORT COMPANY (USDOT 1109502). Recorded conditions: 2 / 1 / 1 pavement. Reported by ALLAN MYERS MATERIALS, FMCSA reference PA210567500X.

Carrier pattern note

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

Fatalities
1
Injuries
0
Vehicles
2
Carrier
ALLAN MYERS TRANSPORT COMPANY
Vehicle Type
Truck
Severity
Fatal

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
5
1 fatal · 3 injury
Crashes per 100 power units (24 mo)
3.1
6 crashes · 195 units
Days since prior carrier crash
52
Last on Jul 26, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,773 carriers

Geographic context

How this crash sits in its setting.

Within TINICUM UPPER TOWNSHIP, Pennsylvania, 23 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 #:
PA210567500X
Date:
Sep 16, 2022
Time:
2131
State:
Pennsylvania
City:
TINICUM UPPER TOWNSHIP
Fatalities:
1
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
ALLAN MYERS TRANSPORT COMPANY (1109502)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 — 6 1M2AX09C5JM038648 290ED26 (MD) ALLAN MYERS MATERIALS 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
cr_5085413 Dec 1, 2025 DE Tow-Away 0 0
cr_5007431 Jun 30, 2025 PA Tow-Away 0 0
cr_4947561 Apr 18, 2025 DE Injury 0 1
cr_4918546 Mar 24, 2025 PA Injury 0 1
cr_4921791 Mar 4, 2025 MD Tow-Away 0 0
cr_4870828 Nov 27, 2024 DE Injury 0 2
cr_4815860 Sep 13, 2024 PA Tow-Away 0 0
cr_4825953 Sep 12, 2024 PA Tow-Away 0 0
cr_4820986 Aug 22, 2024 PA Tow-Away 0 0
cr_4796089 Aug 1, 2024 PA Tow-Away 0 0

Related records

Vehicle
2018 MACK GU (Granite)
NHTSA recalls and complaints for this make/model/year.
Carrier
ALLAN MYERS TRANSPORT COMPANY
USDOT 1109502 · 65 crashes · 191 inspections
Vehicle
VIN: 1M2AX09C5JM038648
Decode this VIN for make, model, year, and recall data.
State
Crashes in Pennsylvania
Statewide crash records.
Agency
ALLAN MYERS MATERIALS
Crashes reported by this law-enforcement agency.
City
Crashes in TINICUM UPPER 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.