Crash Record PA108485400X

FMCSA crash record in UPPER MILFORD TOWNSHIP on Aug 26, 2021.

Tow-Away Federal Recordable

What happened

On August 26, 2021, FMCSA recorded a tow-away crash with no reported injuries in UPPER MILFORD TOWNSHIP, Pennsylvania. The vehicle was operated by GTC LOGISTICS INC (USDOT 2282557). Recorded conditions: 1 / 1 / 1 pavement. Reported by GTC LOGISTICS INC, FMCSA reference PA108485400X.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

GTC LOGISTICS 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 injury · 8 tow-away

Crashes per 100 power units (24 mo)

5.4

19 crashes · 350 units

Days since prior carrier crash

167

Last on Mar 12, 2021

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,684 carriers

Geographic context

How this crash sits in its setting.

Within UPPER MILFORD TOWNSHIP, Pennsylvania, 5 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

DANIEL SEDLER · 1 reports
MP CUSTOM SERVICES LLC · 1 reports
PITT OHIO EXPRESS LLC · 1 reports

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 #:: PA108485400X
Date:: Aug 26, 2021
Time:: 0741
State:: Pennsylvania
City:: UPPER MILFORD TOWNSHIP
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: GTC LOGISTICS INC (2282557)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	4V4NC9EH0LN260006	2883887 (IN)	GTC LOGISTICS INC	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	Injuries
cmqkg787c00frp8fy9l4l3x8f	Jun 10, 2026	NC	Tow-Away	0
cmpupuhtm000dmok7o5ekqutr	May 27, 2026	TN	Tow-Away	0
cr_5113952	Feb 19, 2026	VA	Injury	1
cr_5096477	Jan 25, 2026	VA	Tow-Away	0
cr_5075935	Dec 14, 2025	NC	Tow-Away	0
cr_5069135	Dec 8, 2025	MN	Tow-Away	0
cr_5064727	Nov 1, 2025	IL	Tow-Away	0
cr_5046709	Sep 11, 2025	IN	Tow-Away	0
cr_4996557	Aug 11, 2025	IL	Tow-Away	0
cr_5089273	Jun 27, 2025	NC	Injury	2

Related records

Carrier

GTC LOGISTICS INC

USDOT 2282557 · 57 crashes · 434 inspections

Vehicle

VIN: 4V4NC9EH0LN260006

Decode this VIN for make, model, year, and recall data.

State

Crashes in Pennsylvania

Statewide crash records.

Agency

GTC LOGISTICS INC

Crashes reported by this law-enforcement agency.

City

Crashes in UPPER MILFORD 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.